1 Message

November 9th, 2004 18:00

I went through the motions described here and the install still hangs right after the InstallShield dialog box completes preparing for the install.  Also, Setup.exe and IKernel.exe (InstallShield's executable) can be seen running in the task manager.  Any other ideas?

2 Intern

 • 

127 Posts

December 29th, 2004 10:00

If your installation still hangs at various times please create a generic Administrator/Domain Administrator account with no special profile settings and use it to perform the installation.

15 Posts

May 3rd, 2005 02:00

Do you have the SMS client installed?

7 Posts

May 31st, 2005 17:00

It may be worth mentioning the OMClean utility which cleanly removes all OpenManage software except the very oldest.

8 Posts

November 9th, 2005 13:00

I'm trying use the OMClean that comes with the 4.5 version and it's saying that it only works with version 4.3 or older. Is there a version that works with 4.5?

9 Posts

December 17th, 2005 04:00

hello everybody

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

28 Posts

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.

January 19th, 2006 17:00

When I try to uninstall or upgrade OpenManage Server Administrator v4.4 I receive an error.
"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?

7 Posts

January 19th, 2006 17:00

Sorry to hear that OMClean is no longer valid on the latest version. Before I started using OMClean, I employed the following technique:

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!

3 Posts

March 21st, 2006 21:00

Hello,
 
Why is it that the "Diagnostics" tag often does not appear in OpenManage installed on a 2650 or 2850 running Linux? It seems to take some time after the Open Manage service is started on the machine before the Diagnostics tab begins to appear.
 
Note that we do not have DRAC/RAC installed on our machines.
 
Thanks for your help.
 
 

3 Posts

April 13th, 2006 17:00

Excellent, thanks!!!

626 Posts

April 13th, 2006 17:00

It's because the Diagnostics portion of OpenManage Server Administrator (OMSA) is more or less like an add-on component to OMSA that separately discovers all the devices on the system and enumerates them in its own device tree.  This is what the Readme for OMSA has to say about it:
 
* Depending on the interval between Server Administrator startup and
 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.

October 2nd, 2006 11:00

Just wanted to share my solution to a problem installing OMSA 4.5 that was driving me nuts. On some systems I would get "install terminated prematurely" just when the installer was trying to stop services.

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..

626 Posts

October 2nd, 2006 13:00

Cool.  Thanks for sharing.

21 Posts

November 2nd, 2006 23:00

I've been through this article and am still having major problems with OMSA 5.1.

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?
No Events found!

Top