Unable to connect: incorrect log on parameters

[waldopepper]

Hope someone can help - I've got an error that's driving me crazy!

I have a report that connects to the ODBC (SQL 2000) data source fine on the server when I locally create a Crystal Report. I get databack fine from here but when I publish it to the Crystal Enterprise (on the same machine), change the password to the same as I've just used locally to get data, everytime the report runs it fails with this message:

Unable to connect: incorrect log on parameters. File E:\Crystal\CrystalEnterprise\ReportJobServer\~tmp9a846d6c1644e0.rpt.

I've unticked the 'prompt user for login' tickbox and it's definitely definitely the correct password (I've pasted the same password to the local report when prompted and that works).

Is there a CE bug that could cause this or am I missing something very silly indeed?

(Crystal Reports & Enterprise v10)

 

[waldopepper]

Ah HA I've got it!

This is the first SQL server I've used at work where the SQL team have created me a specific SQL account for, rather than using the full 'sa' account. Once they granted my account full 'sa' privelidges it worked fine.

They want to now revoke this though

Does anyone know of any specific SQL permissions that the connecting SQL account needs so I get them to grant these - there's no way they will give us full 'sa' access unfortunately.

 

[waldopepper]

OK I'll just keep on talking to myself!

Chatting to our DBAs we've tried a couple of options and it turns out that to get Crystal Enterprise working with SQL servers you just need to enable the permission "Process Admin" on the SQL account - this has sorted it out for me so maybe this might useful for anyone else who gets this error.

 

[synapsevampire]

Whatever account is used on CE must have the proper GRABTS applied to use whatever objects are involved, and they should KNOW this.

As long as the ODBC connection is the same, and the user and password are the same, then everything should be fine.

I suggest that you install CR on the CE server as well to allow you to test reports there as CR tends to give more exhaustive error messages, though that one seems clear, and I guess that they're using pass through authentication, which would mean that the account that the CE servers run under need permission to the objects, or switch to an account set up on the SQL Server directly.

Your dba will know what this means.

-k

 

[synapsevampire]

Too early to type:

Whatever account is used on CE must have the proper GRABTS applied...

 

[waldopepper]

Huh? Do you mean GRANTS?

 

[synapsevampire]

Yeah, sorry.

Coffee is kicking in now...

-k

 

[waldopepper]

Just thought I would add some useful info in case anyone else is having this problem.

This also happened to a Oracle account we are now using.
For CE to run reports from an Oracle data source, the account being used should have permissions "Select Catalog Role" set otherwise a similar error occurs.

 

[Turkbear]

Hi,
We have many, many published reports running against Oracle databases and the login accounts that we use do not have that role assigned ...

Not sure what problem you had that would require that role to be granted..
We reserve that for our warehouse administrators and DBAs...










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

 

[waldopepper]

mmm no idea - I don't know anything about Oracle. I was on the phone with someone standing in for the DBA - the account didn't work as it was. He granted full admin access, the report worked fine, then he reverted it back to what it was but granted this "Select Catalogue Role" and it worked fine so we assumed this was the reason why!

 

[Turkbear]

Hi,
OK..

I hope the 'regular' DBA returned and corrected the actual problem...The basic rule for any Database access is 'grant the lowest level of permissions possible'..





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