Enterprise Manager: The connection to SQL Server <server> has been broken.

All~
I am currently running the most recent version of MSDE and using EM as
a front end interface. In EM, I go to look at the databases I had
previously created, but receive the message:
The connection to SQL Server <server> has been broken. The connection
to the SQL Server is broken. Do you want to try reconnection...
I am unable to start SQL Agent, but I am not sure whether this is the
cause. I am able to connect via the Query Analyzer facility fine. I
get the following SQLDump [truncated].
What is the EXCEPTION_ACCESS_VIOLATION and how can I fix it?
...
**
*
* BEGIN STACK DUMP:
* 07/31/04 09:59:24 spid 0
*
* Exception Address = 00000000
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 00000000
...
Your help is greatly appreciated.
Richard
Check your SQL Server error logs for more information. Also
check the SQL Agent log and see if you find any errors
related to that issue. You may also want to check the stack
dump and compare it with that mentioned in the following
article:
PRB: Removal of Guest Account May Cause Handled Exception
Access Violation in SQL Server
http://support.microsoft.com/?id=315523
-Sue
On 31 Jul 2004 07:22:35 -0700, rkinnie01@.excite.com (Richard
K) wrote:

>All~
>I am currently running the most recent version of MSDE and using EM as
>a front end interface. In EM, I go to look at the databases I had
>previously created, but receive the message:
>The connection to SQL Server <server> has been broken. The connection
>to the SQL Server is broken. Do you want to try reconnection...
>I am unable to start SQL Agent, but I am not sure whether this is the
>cause. I am able to connect via the Query Analyzer facility fine. I
>get the following SQLDump [truncated].
>What is the EXCEPTION_ACCESS_VIOLATION and how can I fix it?
>...
>**
>*
>* BEGIN STACK DUMP:
>* 07/31/04 09:59:24 spid 0
>*
>* Exception Address = 00000000
>* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
>* Access Violation occurred reading address 00000000
>...
>Your help is greatly appreciated.
>Richard

Enterprise Manager: The connection to SQL Server <server> has been broken.

All~
I am currently running the most recent version of MSDE and using EM as
a front end interface. In EM, I go to look at the databases I had
previously created, but receive the message:
The connection to SQL Server <server> has been broken. The connection
to the SQL Server is broken. Do you want to try reconnection...
I am unable to start SQL Agent, but I am not sure whether this is the
cause. I am able to connect via the Query Analyzer facility fine. I
get the following SQLDump [truncated].
What is the EXCEPTION_ACCESS_VIOLATION and how can I fix it?
...
**
*
* BEGIN STACK DUMP:
* 07/31/04 09:59:24 spid 0
*
* Exception Address = 00000000
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 00000000
...
Your help is greatly appreciated.
RichardCheck your SQL Server error logs for more information. Also
check the SQL Agent log and see if you find any errors
related to that issue. You may also want to check the stack
dump and compare it with that mentioned in the following
article:
PRB: Removal of Guest Account May Cause Handled Exception
Access Violation in SQL Server
http://support.microsoft.com/?id=315523
-Sue
On 31 Jul 2004 07:22:35 -0700, rkinnie01@.excite.com (Richard
K) wrote:

>All~
>I am currently running the most recent version of MSDE and using EM as
>a front end interface. In EM, I go to look at the databases I had
>previously created, but receive the message:
>The connection to SQL Server <server> has been broken. The connection
>to the SQL Server is broken. Do you want to try reconnection...
>I am unable to start SQL Agent, but I am not sure whether this is the
>cause. I am able to connect via the Query Analyzer facility fine. I
>get the following SQLDump [truncated].
>What is the EXCEPTION_ACCESS_VIOLATION and how can I fix it?
>...
>**
>*
>* BEGIN STACK DUMP:
>* 07/31/04 09:59:24 spid 0
>*
>* Exception Address = 00000000
>* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
>* Access Violation occurred reading address 00000000
>...
>Your help is greatly appreciated.
>Richard

Enterprise Manager broken on SQL 2000, how to put back

I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
SQL appears to be running fine and my SQL applications are working fine too.
How can I put back my SQL Enterprise Manager and SQL Query Analyser?
If I reinstall SQL 2000 will that mess up my installed SQL applications?
Will SQL installer attempt to "repair" things with messing up my installed
databases?
My SQL applications/databases are a bear to reinstall and I don't want to if
I don't have to. Like I said, they are running fine.
Greatful for any help.
RonYou can try to reinstall the SQL Server service pack to start with...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:A7A214E5-B073-4988-8E18-8464F2407483@.microsoft.com...
> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>|||Thank you for your response. I tried first to restart the SQL server. Boy,
that was a mistake (of sorts). When the server came back up, none of the SQL
applications were working (although the SQL service had started).
Tried to reinstall SP3 as suggested (thank you) but niether windows
authentication nor the sa account would work.
So, out of desperation I reinstalled Veritas Backupexec 91 for servers. I
rebooted the machine and bingo, the SQL apps could access the SQL databases
again!
But SQL is still broken, in that Enterprise Manager and SQL query will not
run.
I am almost to the point where I am going to try reinstalling SQL.
Will it recognize my existing SQL databases or will I have to reinstall
everything?
The Win 2003 server itself is fine, it's just that SQL is "not all there" it
seems.
Ron
"Ron" wrote:
> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>

Enterprise Manager broken on SQL 2000, how to put back

I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
SQL appears to be running fine and my SQL applications are working fine too.
How can I put back my SQL Enterprise Manager and SQL Query Analyser?
If I reinstall SQL 2000 will that mess up my installed SQL applications?
Will SQL installer attempt to "repair" things with messing up my installed
databases?
My SQL applications/databases are a bear to reinstall and I don't want to if
I don't have to. Like I said, they are running fine.
Greatful for any help.
Ron
You can try to reinstall the SQL Server service pack to start with...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:A7A214E5-B073-4988-8E18-8464F2407483@.microsoft.com...
> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>
|||Thank you for your response. I tried first to restart the SQL server. Boy,
that was a mistake (of sorts). When the server came back up, none of the SQL
applications were working (although the SQL service had started).
Tried to reinstall SP3 as suggested (thank you) but niether windows
authentication nor the sa account would work.
So, out of desperation I reinstalled Veritas Backupexec 91 for servers. I
rebooted the machine and bingo, the SQL apps could access the SQL databases
again!
But SQL is still broken, in that Enterprise Manager and SQL query will not
run.
I am almost to the point where I am going to try reinstalling SQL.
Will it recognize my existing SQL databases or will I have to reinstall
everything?
The Win 2003 server itself is fine, it's just that SQL is "not all there" it
seems.
Ron
"Ron" wrote:

> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>