Database Lookup fails to connect to the database

SYMPTOMS

Problem connecting to database , the connection failed.

CAUSE

This problem might be caused by a Network Port being blocked.

RESOLUTION

Step 1
To open a port in the Windows firewall for TCP access:
1. On the Start menu, click Run, type WF.msc, and then click OK.
2. In the Windows Firewall with Advanced Security, in the left pane, right-click Inbound Rules, and then click New Rule in the action pane.
3. In the Rule Type dialog box, select Port, and then click Next.
4. In the Protocol and Ports dialog box, select TCP. Select Specific local ports, and then type the port number of the instance of the Database Engine, such as 1433 for the default instance. Click Next.
5. In the Action dialog box, select Allow the connection, and then click Next.
6. In the Profile dialog box, select any profiles that describe the computer connection environment when you want to connect to the Database Engine, and then click Next.
7. In the Name dialog box, type a name and description for this rule, and then click Finish.

To open access to SQL Server when using dynamic ports:
1. On the Start menu, click Run, type WF.msc, and then click OK.
2. In the Windows Firewall with Advanced Security, in the left pane, right-click Inbound Rules, and then click New Rule in the action pane.
3. In the Rule Type dialog box, select Program, and then click Next.
4. In the Program dialog box, select This program path. Click Browse, and navigate to the instance of SQL Server that you want to access through the firewall, and then click Open. By default, SQL Server is at C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Sqlservr.exe. Click Next.
5. In the Action dialog box, select Allow the connection, and then click Next.
6. In the Profile dialog box, select any profiles that describe the computer connection environment when you want to connect to the Database Engine, and then click Next.
7. In the Name dialog box, type a name and description for this rule, and then click Finish.

Step 2
Open SQL Server Configuration Manager/SQL Server Network Configuration.
Enable Named Pipe protocol.
Stop and start SQL Server.

Step 3
In SQL Server Management Studio add a database (LookUpDB), add a table, e.g: table_1

ID Name City Phone
1 jan amsterdam 020 1234567
2 piet utrecht 030 1234567
3 klaas hilversum 035 1234567

Step 4
32-bit ODBC on Windows Server 2008 R2

Heterogeneous data access requires having the right drivers. If you have to use 32-bit ODBC drivers, you won’t find them when you start the Microsoft ODBC Administrator because it is 64-bit. The 32-bit ODBC Administrator is found here: C:\Windows\SysWOW64\odbcad32.exe

1. Open this ODBC Data Source Administrator
2. Select System DSN tab, select create new data source, select SQL Server Native Client.
3. Press Finish. Enter: name (e.g: lookup), description and server name. Press next.
4. Enter credentials and press next. Set default database name (LookUpDB) Step through the wizard without entering additional data.
5. Now the name of the new data source is listed: lookup.

Step 5
In ZySCAN create new job template.

1. For ZyFIELD add fields:
2. 'ID' of type Database Lookupkey.
3. Enter specific options:
4. Connection string: DSN=lookup;Uid=sa;Pwd=<password>;
5. Table: Table_1
6. 'Name' and 'City' and 'Phone Number' of type plain text.
7. Enter the database column name under the lookup tab by selecting in the pull down menu.

APPLIES TO

6.2 Service Pack 2