Invalid authorization specification (SQL-28000)

------_=_NextPart_001_01C6B4E7.23F552A3
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,
=20
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?
=20
DBI connect('testdb','testuser',...) failed: [unixODBC]Invalid
authorization specification (SQL-28000)(DBD: db_login/SQLConnect =
err=3D-1)
at /usr/local/apps/common/override/bin/GlobalRoutines.pm line 51
=20
=20
Peter Loo

------_=_NextPart_001_01C6B4E7.23F552A3--

RE: Invalid authorization specification (SQL-28000)

Permissions on something?

-----Original Message-----
From: Loo, Peter # PHX [mailto:Peter.Loo@source.wolterskluwer.com]=20
Sent: Monday, July 31, 2006 3:20 PM
To: DBI-Users
Subject: Invalid authorization specification (SQL-28000)

Hi All,
=20
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?
=20
DBI connect('testdb','testuser',...) failed: [unixODBC]Invalid
authorization specification (SQL-28000)(DBD: db_login/SQLConnect =
err=3D-1)
at /usr/local/apps/common/override/bin/GlobalRoutines.pm line 51
=20
=20
Peter Loo

This electronic message transmission is a PRIVATE communication which =
contains
information which may be confidential or privileged. The information is =
intended=20
to be for the use of the individual or entity named above. If you are =
not the=20
intended recipient, please be aware that any disclosure, copying, =
distribution=20
or use of the contents of this information is prohibited. Please notify =
the
sender of the delivery error by replying to this message, or notify us =
by
telephone (877-633-2436, ext. 0), and then delete it from your system.

RE: Invalid authorization specification (SQL-28000)

Do you mean in the database? If so, both Unix IDs are using the same
database ids and passwords.
=20
Peter Loo
Wolters Kluwer Health
(602) 381-9553

-----Original Message-----
From: Reidy, Ron [mailto:Ron.Reidy@arraybiopharma.com]=20
Sent: Monday, July 31, 2006 2:34 PM
To: Loo, Peter # PHX; DBI-Users
Subject: RE: Invalid authorization specification (SQL-28000)

Permissions on something?

-----Original Message-----
From: Loo, Peter # PHX [mailto:Peter.Loo@source.wolterskluwer.com]
Sent: Monday, July 31, 2006 3:20 PM
To: DBI-Users
Subject: Invalid authorization specification (SQL-28000)

Hi All,
=20
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?
=20
DBI connect('testdb','testuser',...) failed: [unixODBC]Invalid
authorization specification (SQL-28000)(DBD: db_login/SQLConnect =
err=3D-1)
at /usr/local/apps/common/override/bin/GlobalRoutines.pm line 51
=20
=20
Peter Loo

This electronic message transmission is a PRIVATE communication which
contains information which may be confidential or privileged. The
information is intended to be for the use of the individual or entity
named above. If you are not the intended recipient, please be aware that
any disclosure, copying, distribution or use of the contents of this
information is prohibited. Please notify the sender of the delivery
error by replying to this message, or notify us by telephone
(877-633-2436, ext. 0), and then delete it from your system.



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.

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 =3D DBI->connect("dbi:ODBC:testdb", "testid", "testpass", {
RaiseError =3D> 1 });=20


=20
Peter Loo

