Last post Dec 22, 2005 07:00 PM by old_man
Dec 20, 2005 11:24 PM|old_man|LINK
I have multiple sites developed and running using VS2003 vb.net that utilize aspx pages. They are running on a SBS2003 server and IIS. They were under ASP1.1,???? I am doing my debuging on the server machine.
I loaded VS2005 and did the conversion. It gave me a few warnings that I fixed. The project builds with no errors.
Validating Web Site
Building directory '/App_Code/'.
Building directory '/_vti_bin/_vti_adm/aspnet_client/system_web/1_1_4322/'.
Building directory '/_vti_bin/_vti_adm/help/1033/publish/'.
Building directory '/aspnet_client/system_web/1_1_4322/'.
Building directory '/'.
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========
The problem is that it does not update the site upon completion of the build like it did in 2003. I get an http 500 error. What am I missing. I updated the IIS to run 2.0 but it is still showing
1_1_4322 above. The site it up and being served by IIS because I can access the .jpg files and such, it just isn't serving the pages.
Maybe the quick and dirty thing to do is to reverse the conversion. How do I retrieve the backup the install did before the conversion and put it back the way it was. I will then explore conversiion on a sample web.
Sorry, I posted this in the wrong forum first. I didn't see this catagory.
Dec 21, 2005 08:44 PM|ScottGu|LINK
By default when you backup files in VS 2005 prior to a conversion, they get put under your "My Documents\Visual Studio 2005\Backup Files" directory. So if you look there you should be able to help find the origionals.
Because your web project compiled and built just fine, I suspect the problems is with how IIS is setup for your web application. Can you try two things:
1) Look in your event log for an error message that describes what the problem was? ASP.NET will by default out an error message there when you have a problem like the one above.
2) Can you provide more details on what IIS application pools you have configured? You need to make sure that V2.0 applications run in separate application pools from V1.1 applications -- so that might be the problem. Can you configure this particular
application to run in its own application pool/process and see if that helps?
3) Can you double-check that the application is configured to run using V2.0? You can do this by opening up the application properties in the IIS admin tool and clicking on the ASP.NET tab. It will then list the version it is using there.
Hope this helps,
Dec 22, 2005 12:15 AM|old_man|LINK
I needed to get the sites back up and going ASAP. Customers get real grouchy. I found the backup files and moved them all back. I was able to get the sites to compile under VS2003 and the sites back up and being served. I can make changes and build the
site. That all works.
NOW, the problem is the accursed debug failure issue.
error while trying to run project unable to start debugging on the web server you do not have permissions to debug the server
I am working as Administrator. The Debuggers group has full permissions on the sites as well. The IIS has been set back to 1.1.4332.
I have other projects that I did not convert, and they all debug just fine, so IE should be set up fine. I compare settings and permissions from working and non working projects and can't find any differences.
I even copied a working web.config from a very similar site.
There must be something local to the project that is screwing up the debuging.
Any ideas? I dealt with this error message a year ago when setting up the sites, but everything I fixed before is fine. I am on the verge of building a new server from scratch and doing a fresh install minus VS2005 and move the sites over. This is a royal
Dec 22, 2005 01:15 AM|ScottGu|LINK
Usually when I see that error message, it is because the application is running under V2.0 and you are trying to debug with VS 2003 (or it is running V1.1 and you are trying to debug with VS 2005).
Are you 100% certain it is running with V1.1? After checking it is running V1.1, can you do an iisreset to make sure that it restarts the worker process?
Dec 22, 2005 02:33 AM|old_man|LINK
If I go to the IIS for the site in question, and then got to the ASP.NET button, it shows 1.1.4322. Is that what you were asking? How would you have me verify it is running V1.1?
I just ran iisreset /RESTART, then restarted the VS2003, still the same results.
I have uninstalled VS2005. Until I can put it on a completely isolated test machine, I will not reload it on any of my servers.
Dec 22, 2005 07:00 PM|old_man|LINK