WINDOWS 2000

[Allen_Hochstetler_(Guest)]

Every time I try to run a report from a particular library rp5, permiyts.rp5 in this case, I receive the following error message:______RRWRUN.EXE has generated errors and Windows will be closed_____The problem also is that these reports were just fine one day and the next day garbage. At this time my other reports in other rp5 libraries work just fine. All users have full control of this particular directory on the NT 4 sp6a server. Also, these reports run fine when accessed using a NT 4 sp6a workstation.____I am not using version 9.0 as yet_still 8.1 with the service pack installed on the NT 4 server.____Can you give me a clue where to look or what might be causing this glitch.______

[Thomas_Freitas_(Guest)]

I am having the exact same problem using Version 9.0 I have a client that was using the program with Windows 98 in a .RP5 report file. Everything worked great until they upgraded to Windows 2000. Now they get the same error that you are mentioning. Let^s hope that someone can give us the answer to this one as it is extremely important.____

[taylorjm]

Do you have Service Patch 1 installed with WIN2K?__Jim Taylor__

[freitas]

One of my clients called and told me that as the system admin in Windows 2000, he could run the reports. But as soon as he made someone else the systems admin, he could not run the reports and they could. He stated that everyone has all rights, delete and so on, so it must be something that the system admin has that no one else does. ____Anyone that is not the systems admin gets the same error message that you have stated. I am waiting like you to find out what we can do to fix this.____Thanks... Tom Freitas

[kfleming]

On my test machine I can run reports in 2000 as admin and and other users who have full privileges to the R&R directory.____Kathleen__R&R Support

[freitas]

Sorry, but if you were my client I wouldn^t have any problems, but your not! And they are having problems. They have my Visual dBase program on their server along with all the Version 9 R&R runtime files, including the .DLL^s____The reports run fine if the admin runs the reports. Nobody else can run a report the receive the error the RRWRUN.EXE has created an error in Windows. If the admin changes someone else to the admin that could not run a report, then they are able to and the previous admin can not.____All users have all rights to every directory on their system. I believe that this is the same problem that the person who originated this problem also has.______Thanks... Tom Freitas

[kfleming]

Are the clients running reports from their local workstation or are they sitting at the server machine and logging in locally?____Can they run the reports using the RRW.EXE Report Designer?____Kathleen__R&R Support

[freitas]

The network admin ran the report, which is on the server, using his PC. It worked fine! Then he made someone else the admin and tried to run the report from the same PC again. He received the Windows Error Screen.

[Allen_Hochstetler_(Guest)]

I have reviewed this problem in our test environment and it appears that there is indeed a problem for a regular user account in Windows2000 to successfully run R&R.____If you are a Power User or Admin, you can run successfully.____There are some notes in the Win2000 help stuff regarding legacy applications vs. Windows 2000 compliant apps.____We will need to see how much effort it will take to become Win2000 compliant to know how soon this might be addressed.____Kathleen__R&R Support

[kfleming]

As a note, I found a rather odd quirk with running reports from and rp5 library using a HP LJ 8100DN (PCL 6) printer installed on an NT 4 sp6a server, R&R version 8.1 with the service pack installed.____The workstation is a WIN 2K with the 8100DN combo driver for NT 4 and Windows 2000.____When I set the 8100DN printer for one of 8 reports in the library in Report designer and save the report back to the library and then try to run the report from an icon--RRWRUN.exe error occurs. If I run one of the other reports within this library that is not set to use the 8100DN--the report runs with out a problem. Now the quirk, If I now select the problem report that is using the 8100DN--the report runs and prints.____If I run the problem report in report designer and use the 8100DN printer, no proiblem.____If I set the default printer for all of the reports in this library to a HP LJ 4+, 5, 4050, etc and then select the 8100DN printer instead, the report will run every time.____For all that are having headaches with printing from WIN 2K__Thanks__Allen____