Crystal Query - fails on scheduling

[paulkeys]

Hi all,

Using Crystal Report Server XI R2, Crystal XI Professional.

I've got a report that uses a sql command/query within the repository to access an oracle database via ODBC.

Using the CRXI client, i can open the report, click refresh and it prompts me to select the correct ODBC DSN, then enter the username and password for the relevant Oracle Db. All runs fine.

When scheduled, the report fails.

I've tried modifying the processing information (database tab) to use custom values, and i've tried every combination i can think of for database driver, server, database, username and password. Depending on which permutation is used i get various errors, either;

Table could not be found,
Unable to connect, incorrect logon parameters.

I was wondering whether anyone has successfully managed to schedule odbc based crystal query reports within CEXI.

Any help most appreciated.

 

[Turkbear]

Hi,
Yes..Assuming the same name for the DSN exists on the Server and the account under which the job server runs has access to it..

Why not use the Oracle Native driver instead?





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[groggle]

Turkbear is right. Crystal Reports Server XI, by default runs its services under the Local System Account. If you haven't set the services to run under an account that has the same network access rights as your user, you will see errors of this nature.

So, setup a specific CrystalServices account, grant it sufficient rights (It'll nee admin rights on the box that it is installed plus any network access rights it may need) and set all of the CRS services to run under this account.

Another useful test is to install Crystal Reports XI onto the server that CRS is also installed. Then you can log onto the CRS server as the same account that CRS is running under, open the report in CR XI and run it from there. You will often see more meaningful error messages via CR compared with CRS.

 

[paulkeys]

Guys,

Thanks for the replies - the CRXI client and CRS are installed on the same box, so share common login and network access rights, and share odbc dsns.

Any more suggestions greatly appreciated.

 

[groggle]

So you can confirm that the CRS services are not using the LocalSystem Account as their user login can you?

Open the Central COnfiguration Manager, Right click the Crystal Reports Job Server and look at the Properties, look at the Logon as user box.

 

[paulkeys]

groggle - thanks for the reply - the job server is in fact using the localsystem account, do you think this could be the cause of the problem?

 

[groggle]

Yes I do.

The LocalSystem account does not have the same rights as your user does when you log on to the server.

Read my first post again. Ie the bit that says:

So, setup a specific CrystalServices account, grant it sufficient rights (It'll need admin rights on the box that it is installed plus any network access rights it may need) and set all of the CRS services to run under this account.

Enlist the help of your Network Administrator if you have access to one.

This is precisely why when you log on and run the report it works and when you run it through CRS it fails.

 

[Turkbear]

Hi,
And, as I asked:
Why not use the Oracle Native driver instead?

That usually eliminates the need for any special account rights and is certainly more efficient and supports anything that Oracle can do..The ODBC drivers are not always fully compatible with all of Oracle's features.






To Paraphrase:"The Help you get is proportional to the Help you give.."