Your RPMSCloud data has, or very soon will be, moved to RPMSCloud2.com.
Since beginning the relocation process, we have encountered two issues that are problematic for some users. Each of them have solutions, and are documented below.
Known Issue 1: After generating a PDF report from the RPMSCloud2, users can’t save the file locally.
This issue is caused by the latest Adobe Reader program our cloud server uses, which ‘sandboxes’ PDF files away from attached drives. The steps to reproduce the problem and the step-by-step solution itemized below are also demonstrated in this video:
Run any report from the RPMSCloud2 and select PDF file as the destination.
1. From within the Adobe reader that pops up automatically on the RPMSCloud2, click File, Save As, and choose a destination folder on your local computer, then click Save.
2. An error is displayed as shown below:
3. Click OK, then in the Adobe Reader menu bar, click Edit, then click Preferences
4. On the Preferences screen
a. Select the category Security (Enhanced)
b. Uncheck the box at the top in the Sandbox Protections section that says “Run in AppContainer”
c. Click OK
5. A message will be displayed that says Adobe must be closed and restarted to save the settings. Close Adobe, regenerate the report from RPMSCloud2, then save locally again. The file will save to your local computer.
Known Issue 2: Some Users running Windows 10 Home or Windows 11 Home can’t launch the RPMSCloud2 RemoteApp twice without Reboot
The issue can be shown on some Windows 10 Home and Windows 11 Home versions with the following steps:
1. Launch the RPMSCloud2 remoteApp, do some work, then close the remoteApp.
2. Attempt to relaunch the RPMSCloud2 remoteApp, and nothing happens.
3. Investigating in task manager, find a ‘hung’ Remote Desktop Connection – one for the orignal use in step 1 above, and extras for each attempt to launch via step 2.
4. Killing (Right-click, end task) each of the Remote Desktop connections allows relaunch of the RPMSCloud2 remoteApp, but still leaves an RDC task running upon exit.
The issue can be solved for those Windows 10 Home and Windows 11 Home exhibiting the problem by installing an RDP that does NOT launch the remoteApp, but instead triggers the RPMSCloud to launch the program for you. This is similar to way that Mac and Chromebook users operate the RPMSCloud. The new RDP is known as RPMCloud2 Home. Install it through the following steps.
1. Delete your current desktop icon for RPMSCloud2
2. Click this link to download a zip file of the RDP installation program: https://www.rpms.com/product/cloud/RPMSCloud2_Home.zip
3. When the file has downloaded, open the file location, then right click the file to extract the contents.
4. Double-click the MSI file that was extracted to launch RDP installation. It will create a shortcut on your desktop that looks like the picture below. Simply double-click it to connect to your data on the new RPMSCloud2 server.
5. The first time you attempt to connect to the RPMSCloud2 server using the RPMSCloud2 Home RDP file, you may be asked again for your network username and network password. Those were listed on your original Your RPMSCloud System is Ready email, and again at the bottom of the Data Relocation email. Your internal RPMS password has not changed. (Depending on your Windows security settings, your network username and network password may be ‘remembered’ – if you get to the RPMS login screen, you are all set.)