Hi,

That means that it knows it needs to run the setup scripts but it either can't find them (ie they are missing on disk) or it does not have read permissions on the files.

When you changed it from .NET 1.1 that means it now uses a different application pool. The identity user of the application pool is the user that needs permissions. It should have read permissions to the entire web and full control on /Data and /App_Data

So either files are missing from under /Setup/applications or file/folder permissions do not allow it to read the files there.

I would not expect missing files if you used the platform installer but I suppose it is possible, it is probably more likely the files exist but permissions are bad.

Hope it helps,

Joe

Hi Jerry,

Thanks much for the beers! Most appreciated!

I think what happens is it just uses the default application pool and if the machine has .NET 1.1 on it there is a good chance that the default app pool is configured for 1.1. 

.NET 1.1 can't share an app pool with other apps running 2.0 or up

.NET 2.0 and 3.5 apps can share the same app pool because 3.5 is really a superset of 2.0

.NET 4 can't share an app pool with any previous versions and in IIS 7.x when you install .NET 4 i creates 2 new app pools one for .NET 4 Integrated pipeline mode and one for Classic.

So the platform installer may not be smart enough to pick the correct app pool in all cases especially under Win 2003 because in older versions there is no convention for different named default app pools for different framework versions, so it has no way of knowing which app pool to use and just uses the default or creates a new one based on the default.

I do know that the platform installer can correctly set the app pool for 4.0 .NET on win 2008/IIS 7.x if the packages indicates .NET version 4 in the manifest.

If you install from the web app gallery that is using our 3.5 .NET package, but our codeplex download for .NET 4 can also be installed using the platform installer at least under IIS 7.x Win 2008, if you import the package from IIS, during the setup it prompts whether to use the .NET 4 application pool.

I no longer have any win 2003 machines so I'm not sure but I suspect the platform installer doesn't work as well there as on win 2008.

Best,

Joe

Hi Jerry,

You could just try making sure the default app pool is for 2.0/3.5 and maybe that will make it go smoother using the platform installer.

Uprading the machine is a bit drastic, it can run fine on win2003, just the platform installer may not work as well there.

Are you using IIS 6 or were you able to install IIS 7.x using the platform installer? The platform installer "might" work better installing applications  with IIS 7.x.

But it is also pretty straightforward to do a manual install.

1. download the mojoportal-x-x-x-mssql-net35-deploymentfiles.zip from codeplex or if you have .NET 4 use the mojoportal-x-x-x-mssql-net40-deploymentfiles.zip
2. extract it and copy the wwwroot folder wherever you want the site to live on disk, rename it if you like
3. create an IIS site with an application pool configured for the framework version, make note of the identity on the app pool, I recommend use NETWORK SERVICE as the identity
4. point the site to the wwwroot folder or whatever you named it
5. right click the wwwroot folder and choose properties, go to security and grant read permission for the identity (ie NETWORK SERVICE)
6. do the same on the /App_Data and /Data folders but give full control permissions
7. rename the user.config.sample file in the root to user.config and set your connection string in that file

the above is essentially the same steps that the platform installer would do for you

visit the /Setup/Default.aspx page, if the above steps were done correctly it will run the database scripts

Hope it helps,

Joe