-----Original Message-----
From: Rob Biedenharn [mailto:Rob@AgileConsultingLLC.com]=20
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
Rob@AgileConsultingLLC.com

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=20
> successfully complete the program as one user and not as another. =20
> Logging into the same database with the same user id and password. =20
> This is very strange.
> The .profile on both ids are also the same. Would someone know what=20
> might be causing this? Has someone experienced this before?
>
> DBI connect('testdb','testuser',...) failed: [unixODBC]Invalid=20
> authorization specification (SQL-28000)(DBD: db_login/SQLConnect
> err=3D-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.

RE: Invalid authorization specification (SQL-28000)

No, permissions on some file at the OS level. You never make it into
the DB.

-----Original Message-----
From: Loo, Peter # PHX [mailto:Peter.Loo@source.wolterskluwer.com]=20
Sent: Monday, July 31, 2006 3:46 PM
To: Reidy, Ron; DBI-Users
Subject: RE: Invalid authorization specification (SQL-28000)


Do you mean in the database? If so, both Unix IDs are using the same
database ids and passwords.
=20
Peter Loo
Wolters Kluwer Health
(602) 381-9553

-----Original Message-----
From: Reidy, Ron [mailto:Ron.Reidy@arraybiopharma.com]=20
Sent: Monday, July 31, 2006 2:34 PM
To: Loo, Peter # PHX; DBI-Users
Subject: RE: Invalid authorization specification (SQL-28000)

Permissions on something?

-----Original Message-----
From: Loo, Peter # PHX [mailto:Peter.Loo@source.wolterskluwer.com]
Sent: Monday, July 31, 2006 3:20 PM
To: DBI-Users
Subject: Invalid authorization specification (SQL-28000)

Hi All,
=20
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?
=20
DBI connect('testdb','testuser',...) failed: [unixODBC]Invalid
authorization specification (SQL-28000)(DBD: db_login/SQLConnect =
err=3D-1)
at /usr/local/apps/common/override/bin/GlobalRoutines.pm line 51
=20
=20
Peter Loo

This electronic message transmission is a PRIVATE communication which
contains information which may be confidential or privileged. The
information is intended to be for the use of the individual or entity
named above. If you are not the intended recipient, please be aware that
any disclosure, copying, distribution or use of the contents of this
information is prohibited. Please notify the sender of the delivery
error by replying to this message, or notify us by telephone
(877-633-2436, ext. 0), and then delete it from your system.



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.

RE: Invalid authorization specification (SQL-28000)

=20
Hi Rob,

I had changed the password to an invalid password and now id that worked
does not. I am sure that there is something within the id that is
forcing the id to use authentication within the OS instead of what I am
passing for the database connection. I am going to check with admins.
=20
Peter Loo

-----Original Message-----
From: Rob Biedenharn [mailto:Rob@AgileConsultingLLC.com]=20
Sent: Monday, July 31, 2006 4:13 PM
To: Loo, Peter # PHX
Cc: DBI-Users
Subject: Re: Invalid authorization specification (SQL-28000)

Peter,
Try changing that to:

$dbh =3D DBI->connect("dbi:ODBC:testdb", "testid", "wildlywrong", {
RaiseError =3D> 1 });

and see if the one user *still* works. That will tell you if the OS
credentials are overriding the ones that you supply.

-Rob

Rob Biedenharn http://agileconsultingllc.com
Rob@AgileConsultingLLC.com

On Jul 31, 2006, at 6:24 PM, Loo, Peter # PHX wrote:

> Hi Rob,
>
> Thanks for the input. What I did was I hard coded the database,=20
> userid and password in the connect string like so and still didn't=20
> work for one but did for the other.
>
> $dbh =3D DBI->connect("dbi:ODBC:testdb", "testid", "testpass", {=20
> RaiseError =3D> 1 });
>
>
> Peter Loo
>
> -----Original Message-----
> From: Rob Biedenharn [mailto:Rob@AgileConsultingLLC.com]
> 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' =20
> may not
> be used (nor the supplied password) and the login credentials of the=20
> current user are used instead.
>
> On the user that works, try changing the 'testpassword' to something=20
> that is "wrong". If *that* user can still successfully run the=20
> program, then you need to look at the configuration of your ODBC=20
> driver manager.
> (someone could probably give more accurate terminology to the=20
> "provider"
> or "driver manager" that I'm slinging around, but I ran into this=20
> problem on Windows where there was a checkbox for whether to use "NT=20
> Authorization" or a username/password)
>
> -Rob
>
> Rob Biedenharn http://agileconsultingllc.com
> Rob@AgileConsultingLLC.com
>
> 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=20
>> 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=20
>> might be causing this? Has someone experienced this before?
>>
>> DBI connect('testdb','testuser',...) failed: [unixODBC]Invalid=20
>> authorization specification (SQL-28000)(DBD: db_login/SQLConnect
>> err=3D-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.

RE: Invalid authorization specification (SQL-28000)

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.
=20
Peter Loo

-----Original Message-----
From: Loo, Peter # PHX=20
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 =3D DBI->connect("dbi:ODBC:testdb", "testid", "testpass", {
RaiseError =3D> 1 });=20


=20
Peter Loo

-----Original Message-----
From: Rob Biedenharn [mailto:Rob@AgileConsultingLLC.com]
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
Rob@AgileConsultingLLC.com

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=20
> successfully complete the program as one user and not as another.
> Logging into the same database with the same user id and password. =20
> This is very strange.
> The .profile on both ids are also the same. Would someone know what=20
> might be causing this? Has someone experienced this before?
>
> DBI connect('testdb','testuser',...) failed: [unixODBC]Invalid=20
> authorization specification (SQL-28000)(DBD: db_login/SQLConnect
> err=3D-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.

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:Rob@AgileConsultingLLC.com]
> 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
> Rob@AgileConsultingLLC.com
>
> 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

RE: Invalid authorization specification (SQL-28000)

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=3D-1)
at /usr/local/apps/common/devl/bin/GlobalRoutines.pm line 51=20

How can I check what ODBC it is using?

Thanks.
=20
Peter Loo

-----Original Message-----
From: Martin J. Evans [mailto:martin.evans@easysoft.com]=20
Sent: Tuesday, August 01, 2006 11:00 AM
To: DBI-Users
Subject: Re: Invalid authorization specification (SQL-28000)

Loo, Peter # PHX wrote:
> Hi Rob,
>=20
> It turns out that the IDs that would fail had an empty .odbc.ini file=20
> within their respective home directories. That in turn was overriding

> the file /usr/local/etc/odbc.ini. Once we removed the file from the=20
> home directories of each of the Unix IDs, the program runs and=20
> successfully completes.
>=20
> Thanks everyone.
> =20

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

>=20
> -----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)
>=20
> Hi Rob,
>=20
> Thanks for the input. What I did was I hard coded the database,=20
> userid and password in the connect string like so and still didn't=20
> work for one but did for the other.
>=20
> $dbh =3D DBI->connect("dbi:ODBC:testdb", "testid", "testpass", {=20
> RaiseError =3D> 1 });
>=20
>=20
> =20
> Peter Loo
>=20
> -----Original Message-----
> From: Rob Biedenharn [mailto:Rob@AgileConsultingLLC.com]
> Sent: Monday, July 31, 2006 2:56 PM
> To: Loo, Peter # PHX
> Cc: DBI-Users
> Subject: Re: Invalid authorization specification (SQL-28000)
>=20
> Depending on how the ODBC provider is configured, the 'testuser' may=20
> not be used (nor the supplied password) and the login credentials of=20
> the current user are used instead.
>=20
> On the user that works, try changing the 'testpassword' to something=20
> that is "wrong". If *that* user can still successfully run the=20
> 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=20
> problem on Windows where there was a checkbox for whether to use "NT=20
> Authorization" or a username/password)
>=20
> -Rob
>=20
> Rob Biedenharn http://agileconsultingllc.com
> Rob@AgileConsultingLLC.com
>=20
> On Jul 31, 2006, at 5:20 PM, Loo, Peter # PHX wrote:
>=20
>=20
>>Hi All,
>>
>>I don't know what is causing the following error, but I can=20
>>successfully complete the program as one user and not as another.
>>Logging into the same database with the same user id and password. =20
>>This is very strange.
>>The .profile on both ids are also the same. Would someone know what=20
>>might be causing this? Has someone experienced this before?
>>
>>DBI connect('testdb','testuser',...) failed: [unixODBC]Invalid=20
>>authorization specification (SQL-28000)(DBD: db_login/SQLConnect
>>err=3D-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.

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:martin.evans@easysoft.com]
> 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:Rob@AgileConsultingLLC.com]
>>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
>>Rob@AgileConsultingLLC.com
>>
>>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.
>
>
>
>

RE: Invalid authorization specification (SQL-28000)

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?
=20
Peter Loo

-----Original Message-----
From: Martin J. Evans [mailto:martin.evans@easysoft.com]=20
Sent: Tuesday, August 01, 2006 11:38 AM
To: DBI-Users
Subject: Re: Invalid authorization specification (SQL-28000)

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



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.