BDE Error byexecution of Filters/Group

[paulhendricks]

Not too long ago we migrated our existing goldmine 4/sql database from an NT based server over to a new MS Server 2003 enterprise with MSSQL 6.5.

While executing a filter search we get the following Error messages:
-----------------------
General SQL error.
Native SQL error: 0

Context: skip 1
MSSQL: gmcompanydb: dbo.CONTACT1

1: Server message:

BDE Error Cat:Code: [51:3]
BDE: 500 [9/6/1998] Goldmine: 4.00.9922

User: PAUL
Window:
Template: PendingListing
Details:
---------------------------------------
General SQL error.
Native SQL error: 0

Context: skip 1
MSSQL: gmcompanydb: dbo.CONTACT1

1: Server message:

BDE Error Cat:Code: [51:3]
BDE: 500 [9/6/1998] Goldmine: 4.00.9922

User: PAUL
Window:
Template: CBError
Details:
-------------------------------------
After receiving the above 2 listed Error Messages, Goldmine crashes and has to be restarted.
I would greatly appreciate any assistance in resolving this issue.

Thanks

 

[DataDivaJill]

here is what I found for that error message. hope it helps. jill messier

Native SQL Error 0

Section: Tech Info -> SQL Servers -> Errors -> ->
Creation Date:May 11, 2000
Last Modified Date:May 11, 2000
Legacy Notes

Native SQL Error 0
Cause(s): This often Indicates network disconnection or not enough user connections have been configured on the MSSQL server.
Steps: Check your network connections or try Named Pipes instead of the more robust TCP/IP for your SQL client utilities' protocol.

To add more user connections.

MSSQL 6.5:
1. Open the Enterprise Manager and right on the server's name and select CONFIGURE.
2. Up the number of User Connections(2-6 per GoldMine users.Synchronizing users will require more, however)

MSSQL 7
1. Open the Enterprise Manager and right on the server's name and select Properties.
2. On the CONNECTIONS tab select Maximum concurrent connections specify 0(zero) for the value of this item.This will allow the MSSQL server to allow as many connections as GoldMine requests.

 

[dougscrm]

I would only run SQL Server 2000 SP3 on Windows Server 2003. SQL Server 6.5 is pretty cranky even running on NT 4.

Doug Steinschneider
DCS Group LLC
Fairfield, CT
203.256.2344

http://www.dcsgroupllc.com