Unsolved
This post is more than 5 years old
1 Message
0
73408
May 27th, 2015 17:00
Issues with Enterprise Manager Data Collector 2015 R1 Install
Hello,
I'm trying to perform an installation of DELL Enterprise Manager Data Collector 2015 R1 on a Windows 2008 R2 SP1 server. The installation itself completes successfully however during the configuration of EM, the Enterprise Manager service fails to start. I get the following messages in the Windows Application logs.
I have a call logged with copilot, but nothing has come out of it yet.
Has anyone else had issues installing EM2015?
Log Name: Application
Source: EnterpriseManagerDataCollector
Date: 27/05/2015 4:36:27 PM
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: hostname.domainname
Description:
Service started successfully.
Log Name: Application
Source: EnterpriseManagerDataCollector
Date: 27/05/2015 4:36:30 PM
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: hostname.domainname
Description:
Stopping Service: JBoss process has disappeared.
Log Name: Application
Source: .NET Runtime
Date: 27/05/2015 4:36:36 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: hostname.domainname
Description:
Application: EmServiceWrapper.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Exception
Stack:
at EmServiceWrapper.EmService.ThrowException(System.String)
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.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()
Log Name: Application
Source: Application Error
Date: 27/05/2015 4:36:37 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: hostname.domainname
Description:
Faulting application name: EmServiceWrapper.exe, version: 15.1.2.45, time stamp: 0x5515aca2
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x5315a05a
Exception code: 0xe0434352
Fault offset: 0x000000000000940d
Faulting process id: 0x135c
Faulting application start time: 0x01d0984764917a87
Faulting application path: C:\Program Files (x86)\Compellent Technologies\Compellent Enterprise Manager\msaservice\jboss-as-7.2.0.Final\bin\EmServiceWrapper.exe
Faulting module path: C:\windows\system32\KERNELBASE.dll
Report Id: b8e3b183-043a-11e5-9c69-005056bf007f
Log Name: Application
Source: Windows Error Reporting
Date: 27/05/2015 4:36:37 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: hostname.domainname
Description:
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: EmServiceWrapper.exe
P2: 15.1.2.45
P3: 5515aca2
P4: EmServiceWrapper
P5: 15.1.2.45
P6: 5515aca2
P7: 16
P8: 77
P9: System.Exception
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_EmServiceWrapper_b472eb7b10a2e2652f8fa55342a673ece794c195_14e6793a
Analysis symbol:
Rechecking for solution: 0
Report Id: b8e3b183-043a-11e5-9c69-005056bf007f
Report Status: 4
Log Name: Application
Source: Windows Error Reporting
Date: 27/05/2015 4:36:37 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: hostname.domainname
Description:
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: EmServiceWrapper.exe
P2: 15.1.2.45
P3: 5515aca2
P4: EmServiceWrapper
P5: 15.1.2.45
P6: 5515aca2
P7: 16
P8: 77
P9: System.Exception
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_EmServiceWrapper_b472eb7b10a2e2652f8fa55342a673ece794c195_14e6793a
Analysis symbol:
Rechecking for solution: 0
Report Id: b8e3b183-043a-11e5-9c69-005056bf007f
Report Status: 0


DELL-Sam L
Moderator
•
7.9K Posts
•
87 Points
0
May 29th, 2015 10:00
Hello ashleybiardaf,
What is the current SCOS that is running on your Compellent? Have you check to make sure that all needed ports are open so that EM can talk to your Compellent & your server? Also when you try to start the client do you get the log in box to come up or do you get the error before then?
Please let us know if you have any other questions.