MikeBronner
Programmer
Hi All,
We have been experiencing this problem for many years now, and even calls to Frontrange tech support didn't result in any lasting results.
I'll show the error, followed by the actions we tool to attempt to resolve it:
To fix this we were instructed to increase the MAXDBPROCESS setting in the BDEMgr by 1024. After initially have Frontrange tech support walk us through some configurations in the BDEMgr, we stopped seeing this problem for about 2 weeks. However, now it has come back and seems to occur on a daily basis again.
Does anyone have any ideas what this error means? Our thought is that something PREVIOUS to the shown query is causing the actual error, resulting in the following query to fail. Unfortunately none of the event logs (in Goldmine, SQL, and Windows) allude to anything being wrong.
Thanks!
Take Care,
Mike
We have been experiencing this problem for many years now, and even calls to Frontrange tech support didn't result in any lasting results.
I'll show the error, followed by the actions we tool to attempt to resolve it:
Code:
General SQL error.
Native SQL error: 10025
Context: SQLQuery: GM_GMBase:
set rowcount 1 SELECT * FROM dbo.CAL (NOLOCK) WHERE ALARMFLAG = 'Y' AND USERID = 'PKHANDJI' AND (ALARMDATE <= '01/28/2008') ORDER BY ALARMFLAG ASC, USERID ASC, ALARMDATE ASC, ALARMTIME ASC set rowcount 0
1: Server message: Possible network error: Write to SQL Server Failed. General network error. Check your documentation.
BDE Error Cat:Code: [51:3]
BDE: 500 [4/11/1999] GoldMine: 6.70.50123
User: PKHANDJI
Window:
Template:
Details:
NATIVEMSG: Possible network error: Write to SQL Server Failed. General network error. Check your documentation.
To fix this we were instructed to increase the MAXDBPROCESS setting in the BDEMgr by 1024. After initially have Frontrange tech support walk us through some configurations in the BDEMgr, we stopped seeing this problem for about 2 weeks. However, now it has come back and seems to occur on a daily basis again.
Does anyone have any ideas what this error means? Our thought is that something PREVIOUS to the shown query is causing the actual error, resulting in the following query to fail. Unfortunately none of the event logs (in Goldmine, SQL, and Windows) allude to anything being wrong.
Thanks!
Take Care,
Mike