[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

SQL Server Errors in Terminal Services

Posted on 2006-07-19
7
Medium Priority
?
645 Views
Last Modified: 2008-01-09
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.
0
Comment
Question by:simon_kirk
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
7 Comments
 
LVL 27

Expert Comment

by:ptjcb
ID: 17137647
What version is your MDAC? What have you installed recently?
0
 
LVL 14

Author Comment

by:simon_kirk
ID: 17137935
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.
0
 
LVL 27

Expert Comment

by:ptjcb
ID: 17138157
From this link: http://groups.google.com/group/microsoft.public.sqlserver.setup/browse_frm/thread/
7a116d43d9e83e14/2fb35ea7721ea398?lnk=st&q=SQL+Server+2000+sqlmangr.exe+-+Application+Error&rnum=5&hl=en#2fb35ea7721ea398

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?



0
 
LVL 14

Author Comment

by:simon_kirk
ID: 17138818
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?

0
 
LVL 27

Accepted Solution

by:
ptjcb earned 2000 total points
ID: 17145869
Yes - .NET frameworks can work side-by-side. They are created with as much backward-compatibility is possible. This link goes through the details: http://www.gotdotnet.com/team/changeinfo/

Terminal Server and SQL Server are on two different servers. Both are on two different Windows 2000 and have the same setup? It is just odd that with nothing changing you would start to receive new errors. Have you checked the logs on both servers? Have you been on the server, running a trace and had someone else (or you could do it) try and TS into the box?



0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
It is possible to export the data of a SQL Table in SSMS and generate INSERT statements. It's neatly tucked away in the generate scripts option of a database.
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question