ERROR : ActiveX component can't create object: 'Scripting.FileSystemObject'


Several customers have had this problem. Thanks to Pete Bjordahl for finding the solution:

After some digging I found this post (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=932473&SiteID=1) on a Visual C++ site:

>>>>>>

I hope you have figured out your problem by now. I can't believe that Microsoft hasn't put a fix out there now that they know what is going on.

Anyway, the problem is that the Scripting.FileSystemObject registry key does not have an owner assigned. From the command prompt, go to regedit and try to access it. If it tells you that you can't access it but you can change the permissions on it; don't believe that. You have to go to Advanced and find out that there is no owner assigned. Change the owner to Administrator (make sure to CheckNames). You'll also have to change the CLSID key in the same manner. Also, there are two other keys that I wasn't able to access:

Scripting.Dictionary and Scripting.Encode. They didn't seem to affect creating projects in Visual Studio.NET but who knows what else was affected?

I don't know what the cause of this problem was but it wasn't my doing. I hope Microsoft is working on it...
>>>>>

Since the error was the same I tried the fix and indeed the problem was solved! What the hell MS! I want my weekend back. Hope this helps others out there with the problem.

References

[1] (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=932473&SiteID=1)

[2] (http://blogs.msdn.com/jledgard/archive/2004/08/23/automation-server-can-t-create-object-and-other-vs-2002-2003-start-page-problems-issues-and-bugs.aspx)

This page was last modified 09:25, 10 Aug 2007.
This page has been accessed 5774 times.