Chris,
Here are a few initial suggestions of where I think the problem may be occurring. Try these ideas out and let me know if they help or not:
1. File Path Problem
It could be that the path to the RPT file is different on the client workstation than it was on the system where you originally built the solution file. Try editing the RRD file on the client workstation and browsing for the RPT file again on the File Name tab to see if the path changes. Save the RRD file and try running it again to see if it works now.
I've also had some issues with using UNC paths in the file name in the RRD. If your file path looks like this:
[code:1]\\SERVERNAME\Reports\Report1.rpt[/code:1]
Try to instead map a network drive to the share containing your reports and point the RRD to the mapped drive path to the report.
The other thing I noticed based on your error message is that the computer doesn't appear to be a member of your domain. So when you access the network share you are probably prompted for a user name and password before you can see the files? Make sure you have accessed the network share and provided these credentials before attempting to run the RRD if this is the case.
2. File Permissions Problem
The problem could also be that the client has permissions to see the RPT file listed in the folder, but does not have enough permissions to open the file. The easiest way to rule this out is to log on as an administrator on the client workstation (and as administrator when you are prompted for a user name and password when connecting to the share) and see if you still get the same error.
3. Local Permissions Problem
The last possibility I could think of is that the user may be lacking the permissions on the local computer to be able to properly write files to the temp directory. As with the previous troubleshooting exercise, the easiest way to determine this is to log on as the local administrator user and see if you get the same errors.
Let me know if you need any additional clarification on any of this and if this does or doesn't solve your issue. We'll figure it out one way or another.
Thanks,
Adam
Post edited by: aellis, at: 2007/09/20 10:32
Post edited by: aellis, at: 2007/09/20 10:32