I'm trying to evaluate the weborb integration product, but I'm having troubles getting it setup for ASP.NET. The installation appears to complete successfully, but when I go to run the weborb console I get a series of errors.
I found some documentation on WebOrb's site about installing WebOrb for IIS 7.
It said I needed to run the command "appcmd migrate config 'Default Web Site/weborb4'".
When I do this, I get the error: "ERROR ( message:Cannot add duplicate collection entry of type 'add' with unique 'name' set to 'weborb.aspx_*' )
I also installed all the extra IIS components (IIS 6 too) that WebOrb suggested installing.
Does anyone know what I might be doing wrong here?
-- FOUND SOLUTION --
While I'm not sure what caused the above error (I'm new to this IIS admin stuff), I was able to get the WebOrb installation to work correctly, which didn't require the above command. The above migration probably wasn't necessary due to the fix I implemented to get the WebOrb console to load correctly. After extensive searching, I was able to find this WebOrb posting:
http://www.themidnightcoders.com/forum/default.aspx?g=posts&t=3591
The fix was to run:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i
which registered .NET 4.0 on my IIS, even .NE 4.0 was already installed. It was defaulting to .NET 2.0.
Now it runs great.
-- FOUND SOLUTION --
While I'm not sure what caused the above error (I'm new to this IIS admin stuff), I was able to get the WebOrb installation to work correctly, which didn't require the above command. The above migration probably wasn't necessary due to the fix I implemented to get the WebOrb console to load correctly. After extensive searching, I was able to find this WebOrb posting:
http://www.themidnightcoders.com/forum/default.aspx?g=posts&t=3591
The fix was to run:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i
which registered .NET 4.0 on my IIS, even .NE 4.0 was already installed. It was defaulting to .NET 2.0.
Now it runs great.