We moved a client's Sage over to a new server - They are now using Sage 2015 Advanced.  We had a program in place that utilizes BOI and have had a problem since the move.

The program uses BOI through BOTH DCOM and 'traditional' - we are ONLY experiencing this problem when attempting to create an SY_SESSION object using the 'traditional' method. 

I created a small script (below) to try and troubleshoot, but the attempt to create the SY_SESSION object throws <NewObject Error: 200>.  This happens EVEN on the actual Sage server.  (Again, we have no problem creating the session object using DCOM).  I've seen error 200's when creating module objects - this was usually caused by the module not being setup or something similar, but I've never seen it when attempting to create the session object.  Any help with this would be greatly appreciated as I'm kind of stuck at this point :(  Thanks. 

Set oScript = CreateObject("Providex.Script")

oScript.Init("\\server\mas90")

SET oSS = oScript.NewObject("SY_Session")  --> Throws new object error 200