Error Activex Component Can Create Object Wscript Shell
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn
Activex Component Can't Create Object Windows 7 64 Bit
more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags activex component can't create object vbscript Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you,
Activex Component Can't Create Object Internet Explorer 11
helping each other. Join them; it only takes a minute: Sign up Error: ActiveX Component Can't Create Object Scripting.FileSystemObject up vote 4 down vote favorite 2 I have a simple vbs-file on my drive c: with following content: http://www.symantec.com/connect/forums/error-activex-component-cannot-create-object-wscriptshell-activex-component-cannot-create-obj Set objShell = CreateObject("Scripting.FileSystemObject") When I'm trying to launch it, I get error c:\fso.vbs(1, 1) Microsoft VBScript runtime error: ActiveX component can't create object: 'Scripting.FileSystemObject' I tried to login as admin and execute wscript -regserver, but didn't help. Can someone help me please? vbscript activex filesystemobject share|improve this question asked Mar 28 '11 at 9:27 vmg 3,85273153 add a comment| 2 Answers 2 active oldest votes up vote 11 down vote accepted Assuming you are logged http://stackoverflow.com/questions/5457000/error-activex-component-cant-create-object-scripting-filesystemobject in as Admin, please have a look in registry for Scripting.FileSystemObject under HKCR. If you can not find this PROGID then you are missing the required files or the component is disabled (not registered). Scripting.FileSystemObject is implemented in scrrun.dll. share|improve this answer edited Oct 22 '12 at 13:04 bluish 9,4041269126 answered Mar 28 '11 at 9:42 byte 1,04511029 4 Yes, you are right, I reregistered scrrun'dll regsvr32 /i "c:\windows\system32\scrrun.dll" and it works! Thanks! –vmg Mar 28 '11 at 9:55 Also disable you virusscanner! –Dabblernl Aug 17 '12 at 20:41 3 If you get an error message "sccrun.dll was loaded, but the DllInstall entry point was not found" then run just run: regsvr32 "c:\windows\system32\scrrun.dll" –StormPooper Nov 15 '12 at 10:50 I just run regsvr32 "c:\windows\system32\scrrun.dll" but then in VB I get same error. –mggSoft Feb 20 '13 at 18:54 add a comment| up vote 0 down vote If re-registering scrrun.dll doesn't fix it, you might have to re-register a lot of other dependencies. The easiest way to do that is with MS Fixit 50123: http://go.microsoft.com/?linkid=9666880 Run that, then try your FSO call again. This is the only thing that worked for me on a couple client computers that had various fake AV programs and reg cleaners. share|improve this answer answered Aug 31 '15 at 5:04 shawn 1 add a comment| Your Answer
YouHadMeAtHelloWorldDecember 12, 200710 0 0 0 I had two posts to resolve an issue with applications that use a 32-bit COM object in a 64-bit OS. Workaround for executable, and ASP.Net. I recently helped someone who https://blogs.msdn.microsoft.com/helloworld/2007/12/12/activex-component-cant-create-object-when-creating-a-32-com-object-in-a-64-bit-machine/ had the same problem, but with a VB Script application, executed with cscript.exe. This VB script application uses a 32-bit COM object and failed to run on a 64-bit OS. The error, Microsoft VBScript runtime error: ActiveX component can't create object: ‘XXXXXX'. To fix the issue, the script must be executed with the right executable. There are two cscript.exe in the 64-bit OSes. One is located at %WINDOWS%\System32, and the second one is located at %WINDOWS%\SysWOW64. The one activex component under System32, is a 64-bit version. The one under SysWOW64 is the 32-bit version. Run the VBS application using the 32-bit application. Why System32 contains 64-bit binaries, and SysWOW64 contains 32-bit is another story, but there is a very good reason behind it, backward compatibility. 🙂
Tags .Net Framework 64-bit com interop Comments (10) Cancel reply Name * Email * Website Brett says: November 14, 2008 at 11:42 am Nice one, thanks -- had us stumped for a activex component can bit. I guess "System32" was an unfortunate choice of names. -Brett Reply Lonnie says: April 1, 2009 at 4:20 pm > Why System32 contains 64-bit binaries, and SysWOW64 contains 32-bit is another story, but there is a very good reason behind it, backward compatibility. 🙂 Seems consistent with Microsoft's other conventions, like selecting "Start" to shutdown your computer. Reply YouHadMeAtHelloWorld says: April 2, 2009 at 5:15 pm @Lonnie You turned the ignition key to shut off you car. 🙂 It was based on usability. http://blogs.msdn.com/oldnewthing/archive/2003/07/22/54559.aspx Reply Joacim says: June 5, 2009 at 7:33 am Thanks for the info. I have an additional question. If you run the script from a 32-bit 2003 server and it has to interact with a DC that is on a 2008 server what do you need to do to get it to work then? Reply YouHadMeAtHelloWorld says: June 5, 2009 at 12:59 pm @Joacim: I am not sure, but I think that should be fine. Reply Joacim says: June 8, 2009 at 3:06 am Well it doesn't for some reason. I guess you somehow have to point it to the %WINDOWS%SysWOW64 catalogue in the script. I assume that %WINDOWS%System32 would be default on the 2008 64-bit machine, or should it be able to identify that automatically? Reply YouHadMeAtHelloWorld says: June 30, 2009 at 3:47 pm @Joacim: You have to point to %WINDOWS%SysWOW64. That folder contains 32-bit i