IIS Logs Error 80040e57 SQL_Server String_or_binary_data_would_be_truncated

[Charlie]

Does InfoPath cause access problems for IE browsers? Any work around
for an IIS log error,
|7|80040e57|[Microsoft][ODBC_SQL_Server_Driver][SQL_Server]String_or_binary_data_would_be_truncated.
500 0 0 508 16 HTTP/1.1

Some IE browser users get a 500 server error when viewing an intranet
web site that has ASP web pages and connection to a SQL Server
database. These people can view the ASP's through web browsers except
IE browsers. They can view PDF files on the web site with their IE web
browsers. Users who had the access problem, found that they could
correct the problem on their PC's by uninstalling Microsoft.NET

The entries in the IIS web access logs on the server for these failed
accesses have this data,

80 GET /default.asp
|7|80040e57|[Microsoft][ODBC_SQL_Server_Driver][SQL_Server]String_or_binary_data_would_be_truncated.
500 0 0 508 16 HTTP/1.1

This is another portion of the IIS web access logs for a failed access,

Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322;+InfoPath.1;+.NET+CLR+2.0.50727)


Other people can successfully view the same pages in IE browsers and
the entries for those successful accesses appear in the IIS logs with
different data from the failed access described above,

80 GET /default.asp - 200 0 0 422 140 HTTP/1.1
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.0.3705;+.NET+CLR+1.1.4322)


Please let me know if you have any ideas about it

Thanks,

Charlie

 

[gjr]

According to MS, the error is data truncation - mostly caused by a
field not being able to accept all the data. ie. if you are recording
the user agent info (as in the IIS logs above) in say a SQL table, the
field size needs increasing to accept the extra string length.

But ...

Our servers have started seeing this issue crop up more and more in the
past few weeks, nearly always when users have installed or updated
drivers for handheld devices such as blackberry.

When MS first shipped beta versions of .Net, they included Win CE MDAC
drivers by mistake. They corrected the problem a few weeks later.
This resurgence of the problem appears similar to that event - which
may imply that some handheld device providors are including bad
mdac/odbc drivers.

Attempting to shorten the data - ie Left (strVar, 100) has no effect.

Inspecting for Null values does appear to correct the problem.

Once our main asp guy is back on the job next week we will attempt to
isolate specific user ids with the problem and output all returned info
to a text file to see if there are any unexpected values being passed
back.

You may want to try the same thing.

Gary