How to install and configure the Client Server ODBC driver (CS ODBC) for Sage MAS 200 versions 4.10.1 through 4.50 How to install and configure the Client Server ODBC driver (CS ODBC) for Sage MAS 200 versions 4.10.1 through 4.50 Products Sage 100 Description How to install and configure the Client/Server ODBC driver (CS ODBC) for retired Sage 100 Advanced (formerly Sage MAS 200) versions 4.10.1 through 4.50 The Client/Server ODBC Driver allows workstations to print Crystal forms and reports using server-side ODBC processing. This option is available in Sage MAS 200 4.10.1 and later. The instructions below should cover retired Sage 100 (formerly Sage MAS 200) versions 4.10.1 through 4.50.

1. Oracle Odbc Drivers

For Sage 100 Advanced versions 2013 and higher, see the Related Resources section in this document. Disclaimer Network Warning This solution requires advanced knowledge of your network. Contact your system administrator for assistance. Modifying Windows security incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows security. Always create a backup of your data before proceeding with advanced solutions. Operating System Warning This solution requires advanced knowledge of your computer's operating system.

Contact your system administrator for assistance. Modifying your Windows Registry incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows Registry. Always create a backup of your data before proceeding with advanced solutions. Resolution Note: Remote workstations running over a WAN link connected through a VPN are ideal candidates for using the CS ODBC Driver. Forms and reports will print significantly faster from remote workstations. Remote workstations that currently use the Sage implementation of Crystal Enterprise (Web Reports) on versions earlier than 4.40 should switch to the CS ODBC Driver.

The CS ODBC Driver has been tested and designed for use with Crystal reports and forms printed through the Sage MAS 200 Business Desktop (Launcher). It has not been tested for use with other ODBC applications (for example, SQL Server queries and Access queries).

Sage Software does not support the use of other ODBC applications that may attempt to use the CS ODBC driver. Sage MAS 200 Setup Enable the CSODBC Driver:. From any workstation, start Sage MAS 200. Expand Library Master and Setup. Double-click System Configuration.

Click the ODBC tab. Select the Enable C/S ODBC Driver check box. In the ODBC Server Name field, enter the server name or the IP address. Enter 20222 for the ODBC server port. Clear the Enable for All Users check box if it is selected. Click the Accept button. Install CS ODBC Server service and set to Automatic:.

Install the CS ODBC Driver service on the server. Browse to. Mas90 home lib appserve, and double-click CSODBCService.exe. This creates the 'Providex IO Service' entry in the Windows Services applet. On the Windows Start menu, click Run. In the Open field, type SERVICES.MSC. Click OK.

This starts the Services applet. Double-click the ' Provide IO Service' to open the Properties window. On the General tab, set the service startup type to Automatic. Click the Start button, and verify that the service starts successfully. Click OK to close the ProvideX IO Service Properties window. Note: The service can run on the system account; there is no reason to change the log in. Configure the Sage MAS 200 user logon:.

At the server, start a Sage MAS 200 workstation. Expand Library Master and Main. Double-click User Maintenance. Select the first remote user and click the Preferences tab. Select the Enable C/S ODBC Driver check box. Clear the Use Crystal Web Reports check box if it selected.

Click the Accept button. Repeat above steps for every remote user.

Test the CS driver on the server:. Exit Sage MAS 200 workstation, and then start it again. Log on as a CS ODBC enabled user. Expand Library Master and Reports. Double-click Company Listing, and preview the report.

If an ISAM error occurs, review all previous settings, paying close attention to step 1.g. If the report previews successfully, close the report but do not exit Sage MAS 200. Run the registry editor. Rename the following key: HKLM SOFTWARE Sage Software 'ProvideX File Server.

(Rename only the ProvideX File Server key.). Preview the company listing report again.

If you receive an ISAM error, that user is enabled, and the CS ODBC driver is installed and configured correctly. Rename the ProvideX File Server key back to the original name, and test again. If you do not receive and ISAM error, and the report appears after renaming the registry key, the standard driver was being used. Double check the user log in preferences and the system configuration ODBC tab. Exit, and then restart the workstation. Test printing from remote workstations:. From a remote workstation, start Sage MAS 200.

