Enterprise Mgr. Won't Open

Here's a strange thing: I've had this installed for years, and it was working fine up until last night, after I installed the latest MS security updates.
After re-booting from that installation, I have not been able to open Enterprise Manager. I get an error titled Microsoft Management Console, then it tells me it has encountered a problem and needs to close.
I've uninstalled and re-installed the SQL Server 2000 client tools, but still get the same error. I've worked around it by running mmc.exe and adding the SQL Server snap-in, but would really like to fix this problem.
I can run mmc.exe, but as soon as I try to open SQL Server Enterprise Manager.msc, mmc crashes.
My OS is WinXP pro, sp 1. Anyone have any idea what's going on?
Thanks for any assistance,
Tom
This is getting stranger. I tried renaming the SQL Server Enterprise Manager.MSC to SQLServerEnterpriseManager.MSC, and it opens without any problem.
What's that all about?
tom
|||Hi Tom,
From your description, I understand that you would like to know why your
SQL Server Enterprise Manager crashes after your updating some Windows
Security Updates. Have I understood the issue correctly and completely? If
there is anything I misunderstood, please feel free to let me know.
I would like to collect some information about it
1. Do you use Windows Updates to do some updates and what updates have you
installed?
2. You could find SQLEM.msc from your SQL Server Install Disk and please
copy it to your SQL Client installed disk
(from CDROM\Enterprise\x86\binn\SQLEM.msc to SQLInstalledDisk\80\Tools\Binn
as SQL Server Enterprise Manager.msc)
Try to do this and see whethere it could solve your problems
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Support
************************************************** *********
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.
|||Michael,
I responded several days ago to your last post, however for some
reason my response was not posted. Here is the gist of it: (I posted
again tonight in the web based group, and the message did not post,
I'm using another newsgroup reader for this post).
I used Windows Update to install the latest security patches (WinXP
Pro).
I did several things, including following your suggestions, however
the only way to open EM was to rename the file. I first accidentally
found this out when I copied the file SQL Server Enterprise
Manager.MSC as test.msc to another directory.
Double clicking that file opened it with no problems. I then renamed
it to SQLServerEnterpriseManager.MSC, and it opened fine. However, if
I try to open it as SQL Server Enterprise Manager.MSC (with the
spaces), I get the error: Microsoft Management Console has encountered
a problem and needs to close.
I can open the file from the installation media (SQLEM.MSC), but as
soon as I rename it to SQL Server Enterprise Manager.MSC I get the
error.
I have no idea why this might be happening.
Tom
On Thu, 15 Apr 2004 08:07:11 GMT, v-mingqc@.online.microsoft.com
("Michael, Cheng [MST]") wrote:

>Hi Tom,
>From your description, I understand that you would like to know why your
>SQL Server Enterprise Manager crashes after your updating some Windows
>Security Updates. Have I understood the issue correctly and completely? If
>there is anything I misunderstood, please feel free to let me know.
>I would like to collect some information about it
>1. Do you use Windows Updates to do some updates and what updates have you
>installed?
>2. You could find SQLEM.msc from your SQL Server Install Disk and please
>copy it to your SQL Client installed disk
>(from CDROM\Enterprise\x86\binn\SQLEM.msc to SQLInstalledDisk\80\Tools\Binn
>as SQL Server Enterprise Manager.msc)
>Try to do this and see whethere it could solve your problems
>Thank you for your patience and cooperation. If you have any questions or
>concerns, don't hesitate to let me know. We are here to be of assistance!
>Sincerely yours,
>Michael Cheng
>Microsoft Online Support
>************************************************* **********
>Get Secure! - www.microsoft.com/security
>This posting is provided "as is" with no warranties and confers no rights.
>Please reply to newsgroups only, many thanks.
>
|||Hi Tom,
Would you please try following steps:
1. When opening SQL Server Enterprise Manager.MSC in mmc.exe, trying to
give a quotation marks like "SQL Server Enterprise Manager.MSC" and see
whether it will work fine.
2. Would you please check your SQL Server and MDAC versions to ensure they
are the latest ones?
3. Deleting the C:\Documents and Settings\<user-id>\Application
Data\Microsoft\MMC\SQL Server Enterprise Manager
try to see whethere it will work fine?
4. If you rename the file with blanks, such as "SQL SEM.msc" will it still
work fine?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Support
************************************************** *********
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.
|||Michael,
Step #3 did the trick. Can you tell me what the problem was (i.e. why did it "break")?
Also, I'm hoping this posts on the newsgroup, as my posts lately don't seem to be "taking"...
Thanks for your help,
Tom
|||Hi Tom,
I am glad to hear that step #3 did the trick.
Based on my knowledge, on a Windows XP machine, the initial launch of SQL
Enterprise Manager creates a file (SQL Server Enterprise Manager) in
C:\Documents and Settings\<user-id>\Application Data\Microsoft\MMC.
Subsequent launches of Enterprise Manager use this file instead of the
original .msc file
Your Windows Security Updates or some other operations may make this file
corrupted. So you could not launch it unless you make it renamed. Renamed
file is recognized as new one, so it could be launched correctly.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Support
************************************************** *********
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.