Unsolved
This post is more than 5 years old
1 Rookie
•
13 Posts
0
108852
August 11th, 2004 23:00
Problems installing OpenManage Server Administrator (OMSA) or Array Manager (AM)?
Introduction
If you are having trouble installing OpenManage Server Administrator (OMSA) or OpenManage Array Manager (AM) and you are an advanced user, try doing the following. These steps do not apply to other OpenManage products.
Disclaimers
Many of the following recommendations are advanced troubleshooting steps. Editing the registry and reconfiguring drivers can cause your system to become unstable. Always backup your data when making changes to critical system components. Dell is not responsible for lost or corrupted data.
Some steps in this article refer to third party websites and products. We do not warrant the accuracy of any third party information. It is provided as a convenience only.
Get the Right Version
The installation file for OMSA is very large; first start downloading it to a different computer on your network. Go to the download section of the support website support.dell.com. Make sure you get the correct version for your server model and operating system.
Preparing for Installation
Verify Hardware
If you have a degraded array, then you usually do not want to flash the PERC firmware. Installing AM or OMSA (which can include AM), may try to update the firmware. If you have a degraded array, fix it first then try to install the software. You may need to call technical support for this.
Service Packs
Having the latest service pack usually helps the installation. Some versions of OMSA and AM require minimal service packs. The readme files in the download indicate what the minimum service pack is.
Event Viewer
Event viewer errors may indicate wider problems that may prevent OMSA from installing. Clear up all event viewer error messages.
Device Manager
Do not have any remote access cards disabled in Device Manager when installing OMSA.
Windows Installer Service
Verify that the Windows Installer Service is not disabled. (Computer Management/Services/Windows Installer Service)
Video Settings
Make sure the video resolution is at least 800x600 with 16-bit color.
Administrative Rights
Always install OMSA with a user account that is part of the local or Domain administrators group.
DCOM Permissions
For NT and 2000:
- Click Start/Run Type DCOMcnfg.exe Click OK.
- Click the Default Security Tab.
-
- Edit Default Access Permissions.
-
- Click Add.
- Click Show Users.
- Add the exact user account that is trying to install OMSA.
- Make sure it says Allow Access.
- Edit Default Launch Permissions.
-
- Click Add.
- Click Show Users.
- Add the exact user account that is trying to install OMSA.
- Make sure it says Allow Launch.
- Edit Default Configuration Permissions.
-
- Click Add.
- Click Show Users.
- Add the exact user account that is trying to install OMSA.
- Make sure it says Full Control.
- Click the Default Properties Tab.
-
- Make sure Default Authentication level is set to Connect.
- Make sure Default Impersonation level is set to Identify.
- Go to Administrative Tools/Component Services.
- Expand Computers
- Right-click My Computer and choose Properties
- In the My Computer Properties dialog box, click the Default COM Security Tab.
-
- Edit Default Access Permissions.
-
- Click Add.
- Add the exact user account that is trying to install OMSA.
- Make sure it says Allow Access.
- Edit Default Launch Permissions.
-
- Click Add.
- Add the exact user account that is trying to install OMSA.
- Make sure it says Allow Launch.
- Click the Default Properties Tab.
-
- Make sure Default Authentication level is set to Connect.
- Make sure Default Impersonation level is set to Identify.
BIOS, Firmware, and Driver Versions
Update all of the following to the latest versions available on the support website:
- BIOS
- ESM firmware (if applicable)
- PERC driver (if applicable)
- PERC firmware (if applicable)
- DRAC II driver (if applicable)
- DRAC II firmware (if applicable)
- DRAC III/ERA firmware (if applicable)
- Remember that most of the following files are hidden or system files. You may need to change folder options to be able to view these files and folders.
-
- In Windows Explorer, click Tools/Folder Options...
- Click the View tab
- Click Show hidden files and folders
- Uncheck Hide extensions for known file types
- Uncheck Hide protected operating system files
- Make sure the following folders exist and that your user account has Full Control:
-
- c:\
- c:\temp\
- c:\winnt\ (or whatever the windir directory is. In 2003, it is c:\windows\)
- c:\winnt\installer\
- c:\winnt\system32\drivers\
- In the c:\winnt\system32\drivers\ folder, if there is a file called ASPI32.sys rename it to ASPI32.old. Important: Some programs require a version of ASPI32 that is incompatible with AM. If that is the case, then you will not be able to run both AM and this other program. Currently AM requires version 4.6.x.
- Rename the c:\program files\common files\installshield\engine\ directory to c:\program files\common files\installshield\engineOLD\
Registry Keys and Registry Permissions
For NT and 2000:
- Click Start/Run and type regedt32 and click OK
- Highlight HKEY_LOCAL_MACHINE.
-
- In the menu bar, click Security/Permissions...
- Click Add.
- Add the exact user account that is trying to install OMSA.
- Give that user Full Control.
- Highlight HKEY_CLASSES_ROOT.
-
- In the menu bar, click Security/Permissions...
- Click Add.
- Add the exact user account that is trying to install OMSA.
- Give that user Full Control.
- Highlight HKEY_USERS.
-
- In the menu bar, click Security/Permissions...
- Click Add.
- Add the exact user account that is trying to install OMSA.
- Give that user Full Control.
- For each of the following keys, look at each entry; if the value in the Data field does not refer to a valid drive in your computer, then follow the instructions in Microsoft Knowledge Base article Q327763
-
- HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
- HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
- Click Start/Run and type regedt32 and click OK
- Highlight HKEY_LOCAL_MACHINE.
-
- Right click and choose Permissions
- Click Add.
- Add the exact user account that is trying to install OMSA.
- Give that user Full Control.
- Highlight HKEY_CLASSES_ROOT.
-
- Right click and choose Permissions
- Click Add.
- Add the exact user account that is trying to install OMSA.
- Give that user Full Control.
- Highlight HKEY_USERS.
-
- Right click and choose Permissions
- Click Add.
- Add the exact user account that is trying to install OMSA.
- Give that user Full Control.
- For each of the following keys, look at each entry; if the value in the Data field does not refer to a valid drive in your computer, then follow the instructions in Microsoft Knowledge Base article Q327763
-
- HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
- HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
- Click Start/Run.
- Type cmd.exe and click Ok.
- At the command prompt, type msiexec /unreg and press ENTER.
- At the command prompt, type msiexec /regserver and press ENTER.
- If it works correctly, you will NOT get a status message.
Uninstall FAST
FAST and Array Manager should not be on the same system.
Uninstall Old Versions
Old versions of OMSA and AM can cause problems. Go to add/remove programs and uninstall all of these items. Reboot after uninstalling.
If Citrix was installed after OMSA or AM then it might be difficult to uninstall OMSA. Call technical support if this is the case.
Run the Installation
After reviewing all of the above steps and rebooting, try installing the program again. If you continue to have problems, please contact technical support.