Download the latest driver, firmware, and software for your HP Pavilion g4-1015dx Notebook PC.This is HP's official website to download drivers free of cost for. Update your HP computer to have the latest software and drivers available. (audio), or video (graphics) driver on the HP Software & Drivers download page? Download the latest driver, firmware, and software for your HP Pavilion g4-2039tx Notebook PC.This is HP's official website to download drivers free of cost for. Tonymacx86.com: Home of the CustoMac Buyer's Guide, iBoot, MultiBeast, UniBeast, and the world's most helpful #hackintosh #mac #osx. Easily find and download software and drivers for your HP products including pcs, laptops, desktops, printers, tablets, apps and services from HP Customer Support. Let's identify your product to get started.

Expand Library Master and Reports. Double-click Company Listing, and preview the report. If the report previews successfully, verify that other currently used reports and forms print and preview successfully. Repeat the steps above for every remote workstation. Server Side Troubleshooting if needed Verify that the ProvideX IO service is set to listen on port 20222:. On the Windows Start menu, click Run. In the Open field, type cmd.

Click OK. Enter the following command, and then press ENTER: netstat -a -n more. A numerical listing by port number appears: Verify that port 20222 is listed in the Local Address column.

If it does not appear, press the spacebar to list more results. If 20222 is not listed in the Local Address column, the client server ODBC driver is not running.

Troubleshoot the ProvideX IO Server service. After verifying that port 20222 is listening properly, type exit. Press ENTER to exit the command prompt. Configure Firewall and Router Policies: Configure the corporate firewall and router policies to allow port 20222 to be accessible from the remote workstations. If personal firewall software is also used on the server, configure it to allow port 20222 to be accessible from the remote workstations.

Configure the share for Sage MAS 200: On the server, a share exists above the. Mas90 folder that allows Sage MAS 200 LAN users and those connected through Terminal Services and Citrix to print Crystal reports and forms.

For the remote user, note the different scenarios of share permissions:. Remote user is granted Read/Write access through the share:.

When printing a form or report from a Business Framework module, the user can either print to any of his or her Windows printers, or select Deferred. If Deferred is selected, the user can then print from Deferred to the printer. When printing a form or report from a legacy module, all the remote user's printers appear. The Deferred printing option is not available. Remote user is granted Read Only access through the share:. When printing a form or report from a Business Framework module, the user can either print to any of his or her Windows printers, or select Deferred. However, if Deferred is selected, the user will not be able to print from Deferred to his or her printer.

Another user with Read/Write access through the share will need to print the Deferred report. When printing a form or report from a Legacy module, all the remote user's printers will appear. The Deferred printing option will not be available.

Remoter user is granted No Access through the share:. When printing a form or report from a Business Framework module, the user can select Deferred only. However, the user cannot print from Deferred to his or her printer.

Another user with Read/Write access through the share will need to print the Deferred report. If Crystal Enterprise / Web Reports is used instead of the CS ODBC Driver, the user will have the option both of Deferred and Crystal Enterprise. When printing a form or report from a Legacy module, all the remote user's printers will appear. The Deferred printing option is not available.

Oracle Odbc Drivers

Client Side Troubleshooting Test the Client Connection to the ODBC server:. From a remote workstation, start Sage MAS 200, and log on so that the Business Desktop (Launcher) is visible.

On the Windows Start menu, click Run. In the Open field, type cmd.

Click OK. Perform a simple ping test.

Enter the following command, and then press ENTER: ping server or ipaddress Replace with the server name or the server's IP address. If the reply is successful, proceed to the next step. If the reply is unsuccessful, this may indicate the router is blocking ICMP requests. Do not perform the telnet test below. Use a port scanning utility instead. Perform a simple telnet test to see if port 20222 is available to the remote workstation.

