By genome - Saturday, February 14, 2015
|
Hi NiKo,
Your error is different form the one originally reported here and one that I have not come across before. Could be down to a problem MS Scripting install. Try this taken from http://support.microsoft.com/kb/949140 to ensure scripting components are registered correctly. You are running a 64-bit version of the Windows operating system, and you receive the error message that is mentioned in the "Symptoms" section while you are using the 32-bit scripting components- Click Start, click Run, type cmd, and then click OK.
- Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\vbscript.dll, and then press ENTER.
- Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\jscript.dll, and then press ENTER.
- Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\dispex.dll, and then press ENTER.
- Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\scrobj.dll, and then press ENTER.
- Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\scrrun.dll, and then press ENTER.
- Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\wshext.dll, and then press ENTER.
- Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\wshom.ocx, and then press ENTER.
|
|
By NiKo - Sunday, February 15, 2015
|
Step:
1. Done 2. Done .. passed 3. Done .. failed .. got error code 0x80004005 .. but upon searching, said it's for Windows XP .. I'm running Windows 8.1? 4. Done .. passed 5. Done .. passed 6. Done .. failed .. same error code as above 7. Done .. failed with error code 0x80040201 . seems to be related to Outlook PST file corruption. I don't use Outlook 8. Done .. failed with same error code as in #7
I read the MS Support article you linked to above ... It did not seem there was an option to Download and Reinstall Windows Script for Windows 8.1. When I tried searching on Windows Script in Windows 8.1, I got the reply "Hmmm…we seem to be experiencing technical difficulties, but we’re working on a solution right now. Please try again later."
|
By genome - Sunday, February 15, 2015
|
Ok just clutching a few more straws now. Tried this on my 32bit 8.1 and for example got same error in 6 unless I ran command prompt as administrator. (Start, click search and type the word 'command'. Right click command prompt icon and chose run as administrator). scrrun.dll happens to contain the scripting file system object that is failing. Also hope you are not running or have run Symantec/Norton Security. Historically this has messed up scripting.
|
|