mgpacific
1 Message
0
November 9th, 2004 18:00
MichelleT
2 Intern
•
127 Posts
0
December 29th, 2004 10:00
rsbomar
15 Posts
0
May 3rd, 2005 02:00
jkguyton
7 Posts
0
May 31st, 2005 17:00
jholbach
8 Posts
0
November 9th, 2005 13:00
Pirulino
9 Posts
0
December 17th, 2005 04:00
I need to install dell open management in a server Power Edge 2850 with system Microsoft Windows 2003 standard edition,
can they help me indicating the exact link to be able to install it in the server?
thank you for their help, I accept advice
Message Edited by Pirulino on 12-17-2005 12:42 AM
Troy Tripp
28 Posts
0
January 6th, 2006 17:00
Thanks a lot, Dell. I followed your directions and now my server is totally hosed.
I'm an HP man from now on.
Brandes-RyanO
9 Posts
0
January 19th, 2006 17:00
"Failed to load OMIL Library". I have tried using the add/remove programs and the v4.5 CD.
The OMClean only works on v4.3 and earlier versions...
How can I remove v4.4?
jkguyton
7 Posts
0
January 19th, 2006 17:00
Restart the server.
Install the exact same version of the software that you already have installed in exactly the same manner using the same options.
Restart the server.
Try to uninstall again.
For whatever reason the initial install may not have been completely successful. Reinstalling the software over the top of itself, usually allows me to subsequently have a 'clean' uninstall.
Best of luck!
ns_support
3 Posts
0
March 21st, 2006 21:00
ns_support
3 Posts
0
April 13th, 2006 17:00
tester25
626 Posts
0
April 13th, 2006 17:00
login, the "Diagnostics Service" tab may not be available in Server
Administrator or listed on the "Health" page.
Diagnostics Service waits for Server Administrator to start
completely before enumerating (scanning system for available
devices to diagnose). If you press to refresh, the
"Diagnostics Service" tab displays when enumeration is complete.
This process can take several minutes on some systems. The
"Diagnostics Service Link" does not work until the "Diagnostics
Service" tab is displayed.
BorgSquirrel
3 Posts
0
October 2nd, 2006 11:00
I ran MSI with logging (d:\SysMgmt.msi /L*V c:\verboselog.txt) and discovered that it failed to stop the WMI service. Trying to stop it manually resulted in it saying that SMS Host-service is depending on it. Once I managed to stop WMI, installation went just fine.
I reconed that the whole problem stemmed from me upgrading BIOS/firmware/driver just before installing OMSA. The server had just been rebooted and therefore SMS and/or WMI where unresponsive becuase they were busy with some kind of inventory or such. Waiting a bit after reboot probably helps, or like I did, stopping WMI manually first. No more problemos..
tester25
626 Posts
0
October 2nd, 2006 13:00
bentz
21 Posts
0
November 2nd, 2006 23:00
Product: Dell OpenManage Server Administrator -- SYSTEMSMANAGEMENT: The install failed to update configuration files. Please make sure that you have read/write/modify permissions in the directory where you are installing.
dcecfg.exe error code = -1066598273
System is a Dell PowerEdge 1950 running Windows Server 2003 Service Pack 1.
Permissions are fine, by default SYSTEM has Full Control to C:\Program Files and all new subdirectories (permission inheritance) and I'm performing the install as a member of the local Administrators group.
I get the following error in the Event Log:
Source: Application Error
Faulting application dcecfg32.exe, version 5.6.0.4769, faulting module kernel32.dll, version 5.2.3790.2756, fault address 0x00015e02.
Source: MsiInstaller
Product: Dell OpenManage Server Administrator -- SYSTEMSMANAGEMENT: The install failed to update configuration files. Please make sure that you have read/write/modify permissions in the directory where you are installing.
dcecfg.exe error code = -1066598273
So almost at the very end of the install, dcecfg32.exe is crashing, and the entire installation is rolled back. There's almost no software on here (just a bare Windows Server 2003 installation with all updates as of today, 11/2/2006).
I aborted the rollback and was left with the three SA services, but two of them DSM SA Data Manager and DSM SA Event Manager also manage to crash on kernel32.dll. DSM SA Shared Services starts fine.
I tried disabling WMI before the install, didn't help at all.
I'm pretty sure I don't want this software running on my servers if it's going to be unstable and crash all the time. It's really a shame, I'd like to use the RAID management and SNMP hardware monitoring features on these new servers we just ordered.
What gives?