Try this...
When IDS Backline support picked it up, they provided an updated
DATASERV.EXE dated January 19, 1999, which immediately resolved the
problem! The readme included was:
1. Pervasive.SQL I*Net Data Server version 1.1
released 7/14/99
2. Components included in this FTF:
dataserv.exe 1/19/99 97,280
3. Build Directory:
4. Test Environment:
This FTF was tested with the Pervasive.SQL v7.0 SP4 components.
Platforms tested were:
NT 4.0 Server with NT Service Pack 4 (IDS/P.SQL server)
Windows 98 IDS Win32 client requester
5. Test Suites Run:
Btrieve Regression
Communications Stress via SmartScout
6. Special Instructions to always go with this FTF:
a) Stop the IDS service via the IDS Tray Icon or the NT Services Admin
GUI.
b) Back up the original dataserv.exe
c) Copy the new dataserv.exe to the \winnt\system32 directory
d) Restart the IDS service.
7. Specific issues addressed in this release are:
Bug Number Bug Description
------ ------------------------------------------------------------
15507 I*Net Data Server returns error 3128 accessing database on NT 4.0
server with NT Service Pack 4 installed.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Pervasive.SQL Service & Support Classes ***
Chicago: August, 2004: See our web site for details!
Bill OConnor wrote:
Quote:
Using IDS to connect to server(ver 7). Simple insert-updates ok - only
using transactions. Multiple server accesses (bundled in transactions)
give error 3128. Sometimes ok but severity increases with number of
records accessed/inserted/updated.
Connection worked flawlessly for 2 years but problem has suddenly
appeared.
Any help appreciated |