Access violation at address 005297BC

[stonebas]

After every scheduled task to run RPC I get the following window: Remote Profile Cleaner: "Access violation at address 005297BC in module 'proclean3.exe'. Read of address FFFFFFFF". The message just remains on screen until I click the OK button. I have about 25 individual tasks which run throughout the day and I have to clear this error message each time the program runs.

Although this doesn't happen when the program is run manually (ie not as a scheduled task) the RPC windows must still be closed manually.

Stewart Stonebank

[msis]

This issue has not been reported before and therefore we need to investigate. With this we need your help, can you provide us with the following information:

• what version and build are you running?
• what os are you running on the computer running Remote Profile Cleaner.
• does this only happen on one computer or have you noticed the same problem on other computers?
• Can you run Remote Profile Cleaner once as scheduled job with the additional parameters "/debug" and "/noclose" and send us a copy of the log-file. Please feel free to mask computernames and usernames.
• it will also help us if you can show us on what point during executing the error occurs.

note: the "/debug" parameter add extra information to the log-file we might need to solve this problem. The "/noclose" parameter prevents Remote Profile Cleaner from automatically closing after a scheduled job.

You can use the email address found in the contact information you received together with you activation key to send the log-file to us.

[stonebas]

"Help About" shows version: 0.00
OS is Win 2003 server
I have copied the entire RPC folder from the server onto a workstation and I get exactly the same problem when I run RPC from the workstation
I am sending the log file as requested
The problem occurs right at the end of the job. The task starts and runs fine then, right at the very end when you would expect the program to close, the Access Violation error message appears. Click OK and the message disappears but the RPC console remains open until it is manually closed down.

Thanks for your help.

Stewart

[msis]

Thanks for the information, we've also recieved your log-file and will contact you by email soon.

[msis]

The "access violation" is traced back by our programmers to the "l:" parameter in combination with only a log file name (no drive, path and extension added to the file name) specified. A quick workaround for now is to include both the full path and the extension to the log file name in your command-line parameters. For example if your parameter looks like "l:myLogFile" change the parameter into "l:C:\program files\remote profile cleaner 3.0\user\log files\mylogfile.txt".

To adjust your command-line parameter simply open the *.bat file in a text editor and correct the l: parameter syntax.

We will fix this error as soon as possible in release 3.0b. Depending on the time to fix this issue and the forthcoming release date of 3.0b there might also be an update for release 3.0a.

[msis]

This bug has been fixed in both release 3.0a build 470 and 3.0b build 485. Both versions are available for download through our website.