Does this mean BOI and external scripting is not feasible running the 64 bit version of Sage 100?

Yes, you can use scripting with the 64-bit version of Sage 100.  We have tested this here internally.  Kevin M, we are looking at why the SPC implementation is not allowing you to.  Thanks for bringing this up here, and stay tuned as we have a look at the image and see what the issue is.

Thanks

E

Thanks Elliott,

While we don't need to run in 64-bit, I didn't want to be satisfied by the change to 32-bit... posting here and giving Sage time to fix it as a non-urgent issue.

So PVXCOM (copy of ProvideX with a COM UI) is still 32 bit as is the host scripting component used for internal scripting? Does the 64 bit version of Sage 100 use a 64 bit ODBC driver?

Both the PVXCOM and scripting components are 64-bit when using the 64-bit version of Sage 100 and 32-bit when using the 32-bit version of Sage 100. Both 32-bit and 64-bit ODBC drivers are installed to enable access from both 32-bit and 64-bit applications

COM / OLE is 32 bit. Are you saying the ProvideX 64 bit version no longer supports COM / OLE?

"COM / OLE is 32 bit." - That statement is incorrect.

learn.microsoft.com/.../the-component-object-model.

The original question/issue stemmed from our Script Host component not getting registered properly and is something we are looking into. As to your question, it was previously answered; Scripting (COM/OLE) is supported using Sage 100 x64. In this scenario, the full COM component stack is x64 down to the language libraries. Note: Microsoft provides both x86 and x64 scripting language libraries (vbscript.dll/jscript9.dll), which can be found in Windows\SysWOW64 and Windows\System32 respectively.

It seems 64 bit COM/OLE is a small world with only VBA and JavaScript supporting it. It doesn't look promising for C# and OLEDB for 64 bit seems to have issues and not recommended. Would moving to .NET be a rewrite? I've seen 64 bit apps calling 32 bit COM objects. My vote for 64 bit ProvideX would be supporting 32 bit COM as an option.

Will 32 bit ProvideX be around for awhile?

So there is no current resolution for this? We are also having this issue with the 64bit version of Sage 2022.

You should find a file called "RegCom64.bat" in the folder "C:\ProgramData\Sage\Common Components". Close down Sage 100 if running and run this batch file. The batch file will self elevate and perform the COM registration(s). Note: you will need to be an administrator or a user that is part of the administrator group for this to register the components correctly.

If this does not resolve the issue then please report back so we can research further.

Regards,
Russell

You should find a file called "RegCom64.bat" in the folder "C:\ProgramData\Sage\Common Components". Close down Sage 100 if running and run this batch file. The batch file will self elevate and perform the COM registration(s). Note: you will need to be an administrator or a user that is part of the administrator group for this to register the components correctly.

If this does not resolve the issue then please report back so we can research further.

Regards,
Russell

So that didn't work initially, the batch file was stating it couldn't find tsc64.dll. I was able to locate this DLL on the server under ..MAS90\Migration\_Repository\_Repository_x64\wsc7.10\env\any\CommonProgramFiles\Sage\Common Components.

Copied this to all clients' ProgramData, then ran the RegCom64.bat and am no longer receiving this error on any of the clients! Thank you so much!!!!

Glad you were able to sort it, and sorry for the inconvenience. We will be working to resolve the workstation install issue.

Regards,
Russell