Community
RU Remote Printing Failure
Links used in this discussion
George Vaughn,
User (Posts: 2)
Nov 14, 2020 3:59:03 pm EST
Support level: Free or trial
I installed RU 6.10.10.0 Viewer and Host on computers both running Windows 10 about six weeks ago. Everything seemed to work fine at first. In the last two to three weeks, I began to experience difficulty printing remotely fr om the Host to the Viewer. The scope and frequency of the difficulty have gradually expanded so that remote printing is almost always unavailable.
Each failure is followed with a window at the Viewer end titled "Error Report - Remote Utilities Viewer" with a lengthy error message which is summarized by this text: "Error (EOUTOFRESOURCES): not enough memory available to process command." There have been no significant hardware or software changes in the Viewer computer since installation. Just over 6 gigs of physical memory is installed, with over 2 gigs of available memory while my usual programs are running.
The Error Report Window has on it a button allowing the report to be sent to RU. I have done this repeatedly, most recently, today. There is an ID# associated with the report, and that number for the last report sent is: {8231875B-68E7-41D4-8D94-0BDF97734BDB}.
The Error Report Window has another button allowing the report to be copied. However, there is no indication of wh ere the report is being copied so I cannot access the "copied" report to view it or include it in this post. I am sure it would be helpful in addressing this issue.
I have tried a number of things, including running Viewer as Administrator, without success. I hope someone can take a look at this as soon as possible. I do like the program, but this is a big negative.
Thanks.
Each failure is followed with a window at the Viewer end titled "Error Report - Remote Utilities Viewer" with a lengthy error message which is summarized by this text: "Error (EOUTOFRESOURCES): not enough memory available to process command." There have been no significant hardware or software changes in the Viewer computer since installation. Just over 6 gigs of physical memory is installed, with over 2 gigs of available memory while my usual programs are running.
The Error Report Window has on it a button allowing the report to be sent to RU. I have done this repeatedly, most recently, today. There is an ID# associated with the report, and that number for the last report sent is: {8231875B-68E7-41D4-8D94-0BDF97734BDB}.
The Error Report Window has another button allowing the report to be copied. However, there is no indication of wh ere the report is being copied so I cannot access the "copied" report to view it or include it in this post. I am sure it would be helpful in addressing this issue.
I have tried a number of things, including running Viewer as Administrator, without success. I hope someone can take a look at this as soon as possible. I do like the program, but this is a big negative.
Thanks.
Pauline,
Support (Posts: 2862)
Nov 16, 2020 2:58:34 pm EST
Hello George,
Thank you for your message.
Could you please try updating to the latest 6.12.2.0 Beta 2 version and see if the issue persists after the update? It might be that the issue was already resolved in the latest update. Please note that despite its name, the 6.12.2.0 Beta 2 version is a fully functional release as it only consists of bug fixes and improvements.
The latest 6.12.2.0 Beta 2 version is available for the download on this page.
When updating Remote Utilities please make sure to update both Host and Viewer as the version mismatch might lead to performance issues or some features not working.
In addition, in case if the issue persists after updating to the latest version, please try deleting the contents of the following folder C:\Program Files (x86)\Remote Utilities - Host\Printer\Common and see if this helps to resolve the issue.
Please let me know if the solutions above did not help and the issue persists.
Thank you for your message.
Could you please try updating to the latest 6.12.2.0 Beta 2 version and see if the issue persists after the update? It might be that the issue was already resolved in the latest update. Please note that despite its name, the 6.12.2.0 Beta 2 version is a fully functional release as it only consists of bug fixes and improvements.
The latest 6.12.2.0 Beta 2 version is available for the download on this page.
When updating Remote Utilities please make sure to update both Host and Viewer as the version mismatch might lead to performance issues or some features not working.
In addition, in case if the issue persists after updating to the latest version, please try deleting the contents of the following folder C:\Program Files (x86)\Remote Utilities - Host\Printer\Common and see if this helps to resolve the issue.
Please let me know if the solutions above did not help and the issue persists.
George Vaughn,
User (Posts: 2)
Nov 26, 2020 9:53:47 pm EST
Support level: Free or trial
Thank you, Polina, for your suggestions. I am sorry to report they did not work. With the beta version installed, I was still unable to print. The beta version also displayed other issues, especially with cursor activity, that made it difficult to use. While I was using the non-beta and beta versions of the program, I also experienced too frequent connection interruptions. My experience has led me to search out an alternative product for remote access. I wish your company much success, but your software does not seem to be the solution which will work for me.
Pauline,
Support (Posts: 2862)
Nov 27, 2020 10:00:16 am EST
Hello George,
I'm sorry to hear that you had such experience with our program.
If possible, could you please provide us some more details regarding the issues with the cursor when using the latest 6.12.2.0 Beta 2 version? Unfortunately, we couldn't reproduce any strange behavior of the cursor and we haven't been reported any serious issues on the cursor's behavior recently.
As for the frequent disconnects issue - perhaps, this troubleshooting KB guide could provide some helpful information.
However, we apologize for any inconvenience. Please feel free to post another message if you have other questions in the future.
I'm sorry to hear that you had such experience with our program.
If possible, could you please provide us some more details regarding the issues with the cursor when using the latest 6.12.2.0 Beta 2 version? Unfortunately, we couldn't reproduce any strange behavior of the cursor and we haven't been reported any serious issues on the cursor's behavior recently.
As for the frequent disconnects issue - perhaps, this troubleshooting KB guide could provide some helpful information.
However, we apologize for any inconvenience. Please feel free to post another message if you have other questions in the future.
* Website time zone: America/New_York (UTC -5)