x Want to participate? Join the group to interact
Options
  • Replies 5 replies
  • Subscribers 87 subscribers
  • Views 1524 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
Kevin M

OITest.exe error "OI Access Failed"... v2020 Premium

Posted By

We are getting this error after an upgrade to v2020.1 Premium, running directly from the server, As Admin, using a server admin login and Sage user with All Access.

I've gone through KB46242 and KB31463 with no change. 

  • Allow External Access is enabled in the company code I am testing. 
  • SOTA.INI and MASSQL.Settings both reference "SQL Server Native Client 11.0", which is in the server's list of both 32 and 64 bit ODBC drivers. 
  • The workstation path referenced the 10.0 native client but changing to 11.0 had no effect.
  • Per KB55047 (for a slightly different error) I made sure I can create a file in \MAS90\Home\Lib\...

I'll be creating a case, but if anyone has any hints / tips, they would be appreciated.

(The problem we are trying to solve is a 3rd party program interface through BOI... I've been told that this Sage tool tests if the BOI interface is working properly.  Sage 100 itself is working fine).

Parents Reply
  • in reply to connex

    What do you mean about a new port setting?  Sage 100 proper is working fine (so there are no firewall issues), and we're running the OITest from the Sage server.

    AV was completely uninstalled during testing.

Children
  • in reply to Kevin M

    I'm not sure whether the customer issue is fixed, but we traced the OITest error to a blank PVX.INI in the MAS90\Home folder on the Sage server.  Restoring from a backup copy (from before the live upgrade) allowed a successful test.

*Community Hub is the new name for Sage City