Research Output Repository Platform

Re: How to avoid common installation mistakes

davidkane — Wed, 11 Feb 2009 20:51:08 GMT

Yay! It works.

This looks very interesting and different. I am going to have little
enough time to play with it right now, but I am really pleased that it
works.

I am delighted. Now, let's see what we can do with it..

Thanks Shailesh.

David.

2009/2/11 Shailesh Nikam
:
> Hi David, As part of our installer, we ask user for application pool
> credentials for IIS 6.0. People usually give their domain credentials there.
> Sometimes those credentials does not get added to the IIS_WPG group.This may
> happen due to some IIS issue, few related issue is mentioned here,
> http://support.microsoft.com/kb/918041 To resolve this issue, could you
> please try steps mentioned below? 1. Click Start, right-click My
> Computer, and then click Manage.2. Expand Local Users and Groups, and
> then click Groups.3. Right-click IIS_WPG, and then click
> Properties.4. In the IIS_WPG Properties dialog box, click Add.5.
> Enter the 'application pool identity user account name', click Check Names.
> This should resolve the full name.6. Click OK.7. Click OK on
> main properties window. Restart the IIS as mentioned in steps
> below, 1. From the Start menu, click Run.2. In the Open box,
> type cmd, and click OK.
>
> 3. At the command prompt, type iisreset /noforce, and press ENTER.
> (This will stop and restart all IIS services)
>
> Try accessing your site again as, http://localhost:9090/webui/Default.aspx
>
> Let us know if this helps.
>
>
>
> Regards,
>
> Shailesh
>
>
>

Re: How to avoid common installation mistakes

Shailesh Nikam — Wed, 11 Feb 2009 20:10:48 GMT

Hi David,
As part of our installer, we ask user for application pool credentials for IIS 6.0. People usually give their domain credentials there. Sometimes those credentials does not get added to the IIS_WPG group.
This may happen due to some IIS issue, few related issue is mentioned here, http://support.microsoft.com/kb/918041

To resolve this issue, could you please try steps mentioned below?
1. Click Start, right-click My Computer, and then click Manage.
2. Expand Local Users and Groups, and then click Groups.
3. Right-click IIS_WPG, and then click Properties.
4. In the IIS_WPG Properties dialog box, click Add.
5. Enter the ‘application pool identity user account name’, click Check Names. This should resolve the full name.
6. Click OK.
7. Click OK on main properties window.

Restart the IIS as mentioned in steps below,
1. From the Start menu, click Run.
2. In the Open box, type cmd, and click OK.
3. At the command prompt, type iisreset /noforce, and press ENTER. (This will stop and restart all IIS services)

Try accessing your site again as, http://localhost:9090/webui/Default.aspx

Let us know if this helps.

Regards,
Shailesh

Re: How to avoid common installation mistakes

davidkane — Tue, 10 Feb 2009 16:00:36 GMT

Hi Shailesh,

It was a clean installation. I changed the paths to reflect my setup
- changing MSSQL.1 to

MSSQL10.FAMULUS, which is as it exists in our system.

I no longer get the old error message, but a different one.

I got another error that seemed to indicate that I needed to activate
FILESTREAM

functionality for the SQL server instance and database. So, I did that.

Then I got a permissions error, which seemed to indicate that it could
not do anything with

C:/.../FamulusFiles This was my bad - I created the folder for the
application myself.

Once I deleted the folder, and let the application install everything went fine.

Now it is installed, I am just looking at IIS.

http://myhost:9090/webui/Default.aspx - gives a message saying
'Service Unavailable'.

Do you have any hints to get this working? I know, It may be
something obvious, but i have not worked with IIS for a while.

Thanks,

David.

2009/2/10 Shailesh Nikam
:
> Hi David,
>
> The machine on which you are trying the installer is clean machine or it has
> earlier version of Famulus?
>
> Couple of options you can try,
>
> 1. If your machine contains earlier version of Famulus then you need to
> manually delete the database 'MicrosoftFamulus' from SQL management studio.
>
> 2. Can you also check if the path for primary data file shown on installer
> screen "SQL server setup", i.e. "C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\" is available on your file system? Installer
> throws error if folder mentioned in path is not present on file system. You
> can change the path through installer screen to existing folder and then
> check again.
>
> Let us know if any of the above options works for you.
>
> Regards,
>
> Shailesh
>
>
>
>
>

Re: How to avoid common installation mistakes

Shailesh Nikam — Tue, 10 Feb 2009 01:18:48 GMT

Hi David,

The machine on which you are trying the installer is clean machine or it has earlier version of Famulus?

Couple of options you can try,

1. If your machine contains earlier version of Famulus then you need to manually delete the database 'MicrosoftFamulus' from SQL management studio.

2. Can you also check if the path for primary data file shown on installer screen "SQL server setup", i.e. "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\" is available on your file system? Installer throws error if folder mentioned in path is not present on file system. You can change the path through installer screen to existing folder and then check again.

Let us know if any of the above options works for you.

Regards,

Shailesh

Re: How to avoid common installation mistakes

davidkane — Mon, 09 Feb 2009 16:56:23 GMT

Hi Shailesh, I have been trying to install the repository platform on Windows Server 2003 today, with SQLServer Express 2008. It's been going okay until the point just before the end where the wizard is installing the databases. Then, an error dialog pops up. It says:

Error -2147217900: failed to create SQL database: MicrosoftFamulus, error detail: CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

Can you give me any help? Many thanks, David.

Re: How to avoid common installation mistakes

Shailesh Nikam — Sat, 07 Feb 2009 00:35:35 GMT

Hi David,

Thanks for the suggestion.

We were supporting Windows Server 2003 till Alpha release.

However, from earlier Beta-1 release and also with Beta-2 release (which will happen mid Feb09) we are officially supporting only Windows Vista (32 + 64 bit) & Windows Server 2008 (32 + 64 bit).

I can check if we can do the smoke test on Windows Server 2003 though.

Thanks,

Shailesh

Re: How to avoid common installation mistakes

davidkane — Fri, 06 Feb 2009 10:36:58 GMT

Probably also important to use Windows Server 2003, rather than 2008 also. :-) David.

How to avoid common installation mistakes

Shailesh Nikam — Wed, 21 Jan 2009 00:39:13 GMT

Vista comes with UAC and “Research output repository platform” installer may show error prompts during the installation such as,
*Cannot connect to Internet Information Server.(-2147221164)
*Failed to read IIsWebs table.(-2147024891)

Few Tips to avoid these error messages,

*Launch “Setup.exe” with admin privilege
-Right click “Setup.exe”, select option “Run as administrator”
-Current installer does not elevate user rights automatically, so this explicit action is required from user side

*Make sure that user has administrative privileges on the machine on which installer needs to run
-Add user to “Administrator” group
-User should have access to “%SystemDrive%\Inetpub” folder as installer creates default web application at this location

*Check that all IIS features are installed
-Default ASP.Net web application uses few IIS features, which does not get installed as part of the default IIS installation

*Enter correct IIS authentication details during installer screen
-Enter information in the correct format as, Domain\Username

Please make sure that user follows the above guidelines to avoid installer issues.
Let us know if you face any other issues.