Can anyone suggest what might be causing the error "Invalid LNA response packet", which is apparently coming from the PSQL11 client software and complaining about the data coming back from the P11 server ?
I've seen this error a few times on various systems, going back as far as P9.5, and it has usually required a restart of the Windows services to clear (all our Pervasive stuff is on Windows). But on one -- and only one -- of our customers' sites they are getting this error sporadically but quite frequently, and although it sometimes seems to clear itself for a while, it doesn't stay cleared.
It's difficult to get details of this particular customer's software/hardware environment, but what I know today is:
All the Pervasive software is version 11 (don't know what SP level), running on Windows Server 2003, 32-bit.
The "client" software is actually a web server running is the MS IIS container (I think IIS6). That software is written in C#, ASP.NET framework 2.0, and uses a connection string like the following:
connectionString="Server=XXXX; Database=YYYY;" />
Normally the application works correctly, but occasionally the DB connection will throw an error with the above text. If it helps, it usually (perhaps always) happens while we are trying to close the connection. A partial stack trace is:
at Pervasive.Data.SqlClient.Lna.ae.a(Stream )
at Pervasive.Data.SqlClient.Lna.am.a(v , u )
at Pervasive.Data.SqlClient.Lna.am.ci(v , u )
at Pervasive.Data.SqlClient.Lna.w.a(Int16 )
at: ... our custom code below here...
The same software is running on other customers' sites (with similar sized DBs and workloads) without these problems. I don't know for sure if any of those other sites are running similar hardware/software combinations to the problem site.
Can anyone suggest a cause, a fix, or what extra data I should try to collect ?