Scripting

A client is getting ""Unable to set MSScript Properties - Error 88 Invalid/Unknown Property Name"" when clicking on a button to execute a linked VBScript. This is in Sage 100 ERP 2015 Premium (SQL version). The same script works fine from the server and from other workstations. The script will not work from his workstation in client/server or peer-to-peer mode. That same workstation can execute Sage 100 ERP 2013 version (from backup on that same server) and the script works fine. The workstation is the same regardless of the version of Sage 100 we're running. The server is the same and both 2015 and 2013 are running on the same server. The script works in 2013 both peer-to-peer and client/server but does not work in 2015 from that workstation at all. What would be the difference? Is there some issue with SQL as the backend that would cause this problem? Any ideas? The script does not get far enough to actually use any objects. Thanks - Phil

BTW,all the user, role, system and company settings are the same between 2013 and 2015.

Is the button set to run on the client or on the server? On that workstation did you try logging into MAS as a different user?

It is set to run on the client, same as it was on 2013. It does not work for any user logged into Sage 100. I was attempting today as a Sage 100 admin. It also does not seem to matter what Windows user logs in. I was logged into the workstation as a domain admin and it failed.

I'd try reinstalling the client and on that machine make sure that UAC is off, windows firewall is off, etc just to rule out all possibilities. Also make sure that the 2015 version is set to run as administrator. Its sounds like something is blocking it. Did you add a debugprint line at the beginning of the script to see if it gets that far?

I'm a little embarrassed here. I wrote that it was VBScript, but the script I was testing is actually PVXScript. This is the second time at 5.20 (2015) that I have found that PVXScript is not supported. Does anyone know what the policy is about PVXScript? There are some things that are just easier to do with PVXScript, and we are finding that VBScript is not always supported on new workstations.

I was able to figure out the problem. Apparently with Sage 100 ERP 2015 they have updated the PVXScript.DLL. For some reason, on the workstation where the script was failing, they had an older and smaller PVXScript.DLL in the Sage\Common Components folder. I copied the newer, larger PVXScript.DLL from the home folder to the Common Components folder and registered it there. Now the PVXScript works.

My guess is that uninstalling both the 2013 and the 2015 workstation on that machine - and making sure it removed all DLLS, then reinstalling only the 2015 version would have fixed the problem. So Nicole's solution probably would have fixed it, also.

Glad you got it fixed Phil!