Frequently Asked Questions (FAQs) - SKF @ptitude Connect (cloud)
SKF @ptitude Thin Client Transfer (TCT) hangs when attempting to upload data to the MHRP cloud server.
- Verify the SKF @ptitude TCT version currently installed on the client computer. If the TCT version is v18.104.22.168 or earlier, then upgrade the client software to newer version v8.1.3136.3, which has improved transfer capabilities. Newer versions of SKF @ptitude TCT such as this one will require local administrator rights on the client computer for installation. To obtain a copy of this particular software version, open a support case with the Technical Support Group at www.skf.com/cmTSG.
Which ports must be open in the firewall in order to upload and download data via the SKF cloud?
- Bi-directional TCP communication must be allowed for IP addresses 22.214.171.124 (forwarded) and 126.96.36.199 (current). Similarly, bi-directional TCP communication must be permitted for the port number that was assigned to your cloud connection (e.g. port 8088 for MHRP database server). Please refer to the SKF @ptitude Connect setup instructions given to you for the correct port number. Otherwise, this information can be obtained by opening a support case at www.skf.com/cm/TSG.
How can I obtain the correct USB driver for connecting my SKF Microlog Analyzer device to the SKF cloud?
- A signed SKF USB Driver required for Microlog Analyzer model numbers CMXA 45, 48, 75 and 80 can be downloaded using the link below:
I cannot connect to the Transaction Server after launching SKF @ptitude TCT:
“Could Not Connect To Transaction Server"
- The most common reason for the above error is that an incorrect Transaction Server has been configured. Please refer to the original setup documentation provided and ensure the proper server connection details (server name and port number) have been configured correctly. There are two ways to modify connection information:
Re-run the SKF @ptitude Analyst Thin Client Transfer software installation. When going through the installation wizard, choose the option to 'Modify' the existing installation. You will be prompted to enter/modify server connection details.Correct the server name and/or port number according to the original setup documentation provided by SKF.
Create or modify the existing SKF @ptitude TCT shortcut.This can be helpful in cases where multiple Transaction Server services are being used.To get started, create a new shortcut for SKF @ptitude TCT on the local desktop, if one does not already exist. Next, right-click on the desktop shortcut and select Properties. Modify the Target field with the correct name and port number to the cloud database server environment (example below). Refer to the setup documentation for the information.
Target: "C:\Program Files (x86)\SKF-RS\SKF @ptitude Analyst\skfTCT.exe" -TS:emeaservices.cmcrdc.com,8088
(where -TS:emeaservices.cmcrdc.com,8088 consists of the server path and port number assigned to the SKF cloud database)
I cannot login to RDCHome - the site says my user name is not associated with this Remote Diagnostics Center (RDC) web portal:
- SKF hosts several RDCHome web interface portals for SKF @ptitude software services, each of them having slightly different website URLs (suffixes). Every registered cloud user is granted access to RDCHome under one of the web portal instances and provided the exact URL for logging in. If you are seeing the above message, refer to the original SKF @ptitude Connect setup documentation to verify the specific RDCHome web portal address in which you were assigned. Keep in mind that users from the same company and/or database may be assigned to different RDCHome web portals - meaning that your colleague's URL may slightly differ from the URL in which you were given. If you still have trouble logging in after verifying the RDCHome URL for your particular user account, please open a support case for further assistance at www.skf.com/cm/TSG.
I am not able to connect to my SKF Microlog Analyzer device from within the cloud. The message, “Microlog Analyzer not responding. Check connections and baud rate" keeps appearing:
- The SKF @ptitude Thin Client Transfer (TCT) client software application must be used in order to upload and download data from the handheld to the cloud. Download and install the appropriate version of the software onto the client PC. To download the most current version, use the link below:
When attempting to launch SKF @ptitude Analyst from the RDCHome web dashboard, a RemoteApp error about an unknown publisher appears.
- Ensure the login name you entered for the RDP connection is in the following format: RDCNLAM\username. If correct, verify the username and password you are correct. If you do not have access to the original setup documentation, open a support case at www.skf.com/cm/TSG and the Technical Support Group will verify your credentials.
RemoteApp is not able to connect because an error occurred on the remote computer:
“Your computer can't connect to the remote computer because an error
occurred on the remote computer that you want to connect to."
- This error is usually caused by a communication issue between the client PC and the remote SKF server. First, contact the local IT administrator to ensure RDP traffic to the SKF cloud server is not blocked. If the IT administrator is unable to solve the problem, a registry key can be added that would change the way the computer connects to the SKF server:
1. Open the Registry Editor on the client PC. To do so, type regedit into the search bar within the Windows Start menu.
2. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client.
3. Add a new Dword32 key and name it as RDGClientTransport:
4. Lastly, right click on the new key and select Modify. Set the value to 1, then press OK and save your changes when exiting.