Skip to Content.
Sympa Menu

freetds - Re: [freetds] Please Help...Log files Included-Connection kickedoffofMSSQL db

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <james.k.lowden AT alliancebernstein.com>
  • To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] Please Help...Log files Included-Connection kickedoffofMSSQL db
  • Date: Wed, 12 Apr 2006 09:30:19 -0400

> On 4/11/06, blackwater dev <blackwaterdev AT gmail.com> wrote:
> >
> > Ok, I set the config dump and saw where it was getting the config.
> > I then set up a section in the config:
> >
> > [mystuff]
> > host = xxx.xx.xxx.xx
> > port = 1433
> > tds version = 8.0
> >
> > and in the php mssql_connect function pass in
> > ("mystuff",$username,$password);
> >
> > The problem is, if I use version 8.0, I get this for just about
> > every column if not every column:
> >
> > Warning: mssql_query(): WARNING! Some character(s) could not be
> > converted into client's character set. Unconverted bytes were
> > changed to question marks ('?'). (severity 16) in
> > /usr/local/apache2/htdocs/nh/includes/lib/ms_db.class.php on line
> > 182 PHP Warning: mssql_query(): WARNING! Some character(s) could
> > not be converted into client's character set. Unconverted bytes
> > were changed to question marks ('?'). (severity 16) in
> > /usr/local/apache2/htdocs/nh/includes/lib/ms_db.class.php on line
> > 182
>
> From: blackwater dev
> Sent: Tuesday, April 11, 2006 2:18 PM
>
> I just checked and my char set is:LANG="en_US.UTF-8"
> SUPPORTED="en_US.UTF-8:en_US:en"
>
> So seems like UTF-8 should have worked unless I messed up the entry
> in conf.

Could I see the first 10 or so lines from your TDSDUMP log? I'd like to
see what character set is being used for your TDS 8.0 connection. If
you could include in it a short query that elicits the error, that might
also be helpful.

There is almost no such thing, for our purposes here, as a character
that cannot be encoded as UTF-8. It *is* possible to have misencoded
data on the server (which would stymie the iconv library with invalid
input), but that's a rare problem that takes some doing to create. More
likely is some kind of client misconfiguration.

You're getting there, even if by inches. :-)

--jkl

-----------------------------------------
The information contained in this transmission may be privileged and
confidential 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. If you, as the intended
recipient
of this message, the purpose of which is to inform and update our clients,
prospects
and consultants of developments relating to our services and products, would
not
like to receive further e-mail correspondence from the sender, please "reply"
to the
sender indicating your wishes. In the U.S.: 1345 Avenue of the Americas, New
York,
NY 10105.




Archive powered by MHonArc 2.6.24.

Top of Page