Cannot open Enterprise Manager

I have performed a windows update on the server and now i am presented with
an error when trying to open enterprise manager. The MMC cannot find the
file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterprise
Manager.msc
My sql server resides on D: and I have never had a problem opening SQL
Enterprise Manager. I can access the enterprise manager by adding the
snapin. Any ideas.
If you are launching it from a program icon those are all
shortcuts. Right click on the icon and select properties and
check the path to your SQL Server Enterprise Manager.msc
file.
-Sue
On Mon, 7 Nov 2005 06:30:09 -0800, KMD
<KMD@.discussions.microsoft.com> wrote:

>I have performed a windows update on the server and now i am presented with
>an error when trying to open enterprise manager. The MMC cannot find the
>file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterprise
>Manager.msc
>My sql server resides on D: and I have never had a problem opening SQL
>Enterprise Manager. I can access the enterprise manager by adding the
>snapin. Any ideas.

Cannot open Enterprise Manager

I have performed a windows update on the server and now i am presented with
an error when trying to open enterprise manager. The MMC cannot find the
file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterprise
Manager.msc
My sql server resides on D: and I have never had a problem opening SQL
Enterprise Manager. I can access the enterprise manager by adding the
snapin. Any ideas.If you are launching it from a program icon those are all
shortcuts. Right click on the icon and select properties and
check the path to your SQL Server Enterprise Manager.msc
file.
-Sue
On Mon, 7 Nov 2005 06:30:09 -0800, KMD
<KMD@.discussions.microsoft.com> wrote:
>I have performed a windows update on the server and now i am presented with
>an error when trying to open enterprise manager. The MMC cannot find the
>file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterprise
>Manager.msc
>My sql server resides on D: and I have never had a problem opening SQL
>Enterprise Manager. I can access the enterprise manager by adding the
>snapin. Any ideas.

Cannot open Enterprise Manager

I have performed a windows update on the server and now i am presented with
an error when trying to open enterprise manager. The MMC cannot find the
file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterpris
e
Manager.msc
My sql server resides on D: and I have never had a problem opening SQL
Enterprise Manager. I can access the enterprise manager by adding the
snapin. Any ideas.If you are launching it from a program icon those are all
shortcuts. Right click on the icon and select properties and
check the path to your SQL Server Enterprise Manager.msc
file.
-Sue
On Mon, 7 Nov 2005 06:30:09 -0800, KMD
<KMD@.discussions.microsoft.com> wrote:

>I have performed a windows update on the server and now i am presented with
>an error when trying to open enterprise manager. The MMC cannot find the
>file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterpri
se
>Manager.msc
>My sql server resides on D: and I have never had a problem opening SQL
>Enterprise Manager. I can access the enterprise manager by adding the
>snapin. Any ideas.

Cannot load SQL Server Enterprise Manager

This morning when I tried to load SQL Server Enterprise Manager I got the
following error message dialog.
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.MCS.
This may be because the file does not exist, is not an MMC console, or was
created by a later version of MMC. This may also be because you do not have
sufficient access rights to the file.
The file exists, I've made the assumption it is an MMC console, I've had the
same version installed since sp-3 was distributed and I'm logged in under a
system adminsitrators account. Further, I've had and run the same setup for
several months with no problems.

Quote:

Originally posted by Charles
This morning when I tried to load SQL Server Enterprise Manager I got the
following error message dialog.
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.MCS.
This may be because the file does not exist, is not an MMC console, or was
created by a later version of MMC. This may also be because you do not have
sufficient access rights to the file.
The file exists, I've made the assumption it is an MMC console, I've had the
same version installed since sp-3 was distributed and I'm logged in under a
system adminsitrators account. Further, I've had and run the same setup for
several months with no problems.

Cannot kill process

