Hi,

Assuming you have .NET 3.5 SP1 installed, the most likely cause of that kind of error,  is you have mojoportal running at http://localhost/mojoportal or some virtual folder beneath http://localhost, but there is another .NET app running at the root folder http://localhost and the Web.config file there is interfering.

If you do some googling you'll find there is usually a way around it by configuring the conflicting web.config section/setting using a <location> tag.

Hope it helps,

Joe

Hi Richard,

The next steps I would try is grant read permission on the mojoportal root folder to the "Network Service" user and then grant the same user full control on the /Data folder.

How are you resolving the hostname "mojo"? Can you try running it just as http://localhost?

Usually on Vista you only have 1 root web site, the Default Web Site which runs at http://localhost, and you either run a .NET app at the root of that site as http://localhost or you run it as virtual directory application and the url is http://localhost/appname.

If you have a .NET app running in the root web site and .NET app(s) running as virtual directories there can be conflicts between web.config files. Usually its the apps in the virtual directories which get broken because the settings in the root app are overriding the web.config in the virtual directory.  It can be resolved by pointing the root web site somewhere else like an empty folder where there is no Web.confiog file.

Other things you can try are changing the Application Pool from "Integrated" to "Classic".

Removing the <system.webServer> and <system.web.extensions> and <system.serviceModel> sections completely from the mojoportal Web.config (back it up first in case that doesn't solve it).

Hope it helps,

Joe

Hi Richard,

Glad to hear you got it working!

I work on Vista every day so I suspect it is just some configuration difference or it could be if your machine is part of domain it may push down some settings via group policy that prevent some settings from being overridden in Web.config

Or it could also be that you don't have the IIS Request Filtering Module installed. If you go to control panel add/remove programs > Turn Windows Features on or off, and branch down the IIS node, on mine I have this:

Not sure, maybe I should comment that out by default, I'm not sure if Request Filtering is installed by default with IIS 7 or not, if not I may get more reports of this issue. I think I only added that setting recently while troubleshooting a problem with NeatUpload.

Best,

Joe