CloudEndure Agent Stops Unexpectedly Before Initial Replication

Issue

When performing an initial replication on Windows, the progress does not move from 0% after installing the agent successfully.

Log Name:      Application
Source:        CloudEndureConverter
Event ID:      4100
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
The CloudEndureConverter service has stopped : process exited unexpectedly.


A number of other errors are seen in the Application event log:

Log Name:      Application
Source:        CloudEndureTailer
Event ID:      11
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
The Python service control handler failed. 
Traceback (most recent call last):
  File "win32serviceutil.pyc", line 821, in ServiceCtrlHandlerEx
  File "windows_service_wrapper.pyc", line 30, in SvcStop
  File "win32serviceutil.pyc", line 797, in ReportServiceStatus
error: (6, 'SetServiceStatus', 'The handle is invalid.') 
%2: %3

Log Name:      Application
Source:        CloudEndureService
Event ID:      11
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
The Python service control handler failed. 
Traceback (most recent call last):
  File "win32serviceutil.pyc", line 821, in ServiceCtrlHandlerEx
  File "windows_service_wrapper.pyc", line 30, in SvcStop
  File "win32serviceutil.pyc", line 797, in ReportServiceStatus
error: (6, 'SetServiceStatus', 'The handle is invalid.') 
%2: %3

Log Name:      Application
Source:        CloudEndureDriverTailer
Event ID:      11
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
The Python service control handler failed. 
Traceback (most recent call last):
  File "win32serviceutil.pyc", line 821, in ServiceCtrlHandlerEx
  File "windows_service_wrapper.pyc", line 30, in SvcStop
  File "win32serviceutil.pyc", line 797, in ReportServiceStatus
error: (6, 'SetServiceStatus', 'The handle is invalid.') 
%2: %3

Log Name:      Application
Source:        CloudEndureVolumeUpdater
Event ID:      11
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
The Python service control handler failed. 
Traceback (most recent call last):
  File "win32serviceutil.pyc", line 821, in ServiceCtrlHandlerEx
  File "windows_service_wrapper.pyc", line 30, in SvcStop
  File "win32serviceutil.pyc", line 797, in ReportServiceStatus
error: (6, 'SetServiceStatus', 'The handle is invalid.') 
%2: %3


The following can be seen in the C:\Program Files (x86)\CloudEndure\agent.log.0 log file:
{"message":"Boot device 'c:0' is missing from volume map","log":{"type":"Remote","name":"Agent","level":"ERROR","level_number":40},"source_code":{"function":"removeDuplicatedVolumes","file":"com.cloudendure.agent.platform.HardwareInfoGetterWindows"},"runtime_thread":21,"origin":{"hostname":"host"},"@timestamp":"2020-04-21T05:59:32.258Z"}>>>
{"message":"Creating SourceNetworkCfg folder","log":{"type":"Remote","name":"Agent","level":"ERROR","level_number":40},"source_code":{"function":"storeCurrentTcpipSettings","file":"com.cloudendure.agent.platform.HardwareInfoGetterWindows"},"runtime_thread":21,"origin":{"hostname":"host"},"@timestamp":"2020-04-21T05:59:32.291Z"}>>>
{"message":"Load module failed","log":{"type":"Remote","name":"Agent","level":"ERROR","level_number":40},"source_code":{"function":"load","file":"com.cloudendure.agent.TraceDriverAdapter"},"runtime_thread":17,"origin":{"hostname":"host"},"@timestamp":"2020-04-21T06:00:22.243Z"}>>>
{"message":"Changing volumes {0} failed","log":{"type":"Remote","name":"Agent","level":"WARNING","level_number":30},"source_code":{"function":"changeVolumes","file":"com.cloudendure.agent.VolumesChanger"},"runtime_thread":17,"args":["[name: \\\\?\\PhysicalDrive0, size: 192199786496]"],"origin":{"hostname":"host"},"@timestamp":"2020-04-21T06:00:22.244Z"}>>>
{"message":"Error changing volumes","log":{"type":"Remote","name":"Agent","level":"ERROR","level_number":40},"source_code":{"line":69,"function":"getChannel","file":"com.cloudendure.agent.ClientCommunicator"},"runtime_thread":17,"exception":{"message":"java.io.IOException: loadDriver failed with error code 577, stderr: "System error 577 has occurred.\n\nWindows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.\n\n", stdout: "\nC:\\Program Files (x86)\\CloudEndure>echo off \n[SC] StartService FAILED 577:\n\nWindows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.\n\n"","type":"com.cloudendure.agent.VolumesChanger$VolumeChangeException","trace":"com.cloudendure.agent.VolumesChanger$VolumeChangeException: java.io.IOException: loadDriver failed with error code 577, stderr: "System error 577 has occurred.\n\nWindows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.\n\n", stdout: "\nC:\\Program Files (x86)\\CloudEndure>echo off \n[SC] StartService FAILED 577:\n\nWindows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.\n\n"\r\n\tat com.cloudendure.agent.VolumesChanger.changeVolumes(VolumesChanger.java:69)\r\n\tat com.cloudendure.agent.ClientCommunicator.getChannel(ClientCommunicator.java:229)\r\n\tat com.cloudendure.agent.ClientCommunicator.receive(ClientCommunicator.java:334)\r\n\tat com.cloudendure.agent.ClientMessageHandler.run(ClientMessageHandler.java:66)\r\nCaused by: java.io.IOException: loadDriver failed with error code 577, stderr: "System error 577 has occurred.\n\nWindows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.\n\n", stdout: "\nC:\\Program Files (x86)\\CloudEndure>echo off \n[SC] StartService FAILED 577:\n\nWindows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.\n\n"\r\n\tat com.cloudendure.common.ProcessUtils.runCommand(ProcessUtils.java:121)\r\n\tat com.cloudendure.common.ProcessUtils.runShellCommand(ProcessUtils.java:84)\r\n\tat com.cloudendure.agent.TraceDriverAdapter.load(TraceDriverAdapter.java:245)\r\n\tat com.cloudendure.agent.AgentManager.start(AgentManager.java:962)\r\n\tat com.cloudendure.agent.VolumesChanger.changeVolumes(VolumesChanger.java:63)\r\n\t... 3 more\r\n"},"origin":{"hostname":"host"},"@timestamp":"2020-04-21T06:00:22.245Z"}>>>


Additional installation logs are available from cloudendure.txt in the agent installation directory.

Resolution

From and administrative PowerShell command prompt confirm Secure Boot is enabled:
PS C:\WINDOWS\system32> Confirm-SecureBootUEFI
True


Disable Secure Boot
From Windows:
- Select Start | Settings
- Select Update and Security
- Select Recovery
- Click Restart now under Advanced startup
- Select Troubleshoot
- Select Advanced options
- Select Startup Settings
- Click Restart
- Press 7 on Startup Settings to disable driver signature enforcement
- Reboot

Reinstall the CloudEndure agent.

References

Products

Amazon CloudEndure (any)

Created: 23rd April 2020
Updated: 23rd April 2020


© 2005-2020 Jamie Morrison