Skip to main content
Start a Conversation

Unsolved

rv19

21 Posts

9670

October 21st, 2020 04:00

Dell Open Manage Server Administrator not working on PowerEdge R510

Hello,


I have a Dell PowerEdge R510 with Server 2012 R2 but cannot get Dell Open Manage Server Administrator to work properly. I have confirmed that version 9.3, 9.2 should work with the hardware and OS but when it opens it does not display system information but only session management information.
I haven't had this issue with other model servers or OS. Has anyone experienced this issue and if so, what is the solution?


Thanks,
Roger

DELL-Shine K

6 Operator

 • 

3K Posts

October 21st, 2020 06:00

Can you check whether all Open Manage Server Administrator (OMSA) services are running. You can refer below link for list of services. You can also try uninstall and install OMSA it again

https://www.dell.com/support/manuals/en-tw/openmanage-server-administrator-v9.3/omsa_9.3_users_guide/server-administrator-services?guid=guid-ccdabde1-2904-4aa9-8c9a-9fbcde5df616&lang=en-us 

rv19

21 Posts

October 21st, 2020 08:00

Hello Shine,

Thank you.

I don't see any Windows: SM SA services listed.  I don't see them on the other Dell servers we have, where OMSA is working properly.  What am I missing?

I have uninstalled and reinstalled version 8.5, 9.2 and 9.3 but the results are the same. 

Thanks,

Roger

Sachin_Gani

3 Posts

October 21st, 2020 20:00

Hi Roger,

You please check for windows: DSM SA services and try to start those if they are in "Stop" state.

Thanks,

Sachin

#IWork4Dell

DELL-Shine K

6 Operator

 • 

3K Posts

October 21st, 2020 20:00

Can you reboot the server and check whether that fixes the issue. Is iDRAC on the server is accessible and showing the details of the server. Can you also run "racadm getsysinfo" command on the operating system command terminal and check the behavior.

rv19

21 Posts

October 22nd, 2020 03:00

Hello Sachin, I checked the DSM SA services and they are in the running state. Thanks, Roger

rv19

21 Posts

October 22nd, 2020 03:00

Hello Shine, Rebooting the server had no effect. I ran racadm systeminfo: What am I looking for? C:\Windows\system32>racadm getsysinfo RAC Information: RAC Date/Time = 10/22/2020 06:31:19 Firmware Version = 1.90 Firmware Build = 04 Last Firmware Update = 04/18/2012 16:22:22 Hardware Version = 0.01 MAC Address = XXXXX Common settings: Register DNS RAC Name = 0 DNS RAC Name = idrac-XXXXX Current DNS Domain = Domain Name from DHCP = 0 IPv4 settings: Enabled = 1 Current IP Address = XXXXX Current IP Gateway = XXXXX Current IP Netmask = 255.255.255.0 DHCP Enabled = 1 Current DNS Server 1 = 0.0.0.0 Current DNS Server 2 = 0.0.0.0 DNS Servers from DHCP = 0 IPv6 settings: Enabled = 0 Current IP Address 1 = :: Current IP Gateway = :: Autoconfig = 1 Link Local IP Address = :: Current IP Address 2 = :: Current IP Address 3 = :: Current IP Address 4 = :: Current IP Address 5 = :: Current IP Address 6 = :: Current IP Address 7 = :: Current IP Address 8 = :: Current IP Address 9 = :: Current IP Address 10 = :: Current IP Address 11 = :: Current IP Address 12 = :: Current IP Address 13 = :: Current IP Address 14 = :: Current IP Address 15 = :: DNS Servers from DHCPv6 = 0 Current DNS Server 1 = :: Current DNS Server 2 = :: System Information: System Model = PowerEdge R510 System Revision = II System BIOS Version = 1.14.0 Service Tag = XXXXX Express Svc Code = XXXXX Host Name = XXXXX OS Name = Microsoft Windows Server 2012 R2, Standard x64 Edition Power Status = ON Embedded NIC MAC Addresses: NIC1 Ethernet = XXXXX iSCSI = 00:00:00:00:00:00 NIC2 Ethernet = XXXXX iSCSI = 00:00:00:00:00:00 NIC3 Ethernet = N/A iSCSI = N/A NIC4 Ethernet = N/A iSCSI = N/A Watchdog Information: Recovery Action = None Present countdown value = 299 seconds Initial countdown value = 480 seconds C:\Windows\system32> Thanks, Roger

DELL-Shine K

6 Operator

 • 

3K Posts

October 22nd, 2020 04:00

I was checking whether racadm component of OMSA is working or not.  Can you run below commands and see whether it is working. This will help us to see whether it is a OMSA GUI issue or not

omreport chassis fans
omreport mainsystem fans

If above commands are working you can try to launch OMSA on a different browser or remotely from a different machine using https://host IP:1311

Below link have details on configuration required on the browser for OMSA. Can you check whether these settings are configured.

https://www.dell.com/support/manuals/en-tw/dell-openmanage-server-administrator-8.5/omsa_8.5_users_guide/configuring-security-settings-on-systems-running-a-supported-microsoft-windows-operating-system?guid=guid-9932883f-939e-4d9c-888e-5df669610f47&lang=en-us 

