Sage 100

We have a client getting ""error connecting to MAS BOI: This module is in trial mode."" They are on MAS 200 4.5. No key to install on this version. Company Maintenance > Preferences > Allow External Access is checked. Ran OITest.exe program and got the ""Object interface is working correctly"" dialog box and the main account table and key columns are listed. The customer number is the new one and the keys are current. InfoSource is the only KB that returned anything and I have exhausted what was there that applied. The third party has this plugin running fine on other 4.5 installs. Anyone seen this before or have an idea what may be wrong. @Sage 100 Advanced Scripting

@Sage100AdvancedScripting

Thanks, I didn't know you had to run the items after Sage together.

I had the customer start a case with Sage but no one has responded. Does anyone know who at Sage Tech Support would be the Go to person for BOI? Thanks @SAGE 100 Advanced Scripting

Brian Reddemman but I didn't send you ok. The OITest.exe does a simple G/L test. So which module is your client running their BOI code on? Can you post a code snippet of the suspected area where the error is occurring

Might be hard to get code snippet if third party. OITest only accesses GL. Is the error a red herring or is the application try to accesses an unlicensed module?

@AlnoorCassim, thanks for replying. I think I will just let the Sage support handle it there way. I don't want to drop a name that shouldn't be out here. The BOI code belongs to a third party called Exactor that does Sales Tax similar to Avalara. The client found this product on there own and came to me to determine if it could be interfaced. I suggested it would likely be expensive and suggested they check out Avalara. They indicated they had done that and had a bad taste in their mouth about it. I checked and determined Exactor already had done a BOI interface which was in use by several clients. As there wasn't any real need to be involved, I left it with the client's IT and Exactor. They have kept me in the email loop and when the error appeared, I checked and found nothing and suggested the customer start a case with Sage. They did but haven't heard back. I am going to suggest the client lean on Exactor to use their BOI resources. @MyronStevenson, the modules a Tax interface would need are all licensed.