Re: freetds.log message

On Wed, 17 Oct 2012 19:25:53 -0400
Evan Panagiotopoulos <[email protected]> wrote:

> I keep working on debugging a connection to a ms sql server and I get
> the following message in the log file:
> 
> net.c:542:Received packet
> 0000 aa 68 00 18 48 00 00 01-0e 21 00 4c 00 6f 00 67
> |.h..H... .!.L.o.g| 0010 00 69 00 6e 00 20 00 66-00 61 00 69 00 6c 00
> |65 |.i.n. .f .a.i.l.e|
....
> The above is teling me that the user id failed to connect.
> I am trying to understand what the following means, though.

Not to be pedantic, but I think it's helpful to distinguish: the above
is telling you that the client connected to the server.  The login
packet was sent to the server, and the server rejected it.
You're connecting; your network settings are OK.  You're just not
logging in.  

> token.c:314:looking for login token, got  aa(ERROR)
> token.c:105:tds_process_default_tokens() marker is aa(ERROR)

Instead of a login acknowledgement, 
the server returned an ERROR packet, type 0xAA. 

> token.c:2439:tds_process_msg() reading message from server
> read.c:179:tds_get_string: reading 66 from wire to give 33 to client.
> read.c:179:tds_get_string: reading 26 from wire to give 13 to client.
> token.c:2501:tds_process_msg() calling client msg handler

The text of the message in the error packet was reduced by 50% because
it arrived as UCS-2 and was converted to a single-byte encoding,
perhaps UTF8 or ISO 8859-1.  The message was forwarded to the client
handler, which eventually gave it to PHP, where I believe you saw it.  

> Any suggestions?

What kind of authentication is your server set up to accept?  If it
doesn't accept a plaintext login, you'll have to link FreeTDS to
Kerberos.  I would look in that vicinity. 

--jkl