Question

MAS 90 ODBC

Version 9 Workflow Laserfiche Answers Site Administration

Updated February 23, 2015

asked on February 20, 2015

Good Evening All,

I'm having an issue with a clients MAS90 ODBC connection to Laserfiche 9.2. Upgrade to the environment went perfectly, including updating the x64 MAS90 drivers for the x64 environment. When I perform the x64 ODBC connector tasks including the debug test under the ODBC32 manager (under Windows\System32.. the x64 location), I successfully connect to the MAS 90 databases.

I then went into Workflow designer and used a blank workflow and added a Query object and began performing the tasks to utilize the ODBC connection. I was able to select Windows ODBC, then was able to see the SOTAMAS90 ODBC installed instance under the System Tab, went through the rest of the setup with no apparent issues. When I attempted to test the connection from the Workflow Data Source Administrator. It times out.

Does anyone have any suggestions on why the ODBC connection is fine via x64 but not from within WF Designer or Workflow Admin Console ?

0 0

Answer

SELECTED ANSWER

replied on February 23, 2015

Good Morning All,

Thanks to Chris, Raymond, and a few others here on Answers, I found the solution that works.

If you are using MAS90 AKA Sage 100, and are running a x32 version of MAS90, you should use the x32 version of Laserfiche Workflow and the x32 driver for SOTAMAS.

If you are running a x64 version of MAS90, you should use the x64 version of Laserfiche Workflow.

Apparently, from what I found here, and from Sages site, the x64 version driver / application of MAS90 doesn't like the x32 environment in any way.

Thanks to Raymond for verifying the info I found, and Chris and others who helped lead me to a solution.

Regards,

Brian

1 0

replied on February 23, 2015

Glad to see you got it sorted Brian!

Guess the X32 bit burning in my brain wasn't too far off

0 0

Replies

replied on February 21, 2015

Hi Brian,

Did you install the X32 or X64 version of Laserfiche Workflow? This could have an impact?

1 0

replied on February 21, 2015

Good Morning Brian,

I only ask as I have had problems in the past using X64 ODBC connections. I can't remember what the exact details were (it was such a long time ago!) but installing LF in x32 and configuring the ODBC to use x32 resolved the issue. Don't know how feasible that is to try in your circumstances? But something is burning in the back of my brain on this one....

1 0

replied on February 21, 2015 • Show version history

Chris, that is good thinking, but we had the MAS90 connector working previously when we attempted the last upgrade where we found that the 8.2 to 9.0 broke a lot of the workflows because they required so much scripting. I have essentially re-wrote the workflows and incorporated all the new features of the 9.2 environment. The workflows are exceptionally fast compared to what it was before since the native processes have taken over from having to use scripts. The client and myself both recall that the issue was something very very small, like a grain of sand on the beach, but we both have lost all notes and records to the exact "thing".

Did you notice a reduction in performance using the x32 variant ?

Additionally, all documentation I am finding indicates that the system is going to force the 8.2 x32 version into a x64 version when I run the 9.2 installer unless I choose the x32 option. Wouldn't this result in a degraded performance install since the server achitecture is x64 ?

0 0

replied on February 23, 2015

The instance in which this applied in my situation, the ODBC lookup wasn't really in a load intensive environment. So performance isn't something that I particularly noticed. But on the face of it, there didn't seem much difference to be honest....

0 0

replied on February 23, 2015 • Show version history

Is your Workflow installation a 64 bit installation?

What is the path to your Workflow installation?

You should note that the CPU architecture of Mas90 should match the Workflow Server as well (x64 if WF is x64, x86 if Workflow is x86).

If you have a 64 bit WF installation, you need to use 64 bit data sources. See: https://support.laserfiche.com/KB/1012915 and the WF Admin Guide.

Are you getting a specific message when you try to connect?

1 0

replied on February 23, 2015

Hi Raymond,

The error was "This request operation sent to net.tcp://localhost:8085/ManagementService did not receive a reply within the configured timeout (00:00:30). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.

0 0

replied on February 23, 2015

What application are you getting this message from specifically? If from the Designer, is everything in the same domain?

Is 8085 a free port (you may need to run netstat -ab to determine this)?

If you are running an antivirus application on either end, try temporarily disabling or uninstalling it from both. We've had cases where that is the cause of this.

0 0

replied on February 21, 2015

Good Morning Chris,

It is the x64 version of Workflow. and we have installed the x64 drivers for MAS90 also, on an x64 Windows 2008 R2 box.

0 0

replied on February 21, 2015

Good Morning All,

I've uploaded 2 Videos, MAS90 Issue Part 1 and MAS90 Issue Part 2, which show the settings used on the active system. I had to use my sandbox for the video as we have already rolled back the production environment to the 8.2.x variant..

The settings are EXACTLY the same except as listed :

1. The Production environment had both the x32 and x64 SOTAMAS90 drivers installed.

2. In the Production environment, under the x64 ODBCAD32 (c:\Windows\System32) there was an entry for the SOTAMAS under both the USER DSN and the SYSTEM DSN. They both reference the proper driver dated 5-21-2013.

3. In the Production environment, under the x32 (C:\Windows\SysWOW64) there was a reference to the SOTAMAS90 driver dated 2012 which is installed when the Sage 100 ERP client is put on the Laserfiche Server (This client is required to facilitate connection between the Sage databases and any local program).

I've tried full removal of all Sage products from the LF server, and installation of just the x64 drivers. You still have to have the client installed. I then installed the client. same issue, connection times out / not connecting within the LF Data Source Manager when you try to test.

I also have tried deleting the user dsn. No change. I'm about to pull down a trial version of MAS90 into my sandbox, but before I do this, I wanted to see if there might be an answer that requires less extreme troubleshooting.

Again, the ODBC connections work perfectly under both x32 and x64 ODBCAD32 versions. The issue is inside the LF Data Source Manager

NOTE: I had to change the extension of the videos from .MP4 to TXT to get them to upload. You will need to rename the extension back to MP4.

Regards,

Brian

MAS90 Issue Part 1.txt (1.96 MB)

| Download

MAS90 Issue Part 2.txt (3.36 MB)

| Download

0 0

replied on February 21, 2015

Note, it is impossible to get a trial version of Sage 100 ERP (fka MAS90) without talking to a sales rep....sigh..

0 0

replied on February 21, 2015

Is there a reason you are using a User DSN rather than a system DSN?

0 0

replied on February 21, 2015

Chris,

I think the user DSN is a default setup that the Sage 100 ERP creates when the client installs. In the production environment, the former engineer had to set up the System DSN just as I have with the x64 variant

1 0

replied on February 21, 2015 • Show version history

ah ok. As long as you have the x64 components setup in system DSN.

I guess the answer here is going to come from someone who specializes in ODBC connections or an experienced DBA (not me sadly I'm strictly Laserfiche)

Guess that might be difficult on a Saturday...

0 0

replied on February 21, 2015

Your thoughts and ideas are appreciated :)

0 0

You are not allowed to follow up in this post.

Question

Question

MAS 90 ODBC

Answer

Replies

Sign in to reply to this post.