Windows Server 2003 R2 File Server Management MMC could not create the snap-in Name: File Server Management CLSID: FX:{f7da6f14-f244-401a-9259-f015a82057d3} I tried this http://forums.microsoft.com/Technet-...7195&SiteID=29 ] but it can not fix this problem. So, I try to post problem here to find some help.
Hi Meinolf,
I try to open it on Windows Server 2003 R2. I found another kb to check system Var on "Path", but the value is like normal => "%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem"
finally, this problem solved.
because .Net Framework, after removed and re-install it.
the MMC works fine.
If you were to post direct to an MS group, explaining your problem, you might get a formative response, rather than posting to another group that leaches off the MS groups and posts a none explicit explanation I feel your pain. Go to Microsoft Training Website, its free and there's a wealth of information ref: Windows Vista. I was pretty happy when I found Vista has its on server. The more I know about Vista the more I enjoy it. You can only do "VPN" virtual private networking if you have different operating systems e.g., Vista & XP etc.
... as what? The thread you've responded to is from 2007 (!) and has expired
from the news server.
Please start a new thread and describe in detail what problem you're having,
including your operating system, service pack level, etc.
I dont know who or why everyone is going through so much hassle with this problem and so much work to fix it try this ::::
In *Computer Management*, verify that you are in the console for the remote computer.
*HERE WE GO CLICK START::*
*TYPE IN ::Services - and click on it*
*IN THE DETAILS PANE::::::*
*RIGHT CLICK ::REMOTE REGISTRY*
*select ::PROPERTIES*
*start up type ::AUTOMATIC*
*then click ::START*
*then click ::APPLY *
*then click ::OK *
*That should do it - if not ill eat my hat =*
*ohh wait - sorry i dont own a hat!!! lol ohh well *
Member
Didn't work for me. Nice try, It stopped working with the last service pack. I think it has something to do with a security conflict. The security update created a new user and whichever process creates the snapins doesn't have permission to create these snapins. Vista is a joy/sarc
Posting Permissions
Reply With Quote
Bookmarks