MSSCript.ocx is either not installed or not regiestered error.....Help!!

Question

I get the error "MSScript.ocx is either not installed or not registered" when using VBscript. I ran "regsvr32 msscript.ocx" and it says "DllRegisterServer in msscript.ocx succedded" yet I still can't run vbscript in my program.

Any ideas why this is happening or what else needs to be done so I can use vbscript?

Answer 1

Hi K_Linville,

Welcome to the MSDN forum.

I assume you use VB.Net application. Please make sure that your application has target to 32bit and try to solve your issue by copying a 32-bit msscript.ocx into the folder “..\windows\syswow64 ” under 64-bit machine.

If this doesn’t work for you, I will suggest you to use Process.start methodto invoke VBScript in VB.Net application. Here is a sample: Running VbScript off of Vb net: http://social.msdn.microsoft.com/Forums/en-US/vbgeneral/thread/19571370-a4a3-4c9e-b66d-ddb67f361b8b/

Hope this helps.

---

Mark Liu-lxf [MSFT]
MSDN Community Support | Feedback to us

Answer 2

Thanks Mark,

   I am Working with K_Linville on the problem.  She is using ArcGIS software on a 32bit machine.  Everything is 32bit.  The OS is WinXp, the software and MSSCRIPT.OCX.

From within ArcMap,  A hyperlink, when clicked, invokes the script.

Function OpenLink ( [SP_ID]  )
Dim formFilter
formFilter = [SP_ID]
Dim objAccess
Set objAccess = CreateObject("Access.Application")
Set objAccess = GetObject("C:\Documents and Settings\.....\Desktop\......._DB\............accdb")
objAccess.DoCmd.OpenForm "frmSign", acNormal, ,("[SP_ID]=" & Chr(34) & formFilter &Chr(34))
End Function

The Parser is VBScript.

One clue... When we Click "Verify" to verify the script, ArcMap says "Error 0 on Line 0"  "MSScript... ... ...

So, it seems that it never even looks at the code.  The problem is before the script??

Thanks much for any help in advance.  wide screenshot next...

Answer 3

In addition to Mark,

there are two regsvr32 versions on a 64 bit machine. You must start the 32 bit version in the syswow64 folder even if the ocx alreday resides in this directory.

---

Armin

Answer 4

Just to reiterate, I am working on a 32bit machine with an OS of Windows XP.

Answer 5

Hi K_linville,

You need to share more information with us. Do you have the same situation as Trapeziux showed?

According to your description, you have registered the ocx file successfully.  And you have set the target platform to x86.

So did you add the reference to your application? If not, you can right click your application name in solution explorer windows -> add reference…->Browse -> choose the file.  At the same time, add the “Imports msscript.ocx” code to the top of the application.

By the way, how about the suggestion about saving all script code as a .vbs file and use process.start method invoke it instead of msscript.ocx?

I look forward your reply.

---

Mark Liu-lxf [MSFT]
MSDN Community Support | Feedback to us

Answer 6

Hi K_linville,

Any update abput my suggestion?

---

Mark Liu-lxf [MSFT]
MSDN Community Support | Feedback to us

Answer 7

Trapeziux and I have been working on this issue together and still have not found a successful solution. We tried to add the ocx to the application but the application would not allow it. We are working with ArcGIS10.1.

as far as your suggestion to save script as .vbs and use the process.start method, I am not familar with this. Can you give more information?

This error is associated with Windows XP 32bit because the vbscript I'm using works fine with Windows 7. But I am working on an XP machine and need to verify that the script can work on any machine our client may use.

Thank you in advance

Answer 8

Hi K_linville,

Using process.start can invoke any other software, so if you can save all the script to be a .vbs files, you can invoke it by sending the path to process.start method, please check this link:http://msdn.microsoft.com/en-us/library/system.diagnostics.process.start.aspx

>>This error is associated with Windows XP 32bit because the vbscript I'm using works fine with Windows 7.

As for the different OS caused the issue, I will suggest you to publish different versions of application for different OS.

Hope this helps. 

---

Mark Liu-lxf [MSFT]
MSDN Community Support | Feedback to us