Crystal Enterprise 9 and SQL on Windows 2003

[FordFairlane]

I have CE9 on a Windows 2000 server and the data was sitting on SQL2000 under Windows 2000. I have since moved the data to a Windows 2003 server still running SQL2000. I have changed the CE9 ODBC to point to the new server (only changing the server name) and using SQL Authentication and the ODBC tests fine - However when running the reports you are prompted for a Username and password repeatedly. The reports work fine Using Crystal Report writer on PC's with the same ODBC settings - any new reports published also have the same problem. Earlier in the week I managed to point CE9 to another server by changing the server name(But it was running NT4). Are there security features in Windows 2003 that I have to turn on in order for CE9 to work because Windows 2003 is so locked down by default. Doesn't explain why the ODBC test works from the CE9 server though?

 

[Danster]

Fordfairlane,
Try doing a Set Location and Verify Database (terminology from CR 8.5 but should be same in CR9?).
When you do a Set Location, you'll be asked to refresh the links to the tables in the database, then just do a Verify Database to be sure everything is up to date such a field definitions etc.

cheers

Danster

 

[FordFairlane]

Hi Danster,

No Go.

We have tried this - but the problem arises when we publish and try to run the report through Crystal Enterprise. The reports work on the PCs using the CR report Writer nromally as expected.

The problem to me seems to be the way the Crystal Enterprise Server is communicating with the Windows 2003 Database server.

Thanks
FordFairlane