rv19

21 Posts

October 22nd, 2020 05:00

Hello Shine, The two commands do not work as I get the following: C:\Windows\system32>omreport chassis fans Error! No fan probes found on this system. C:\Windows\system32>omreport mainsystem fans Error! Invalid command: mainsystem I am unable to launch OMSA from another browser (Chrome) or system using https://host IP:1311. I can ping the server successfully but not open OMSA from another system. When I try to connect I get a "malformed URL" message regardless of using "Server FQDN/IP address and my user name and password Hostname / IP address: Username: Password: I have never had to make any browser changes other than adding it to the trusted site zone. This has always worked regardless of the version. I have other model PowerEdge servers with OMSA version 9.3 and it works fine. There is apparently something on the R510 that is preventing OMSA from displaying properly. When I open it, only session management information is shown instead of the standard system information. Thanks, Roger

Sachin_Gani

3 Posts

October 22nd, 2020 23:00

Hi Roger,

From the above data, it is clear that DSM SA data manager service is not working and DSM SA connection is functioning properly
since you can see session management information.
Please uninstall the installed OMSA and after that delete the OMSA backup file in C:/Program Files/Dell. Delete this Dell Folder.
For better part reboot the server once and install OMSA again. Then try running the OMSA command "omreport chassis fans"

Thanks,
Sachin
#IWork4Dell

rv19

21 Posts

October 26th, 2020 05:00

Hello Sachin,

Uninstalling OMSA  automatically deleted the OMSA backup file.  Rebooting the server the server and reinstalling had no effect.  I used the latest version 9.5. According to the dialog the installation completed successfully but I did notice that the DSM SA data manager service was not started automatically although it is set to do so. I started it  but noticed it immediately returns to the stopped state. As a result re-launching OMSA displays only  the Session Management information.

Any idea on what could cause the DSM SA Data Manager to refuse to stay in the started state?

Thanks,

Roger

rv19

21 Posts

October 29th, 2020 10:00

Hello, Does anyone know what could cause the DSM SA Data Manager to refuse to stay in the started state and how to correct this? Thanks, Roger

DELL-Shine K

6 Operator

 • 

3K Posts

October 29th, 2020 21:00

I am not sure why this service is not getting started on your server. Can you check windows event viewer and see whether there is any information related to DSM SA Data Manager service start failure.

rv19

21 Posts

October 30th, 2020 03:00

Hello Sachin, The OS is Server 2012 R2. This was upgraded in place from Server 2008 R2 as was the other PowerEdge R510 server similarly affected. Reinstalling the OS is not a reasonable option just for this application. Are there specific registry settings associated with the DSM SA Data Manager service that can be verified or adjusted that would make the service remain running instead of immediately stopping? Note: I have also upgraded other servers in place to Server 2012 R2 and installed OMSA version 9.3 without issue. There appears to be something specific with the settings on the R510 that is causing the conflict. I have tried using version 8.5, 9.2, 9.3,9.4 and 9.5 but after each is installed the DSM SA Data Manager service refuses to remain in the running state. Thanks, Roger

rv19

21 Posts

October 30th, 2020 03:00

Hello Shine, Yes, the following error appears in the event viewer that relates to the DSM SA Data manager service: Log Name: Application Source: Application Error Date: 10/29/2020 10:30:59 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: XXXX.XXXX.com Description: Faulting application name: dsm_sa_datamgr64.exe, version: 9.5.0.4063, time stamp: 0x5f1891ee Faulting module name: dcsupt64.dll, version: 9.5.0.4063, time stamp: 0x5f18919f Exception code: 0xc0000005 Fault offset: 0x000000000000b7a2 Faulting process id: 0x1420 Faulting application start time: 0x01d6ae000c1709a8 Faulting application path: C:\Program Files\Dell\SysMgt\dataeng\bin\dsm_sa_datamgr64.exe Faulting module path: C:\Program Files\Dell\SysMgt\shared\bin\dcsupt64.dll Report Id: 5c87cb05-19f3-11eb-80bd-6805ca07ef0e Faulting package full name: Faulting package-relative application ID: Event Xml: 1000 2 100 0x80000000000000 1567296 Application XXXX.XXXX.com dsm_sa_datamgr64.exe 9.5.0.4063 5f1891ee dcsupt64.dll 9.5.0.4063 5f18919f c0000005 000000000000b7a2 1420 01d6ae000c1709a8 C:\Program Files\Dell\SysMgt\dataeng\bin\dsm_sa_datamgr64.exe C:\Program Files\Dell\SysMgt\shared\bin\dcsupt64.dll 5c87cb05-19f3-11eb-80bd-6805ca07ef0e

Sachin_Gani

3 Posts

October 30th, 2020 03:00

Hi Roger,

We are not sure why this is happening in your case..

Are you using which version of windows? ..

if effort is less and possible to install OS again ,please check after reinstalling.

 

Thanks,

Sachin

#IWork4Dell

 

Was this post helpful?

View All

No Events found!

Top