DSN network library shown as "Other" in ODBC Administrator

This article was previously published under Q260249
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
When creating a new SQL Server Data Source Name (DSN) using the ODBC API SQLConfigDataSource function, a network library must be specified. If the network library name is in lowercase letters, the Client Configuration dialog box may show it as "Other".
CAUSE
In Control Panel, the Client Configuration dialog box in ODBC Data Source Administrator is case-sensitive. It compares the network library name from the registry to uppercase network library names. See the "More Information" section for information on the registry entries that are affected by SQLConfigDataSource.
RESOLUTION
Use all uppercase letters in the network library name.

NOTE: This is only cosmetic. Connectivity is not affected by the case of the network library name.
MORE INFORMATION
The ODBC API SQLConfigDataSource function can be used to create new SQL Server DSNs programmatically. For example, the following code creates a new System DSN named MyNewDSN (or modifies if it already exists) connecting to the pubs database using the TCP/IP protocol:
returnCode = SQLConfigDataSource(NULL,ODBC_ADD_SYS_DSN, (LPSTR) "SQL Server",                                (LPSTR) "DSN=MyNewDSN\0"                                "Network=DBMSSOCN\0"                                "Server=MySqlServer\0"                                "Database=pubs\0"                                "Description=New Data Source\0");				
Creating a new DSN enters or modifies the default network library value for SQL Servers stored in the registry under the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo
The DSQUERY string under this registry key contains the default network library for any SQL Server.

If the network library name that is shown in the SQLConfigDataSource call above is coded as "Network=dbmssocn\0" instead of "Network=DBMSSOCN\0", the Client Configuration dialog box will show the network library as "Other".
REFERENCES

229929 INFO: Registry Entries and Keywords for SQL Server Connection Strings
814844 Error message: "Setup was unable to validate the logged user" occurs when you install SQL Server 2000 Service Pack 3 (SP3)

Properties

Article ID: 260249 - Last Review: 02/28/2014 00:32:20 - Revision: 3.2

  • Microsoft Data Access Components 1.5
  • Microsoft Data Access Components 2.0
  • Microsoft Data Access Components 2.1
  • Microsoft Data Access Components 2.5
  • Microsoft Data Access Components 2.6
  • Microsoft Data Access Components 2.7
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 7.0 Standard Edition
  • kbnosurvey kbarchive kbprb KB260249
Feedback