Recently I was struggling with an issue with a clients Windows 2012 Server which refused to check in to Storagecraft’s CMD management portal. Below is the fix that worked for me.
Storagecraft CMD is the free management component for Storagecraft Shadowprotect SPX; perhaps the most ubiquitous SME backup tools and super MSP friendly.
This particular backup server wasn’t checking in to our CMD portal. Despite some emails back and forth to Storagecraft we just couldn’t get it to check in. We ran the gamut of rebooting, re-installing, updating.
We checked the CMD log file, which can be found in C:\ProgramData\StorageCraft\endpt\log, and found the following error:
170426 07:26:21 I [8148] cmd_endpt.core.services.base_factory (203): spx.rest_access.no_response<{"cause": "stcx.NoConnection('Cannot Connect: Connection to 'https://127.0.0.1:13581/spx/version/' failed: HTTPSConnectionPool(host='127.0.0.1', port=13581): Max retries exceeded with url: /spx/version/ (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 403 Forbidden',)))', data=b{})"}
The cannot connect to proxy error was a little confusing. Disabling the firewall on the server didn’t help and we weren’t using a proxy for internet access.
When we tried to access the URL shown in the log, https://127.0.0.1:13581/spx/version/, we got a 404 error rather than the 403 shown in the log. Perhaps that was the clue, what if the files weren’t there because they couldn’t be put in to the right place.
We stopped the Storagecraft SPX service and set the Logon tab to use a domain administrator account. We did the same for the Storagecraft Endpoint Agent service.
After restarting the services we could connect to the URL above and get a response. The agent checked in within about 10 minutes and everything was good.
We subsequently set the Storagecraft SPX service back to log on as the Local System account and everything remains working.
If you found another cause for this then let me know in the comments below.