cancel
Showing results for 
Search instead for 
Did you mean: 

Strange Data Insight error: Port must not be empty in the source connection

Former Member
0 Kudos

I installed Data Insight XI 3.0 (12.1) on Windows XP and created the metadata repository on MSSQL Server 2000 on the same machine. The engine and GUI were started OK. I can also create a new project, and a new connection to the "Northwind" database on the same MSSQL 2000 server. However, when I tried to run any profile task on any table, I got the following error in the engine's error log "Iqieng.log". I don't know why it complainted about the empty port number because the MSSQL server runs on the default port 1433. And I can actually open all tables and view the data in the project so the connection must be good. I tried to search the document and all options in the GUI, "iqi.ini" file, and even the registry but couldn't find where to set the host name and port number. Can someone shed light on this? Thanks very much!

********************************************************************

Mon Jan 5 2009 00:04:24.703000>

      • Thread <4688> Task bypassed; Port must not be empty in the source connection. Connection Name: <Northwind> DatabaseVendor: <SQL SERVER> DataSource: <SFON00460026A\SAP_DEFAULT> Host: <> Port: <>

      • Task: <DATAPROFILE1> PtkId: <12> PrsId: <23>

      • Location: RequestDispatcher::RejectRequest()

Mon Jan 5 2009 00:04:24.703000>

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Larry,

An alternative workaround is to update the MS SQL connection information for Data Insight.

Please update the IQI_CONNECTION table source connection as follows:

1. Run the following statement from a query tool (e.g. Query Analyzer):

SELECT * FROM IQI_CONNECTION WHERE IQI_CONN_NM = '<connection_name>';

Example of a valid connection is:

Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Data Source=MachineName;Port=1433;Trusted_Connection=Yes;

2.Add the port number using Query Analyzer or Enterprise Manager.

Let me know if you have any questions.

Regards,

Bev

Former Member
0 Kudos

Thanks Bev, it works! It's strange the port number 1433 wasn't added when the connection was created. Do I have to perform this manual step with all subsequent connections I create in the future? Is this a bug or configuration issue?

Thanks,

Larry

Former Member
0 Kudos

Larry,

Other source connections for MS SQL may also need this "fix" for this existing bug entry for Data Insight.

Regards,

Bev

Former Member
0 Kudos

Hi Bev,

I am very new to SQl server.. i am able to open this table.. what entries i have to put in this table?? do i have to insert something in this table?

Answers (1)

Answers (1)

Former Member
0 Kudos

Larry,

This is a known issue with a work around available.

The registry entry is the key. Apparently when SS2005 is installed locally, the registry entry is configured to use named pipes instead of TCP/IP, and the entry doesnu2019t follow the string format expected. Modify the entry to specify a tcp/ip format and then it will work OK.

Hereu2019s the format of the original entry for that connection entry in after install:

1111111111:np:
.\PIPE\MSSQL$SS2005\SQL\QUERY

Modified it to this:

1111111111:tcp:LAA-X-11-TAAAA,2191

Let me know if you have further questions.

Bev

Former Member
0 Kudos

I don't have MSSQL 2005 installed. I verified this in the "Add or Remove Programs" in the Control Panel and the registry. Under registry key "My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server", there are just "8.00.000", "80", and "SAP_DEFAULT" (my MSSQL 2000 database instance). If SQL 2005 was installed, there should be an entry "90" but there is no such entry.

Are the keys in your reply under SQL2005 or Data Insight registry entries? I can find some similar keys under SQL2000 but none under the Data Insight registry entry. The ones for SQL2000 are listed below.

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SAP_DEFAULT\MSSQLServer\SuperSocketNetLib

Value Name: "ProtocolList", Value Data: "tcp np"

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SAP_DEFAULT\MSSQLServer\SuperSocketNetLib\Np

Value Name: "PipeName", Value Data: "
.\pipe\MSSQL$SAP_DEFAULT\sql\query"

Key Name:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SAP_DEFAULT\MSSQLServer\SuperSocketNetLib\Tcp

Value Name: "TcpDynamicPorts", Value Data: "1246"

Value Name: "TcpPort", Value Data: "1246"

Value Name: "TcpHideFlag", Value Data: "0"

Key Name:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib

Value Name: "ProtocolOrder", Value Data: "tcp np"

Key Name:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib\Np

Value Name: "DefaultPipe", Value Data: "sql\query"

Key Name:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib\Tcp

Value Name: "DefaultPort", Value Data: "1433"

Thanks,

Larry