I had a similar problems a few days ago, figured that one out but now I am getting a new problem... Their website and documentation don't actually contain usefull information to fix it so I must post here once again.
When running reports , I get the following error :
Status: Failed
Printer: The instance is not printed.
External Destination: Mail the instance to "Address" with a subject of "Subject".
Data Refresh Settings: Use the server defaults.
Start Time: 08/12/2005 12:24:51 PM
End Time: 08/12/2005 12:24:54 PM
Server Used: mnap141.reportjobserver
Error Message: Unable to connect: incorrect log on parameters. File D:\Program Files\Enterprise 10\Data\procSched\mnap141.reportjobserver\~tmpfac41a77453d50.rpt.
Now what I don't understand is that I tested with 3 reports, 2 on the same ODBC using different views and one on a separate ODBC. One view works while the other does not and the second ODBC results in the same error message.
Bearing in mind I don't have access to this server, is there anything I can do to fix this problem? I am using the default database logon information so I know that is correct.
One thing I wonder that likely isn't setup. Do I on the server need to setup all the same DSN's as I have on my workstation? On the dev server Crystal Enterprise and Report are both installed so the DSN's are there but on the new server only Enterprise is installed and I highly doubt that the server guys set that up.
Any ideas....?
Thanks,
ITCPhil
When running reports , I get the following error :
Status: Failed
Printer: The instance is not printed.
External Destination: Mail the instance to "Address" with a subject of "Subject".
Data Refresh Settings: Use the server defaults.
Start Time: 08/12/2005 12:24:51 PM
End Time: 08/12/2005 12:24:54 PM
Server Used: mnap141.reportjobserver
Error Message: Unable to connect: incorrect log on parameters. File D:\Program Files\Enterprise 10\Data\procSched\mnap141.reportjobserver\~tmpfac41a77453d50.rpt.
Now what I don't understand is that I tested with 3 reports, 2 on the same ODBC using different views and one on a separate ODBC. One view works while the other does not and the second ODBC results in the same error message.
Bearing in mind I don't have access to this server, is there anything I can do to fix this problem? I am using the default database logon information so I know that is correct.
One thing I wonder that likely isn't setup. Do I on the server need to setup all the same DSN's as I have on my workstation? On the dev server Crystal Enterprise and Report are both installed so the DSN's are there but on the new server only Enterprise is installed and I highly doubt that the server guys set that up.
Any ideas....?
Thanks,
ITCPhil