One of the users posed the question: I can’t remember what the exact details were it was such a long time ago! Did you install the X32 or X64 version of Laserfiche Workflow? Most popular Newest to oldest Most popular Oldest to newest. MAS90 Issue Part 1.
|Date Added:||19 August 2015|
|File Size:||30.64 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
In some environments, not having the correct permissions may lead to a “Database logon failure” message when attempting to run reports. Upgrade to the environment went perfectly, including updating the x64 MAS90 drivers for the x64 environment.
In the Production environment, under the x32 C: Click Start to start the service, then click OK to exit Properties. Glad to see you got it sorted Brian! What application are you getting this message from specifically? This will have to be done each time the application is closed, such as when the server is shut down and restarted. It is the x64 version of Workflow.
64 bit ODBC driver install on SQL Server
Contact your system administrator for assistance. This confirms the bit drivers and all normal pre-req’s are installed. If you have a 64 bit WF installation, you need to use 64 bit data sources.
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. I have essentially re-wrote the workflows and incorporated all the new features of the 9.
64 Bit ODBC and Sage ERP (Formerly Sage ERP MAS 90 and )
Additionally, all documentation I am finding indicates that the system is going to force the 8. Server-Side Configuration as an Application or as a Service. You still have to have the client installed.
Temporarily disable the firewall to see if there is a blockage issue. Sage requires membership for participation – click to join. Sage is not responsible for 09 issues caused by incorrectly modifying your Windows security. Is your Workflow installation a 64 bit installation? But on the face of it, there didn’t seem much difference to be honest Modifying your Windows Registry incorrectly can severely affect system operations.
I’m not sure why the installer is throwing this error message when I definitely have Sage installed on that server. 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.
Thanks to Raymond for mss the info I found, and Chris and others who helped lead me to a solution. But something is burning in the back of my brain on this one If the service is set to always start Automatically, it will do so each time the server is shut down and restarted. I am able to run Sage on this computer – it’s def installed there! Guess the X32 bit burning in my brain wasn’t too far off.
Wayne Schulz is a Sage Consultant located in Connecticut. I can’t remember what the exact details were it was such a long time ago!
64 Bit ODBC and Sage 100 ERP (Formerly Sage ERP MAS 90 and 200)
We’ve had cases where that is the cause of this. Allow it to stay running. MAS90 Issue Part 1.
I’ve tried full removal of all Sage products from the LF server, and installation of just the x64 drivers. Modifying Windows security incorrectly can severely affect system operations.