...
We are currently facing an issue where the CloudConnector is not able to connect to our Azure Relay service. This results in us not being able to connector to the CloudConnector. The issue seems to be related to the current key the CloudConnector uses to connect with. We are investigating the root cause, but have the following solution:
Customer
...
steps
The following steps are to be performed by the IT administrator responsible for the server where the CloudConnector is installed on.
| Note |
|---|
Please note |
...
, if you have multiple connectors installed, you must repeat the following steps for each connector. |
Log onto the server where CloudConnector is installed. You must log on as an Administrator.
Go to Windows Services and find “CloudConnector” for your application.
Stop the service.
Go to C:\ProgramData\ConnectMyApps. The folder may be hidden so you may need to “show hidden folders”.
You will see a “_appkey.json” file for your CloudConnector. *
The key file will have different names, depending on which app is involved:
Active Directory: “msad_appkey.json”
Visma Lønn: “visl_appkey.json»
Visma Business: “visb_appkey.json»
Microsoft SQL Server: “msql_appkey.json»
...
Return to the Windows Services control panel and restart the CloudConnector service.
The service should restart successfully and show “Running” as the status.
10. Reply Reply to the support ticket from ConnectMyApps and confirm that “X” has been added to the key.
11. Wait Wait for ConnectMyApps to reply and confirm the issue is resolved.
...