|
|
|
|
||||||
| ms.sqlserver.setup Questions about SQL Server. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
I've put this in setup since it seems setup/config has been corrupted.
I'm getting several MMC errors, the most problematic is not being able to run EM on my dev box! I get "mmc could not create the snap-in" and a red x. This happens in my custom consoles, as well as a straight EM launch. If I try to "add/remove" snap ins on a new console, I don't even SEE the EM snap-in to add... I also got a "MMC has detected an error in a snap-in" with three choice radio button when clicking the WMI control snap-in. This is essentially an exception handler, as no matter what I select, I subsequently got the "send error to MS" option. Here's a brief history. I'm running XP pro SP2. Ran for YEARS without any EM issues. Installed SQL 2005, then VS2005, then the SQL 2005 extension for SQL 2000 DTS, then (for reasons I can't remember) I installed the MMC 3.0 upgrade. I started getting occassional issues when launching the DTS GUI, so I decided to remove the 2005 DTS extension. That's what killed SQL EM, now I can't do anything on my box SQL 2000 admin related. |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
Hi,
I understand that after MMC 3.0 was installed on your Windows XP SP2, your SQL Server 2000 Enterprise Manager could not work due to the error "mmc could not create the snap-in". You also encountered the warning "MMC has detected an error in a snap-in" when clicked the WMI control snap-in. If I have misunderstood, please let me know. After looked through this KB article: MMC 3.0 update is available for Windows Server 2003 and for Windows XP http://support.microsoft.com/kb/907265 , I would like to check with you to see if Visual Studio 2005 SP1 has been installed before you installed MMC 3.0 since this is a prerequisite of installing MMC 3.0. For the warning message "MMC has detected an error in a snap-in", I found a KB article which described the similar issue: Warning message when you install MMC 3.0 and you are running SQL Server 2000 Analysis Services: "MMC has detected an error in a snap-in." http://support.microsoft.com/kb/915091 You may check if the workaround can work at your side: Continue running and always ignore errors with this snap-in, regardless of user or session. For the error message "mmc could not create the snap-in", I did not find a article for explaining this error. I also tried installinig MMC3.0 on my Windows XP Pro SP2, and SQL Server 2000 EM worked fine. As a possible workaround, I recommend that you reinstall SQL Server 2000 Client Tools to see if it s. If this issue persists, I recommend that you use Process Monitor to monitor the processes sqlmangr.exe and mmc.exe and mail me (changliw_at_microsoft_dot_com) the logs for further research. You can download the tool from this link: Process Monitor v1.12 http://www.microsoft.com/technet/sys...ads/processmon itor.mspx Hope this s. If you have any other questions or concerns, please feel free to let me know. Best regards, Charles Wang Microsoft Online Community Support ================================================== === Get notification to my posts through email? Please refer to: http://msdn.microsoft.com/subscripti...ult.aspx#notif ications If you are using Outlook Express, please make sure you clear the check box "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscripti...t/default.aspx. ================================================== ==== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ================================================== ==== This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== ==== |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
Sorry, I made a mistake. VS2005 SP1 is not a prerequisite of installing mmc
3.0. I had thought that 2.0.50727 was SP1, however after checked the version of original Visual Studio 2005 on my colleague's machine, I found that the difference is the minor version numbers after 50727. Please ignore the following content in my first reply: ================================================== = After looked through this KB article: MMC 3.0 update is available for Windows Server 2003 and for Windows XP http://support.microsoft.com/kb/907265 , I would like to check with you to see if Visual Studio 2005 SP1 has been installed before you installed MMC 3.0 since this is a prerequisite of installing MMC 3.0. ================================================== === Best regards, Charles Wang Microsoft Online Community Support ================================================== === Get notification to my posts through email? Please refer to: http://msdn.microsoft.com/subscripti...ult.aspx#notif ications If you are using Outlook Express, please make sure you clear the check box "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscripti...t/default.aspx. ================================================== ==== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ================================================== ==== This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== ==== |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
I finally just installed the client tools again. I think the lesson learned
here is to avoid MMC 3 unless it's already there. DON'T install MMC 3 unless obligated! I'm also having a completely unrelated (in terms of my workstation) issue on a server that I RDP into regularly. something went wrong with my profile, so I deleted it and logged back in. I then tried to create a new mmc console. Adding the SQL EM snap-in results in the following error: "Connection to application object failed. Ensure that no program modules have been deleted." Honestly, I don't understand WHY a "relatively" stable product has been mangled after so many years. Suddenly I have 2 errors in one week on different machines, and both related to MMC 3? "Charles Wang[MSFT]" wrote: > Sorry, I made a mistake. VS2005 SP1 is not a prerequisite of installing mmc > 3.0. I had thought that 2.0.50727 was SP1, however after checked the > version of original Visual Studio 2005 on my colleague's machine, I found > that the difference is the minor version numbers after 50727. > Please ignore the following content in my first reply: > ================================================== = > After looked through this KB article: > MMC 3.0 update is available for Windows Server 2003 and for Windows XP > http://support.microsoft.com/kb/907265 > , I would like to check with you to see if Visual Studio 2005 SP1 has been > installed before you installed MMC 3.0 since this is a prerequisite of > installing MMC 3.0. > ================================================== === > > > Best regards, > Charles Wang > Microsoft Online Community Support > ================================================== === > Get notification to my posts through email? Please refer to: > http://msdn.microsoft.com/subscripti...ult.aspx#notif > ications > > If you are using Outlook Express, please make sure you clear the check box > "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly. > > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > where an initial response from the community or a Microsoft Support > Engineer within 1 business day is acceptable. Please note that each follow > up response may take approximately 2 business days as the support > professional working with you may need further investigation to reach the > most efficient resolution. The offering is not appropriate for situations > that require urgent, real-time or phone-based interactions or complex > project analysis and dump analysis issues. Issues of this nature are best > handled working with a dedicated Microsoft Support Engineer by contacting > Microsoft Customer Support Services (CSS) at > http://msdn.microsoft.com/subscripti...t/default.aspx. > ================================================== ==== > When responding to posts, please "Reply to Group" via > your newsreader so that others may learn and benefit > from this issue. > ================================================== ==== > This posting is provided "AS IS" with no warranties, and confers no rights. > ================================================== ==== > > > > |
|
|
|
#5 |
|
Messages: n/a
Hébergeur: |
Hi,
Since this issue could not be reproduced at my side, it is hard to say they are related to MMC 3.0. There seems to be some DLLs' version or size are not correct. I recommend that you use Dependency Walker and Process Monitor to monitor the process mmc.exe and compare the outputs to the those from other machine on which SQL Server 2000 EM worked fine with MMC 3.0. You can download the tools from the following links: How To Use Dependency Walker Version 2.1 to Create a Profile http://support.microsoft.com/kb/256872 Process Monitor v1.2 http://www.microsoft.com/technet/sys...ads/processmon itor.mspx Hope this s. If you have any other questions or concerns, please feel free to let me know. Best regards, Charles Wang Microsoft Online Community Support ================================================== === Get notification to my posts through email? Please refer to: http://msdn.microsoft.com/subscripti...ult.aspx#notif ications If you are using Outlook Express, please make sure you clear the check box "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscripti...t/default.aspx. ================================================== ==== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ================================================== ==== This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== ==== |
|
|
|
#6 |
|
Messages: n/a
Hébergeur: |
Hi,
I am interested in this issue. Would you mind letting me know the result of the suggestions? If you need further assistance, feel free to let me know. I will be more than happy to be of assistance. Charles Wang Microsoft Online Community Support ================================================== ==== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ================================================== ==== This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== ==== |
|
|
|
#7 |
|
Messages: n/a
Hébergeur: |
As for the EM on my install on my machine, re-installing the SQL client tools
did the trick. It turns this process straightend out another issue. It turns out that the uninstall I did was from the original stand alone SQL 2000 DTS snap in install. This broke EM, and I re-installed. Now, contrary to my expectations, the legacy DTS editor node still works, presumably from the built-in extension from SP2? When I pull up the legacy DTS editor from SSMS, the window is no longer modal. Before I had to dismiss the DTS edit window before accessing the SSMS window again. As for the other suggestion, I must admit I haven't had the time to test your suggestions. As soon as I do, I'll come back and update you with the results. "Charles Wang[MSFT]" wrote: > Hi, > I am interested in this issue. Would you mind letting me know the result of > the suggestions? If you need further assistance, feel free to let me know. > I will be more than happy to be of assistance. > > Charles Wang > Microsoft Online Community Support > > ================================================== ==== > When responding to posts, please "Reply to Group" via > your newsreader so that others may learn and benefit > from this issue. > ================================================== ==== > This posting is provided "AS IS" with no warranties, and confers no rights. > ================================================== ==== > > |
|
|
|
#8 |
|
Messages: n/a
Hébergeur: |
Hi,
Thanks for your updating and response. I am glad to hear that reinstalling SQL client tools solved the problem. For the new issue, to let me better understand it, could you please mail me (changliw_at_microsoft_dot_com) some screeshots? Does it affect your operations? Look forward to your response. If you have any other questions or concerns, please feel free to let me know. Have a nice day! Best regards, Charles Wang Microsoft Online Community Support ================================================== === Get notification to my posts through email? Please refer to: http://msdn.microsoft.com/subscripti...ult.aspx#notif ications If you are using Outlook Express, please make sure you clear the check box "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscripti...t/default.aspx. ================================================== ==== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ================================================== ==== This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== ==== |
|
![]() |
| Outils de la discussion | |
|
|