If the ping test above failed, the telnet test will also fail. Compile the contents of three. BigLouie over 6 years ago. Most applications I support either upgrade prior versions or conflict with them when installed. Remote user is granted Read Only access through the share:

Uploader: Mikazilkree
Date Added: 25 November 2008
File Size: 54.57 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 28412
Price: Free* [*Free Regsitration Required]

On the Windows Start menu, click Run.

ODBC Drivers for MAS 90 and MAS 200

If you choose to use a drive letter, make sure that the drive letter will be mapped the next time you start up this workstation. Make sur ethe binary is stored at the specified path or debug it to check for problems with the binary or dependent.

Now, this was bit Windows 7, and I know there would be some adjustments for bit Windows 7 and even perhaps for XP, but those can wait. If you do not receive and ISAM error, and the report appears after renaming the registry key, the standard driver was being ams90.

You can then click OK there and return to WorldShip. Repeat the steps above for every remote workstation.

Install ODBC driver without workstation setup

Perform a simple ping test. The service can run on the system account; there is no reason to change the log in. Click the Configure button. Install ODBC driver without workstation setup.


Product Setup > Creating an ODBC Data Source Name

This option is available in Sage MAS 4. Being not a MAS90 fo, but a systems administrator responsible for the broader picture of ensuring the overall health and orderliness of jow servers and workstations, I have often found two things when users remove a program folder manually without a proper uninstallation of the application:.

This tests the ODBC server and returns the number of tables in the dictionary. I answered “No” and proceeded to complete the un-installation. Sage is not responsible for operation issues caused by incorrectly modifying your Windows Registry.

Enter the company code, user logon, and password. When printing a form or report from a Legacy module, all the remote user’s printers will appear. Database Directory — This is important.

It is best if you use a Mas900 address. If the report previews successfully, verify that other currently used reports and forms print and preview successfully.

A database logon prompt should appear. Run the registry editor. BigLouie over 6 years ago.

I could have saved some time by just looking to see if it stayed there in the first place, but either way, it was to no avail, as I received the same message as above: In some environments, not osbc the correct permissions may lead to a “Database logon failure” message when attempting to run reports.


This DLL behaved slightly differently from the uow one in that, while it remained in place in System32 until reboot, it disappeared upon reboot.

The second time the report is run, the.

In the Open field, type cmd Click OK. Did I miss anything, or was there as likely as not a simple ODBC installation routine hiding somewhere in the MAS90 folders on the server–or, worse yet, another post in this forum that explains all of this? Clear the Enable for All Users check box if it is selected. The setup routines for the MAS90 4.

From any workstation, start Sage MAS Note the Installed Directory Path. When printing a form or report from a Business Framework module, the jnstall can select Deferred only. Then there was just one more step, based on a hunch–the deletion of the license information under this registry key with the live informaiton replaced with dummy data, since the live data is our actual serial number: