SQL Server Errors in Terminal Services
HI,
Getting the following error popping up when we connect to our SQL Server via Terminal Services:
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 19/07/2006
Time: 09:51:59
User: N/A
Computer: ********
Description:
Application popup: sqlmangr.exe - Application Error : The instruction at "0x780104ac" referenced memory at "0x018eeba8". The memory could not be "read".
Click on OK to terminate the program
Click on CANCEL to debug the program
This causes the SQL Manager to shut down.
Also seem to get a similiar error when trying to browse available SQL servers in DTS Designer and Query Analyser, in that it causes Enterprise Manager or Query Analyser to crash.
The odd thing is that this ONLY happens when we connect via Terminal Services, and doesn't occur if I'm on on the actual SQL server.
I've already looked at [FIX 814064: SQLBrowseConnect May Cause an Access Violation in the Client Application] and we have no SQL servers hidden in the listing.
This has only happened fairly recently, and I'm pretty sure we've had no SPs or hotfixes applied to the OS.
System Info:
* Windows 2000 SP4
* SQL Server Enterprise Edition 2000 SP3 (8.00.818)
Cheers.
Getting the following error popping up when we connect to our SQL Server via Terminal Services:
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 19/07/2006
Time: 09:51:59
User: N/A
Computer: ********
Description:
Application popup: sqlmangr.exe - Application Error : The instruction at "0x780104ac" referenced memory at "0x018eeba8". The memory could not be "read".
Click on OK to terminate the program
Click on CANCEL to debug the program
This causes the SQL Manager to shut down.
Also seem to get a similiar error when trying to browse available SQL servers in DTS Designer and Query Analyser, in that it causes Enterprise Manager or Query Analyser to crash.
The odd thing is that this ONLY happens when we connect via Terminal Services, and doesn't occur if I'm on on the actual SQL server.
I've already looked at [FIX 814064: SQLBrowseConnect May Cause an Access Violation in the Client Application] and we have no SQL servers hidden in the listing.
This has only happened fairly recently, and I'm pretty sure we've had no SPs or hotfixes applied to the OS.
System Info:
* Windows 2000 SP4
* SQL Server Enterprise Edition 2000 SP3 (8.00.818)
Cheers.
ptjcb
What version is your MDAC? What have you installed recently?
ASKER
MDAC version is 2.71.9030.0
Server OS version is 5.0.2195.4.0.196882
As far as I can tell there have been no software, SPs or hotfixes applied to the server. My thought was that something must have started causing the error, and updates are famous for having knock on effects. Guess the only other possiility would be some sort of setting change, but again I'm not aware of any being made.
Server OS version is 5.0.2195.4.0.196882
As far as I can tell there have been no software, SPs or hotfixes applied to the server. My thought was that something must have started causing the error, and updates are famous for having knock on effects. Guess the only other possiility would be some sort of setting change, but again I'm not aware of any being made.
From this link: http://groups.google.com/group/microsoft.public.sqlserver.setup/browse_frm/thread/
7a116d43d9e83e14/2fb35ea77
It looks as if there was an issue with MDAC 2.7. I don't know if this will solve it or not. It is interesting that it happens only with Terminal Services. I would check on how Terminal Services connects to SQL - ODBC? ADO? It may be how Terminal Services connects. It would be interesting to check if you can open another MMC app and if you have the same issue.
You also say that this has only started recently (so you have been connecting through terminal services for some time before this error). If that is the case then I would guess that somehow the server was updated by a hotfix/service pack or something; is it set to update without intervention?
7a116d43d9e83e14/2fb35ea77
It looks as if there was an issue with MDAC 2.7. I don't know if this will solve it or not. It is interesting that it happens only with Terminal Services. I would check on how Terminal Services connects to SQL - ODBC? ADO? It may be how Terminal Services connects. It would be interesting to check if you can open another MMC app and if you have the same issue.
You also say that this has only started recently (so you have been connecting through terminal services for some time before this error). If that is the case then I would guess that somehow the server was updated by a hotfix/service pack or something; is it set to update without intervention?
ASKER
Thanks for that.
I've looked into the MDAC, and 2.7 was installed when the server was originally built, so I'm reluctant to make any changes to this.
The bugging issue is that TS worked fine before, and no changes to the way it connects to the server have been made.
I've checked with our MIS, and they assure me that no updates have been automatically applied to the server, though looking through Add Remove Programs I've noticed that .Net framework 1.1, 1.1 SP1 and 2.0 are installed. Do you know if they can run on the same server without causing issues?
I've looked into the MDAC, and 2.7 was installed when the server was originally built, so I'm reluctant to make any changes to this.
The bugging issue is that TS worked fine before, and no changes to the way it connects to the server have been made.
I've checked with our MIS, and they assure me that no updates have been automatically applied to the server, though looking through Add Remove Programs I've noticed that .Net framework 1.1, 1.1 SP1 and 2.0 are installed. Do you know if they can run on the same server without causing issues?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.