|
-
February 14th, 2003, 12:31 PM
#1
Group Policy error message
When I try to access Group Policy, I get this error...
How can I correct this? Thanks
-
February 14th, 2003, 12:45 PM
#2
If this only started happening recently then System Restore might be a good idea. Or you could try Start>Run>"sfc /scannow" without the quotes and see if that helps (you'll need the XP CD handy).
One other thought - my gpedit.msc is 34,871 bytes in size, if yours is different then it might be corrupted, you should be able to copy it of the XP CD.
Nick.
-
February 14th, 2003, 01:24 PM
#3
How do I just copy it from the CD, I can't seem to find it. The size file is the same as your's on my system. Thanks.
-
February 14th, 2003, 01:31 PM
#4
Here's the Resource Kit article on extracting files from the CD:
http://www.microsoft.com/technet/tre...g_det_pvfh.asp
Nick.
-
February 14th, 2003, 01:35 PM
#5
After I click on OK from the above error message I recieve, I get the error below...
-
February 14th, 2003, 02:15 PM
#6
PM me your email addy and I'll zip up my gpedit.msc and email it to you.
Last edited by SuperSparks; February 14th, 2003 at 02:18 PM.
Nick.
-
February 14th, 2003, 03:18 PM
#7
Thanks for all your help, turned out being that I was missing a .dll file from the System32 folder. I just made a copy of the same .dll file that is also located in the wbem folder within the System32 folder. I know, but who da' thought it.
-
February 14th, 2003, 03:20 PM
#8
I'm glad you got it sorted - I've got to ask how on earth did you find out that was the problem?
Nick.
-
February 14th, 2003, 04:54 PM
#9
The way I found out that it was a .dll file was through guess work.
I have another system that runs XP Pro, I made a copy of the 'gpedit' file from it and replaced the one I was having trouble with. That didn't help any 'cause I kept getting the same error. Then I ran a search for 'gpedit' on the system (with PowerDesk), came up with the one in the System32 folder, but when I'd highlight it to open it, it'll give me a new error saying that "framedyn.dll' is missing. Did a new search for the 'framedyn.dll' file, came up with one, made a copy of it from the other computer to replace it, then try gpedit again, still got the first error that I listed earlier.
I thought to myself, "What gives!!" Then I thought, "What if I made a copy of the .dll file that's in the "wbem" folder and placed it in the System32 folder where gpedit is listed" I did, what did I have to lose, then tried gpedit again. This time it worked correctly, I guess that the original framedyn.dll file got deleted somehow.
So there it is, the whole complete story!
-
February 14th, 2003, 05:17 PM
#10
-
February 14th, 2003, 05:29 PM
#11
"CHEERS!!"
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|