Sage 100

Problem below was solved on Friday, BUT...the solution seems to only work on one client. Can't figure out what would cause the same error on a different client running the same script after the massql.settings file has been corrected. I have checked the DLLs on this other machine and they are the same as on the server and as the client where the script runs. The client having the problem is a Windows 7 32-bit machine. The one that works is XP. The original problem: BOI problem with SAGE 100 Premium 2013 (4.5.00.4). BOI script runs on server, but not on client. Receiving ""<NewObject Error: 200>"". Have copied ssleay32.dll and libeay32.dll to program files\common files\sage\common components directory as recommended on SageCity posts. The files on the client are the same as those on the server. VB script fails on fourth line of code: Set oScript = CreateObject(""ProvideX.Script"") PathHome = ""\\SERVER\Sage\Sage 100 Premium ERP\MAS90\Home"" oScript.Init(PathHome) Set oSS = oScript.NewObject(""SY_Session"") 'THIS LINE GENERATES THE ERROR ON THE CLIENT

Is the error on the Windows 7 machine happening on same line? If it's the CreateObject line you could try registering pvxscript dot DLL then run pvxcom dot EXE. It's located under Common Components folder.

The error on the Windows 7 machine is happening on the same line, the CreateObject line. I registered the pvxscript DLL and ran the pvxcom EXE. Tried running the test script again and no go. I made the user a local admin, did it all again - still no go. Same NewObject Error 200 problem. Any other ideas?