Hi Martin, I don't have this utility odbconfig on my server. Is there anyway that I can output the list of all the .pm that the program is using when it runs? Peter Loo
-----Original Message----- From: Martin J. Evans [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 01, 2006 11:38 AM To: DBI-Users Subject: Re: Invalid authorization specification (SQL-28000) Loo, Peter # PHX wrote: > Hi Martin, > > The only way that I know that unixODBC is involved is by the > indication within the error message. As soon as I create a .odbc.ini > file in my home directory, the program spits out the following error: > > DBI connect('INSTANCE','userid',...) failed: [unixODBC]Invalid > authorization specification (SQL-28000)(DBD: db_login/SQLConnect > err=-1) at /usr/local/apps/common/devl/bin/GlobalRoutines.pm line 51 > > How can I check what ODBC it is using? > > Thanks. > > Peter Loo Sorry, I should have said. Can you run odbconfig -j and that will return version and locations of ini files. Martin > -----Original Message----- > From: Martin J. Evans [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 01, 2006 11:00 AM > To: DBI-Users > Subject: Re: Invalid authorization specification (SQL-28000) > > Loo, Peter # PHX wrote: > >>Hi Rob, >> >>It turns out that the IDs that would fail had an empty .odbc.ini file >>within their respective home directories. That in turn was overriding > > >>the file /usr/local/etc/odbc.ini. Once we removed the file from the >>home directories of each of the Unix IDs, the program runs and >>successfully completes. >> >>Thanks everyone. >> > > > Were you using unixODBC? > > If so, an empty .odbc.ini file in the user's home account should not > have made a difference since unixODBC scans for DSNs in the user's ini > then the system ini. If you were using unixODBC I'd be interested to > know which version you were using that exhibited this behavior so I > can investigate and have it fixed (if necessary). > > Martin > > >>-----Original Message----- >>From: Loo, Peter # PHX >>Sent: Monday, July 31, 2006 3:24 PM >>To: 'Rob Biedenharn' >>Cc: DBI-Users >>Subject: RE: Invalid authorization specification (SQL-28000) >> >>Hi Rob, >> >>Thanks for the input. What I did was I hard coded the database, >>userid and password in the connect string like so and still didn't >>work for one but did for the other. >> >>$dbh = DBI->connect("dbi:ODBC:testdb", "testid", "testpass", { >>RaiseError => 1 }); >> >> >> >>Peter Loo >> >>-----Original Message----- >>From: Rob Biedenharn [mailto:[EMAIL PROTECTED] >>Sent: Monday, July 31, 2006 2:56 PM >>To: Loo, Peter # PHX >>Cc: DBI-Users >>Subject: Re: Invalid authorization specification (SQL-28000) >> >>Depending on how the ODBC provider is configured, the 'testuser' may >>not be used (nor the supplied password) and the login credentials of >>the current user are used instead. >> >>On the user that works, try changing the 'testpassword' to something >>that is "wrong". If *that* user can still successfully run the >>program, then you need to look at the configuration of your ODBC > > driver manager. > >>(someone could probably give more accurate terminology to the > > "provider" > >>or "driver manager" that I'm slinging around, but I ran into this >>problem on Windows where there was a checkbox for whether to use "NT >>Authorization" or a username/password) >> >>-Rob >> >>Rob Biedenharn http://agileconsultingllc.com >>[EMAIL PROTECTED] >> >>On Jul 31, 2006, at 5:20 PM, Loo, Peter # PHX wrote: >> >> >> >>>Hi All, >>> >>>I don't know what is causing the following error, but I can >>>successfully complete the program as one user and not as another. >>>Logging into the same database with the same user id and password. >>>This is very strange. >>>The .profile on both ids are also the same. Would someone know what >>>might be causing this? Has someone experienced this before? >>> >>>DBI connect('testdb','testuser',...) failed: [unixODBC]Invalid >>>authorization specification (SQL-28000)(DBD: db_login/SQLConnect >>>err=-1) >>>at /usr/local/apps/common/override/bin/GlobalRoutines.pm line 51 >>> >>> >>>Peter Loo > > > > > > This E-mail message is for the sole use of the intended recipient(s) > and may contain confidential and privileged information. Any > unauthorized review, use, disclosure or distribution is prohibited. > If you are not the intended recipient, please contact the sender by > reply E-mail, and destroy all copies of the original message. > > > > This E-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply E-mail, and destroy all copies of the original message.
