R & R v. 9.0.009 Lockups
-
- Posts: 6
- Joined: Tue Oct 10, 2017 12:44 pm
R & R v. 9.0.009 Lockups
Hi,____Hoping someone might be able to help me with a issue that has just popped up two days ago. ____We have R & R v. 9.0.009 installed on a server that until Tuesday operated just fine. As of Tuesday morning we have found that when the rrw.exe application is run from a workstation it completely locks the PC up to the point that it requires a complete shutdown. Oddly however, running the rrw.exe application from the server works without incident.____In addition, we have found that running any of the report shortcuts on a workstation created by the shortcut maker run fine.____I^m wondering if a Windows update may have created a conflict of some sort with rrw.exe running on the network?____Would appreciate any advice or help.____Thanks in advance,____Rick Tibbitts__
=> RE: R & R v. 9.0.009 Lockups
Does the problem occur when you are previewing a report?____Kathleen__R&R Support
-
- Posts: 6
- Joined: Tue Oct 10, 2017 12:44 pm
==> RE: R & R v. 9.0.009 Lockups
If I try and actually load R & R using rrw.exe I can^t get far enough to try and preview a report. It just locks up the PC tight as a drum.____However as I noted when running any report shortcuts created using shortcut maker runs fine and we can preview and print reports normally.____Thanks for your help, Kathleen!____>Does the problem occur when you are previewing a report? __>__>Kathleen __>R&R Support __
===> RE: R & R v. 9.0.009 Lockups
Have you tried a re-install?____Kathleen__R&R Support
-
- Posts: 6
- Joined: Tue Oct 10, 2017 12:44 pm
====> RE: R & R v. 9.0.009 Lockups
We haven^t done that yet and while I know in one sense it makes sense and is the right next step, the fact that it works on the server but not over the network made me think that there was something else at play. Is there any one or several files that are a part of the install that facilitate network usage?
=====> RE: R & R v. 9.0.009 Lockups
When RRW.EXE is launched, users need to be able to write to the RRW.LIC license file. If the workstation can successfully run a report when using RRWRUN.EXE but has the lockup with RRW.EXE then rights to the LIC file may be the source of the problem.____Kathleen__R&R Support
-
- Posts: 6
- Joined: Tue Oct 10, 2017 12:44 pm
======> RE: R & R v. 9.0.009 Lockups
Hi,____First, thank you for being so responsive and helpful Kathleen. I really do appreciate it :-)____I^ve looked at the file permissions and see that there is no attributes that would prevent it from being written to and I see the file date stamp is as recent as yesterday. I^ve asked our Network Services Manager if there is possibly some other way users are being denied access to writing to this file but I don^t think anything else is preventing access to the file from workstations.____I^ve asked our IT department to reinstall the application at the server however I do have two other questions...____Whenever we close R & R (whether it was opened from the network drive or if it is opened from a locally installed folder) we receive the following message:____"rrw.exe has generated errors and will be closed by Windows. You will need to restart the program.____An error log is being created"____I^ve searched the network folder where R & R is installed as well as my local drive but don^t find an error log I can review. Do you have any suggestions?____Finally - whenever we run the R & R Shortcut maker, the initial shortcut it creates has to be modifed removing some quotation marks, reversing slashes from back slashes to forward slashes. I hope what I^ve just described makes sense and is familiar to you. If so, is there a patch to take care of this problem? If this issue is not familiar to you I^ll follow up with step by step details.____Thanks again Kathleen!____Rick Tibbitts
=======> RE: R & R v. 9.0.009 Lockups
The problem with the shortcut maker was a bug that was addressed in a later release. For V, the workaround is to manually edit the command line that is generated by the shortcut maker.____The crash on exit is generally due to a problem in releasing the PDF printer driver. To cure this, you need to find and rename all instances of the file CDINTF.DLL. It may be in the RRW directory or in your local windowssystem32 (For XP) You can rename the file CDINTF.OLD. If this does not help, do another search to be sure that you have found all instances of this file.____Kathleen__R&R Support