Unsolved
1 Rookie
•
23 Posts
0
2639
January 19th, 2023 22:00
Cannot get Dell Storage Manager Data Collector working
Our previous installation of Storage Manager Client and Data Collector crashed, due to the hard drive being constantly filled with dozens of mdmp files. I deleted them, and they just kept regenerating.
I could not troubleshoot much, as the hard drive would keep filling up with these files, so I thought it best to reinstall from scratch.
I created a new VM, Windows Server 2019. Firewall currently disabled
I accidentally installed the DSM Client first, but then realised it was not the full product.
I then installed SQL Server Express 2019, enabled the TCP/IP protocol as the website mentions. Then I installed the Data Collector.
It seemed to install fine. However, when I try to open the Dell EMC Unisphere Central shortcut on the desktop, it just says:
Problem with Shortcut: The item 'Shortcut.url' that this shortcut refers to has been changed or moved, so this shortcut will no longer work properly. Do you want to delete this shortcut? Yes/No
The only relevant errors in the Event Viewer that I can see are:
Log Name: Application
Source: StorageManagerDataCollector
Date: 20/01/2023 5:29:16 PM
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: ServerName
Description:
Stopping Service: JBoss process has disappeared.
Event Xml:
http://schemas.microsoft.com/win/2004/08/events/event">
0
4
0
0x80000000000000
2141
Application
ServerName
Stopping Service: JBoss process has disappeared.
================================================================================
Log Name: Application
Source: Application Error
Date: 20/01/2023 5:23:12 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ServerName
Description:
Faulting application name: EmServiceWrapper.exe, version: 20.1.10.79, time stamp: 0x62c7de34
Faulting module name: KERNELBASE.dll, version: 10.0.17763.3887, time stamp: 0x3e07c6b6
Exception code: 0xe0434352
Fault offset: 0x00000000000349b9
Faulting process id: 0x2d8
Faulting application start time: 0x01d92c962f69a5ab
Faulting application path: C:\Program Files\Dell EMC\Storage Manager\msaservice\wildfly-17.0.0.Final\bin\EmServiceWrapper.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: f3b2b507-8dbe-4a46-8cac-5f66de1e0b3f
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
http://schemas.microsoft.com/win/2004/08/events/event">
1000
2
100
0x80000000000000
2035
Application
ServerName
EmServiceWrapper.exe
20.1.10.79
62c7de34
KERNELBASE.dll
10.0.17763.3887
3e07c6b6
e0434352
00000000000349b9
2d8
01d92c962f69a5ab
C:\Program Files\Dell EMC\Storage Manager\msaservice\wildfly-17.0.0.Final\bin\EmServiceWrapper.exe
C:\Windows\System32\KERNELBASE.dll
f3b2b507-8dbe-4a46-8cac-5f66de1e0b3f
====================================================================================
Log Name: Application
Source: .NET Runtime
Date: 20/01/2023 5:23:12 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ServerName
Description:
Application: EmServiceWrapper.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Exception
at EmServiceWrapper.EmService.ThrowException(System.String)
at EmServiceWrapper.EmService.ServiceWorkerThread(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
Event Xml:
http://schemas.microsoft.com/win/2004/08/events/event">
1026
2
0
0x80000000000000
2034
Application
ServerName
Application: EmServiceWrapper.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Exception
at EmServiceWrapper.EmService.ThrowException(System.String)
at EmServiceWrapper.EmService.ServiceWorkerThread(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()


TheGreenAnt
1 Rookie
•
23 Posts
0
August 3rd, 2023 16:00
I do apologise, though, I should at least have posted this as a workaround.
TheGreenAnt
1 Rookie
•
23 Posts
0
August 3rd, 2023 16:00
Hi @hutcha4113 - Kind of yes, but (IMO) not satisfactorily.
The issue is with Java working on older CPUs.
When our Windows Hyper-V Virtual machine containing the DSM application was hosted on a server node with the Intel® Xeon® Gold 6136 Processor, it did not work.
If I moved it to a server node with the Intel® Xeon® Gold 6246 Processor, it worked.
Not everyone has two server clusters, so will not have access to this option.
Dell were not able to provide an alternative, though. So, to me, this is still an unresolved case.
hutcha4113
1 Rookie
•
49 Posts
0
August 4th, 2023 05:00
Wow...that is random. I have a couple of other Hyper V clusters, so will try moving the VM there and see what happens.
Did you have to reinstall when you moved the VM, or did it just start working?
TheGreenAnt
1 Rookie
•
23 Posts
0
August 6th, 2023 23:00
I did not have to reinstall the VM.
A bunch of memory dump files to delete, but just restarting the VM was enough.
One of my clusters has a mix of server nodes in it, and the VM only works on two of them. It does not work on the third node.
VATechTech
3 Posts
0
October 25th, 2023 19:22
Ran into something similar today. We got the jboss process has disappeared error but also an indication to look in server.log which I found under the wildfly-17 folder ("c:\program files\dell emc\storage manager\msaserverice\wildfly-17.0.0.final\standalone\log\server.log"). In that file was an error indicating a configuration could not be parsed. In the app crash stack there's a message about file not found for "c:\program files\dell emc\storage manager\msaserverice\wildfly-17.0.0.final\modules\system\layers\base\org\apache\log4jv2\main\log4j-core-2.17.0.jar"
Turns out one of our engineers removed the file to address the log4j vulnerability but didn't notice that it caused DataCollector to fail to restart.
You probably won't have the exact same issue but scan that log for errors that may help.