Skip to Content
Author's profile photo Raghunathan Balasubramanian

How to resolve connectivity error “BODI-1112172” when running SAP Business Objects Data Services Designer on Windows 7 Client

Applies to:

This document applies to SAP Business Objects Data Services14.x running on Microsoft SQL Server 2008 or higher as repository database and being accessed via the designer client software on a Windows 7 (32-bit) client pc/laptop.



This document explains about resolving connectivity error when accessing a Business Objects Data Services repository from Windows 7 using the designer client.  Error code – BODI-1112172


When Accessing SAP Business Objects Data Services repositories in SQL Server 2008 the connectivity error code BODI-1112172 is a common one. The error predominantly occurs with accessing running SAP Business Objects Data Services Designer Client on a Windows 7 pc/laptop to access a MS SQL Server or ORACLE repository. This document applies only to cases where the repository database is hosted in Microsoft SQL Server.

Fig 01.png

Some of the common causes for this error are


  1. Windows firewall settings
  2. Data Source is not accessible via ODBC
  3. SQL Server connectivity is set to listen for dynamic port instead of the default port 1433 for BOE

In cases where the connection to the SQL Server repository database is not through windows active directory, there will be a prompt for Repository Password as show in the figure below.

Fig 2 RepositoryPassword.png


Resolution Steps

The working assumption of this document is that the Repository Password entered is correct. A resolution for this issue when connecting using ODBC for SQL Server 2008 is to create a system DSN on the client PC that is used for running SAP Business Objects Data Services Designer Client software. The steps involved are provided below.

Step 1 – Go to Control Panel and open Administrative Tools

Fig 3.png

Step 2 – Open “Data Sources (ODBC)”

Fig 4.png

This will display the “ODBC Data Sources Administrator”

Step 3 – Click on the Add button.

Fig 5.png

This will display the “Create New Data Source” dialog box

Step 4 – In the “Create New Data Source” dialog box, select SQL Server and click on finish

Fig 6.png

Clicking Finish will open the “Create New Data Source to SQL Server” dialog box in Step 5

Step 5 – In the “Create New Data Source to SQL Server” dialog box, enter the connection details.

Fig 7_1.png

Step 6 – Choose the authentication method

  • In case of Windows Active Directory access model, choose the “With Windows NT authentication using Network login ID

          Fig 8.png

  • If SQL Server Authentication is used choose the “With SQL Server authentication using a login ID and password entered by the user“. Enter the user name and password accordingly as shown in figure below

               Fig 9.png

Note that in case of SQL Server authentication, it is not necessary to user system administrator credentials. Any SQL Server user account with relevant level of access to the repository database(s) is sufficient.

After choosing the relevant authentication method and entering the credentials where applicable, click on “Client Configuration” button. This will open the “Add Network Library Configuration” dialog box in Step 7.

Step 7 –  Enter the network configuration as shown in the figure below. 

Fig 10.png

Note that the port must be set to the default BOE140 installation port 1433 and the option “Dynamically determine port” must be unchecked. The protocol used is TCP/IP for MS QL Server connection using ODBC.

Also note that the server alias or server name must not be changed and should be the same as the SQL Server mentioned in Step 5.

Click on ‘OK’ after completing the settings. This will take the control back to the previous dialog box as shown below.

Fig 11.png

Click on “Next”

Step 8 – For the purposes of SAP Business Objects Data Services Designer client connectivity to the repository in MS SQL Server, do not alter the setting in the subsequent two dialog boxes and click on “FINISH”

Fig 12.png

Fig 12a.png

Step 9 – Upon clicking Finish, the “ODBC Microsoft SQL Server Setup” dialog box will appear. Click on “Test Data Source” button.

Fig 14.png

If the connection parameters and logon credentials entered are correct, the test should be completed successfully as shown below in the “SQL Server ODBC Data Source Test” dialog box.

Fig 15.png

Step 10 – Click on OK on the “SQL Server ODBC Data Source Test” dialog box and then on “ODBC Microsoft SQL Server Setup” dialog box.

If the tests were successful, the “ODBC Data Source Administrator Window” will appear with a new System DSN BOE140. Click on the ‘OK’ button to close the dialog box.

Fig 16.png

Step 11 – Open the Data Services Designer Logon Window, enter the credentials and click on “Lon On”

Fig 17.png

If using enterprise authentication and the windows logon ID is not synced with the SQL Server via Active Directory, then enter the repository password in the “Repository Password” dialog box and click “OK”.

Fig 2 RepositoryPassword.png

If the password entered is correct and the access is allowed for the user to the repository database in MS SQL Server security, then the SAP Business Objects Data Services Designer Client window will open for managing SAP Data Services Objects in the repository.

Fig 18.png

If the access for the user is set to read-only, in the SQL Server Security set-up, then the user will only be able to view the objects saved in the repository. If full read/write access is provided for the user to the repository database, then the user can create/edit/delete objects in the repository. Similar access can be set-up using a specific security model targeting a given set of security requirements in the CMC.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      We had this issue recently and this was very handy to fix the issue.

      Author's profile photo Former Member
      Former Member

      I had the issue fixed with ODBC connection for BODS by following these steps, very useful and detailed