process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running process
but it is not terminating since several days.
Thanks a lot in advance for help!Urban,
Try:
KILL <SPID> WITH STATUSONLY.
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>|||process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running process
but it is not terminating since several days.
SORRY, forgot to mention, that I tryed KILL 51, of course.
Thanks a lot in advance for help!|||Urban,
STATUSONLY will show you the estimated rollback completion. Is this a test
box, you could try stopping the SQL Server service and then starting the SQL
Server service then the SQL Server Agent service. Any errors reported in
either the SQL logs or the app event logs?
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> SORRY, forgot to mention, that I tryed KILL 51, of course.
>
> Thanks a lot in advance for help!
>|||Query analyser returns:
Status report cannot be obtained. Rollback operation for Process ID 51 is
not in progress.
Kill 51 is making the entries in tempd, but not killing the process.
"Jerry Spivey" wrote:
> Urban,
> Try:
> KILL <SPID> WITH STATUSONLY.
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> > process with status runnable in MASTER db (waiting for lock shown in mmc).
> > as consequence, SQL Server agent is not starting anymore!
> > how can I kill this process?
> > master..sysobjects shows this process as non-blocked (blocked=0).
> > in tempdb the entry is shown with SPID #51 correponding to the running
> > process
> > but it is not terminating since several days.
> >
> > Thanks a lot in advance for help!
> >
>
>|||Restart tried several times, even restatred machine.
No errors reported, Just that Process 51 has been killed, but is a true lie;-)
the process is still alive!
"Jerry Spivey" wrote:
> Urban,
> STATUSONLY will show you the estimated rollback completion. Is this a test
> box, you could try stopping the SQL Server service and then starting the SQL
> Server service then the SQL Server Agent service. Any errors reported in
> either the SQL logs or the app event logs?
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
> > process with status runnable in MASTER db (waiting for lock shown in mmc).
> > as consequence, SQL Server agent is not starting anymore!
> > how can I kill this process?
> > master..sysobjects shows this process as non-blocked (blocked=0).
> > in tempdb the entry is shown with SPID #51 correponding to the running
> > process
> > but it is not terminating since several days.
> > SORRY, forgot to mention, that I tryed KILL 51, of course.
> >
> >
> > Thanks a lot in advance for help!
> >
>
>|||How are you looking that this? EM, current activity? Perhaps this is your connection that EM is
using to show you the information?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running process
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>|||Thanks a lot! I'm ashamed, you're right!!!!
It is indeed my own process. I didn't recognize, because I used the run as
command for mmc with the same user that is running SQL-Server, and not my
common user.
I understand, that the prozess is not allowed to kill itself. - Strange,
that it was alive for more than 10 days.
Meanwile, SQL Server Agent was able to start, after about 10 days. This I
don't understand. But even after restarting the databse it works fine.
Propably a problem when patching the server.
Anyway, you have solved my Problem, Tibor. Thanks a lot!
"Tibor Karaszi" wrote:
> How are you looking that this? EM, current activity? Perhaps this is your connection that EM is
> using to show you the information?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> > process with status runnable in MASTER db (waiting for lock shown in mmc).
> > as consequence, SQL Server agent is not starting anymore!
> > how can I kill this process?
> > master..sysobjects shows this process as non-blocked (blocked=0).
> > in tempdb the entry is shown with SPID #51 correponding to the running process
> > but it is not terminating since several days.
> >
> > Thanks a lot in advance for help!
> >
>

Cannot kill process

process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running process
but it is not terminating since several days.
Thanks a lot in advance for help!
Urban,
Try:
KILL <SPID> WITH STATUSONLY.
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>
|||process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running process
but it is not terminating since several days.
SORRY, forgot to mention, that I tryed KILL 51, of course.
Thanks a lot in advance for help!
|||Urban,
STATUSONLY will show you the estimated rollback completion. Is this a test
box, you could try stopping the SQL Server service and then starting the SQL
Server service then the SQL Server Agent service. Any errors reported in
either the SQL logs or the app event logs?
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> SORRY, forgot to mention, that I tryed KILL 51, of course.
>
> Thanks a lot in advance for help!
>
|||Query analyser returns:
Status report cannot be obtained. Rollback operation for Process ID 51 is
not in progress.
Kill 51 is making the entries in tempd, but not killing the process.
"Jerry Spivey" wrote:

