The first problem I hit when I installed WebOrb for .Net is that after what looked like a successful installation, the installer took me to what was supposed to be the management console for WebOrb. However, I got the following error instead:
—–
Server Error in Application “Default Web Site/WebOrb30”
Error Summary:
Http Error 500.23 – Internal Server Error
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.
I am working on Windows 7, so I am dealing with IIS7, not IIS6. I suspect you would face this issue on Windows Vista as well.
This happens because IIS7 hosts ASP.Net Applications using the ASP.NET Integrated mode by default. ASP.NET Integrated mode provides applications with a lot of very useful and efficiency-boosting features such as
- ASP.NET services such as Forms Authentication, URL Authorization, Output caching etc. are not available to all content types – where they were previously available only to ASP.NET content types such as .aspx pages.
- IIS7 has tighter unified configuration for IIS and ASP.NET modules/handlers.
- IIS’s modules were traditionally developed using the C++ server API and server extensions previously needed to be (not always but most of the time) developed in the ISAPI filter or extension extensibility mode. This is no longer the case and ASP.NET modules can now talk to the server pipeline directly.
A good detailed explanation of the ASP.NET integration architecture and advantages can be read here:
http://learn.iis.net/page.aspx/243/aspnet-integration-with-iis7/
However, this also means that applications, such as WebOrb which were not developed for IIS7 in particular and don’t use ASP.NET Integrated mode will break as shown above.
The solution is easy enough however – we basically take the first option listed in the “Things you can try” section of the error page. However, because the option text is a little cryptic, I thought I would list the specific steps:
- Open up command prompt in the administrative mode. (Make sure you are in admin mode else you will get an insufficient permissions error)
- Go to C:\Windows\System32\inetsrv directory – assuming C:\Windows is your system root.
- Type in
appcmd migrate config "Default Web Site/weborb30”
This is assuming you deployed WebOrb under “Default Web Site” during installation. If not, just replace it with the name of the website you put WebOrb under instead.
You should see something like this: 
Go back to the page where you got the error and refresh. You should see the management console which looks like the screenshot below. If you have already closed the window, just browse to http://localhost/weborb30/ assuming that’s where you put WebOrb. Your URL should look similar.
We are set!