Showing posts with label msc. Show all posts
Showing posts with label msc. Show all posts

Thursday, March 22, 2012

Enterprise Manger Error

I am getting an error:
MMC cannot open the file C:\program files\Miscorosft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
This may be because the file does not exist, is not an MMC console, or was
creted by a later version of MMC. This may also by because you do not have
sufficient access rights to the file.
I've tried uninstalling/reinstalling reapplying SP3a etc. with no luck.
I did find that renaming the file to anything else will allow it to work.
Which makes for an easy enough work around but was wondering if anybody knew
what is going on?
TIA
Hi
Have you tried running MMC and opening the file from there?
Check the file permissions.
If you have EM on another machine you may want to try copying the file.
Alternatively may want to extract the MSC file from the original CD.
John
"Ken Rinaman" <go@.away.net> wrote in message
news:%23sPCyhiUEHA.2972@.TK2MSFTNGP12.phx.gbl...
> I am getting an error:
> MMC cannot open the file C:\program files\Miscorosft SQL
> Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
> This may be because the file does not exist, is not an MMC console, or was
> creted by a later version of MMC. This may also by because you do not have
> sufficient access rights to the file.
> I've tried uninstalling/reinstalling reapplying SP3a etc. with no luck.
> I did find that renaming the file to anything else will allow it to work.
> Which makes for an easy enough work around but was wondering if anybody
knew
> what is going on?
> TIA
>
|||
> Have you tried running MMC and opening the file from there?
Yes, same error.

> Check the file permissions.
I have the ability to rename, delete, etc.

> If you have EM on another machine you may want to try copying the file.
> Alternatively may want to extract the MSC file from the original CD.
I did pull the file from the CD which is how I discovered changing the name
fixes the problem. On the CD the file is called SQLEM.msc if I copy that
file to my computer it runs fine. However if I rename it to SQL Server
Enterprise Manger.msc it no longer runs.
sql

Wednesday, March 21, 2012

Enterprise Manager won't work - "snap-in failed to initialize"

On one node of a cluster I have I began getting this message today after a
failover. How do I resolve? I've tried copying SQLEM.msc and replacing it
an it in 80\tools\binn but it still doesn't work. This is the exact error
message:
Snap-in failed to initialize
Name: Microsoft SQL Enterprise Manager
Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}See this KB Article. it may helpful
http://support.microsoft.com/?kbid=297064
Petchikumar
"Cathy Soloway" wrote:

> On one node of a cluster I have I began getting this message today after a
> failover. How do I resolve? I've tried copying SQLEM.msc and replacing i
t
> an it in 80\tools\binn but it still doesn't work. This is the exact error
> message:
> Snap-in failed to initialize
> Name: Microsoft SQL Enterprise Manager
> Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}
>|||That didn't work either. I called support and they walked me through
checking out all the DLLs and functionality and finally suggested we do a
re-boot. Will try that over the weekend. Thanks for the response, though.
"Petchikumar" wrote:
[vbcol=seagreen]
> See this KB Article. it may helpful
> http://support.microsoft.com/?kbid=297064
>
> Petchikumar
>
> "Cathy Soloway" wrote:
>

Enterprise Manager won't work - "snap-in failed to initialize"

On one node of a cluster I have I began getting this message today after a
failover. How do I resolve? I've tried copying SQLEM.msc and replacing it
an it in 80\tools\binn but it still doesn't work. This is the exact error
message:
Snap-in failed to initialize
Name: Microsoft SQL Enterprise Manager
Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}See this KB Article. it may helpful
http://support.microsoft.com/?kbid=297064
Petchikumar
"Cathy Soloway" wrote:
> On one node of a cluster I have I began getting this message today after a
> failover. How do I resolve? I've tried copying SQLEM.msc and replacing it
> an it in 80\tools\binn but it still doesn't work. This is the exact error
> message:
> Snap-in failed to initialize
> Name: Microsoft SQL Enterprise Manager
> Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}
>|||That didn't work either. I called support and they walked me through
checking out all the DLLs and functionality and finally suggested we do a
re-boot. Will try that over the weekend. Thanks for the response, though.
"Petchikumar" wrote:
> See this KB Article. it may helpful
> http://support.microsoft.com/?kbid=297064
>
> Petchikumar
>
> "Cathy Soloway" wrote:
> > On one node of a cluster I have I began getting this message today after a
> > failover. How do I resolve? I've tried copying SQLEM.msc and replacing it
> > an it in 80\tools\binn but it still doesn't work. This is the exact error
> > message:
> >
> > Snap-in failed to initialize
> > Name: Microsoft SQL Enterprise Manager
> > Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}
> >