Connector Timeout & Max Lanpak Message (4 replies)
Wesley, I think you're correct in saying this is a network issue (though I am a bit confused as to where the various servers are).
- Where in respect to the server on which IMan is installed is the Sage300 shared data?
- How is Sage300 installed on the IMan server? I would highly recommend Sage300 is installed locally.
- Under which windows user is the IMan set to run? (Admin Console, Permissions)
FYI All communication between IMan & Sage300 is made either in the Realisable Data Service (this is the probable location of your error) or IntEngine (when processing), so altering the timeout settings will make no difference.
Thanks
The two offices are 150 KM apart, connected by a dedicated 5Mbps connection.
1. Our Iman install is on the webserver (WPGWS01) located in Winnipeg, shared data is located on the server in the different office located in Morden (MDNAccpac), and the back end database server for Accpac is in that same office (MDNDB01).
2. We installed a local copy of Sage300 on the Iman server, pointing to the shared data in the other office (Sage300 is quite a bit slower, but does operate).
3. The IMan permissions are running as an administrator account that has full permissions to pretty much everything on the network (we were hoping we could turn down the permissions once we were sure permissions were not an issue).
If it's suspected the network is the issue, we could reinstall on that same server to take it out of the equation. I'm assuming that a DB read across the network to pull our sales information may be more tolerant to latency than the tighter connection into Sage300?
Wesley, thanks for the feedback.
I suspect you've got a name resolution issue (you could put entries in to the hosts file for both WPGWS01 & MDNDB01 to see if it makes a difference).
However, due to the amount of Sage300 chatter (both database and network) I would install IMan in the Morden subnet (something which you've already realised). Not only will you see better performance, but the chance of record locking conflicts, with our users will be reduced...pushing 100s of transactions in via an automated tool greatly increases the chance of record locks vs. someone entering manually.
Permissions - See the Admin Guide...you don't need Admin.
Hope this helps.
Installed on the same subnet and all the problems have been resolved.
Thanks for the assistance,
-W
I have recently installed the Iman software on our IT infrastructure, and we are running into some problems with the software giving timeout errors when loading transforms/connectors that connect to our Accpac installation. We have been dealing with our Sage partner to setup and configure the software but they have ran out of solutions.
We fairly consistently (approx. 90% of the time) get a combination of these two error messages. We have 9 more licences than have current users, so this leads us to think the network infrastructure is to blame in timeouts, and missing licence info. We have also adjusted the site IIS timeout to 4 minutes, as well as the timeout within the Iman Administration console to the same. When we start getting the LanPak message, we can go re-enter the permissions in the admin console, save and restart the app pool, and then we start getting the other message.
The server configuration is as follows.
We have an database server in one of our offices that houses our Accpac databases, along with a terminal server in that location with an Accpac installation (where our licence info is stored and users remote into this server to run Accpac).
We have a dedicated web server in another office that we have installed Accpac on, pointing to the licence info on our main server, as well as have installed Iman here. Accpac loads up fine, although quite a bit slower than on the main machine. The Iman software works fine for everything else we have tested, but cannot open any sage connectors. The web server is located in the office we will be pulling our integration data from.
The network connection itself between the offices is on a vlan, with an average ping time of about 32ms between servers.