TDS, RPC malformed packets with SQL Server 2005



Hello,

we have a standard apappliaction which uses a sql server.
Till last week we use a sql server 2000 and no problems.

Now we use SQL Server 2005 and now we got 40% malformed Packets in
application traffic to SQL Server.

Wireshark means TDS, RPC malformed packets.
If the session crash the application crashs also.
I have tested with two different Clients and two Hardware different
SQL Servers.
Both SQL Server has the same problem.

We use:
SQL Server: Win 2003 R2 engl., SQL Server 2005 SP2 engl.
Client: Win2000/ Win2003 engl.
NW Lib: Native Client with TCP/IP (no Shared Memory, no NWlink)

Does someone has an idea what i can test or what i can do?


greetings
Henrik

.



Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Best way to populate webpages from multiple tables
    ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Best way to populate webpages from multiple tables
    ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... an Access database in former times this was a lot of work which took me ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... client for programming easy, fast and good applications. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL and Bandwidth use
    ... In addition to the other responses, take a look at the memory and CPU usage ... in Great Plains Client software. ... > near 100Mb/sec bandwidth). ... Client PC is on same segment as SQL server (not passing through ...
    (microsoft.public.sqlserver.server)

Loading