Server Administrator Version check failed

It may be failing to install due to certain dependency checks failing (old PERC Driver/Firmware/etc).

Look in C:\TEMP\OMINSTAL.LOG to see what the cause of the failure is.

I am having the same problem with one of my PE 2650s, "Server Administrator Version check failed. Server Administator is not installed correctly. An error occurred while installing Server Administrator. Some components were not installed properly."

All of my other 2650s have not had any problems with OM 3.7.  When installing OM 3.7 the DRAC II option is greyed out because it is not supported.  Follows is the log file from the install.

Applications with a DEPENDENCY message cannot be installed using unattended mode.
Applications with a WARNING message can be installed using unattended mode with "force" option.
HOST Name: aal043nt7
---------START Fri Mar 19 09:46:26 AKST 2004 -----------------------------------
OK: Server Administrator requirements have been met for installation. 
OK: Remote Access requirements have been met for installation. 
WARNING: Storage Management : Current version is already installed on the system.   
OK: Diagnostic Service requirements have been met for installation. 
OK: Update Service requirements have been met for installation. 
DEPENDENCY: DRAC II : DRAC II is not supported on this system. 
OK: Intel Agent requirements have been met for installation. 
OK: Broadcom Agent requirements have been met for installation. 
DEPENDENCY: Symbios Agent : This application is not supported on this system.  
Finished Installing Intel Agent.
Finished Installing Broadcom Agent.
Finished Installing Server Administrator.
Finished Installing Update Service.
Finished Installing Diagnostic Service.
An error occurred while installing Server Administrator.  Some components were not installed properly.
Installation Finished.
---------END Fri Mar 19 10:03:30 AKST 2004 -----------------------------------

Help!!

Thanks for the reply... But Server Administrator does not get installed correctly.

The OMSA directory is not created, and when the server is restarted you get a lot of error messages that DLLs could not be found.

I have uninstalled, ran OMCLEAN, and still get the same results on this server.

Cheers

Hi.

Is this machine a DC? That is where I was having problems and it turned out it was being caused by having the source installation files located on the DC itself. I copied the files to another server, browsed to it, \\server\d$\sadmin\setup.exe, and the install worked fine. If your 2650 is a DC then this will probably work. If not, I don't know what could be causing the problem. Make sure when you remove the software you reboot, then when you run omclean reboot again. Good luck. 

I get the following warning message three times in the application log:

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1015
Date:  4/5/2004
Time:  10:35:19 AM
User:  N/A
Computer: XXXXXXXXXX
Description:
Failed to connect to server. Error: 0x80080005

Message Edited by geoWorm on 04-05-2004 11:19 AM

I also get the following error message twice in the system log :

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date:  4/5/2004
Time:  10:36:38 AM
User:  XXXXXXXXXX\Administrator
Computer: XXXXXXXXX
Description:
The server {000C101C-0000-0000-C000-000000000046} did not register with DCOM within the required timeout.

Message Edited by geoWorm on 04-05-2004 11:19 AM

For the person with the DCOM error, you need to modify the DCOM permissions. From the run line, type DCOMCNFG .

If you are running W2k, this will open Distributed COM Configuration Properties. Choose the Default Security tab, then click the Edit Default for the Default Access Permissions. Add the Domain Admin Group and the account you are using to login with Allow Access Permission. Then also add these accounts to the Default Launch Permissions. Choose the Default Securities tab and verify that the Default Impersonation Level is set to Identify.

If you are running W2k3, this will open Component Services. Open Component Services on the left, then click on the Computer Icon in the bar on the top of the window to Configure My Computer. Choose the Default Com Security tab, then click the Edit Default for the Access Permissions. Add the Domain Admin Group and the account you are using to login with Allow Access Permission. Then add these accounts to the Default Permission with Allow access.  Choose the Default Properties tab and verify that the Default Impersonation Level is set to Identity.

For the person with the MSI error, there is a problem with the MSI installed. I am currently researching the fix for you.

For the person getting the MSIInstaller error, try the 2 fixes for the MSI installer address in MS KB article 296174. PRJ2000:Error Message When you Install Microsoft Project to fix this error.
Let me know if this works.
http://support.microsoft.com/default.aspx?scid=kb;en-us;296174