Run Time Error 52 - Bad file name or number

From Support

If you have a question or seek clarification, please call Technical Support.

Problem:

The report server makes a successful download pass to downloads all selected report files and then the Runtime error 52 happens and the program exits.

Solution:

This problem can be resolved by changing the Polling Interval so it's between 1 and 59 minutes. If the value is set to 60 or above, the Report Server causes this error after a download pass.

This problem has also been fixed with WinSpool/400 Batch Report Server V2.0.16 and above. This problem has also been fixed with WinSpool/400 Email Report Server V3.0.11 and above.

or

We have seen this happen a couple of times where it appears that the customer is running the report server software all the time and they are also running a Backup software product such as Arcserv. Backup products will usually lock files during processing and this could be causing the error 52 problem which exits the program.

We have not been able to recreate the problem, but speculate that this is the issue.

A workaround would be to run the report server from a job scheduler program using the following command line:

WinSpool/400 Batch Report Server C:\WSPBCH32\WSPBCH32.EXE ONCE

WinSpool/400 Email Report Server C:\WSPESR32\WSPESR32.EXE ONCE

This will cause the program to make a single download pass and then exit after each pass. The job scheduler should be set not to process reports during the same period of time that the backup software is running.

Note: Internet Explorer 5.0 contains a job scheduler program that can be used with Windows 95/98/NT.