SAGE 300 ERP 2014, Installed on RDP cluster. Needs a Client server install. (non-workstation).

SOLVED

We have a SAGE 300 ERP 2014  installation, and basically all installs are Workstation installs.  And work with no problem,  except for one instance.  We have a ERP solution called NDUSTRIOS which integrates with SAGE when we post transactions.   When we have users use the Remote Desktop a normal workstation install works fine. 

BUT, the best and fastest method is using the Remote APP, of Terminal server, and in this situation, it needs a local install of the files.   It tries to install it but the workstation install files are transitory, and no executable files exist on the server itself (UNC paths don't work with RemoteAPPs very well).   

So my problem I have completely uninstalled the Workstation install of SAGE 300 ERP. and then completely reinstalled from the SAGE 300 ERP 2014 install.   Installed patches to version 3 (Same as the working Workstation installs). Verified the program (pointing locally) and Data paths(Pointing to existing Sage Server) in the Registry.   I can load Database Setup, log in and verify a Database. No problem.  But if I try and launch the SAGE 300 ERP, it shows as below.   

SAGE 300 Error

And in the Event Viewer is says  as below. 

ib.c - 3726 - IB - Bad HPIB in ibUnloadLangDlls

It is installed to folder C:\Sage\Sage ERP Accpac. 

And is launched as Administrator. 

Does anyone have any suggestions. ??

Parents Reply
  • 0 in reply to SteveFromTO

    This application is running on a cluster of 4 Terminal servers. We a have a standard service/admin account to configure and run under.   I had previously all 4 running with Sage300ERP Workstation,  with no problems.   All 4 could run SAGE 300ERP in workstation mode. (from shared folders, one for program, one for Data.)   all 4 could launch it locally.   2 were configured as RD servers and 2 as REMOTE APP servers.   and Sage300ERP launched successfully and could be logged into with no problem.   I took one of the Remote App servers, with a working Sage 300ERP Workstation install.  And redid it to have a Client Server install with locally installed programs. 

    TThat's when I started to get this error. With the same credentials and the same server that had no problem running the workstation version.

    The other servers still launch and log  in no problem to sage. 

Children