Blank DB Logon?? 1

[tctchad]

Greetings all!
I was wondering if anyone could give me any insight into a database logon issue from crystal enterprise. I'm running CE 8. The data source is a Progress database connected through ODBC. The reports are set to run under a blank userid/password through the ODBC connection and work fine in Crystal Reports (8.5). The problem is once they are published, the db connection can't be made. Is it possible to use a blank userid/password through CE? The default database logon information has been left blank in the management console, as well as defined as blank during publishing. Can anyone help me?? Thanks in advance

 

[obiwan]

does the CE server have the Progress ODBC driver available? you need to make sure that the Page Server and Job Server have that ODBC driver available to process the report. what is the error that you get?

 

[tctchad]

obiwan,
thanks for the response! The server does have the driver installed properly. There are no error messages, what happens is that the parameter entry page is displayed asking for a database logon and password. If the fields are left blank and the information is sent, the parameter page comes back and still requires the logon info. This is the sticking point to accessing the report. Any thoughts?

 

[IdRatherBeGolfing]

I don't know if you have tried this or not, but I have found it useful to have a copy of the Report Designer installed on the server itself. Try running the report from the designer on the server machine and see what happens.

Another thing that you may want to consider (I myself have no experience with Progress) is to see if it by chance is passing NT authentication. In which case, it may matter which account is logged into the server machine - which could explain why it works from the designer but not on the server.

Hope that helps

 

[tctchad]

Thanks for the response. I haven't tried to install the Report Designer on the server yet. I'll test that out and let you know what happens.....

 

[AEldridge]

Also, make sure the ODBC DSN is defined as a SYSTEM DSN, not as a USER DSN.

Another thing to try would be to run the page server (for on-demand reports) and the job server (for scheduled reports) services under a named user ID instead of under the local system account.

Cheers, Alan Eldridge
Melbourne, Australia

 

[tctchad]

Well, that did it! I changed the page server and job server properties to run under a user account in the domain and now my reports are viewable. Thanks everybody!!

 

[AEldridge]

I've put this up as a FAQ - the first for this forum, in fact - as this is likely to be asked often.

Glad your proble is resolved.

Cheers, Alan Eldridge
Melbourne, Australia

 

[ianbla]

Thnaks for this, it also solved my problem with an access database, I kept getting prompted for the username/password even though the DB didn't need one.

I changed the Page Server & Job Server to a Domain account and hey presto all works.

Thanks again
Ian.

 

[ianbla]

Forgot to mention, this is with version 8.5 over a year after and they still haven't fixed this 'bug'