Scripting

I have a BOI (VB dotNet) app that worked on 4.50 SQL, that is now failing to create the session object on Sage 100 2014 premium. oSOOrder = oScript.NewObject(""SO_SalesOrder_bus"", oSS) generates error: Exception from HRESULT: 0x80020009 (DISP_E_EXCEPTION) Allow external access is on, sota.ini and pvx.ini all look correct, and app is running on the server. Any ideas?

did you check to make sure if oSS is a valid object? something above that line might have failed causing an error the first time you try to use oSS

oSS is valid

Is Avatax installed?

no avatax

Had a similar issue two weeks ago on this. Still unresolved. New SQL Server, same 4.50 install. we can create GL BOI objects, but nothing involving Sales Order or invoice data entry. Does Sage's test BOI work?

Phil I'm pretty sure this is the BOI issue on 2013 SQL higher issue that some others here ran into: There are 2 ways to fix - see attached

MAS90_VB2 sales order works. SQL Client already at 10. massql.settings change did not change the behavior

After further digging, I discovered that the BOI logon routine was adding a third character (blank) to the two letter username. Gave it a 3 letter username, and now the login fails with oSS.sLastErrorMessage = ""Warning: Object only available in online environment."" after If CBool(oSS.nLogon()) Then