The error normally shows if the user account that is trying to access the report does not have the correct permissions.
Moving the report to a location that is accessible to everyone normally solves the issue.
Please see this thread on the SAP SCN: https://archive.sap.com/discussions/thread/2138029
Server component:
The issue is the same as explained above but please note that the server component runs as under the local system account on the machine. This means that the local system account needs to have access to the Crystal or you can change the service to run under a different user account that has the correct permissions.
Edit: For server components and users this can be solved by making sure that the folder where the Crystal Reports are saved has set permissions for the user: "Everyone" to read. (Works on Cloudiax).
Comments
2 comments
you saved my day....
The report was working fine in mass delivery mode when i accessed from directly; not scheduled .
The issue was Boyum tried to use drive i mapped ; so after i gave full path , all good
safe many days... ty
Please sign in to leave a comment.