Unsolved
This post is more than 5 years old
685 Posts
1
3676
Announcement: Hotfix for OME 2.4 is available now (Recommended)
Hi All,
The Hotfix for System Update issues in OME 2.4 is available now. Here is a direct link to download the same:
Here are the instructions for installing the Hotfix:
- Ensure that you have OpenManage Essentials version 2.4 installed.
- Download OpenManageEssentials_2_4_0_1_A00.exe (Hotfix executable) and run it as Administrator.
- Verify that the HF1013.2.4 is shown by hovering the mouse over OME version in the About window.
OpenManage Essentials version 2.4.0.1 (Hotfix HF1013.2.4) provides fixes for the following:
- The 'Non-Compliant Systems' view has devices or updates missing, or is completely blank. In a few instances, when the catalog is updated or the Compliance view is refreshed, the Console stops responding and display the message:
'Unhandled error in the application. The data cache did not refresh correctly'. - The 'Non-Compliant Systems' view is missing Hyper-V servers which are managed by the operating system IP address.
pesson
11 Posts
0
June 28th, 2018 02:00
Hi Folks,
Has anyone seen issues with DSM Essentials Task Manager not starting after 2.4 Hotfix applied? In fact, looks like fix doesn't apply as "About" still shows version as 2.4.0.930.
Application Error Event 1000
Faulting application name: DSM_OMSE_TaskManager_64.exe, version: 2.2.0.2060, time stamp: 0x57c56ded
Faulting module name: xerces-c_3_1_vc11.dll, version: 6.3.9600.18969, time stamp: 0x5aa29ff0
Exception code: 0xc0000135
Fault offset: 0x00000000000ecf30
Faulting process id: 0x134c
Faulting application start time: 0x01d40ec18cc6ac26
Faulting application path: E:\Program Files\Dell\SysMgt\Essentials\bin\DSM_OMSE_TaskManager_64.exe
Faulting module path: xerces-c_3_1_vc11.dll
Report Id: ca77fcbb-7ab4-11e8-80e4-005056b963cf
Faulting package full name:
Faulting package-relative application ID:
Regards,
Paul Esson
DELL-Shivendra K
685 Posts
0
July 2nd, 2018 06:00
Hi Paul,
We haven't seen this. Hope no XML files were modified manually under OME's Configuration directory?
Good to open a ticket with Dell Support. They'll help to resolve the problem. Keeping the task manager service logs and crash dump is always handy.
mkeir
1 Message
0
August 13th, 2018 21:00
Seeing the same issue, task manager and network monitor services not starting within the 30 second timeout.
If you hover the mouse over the version number link, the hotfix shows in a popup box.
I have opened a case with support for more help.
brastedd
336 Posts
0
August 17th, 2018 13:00
Paul 35308
1 Message
0
September 26th, 2018 14:00
I had this problem. The "DSM_OMSE_TaskManager_64.exe" was not updated when I upgraded my installation. The date on the file was from the previous OME version I upgraded from.
C:\Program Files\Dell\SysMgt\Essentials\bin\DSM_OMSE_TaskManager_64.exe
I extracted the same file from the OpenManageEssentials_2_4_A00 installation file. e.g. extract to a folder, but don't RUN. Inside the extracted folder locate the CAB file \windows\ManagementStation\Essent~1.cab
You can open that using the windows file manager and extract the "dsm_omse_taskmanager_64.exe.674D7E1A_589B_4C7E_8307_2DB62F9596E4" file
Use the expand.exe tool to expand the file. e.g.
expand.exe dsm_omse_taskmanager_64.exe.674D7E1A_589B_4C7E_8307_2DB62F9596E4 DSM_OMSE_TaskManager_64.exe
Then simply replace the file in the the installation directory and start the service.