Sage 100

Sage 100 version 2022 Standard after switching from 32 to 64 bit.  We have a button script in Shipping Data Entry that doesn't work on one computer.  The error is "cannot create the Windows Script OCX object:  MSScriptControl.ScriptControl.  Tried running RegCom64.bat from the administrator command prompt and that didn't help.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------

The following should be done on the affected workstation.

Check for the existence of the tsc64.dll on the workstation.  This is what is used in place of the MS script control when running 64-bit Sage 100.  It should exist under C:\ProgramData\Sage\Common Components and should be included in the RegCom64.bat file.  I believe there were issues in 2022 that impacted tsc64.dll being successfully copied to workstations.  If it is missing, check this directory on the server for it, MAS90\Migration\_Repository\_Repository_x64\wsc7.20\env\any\CommonProgramFiles\Sage\Common Components.

Try creating a test VBS file and executing.  All it needs to contain is MSGBOX "Test".  You can also try drop it on the cscript.exe and wscript.exe applications under C:\Windows\System32 and C:\Windows\SysWOW64 to make sure the script hosts are not being blocked.

Try executing the pvxcom.exe application.  You should find this under C:\ProgramData\Sage\Common Components.  You won't see any screens because it should close right away.  

Try running the MAS90\Home\OITest.exe application and confirm it can read from GL_Account table successfully.

------------------------------
David Speck II
Blytheco LLC
------------------------------

Thank you @David Speck II  !!

I was able to get this resolved.  By chance, the same user called again this morning and was getting an "Operation not yet implemented" error printing forms, so I uninstalled and re-installed the two Crystal run times and the Sage 100 workstation.  After re-installing workstation setup, the Crystal forms still didn't work, however, the button script worked.  I tracked down the forms error to an Azalea bar code font missing on the computer.   So, it seems there were several issues on this computer:  Missing fonts, and missing or unregistered DLLs.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------

Original Message:
Sent: 05-07-2024 12:40
From: David Speck II
Subject: Button Script Issue After Switching to 64-Bit

The following should be done on the affected workstation.

Check for the existence of the tsc64.dll on the workstation.  This is what is used in place of the MS script control when running 64-bit Sage 100.  It should exist under C:\ProgramData\Sage\Common Components and should be included in the RegCom64.bat file.  I believe there were issues in 2022 that impacted tsc64.dll being successfully copied to workstations.  If it is missing, check this directory on the server for it, MAS90\Migration\_Repository\_Repository_x64\wsc7.20\env\any\CommonProgramFiles\Sage\Common Components.

Try creating a test VBS file and executing.  All it needs to contain is MSGBOX "Test".  You can also try drop it on the cscript.exe and wscript.exe applications under C:\Windows\System32 and C:\Windows\SysWOW64 to make sure the script hosts are not being blocked.

Try executing the pvxcom.exe application.  You should find this under C:\ProgramData\Sage\Common Components.  You won't see any screens because it should close right away.  

Try running the MAS90\Home\OITest.exe application and confirm it can read from GL_Account table successfully.

------------------------------
David Speck II
Blytheco LLC
------------------------------