Skip to Content.
Sympa Menu

freetds - RE: [freetds] Receive "Login failed for user '(null)'" Error

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] Receive "Login failed for user '(null)'" Error
  • Date: Mon, 1 Dec 2003 15:46:59 -0500

> From: Mark Segall [mailto:Mark.Segall AT morganstanley.com]
> Sent: December 1, 2003 3:29 PM
>
> I did a print of $app_server. It actually has the value
> "dbi:Sybase:server=appserver", where appserver is the server entry in
> freetds.conf

I should have thought of that. :-/ OK.

> Could there possibly be a hidden null at the end which is causing the
> problem?

I don't see how that could happen.

> I did a tdsdumpconfig plus tdsdump and I can see that it is accessing
> the freetdsconf file and resolving appserver to the proper ip address
> and port

Right, good.

The only thing that occurs to me is that the username is empty or has a
backslash in it. The TDS 7.0 login packet is suppressed from the log, so
you can't see it without recompiling FreeTDS.

You could, however, export TDSVER=4.2. That would force a 4.2 login, which
is not suppressed (and in any case doesn't support domain logins). If that
fails, it will be for other reasons, which might help us triangulate things.


I'm sure you don't want to post your login data, and it's not necessary; the
packet is correctly formed and documented so that you can verify it
yourself. I think you'll be able to locate the username and password
readily enough.

Standing by.

--jkl
-----------------------------------------
The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the original
message. Please note that we do not accept account orders and/or instructions
by e-mail, and therefore will not be responsible for carrying out such orders
and/or instructions.






Archive powered by MHonArc 2.6.24.

Top of Page