Enter the following command, and press ENTER: telnet server or ipaddress 20222 Replace server or ipaddress with the server's name or IP address. For example if the server's name is Server1, type telnet SERVER1 20222. If a blinking cursor appears, this indicates that the connection is successful, otherwise, the connection failed. Verify that personal firewall software on the workstation and the server's firewall or router is configured correctly. Note: If the ping test above failed, the telnet test will also fail.

If you are able to start Sage MAS 200 successfully but cannot use the ping and telnet commands, then the ICMP requests are likely being blocked at the router or firewall. Use a port scanning utility instead to verify port 20222 is available to the workstation. Test the client UNC path.

Start Sage MAS 200 from a remote workstation. On the Sage MAS 200 File menu, click Run.

Type.INFO. Click OK. Note the Installed Directory Path. It should be a valid UNC path to the server's. Mas90 folder. Right-click the installed directory path, and click Copy (or press CTRL+C).

On the Window Start menu, click Run. Right-click in the Open field, and click Paste (or press CTRL+V).

Windows Explorer should start fairly quickly. If a Windows challenge response dialog appears prompting for a username and password to access a network resource, this indicates the user logged into the remote workstation was not authenticated through the server's share.

Correct this problem before proceeding to the next step. The requirement is that from the workstation, entering the UNC path to the.

Mas90 folder on the server must result in an unchallenged Windows Explorer window. Note: If the Windows Explorer window opens unchallenged, but appears slowly, the remote workstation may be experiencing a slow name resolution issue. If that is suspected, one possible solution is to exit Sage MAS 200, and edit the workstation's local SOTA.INI file. In the Servers section, change the PATH= clause so that the server name is replaced by the IP address.

For example, change PATH= SERVER1 APPS 200V410 MAS90 to the following: PATH= IPAddress APPS 200V410 MAS90 (replace IPAddress with server's IP address). After the. Mas90 folder can be viewed through the UNC path, in the same Windows Explorer window, click File, point to New, and click Shortcut.

If the Create Shortcut window opens, click Cancel. If an 'Access Denied' message appears, this indicates that permissions on the share are not set up correctly.

Review the 'Configure the Share for Sage MAS 200' section again to verify that the share is correctly configured. Note: Do not select the Enable C/S ODBC Driver check box for workstations connected through a LAN, Terminal Services, or Citrix. Change the SOTAMAS90 DSN Configuration:.

At the remote workstation, close the Sage MAS 200 Business Desktop. On the Windows Start menu, click Run.

In the Open field, enter ODBCAD32. Click OK. Click the User DSN tab, and select the SOTAMAS90 DSN. Click the Configure button. Click the Basic tab. Verify that the database directory contains the path to the.

Mas90 folder relative to the server. The workstation's UNC path to the server should no longer appear. Click the Server tab. Verify that Server name or IP field contains the correct server name or IP address. Verify that TCP/IP Port field is set to 20222.

Click the Debug tab. Click the Apply button to save any changes.

Click the Test Connectionbutton. A database logon prompt should appear. Enter the company code, user logon, and password. This tests the ODBC server and returns the number of tables in the dictionary. The following message should appear: 'Connection succeeded.

Data source includes xxx tables.' . Repeat the steps above for every remote workstation. Additional Notes.

Reports and Forms run slower the first time. The first time a Crystal form or report is printed from the remote workstation using the CS ODBC driver, it takes longer to print because the report is cached locally under the following folder: C: Documents and Settings All Users Application Data Sage Software Cache MAS 200 If the.rpt file for the report does not already exist on the client side in the above folder, or if a newer version of the.rpt file exists on the server side, then the.rpt file is copied from the server. The second time the report is run, the.rpt file is not copied, and it prints faster. Note: Remote users must have sufficient Windows permissions on their local computer for Sage MAS 200 to copy the.rpt files in the location noted above on the user's local drive. The CS ODBC driver is limited 50 concurrent users. The CS ODBC driver license allows a maximum of 50 concurrent users running a Crystal reports or form simultaneously. This limitation does not affect LAN, Terminal Services, or Citrix users using the regular client based ODBC driver.

Related resources Category Data and database ODBC issues or information pertaining to ODBC components Entitlement Open Attachments ID:19372 Last modified: 887.