> Urban,
> Try:
> KILL <SPID> WITH STATUSONLY.
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
>
>
|||Restart tried several times, even restatred machine.
No errors reported, Just that Process 51 has been killed, but is a true lie;-)
the process is still alive!
"Jerry Spivey" wrote:

> Urban,
> STATUSONLY will show you the estimated rollback completion. Is this a test
> box, you could try stopping the SQL Server service and then starting the SQL
> Server service then the SQL Server Agent service. Any errors reported in
> either the SQL logs or the app event logs?
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
>
>
|||How are you looking that this? EM, current activity? Perhaps this is your connection that EM is
using to show you the information?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running process
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>
|||Thanks a lot! I'm ashamed, you're right!!!!
It is indeed my own process. I didn't recognize, because I used the run as
command for mmc with the same user that is running SQL-Server, and not my
common user.
I understand, that the prozess is not allowed to kill itself. - Strange,
that it was alive for more than 10 days.
Meanwile, SQL Server Agent was able to start, after about 10 days. This I
don't understand. But even after restarting the databse it works fine.
Propably a problem when patching the server.
Anyway, you have solved my Problem, Tibor. Thanks a lot!
"Tibor Karaszi" wrote:

> How are you looking that this? EM, current activity? Perhaps this is your connection that EM is
> using to show you the information?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
>

Cannot kill process

process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running proce
ss
but it is not terminating since several days.
Thanks a lot in advance for help!Urban,
Try:
KILL <SPID> WITH STATUSONLY.
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>|||process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running proce
ss
but it is not terminating since several days.
SORRY, forgot to mention, that I tryed KILL 51, of course.
Thanks a lot in advance for help!|||Urban,
STATUSONLY will show you the estimated rollback completion. Is this a test
box, you could try stopping the SQL Server service and then starting the SQL
Server service then the SQL Server Agent service. Any errors reported in
either the SQL logs or the app event logs?
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> SORRY, forgot to mention, that I tryed KILL 51, of course.
>
> Thanks a lot in advance for help!
>|||Query analyser returns:
Status report cannot be obtained. Rollback operation for Process ID 51 is
not in progress.
Kill 51 is making the entries in tempd, but not killing the process.
"Jerry Spivey" wrote:

> Urban,
> Try:
> KILL <SPID> WITH STATUSONLY.
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
>
>|||Restart tried several times, even restatred machine.
No errors reported, Just that Process 51 has been killed, but is a true lie;
-)
the process is still alive!
"Jerry Spivey" wrote:

> Urban,
> STATUSONLY will show you the estimated rollback completion. Is this a tes
t
> box, you could try stopping the SQL Server service and then starting the S
QL
> Server service then the SQL Server Agent service. Any errors reported in
> either the SQL logs or the app event logs?
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
>
>|||How are you looking that this? EM, current activity? Perhaps this is your co
nnection that EM is
using to show you the information?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running pro
cess
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>|||Thanks a lot! I'm ashamed, you're right!!!!
It is indeed my own process. I didn't recognize, because I used the run as
command for mmc with the same user that is running SQL-Server, and not my
common user.
I understand, that the prozess is not allowed to kill itself. - Strange,
that it was alive for more than 10 days.
Meanwile, SQL Server Agent was able to start, after about 10 days. This I
don't understand. But even after restarting the databse it works fine.
Propably a problem when patching the server.
Anyway, you have solved my Problem, Tibor. Thanks a lot!
"Tibor Karaszi" wrote:

> How are you looking that this? EM, current activity? Perhaps this is your
connection that EM is
> using to show you the information?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
>