Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Incorrect logon parameters against Oracle with external authentication

Status
Not open for further replies.

robaker

Programmer
Oct 29, 2004
2
GB
Hi

I have converted some existing reports (Crystal 4.6.1) to use an Oracle database. I have an application that uses the Crystal control in VB6 to launch the report. I use the Connect property to set the logon information like so:

Report.Connect = "DSN = HOST; UID = USERNAME; PWD = PASSWORD"

I now want to use Oracle's external authentication stuff (which is like SQL Server's trusted authentication system) to log on.

The external authentication is functioning through tools such as Toad and through code that uses ADO and also seems to work in Crystal's Report Writer in that I can set the location of the tables without specifying the username or password, but the preview still gets data and Toad shows a connection under my NT account name.

The problem, as I'm sure you've guessed, is that I can't figure out the correct format of the Connect string that works in this scenario - I've tried several variations, but always get the error 'Unable to connect: invalid logon parameters: unable to preview report'.

Any ideas?

Rob
 
Hi,
When the VB app connects what account is it using?
If it does not use your NT account, then the OS authentication would, of course, fail.

What is your Oracle version? ( and its OS)

[profile]
 
Hi Turkbear

Thanks for the quick response. The VB app connects via ADO, but because the Oracle server is set to use external authentication I don't specify an account name or password in the connection string. Toad shows the connection is using the account whos name matches the logged-on user's NT account name, which is what I would expect.

The Crystal report does not use the VB app's connection. I set the Connect property of the Crystal OCX as shown in my original post and Crystal takes care of the connection. I expect it to do the same as the VB app and logon using the account who's name matches the logged-on user's NT account name, but instead I get the message 'Invalid logon parameters'.

The version of Oracle on the server is 8.1.7 (so I'm told).

Robaker
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top