Any 3rd party add-ons installed on the server that have client components that need to be installed on the workstations?

If I recall correctly, Avalara or anything that deals with encryption might require additional files on the workstation.

Check NTFS permissions too, the user running the script should be able to read and write within the MAS90 directory on the server.

Are you sure your path is pointing to the MAS90 directory on the server?

Are you sure the error is occurring on the "Set oSS = oScript.NewObject("SY_Session")" line and not a line further down where you are trying to get a new object to something like CI_Item_Bus?

Any 3rd party add-ons installed on the server that have client components that need to be installed on the workstations?

If I recall correctly, Avalara or anything that deals with encryption might require additional files on the workstation.

Check NTFS permissions too, the user running the script should be able to read and write within the MAS90 directory on the server.

Are you sure your path is pointing to the MAS90 directory on the server?

Are you sure the error is occurring on the "Set oSS = oScript.NewObject("SY_Session")" line and not a line further down where you are trying to get a new object to something like CI_Item_Bus?

We aren't using any third-party add-ons that have client components.

This user is an Administrator and able to create/edit/delete files in the MAS90 directory.

I made a .vbs file with just the following code. The error is on line 3...it never makes it to line 4, which should display an alert.

Set oScript = CreateObject("ProvideX.Script")
oScript.Init("\\10.0.0.206\Sage\MAS90")
Set oSS = oScript.NewObject("SY_Session")
MsgBox("Done")

Try "\\10.0.0.206\Sage\MAS90\Home" instead

I have tried both. The original code that works on our other workstations doesn't contain the "\Home".

Every version of my external scripts point to the MAS90\Home directory on the server. I usually read the registry's SOTAMAS90 DSN record to determine path to MAS90 and then append "\Home" to it before passing it to the Init method.

I wonder if that might be the issue. This is the first new workstation that I have set up since we moved to the SQL version of Sage, so it's the first that does not have a SOTAMAS90 DSN.

i doubt the lack of the DSN is the issue since you are actually specifying the path.

I don't have much experience dealing with the SQL version of sage 100 and so i don't know what components are required for an external script to be able to start the SY_Session class

Typically, the first thing to check is the path, then making sure that the company you want to access has the "Allow External Access" check box checked under Company Maintenance. 

Can you launch sage 100 normally from the new workstation and perform tasks like item inquiry or sales order entry?

Yes, Sage launches and I don't have any issues performing any tasks.

Well, I finally got this resolved. Not really sure what fixed it, but after uninstalling and reinstalling Sage 100 Workstation several times, it suddenly worked.