Last post Aug 18, 2008 06:03 PM by Esmith236
Aug 14, 2008 06:22 PM|Esmith236|LINK
I'm still yet probably over my head on this one.
1. I uninstalled all of Visual studio componets of 2005.
2. I installed the new visual studio 2008 express. VB, VWD, SQL, Plus a Windows installer update.
3. The installation went very smooth although long.
4. I had to recreate my SQL tables via VWD which went well. I populated it with a couple of records.
5. I set up a web site. Did the form work via formview and its datasources and templates. (Lots of work) It went very well.
6. Now the big test. Do a build which worked flawlessly.
7. Submitted the page to Interner Explorer.
8. Bang! I"m dead. Got the old "HTTP error 403". Any experience with this message?
I did all the research I could via Microsoft and other places on the Internet. This is where I am over my head.
Anything with respect to this message and Visual Studio 2008 Express?
My blood pressure reflects my anxieties!
Aug 14, 2008 06:55 PM|ravivb.net|LINK
What do you mean submitted to Internet Explorer? Did you hit F5 or viewing the page in IE?
I think the easiest thing you could do is to hit F5 and debug it...
Aug 15, 2008 08:45 PM|joeaudette|LINK
I'm suddenly getting this problem today on my machine. I am unable to debug in the VS web server nor in IIS, I keep getting error 403. I just upgraded to Visual Studio SP 1 yesterday and things were working fine then all of a sudden these erros started
and now I can't get any work done for the last 5 hours. First I thought something got currup in these folders so I got a new copy of my work in a new folder from svn but the problem is the same.
I'm running VS 2008 Pro SP 1 on Vista 64bit.
I guess I'm going to try uninstalling SP1 of VS and see what happens.
Very frustrated I am behind in my work and now this.
Somebody please help if you can.
Visual Studio 2008
Aug 15, 2008 09:55 PM|jeremyh|LINK
Did you check that iis default user has access to the database?
Aug 15, 2008 09:56 PM|jeremyh|LINK
Did you upgrade the remote debugger?
Links here if you need it
Hope it helps
Aug 15, 2008 10:43 PM|joeaudette|LINK
I've tried uninstalling and re-installing IIS, VS 2008 SP1, and just now at your suggestion I uninstalled the remote debugger and then re-installed it from the separate download but still the same problems. I can't get it to open a page in the debugger
using the VS Web Server no way no how. I pull down the same solution on an older slower xp machine and it works fine.
So I try a few things to see about getting it working in IIS
1. If I try to just get it working in IIS using (All Unassigned) localhost without the debugger I get the same 403, same if I try 127.0.0.1, same if I try the specific ip 172.16.0.101
2. If I delete the web site then add it again and configure it to use a specific ip initially instead of all unassigned it works, it serves the app, everything is fine but I can't debug. If I try to set VS to debug using the ip address it says it needs to
create a virtual directory but then it can't. So I try editing my hosts file and point localhost to my specific ip 172.16.0.101 and again it works in the browser but can't run in the debugger. If I set it back to all unassigned it doesn't work and then to
get it working again I have to delete the site and create it with a specific ip as the initial setting, just changing from All unassigned to a specific ip doesn't work.
I had been working for several hours this morning with no problems and then this 403 happened and now it won't go away. I know there was a big windows update last night, I can't help but suspect that as a factor, but something is really hosed.
Any other suggestions much appreciated.
Aug 15, 2008 10:58 PM|joeaudette|LINK
omg! I just figured it out, how embarrasing is this. I have a custom http module that bans ip addresses based on certain errors that indicate hacking. Apparently it banned my local addresses due to errors when I was debugging. So my own code was making
the 403 happen.
aargh it was all my own fault [:$]
Thanks for trying to help me,its been one of those days.
Aug 16, 2008 01:36 AM|Esmith236|LINK
Talk about lost! I seem to have very little control with VS 2008. 2005 had a sql management process that gave quite good control over my databases. No such thing in VS 2008 You mention iis default user. I see nowhere to give access to the database other
than what was given at install time. I searched my entire disk drive for any instance of iis and only found an iis.inf burried in Windows. Is there any help here or should I abandon VS2008? I would appreciate any advice.
With grateful thanks,
Aug 16, 2008 12:49 PM|jeremyh|LINK
Glad to hear you got it fixed, always the best errors to find.
Aug 16, 2008 12:52 PM|jeremyh|LINK
For a good guide to setting up ASP.NET and SQL take a read of
You should have no problems working with 2008 should just be the same as 2005 but better.
Aug 17, 2008 06:36 PM|Esmith236|LINK
Thanks Jeremy, The your suggested article made reference to all the sql 2005 and VS 2005 with asp.net
Here is what a debug messages gave when I debug my website application...
//Split out for localization.
var L_GOBACK_TEXT = "Go back to the previous page.";
var L_REFRESH_TEXT = "Refresh the page.";
var L_MOREINFO_TEXT = "More information";
var L_OFFLINE_USERS_TEXT = "For offline users";
var L_RELOAD_TEXT = "Retype the address.";
var L_HIDE_HOTKEYS_TEXT = "Hide tab shortcuts";
var L_SHOW_HOTKEYS_TEXT = "Show more tab shortcuts";
//used by invalidcert.js
var L_CertUnknownCA_TEXT = "The security certificate presented by this website was not issued by a trusted certificate authority.";
var L_CertExpired_TEXT = "The security certificate presented by this website has expired or is not yet valid.";
var L_CertCNMismatch_TEXT = "The security certificate presented by this website was issued for a different website's address.";
var L_CertRevoked_TEXT = "This organization's certificate has been revoked.";
How can I resolve this security certificate issue?
This is the URL that causes my http error 403.
Aug 17, 2008 07:00 PM|jeremyh|LINK
It would seem that you are accessing a asp.net page in the App_data, this is not good practice move it out and try again.
The App_data folder should only be used for data storage.
Aug 18, 2008 06:03 PM|Esmith236|LINK
I took your advice and moved my data file to the app_data folder.
Ran debug and its message told me that "RoleManager was set to "true".
I reset that value to false and ran debug again.
VOILA! no http error 403 and the web page acted much more dignified.
Thanks so much for you and others putting up with a "wet behind the ears" asp.net developer"
All the best