Highlighted

Unable to set SQL Server Connection Properties for specific client

Hi everyone,

I've been dealing with this issue without any solution until this moment.

I'm trying to configure a SQL client with NetBackup but the more curious thing for me is that when I start the NetBackup Database Extension, it only shows me a host name in the combo box but not the real name of the client that I am connecting to but another server in the same network which hasn't installed neither NetBackup nor SQL Server. For example it shows only server name VOLCANO01 but the local server name and the one that I need to setup is VOLCANO09. 

When I try to apply settings after typing the correct name of the server and giving the credentials it shows me the common error:

"Application connection failed for VOLCANO09\. Please select a different SQL Server host and instance, or press 'cancel' to exit the NetBackup for SQL Server Graphical User Interface.". 

Setting the logs in verbose this is the detail

15:43:01.325 [3152.3376] <4> VxBSAInit: Veritas NetBackup XBSA Interface - 7.6  0
15:43:01.325 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_API
15:43:01.326 [3152.3376] <4> VxBSAGetEnv: INF - returning - 
15:43:01.326 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_FEATURE_ID
15:43:01.326 [3152.3376] <4> VxBSAGetEnv: INF - returning - <FEATURE_ID>
15:43:01.326 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - BSA_SERVICE_HOST
15:43:01.326 [3152.3376] <4> VxBSAGetEnv: INF - returning - MASTER01
15:43:01.326 [3152.3376] <4> bsa_checkFeatureId: INF - entering bsa_checkFeatureId 
15:43:01.326 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - BSA_SERVICE_HOST
15:43:01.326 [3152.3376] <4> VxBSAGetEnv: INF - returning - MASTER01
15:43:01.337 [3152.3376] <2> vnet_pcache_init_table: [vnet_private.c:208] starting cache size 200 0xc8
15:43:01.345 [3152.3376] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1
15:43:01.345 [3152.3376] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface  ANY
15:43:01.346 [3152.3376] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1
15:43:01.346 [3152.3376] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface  ANY
15:43:01.347 [3152.3376] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1
15:43:01.347 [3152.3376] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface  ANY
15:43:01.348 [3152.3376] <2> async_connect: [vnet_connect.c:1499] connect in progress 1 0x1
15:43:01.362 [3152.3376] <2> vnet_pbxConnect: pbxConnectEx Succeeded
15:43:01.362 [3152.3376] <2> do_pbx_service: [vnet_connect.c:2164] via PBX bprd CONNECT FROM 192.168.200.236.58701 TO 172.30.20.210.1556 fd = 464
15:43:01.363 [3152.3376] <2> async_connect: [vnet_connect.c:1691] connect async CONNECT FROM 192.168.200.236.58701 TO 172.30.20.210.1556 fd = 464
15:43:01.363 [3152.3376] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO MASTER01 172.30.20.210 bprd VIA pbx
15:43:01.363 [3152.3376] <2> init_resilient_cache: [vnet_nbrntd.c:863] Initialize resilient cache. 0 0x0
15:43:01.363 [3152.3376] <2> logconnections: BPRD CONNECT FROM 192.168.200.236.58701 TO 172.30.20.210.1556 fd = 464
15:43:01.363 [3152.3376] <2> vnet_check_vxss_client_magic_with_info_ex: [vnet_vxss_helper.c:894] Assuming no VxSS for DB Agents 0 0x0
15:43:01.701 [3152.3376] <4> bsa_checkFeatureId: INF - Successfully validated FeatureId
15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_VERBOSE_LEVEL
15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - returning - 5
15:43:01.701 [3152.3376] <4> VxBSAInit: Veritas NetBackup XBSA Interface - 7.6  0
15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_API
15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - returning - 
15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_FEATURE_ID
15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - returning - <FEATURE_ID>
15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - BSA_SERVICE_HOST
15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - returning - MASTER01
15:43:01.701 [3152.3376] <4> bsa_checkFeatureId: INF - entering bsa_checkFeatureId 
15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - BSA_SERVICE_HOST
15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - returning - MASTER01
15:43:01.719 [3152.3376] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1
15:43:01.719 [3152.3376] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface  ANY
15:43:01.719 [3152.3376] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1
15:43:01.719 [3152.3376] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface  ANY
15:43:01.719 [3152.3376] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1
15:43:01.719 [3152.3376] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface  ANY
15:43:01.720 [3152.3376] <2> async_connect: [vnet_connect.c:1499] connect in progress 1 0x1
15:43:01.724 [3152.3376] <2> vnet_pbxConnect: pbxConnectEx Succeeded
15:43:01.725 [3152.3376] <2> do_pbx_service: [vnet_connect.c:2164] via PBX bprd CONNECT FROM 192.168.200.236.58702 TO 172.30.20.210.1556 fd = 464
15:43:01.725 [3152.3376] <2> async_connect: [vnet_connect.c:1691] connect async CONNECT FROM 192.168.200.236.58702 TO 172.30.20.210.1556 fd = 464
15:43:01.725 [3152.3376] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO MASTER01 172.30.20.210 bprd VIA pbx
15:43:01.726 [3152.3376] <2> logconnections: BPRD CONNECT FROM 192.168.200.236.58702 TO 172.30.20.210.1556 fd = 464
15:43:01.726 [3152.3376] <2> vnet_check_vxss_client_magic_with_info_ex: [vnet_vxss_helper.c:894] Assuming no VxSS for DB Agents 0 0x0
15:43:02.061 [3152.3376] <4> bsa_checkFeatureId: INF - Successfully validated FeatureId
15:43:02.061 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_VERBOSE_LEVEL
15:43:02.061 [3152.3376] <4> VxBSAGetEnv: INF - returning - 5
15:43:02.061 [3152.3376] <4> VxBSADeleteOldFiles: INF - entering VxBSADeleteOldFiles 
15:43:02.061 [3152.3376] <4> delete_old_files: entering delete_old_files.
15:43:02.062 [3152.3376] <4> CGlobalInformation::VCSVirtualNameList: INF - Veritas Cluster Server is not installed.
15:43:02.062 [3152.3376] <1> CGlobalInformation::VCSVirtualNameList:     CONTINUATION: - The system cannot find the path specified.
15:43:02.062 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Searching for ODBC Driver: SQL Native Client
15:43:02.062 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Registry Install Path: SOFTWARE\Microsoft\Microsoft SQL Native Client\
15:43:02.062 [3152.3376] <4> ODBCDataSource::isInstalled: INF - ODBC Driver Entry Registry Path: SOFTWARE\ODBC\ODBCINST.INI\SQL Native Client\
15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Registry entry not found for: SOFTWARE\Microsoft\Microsoft SQL Native Client\
15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Searching for ODBC Driver: SQL Server
15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Registry Install Path: SOFTWARE\Microsoft\DataAccess\
15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - ODBC Driver Entry Registry Path: SOFTWARE\ODBC\ODBCINST.INI\SQL Server\
15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - ODBC Driver: SQL Server is installed on the system
15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Searching for ODBC Driver: SQL Server Native Client 10.0
15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Registry Install Path: SOFTWARE\Microsoft\Microsoft SQL Server Native Client 10.0\
15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - ODBC Driver Entry Registry Path: SOFTWARE\ODBC\ODBCINST.INI\SQL Server Native Client 10.0\
15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - ODBC Driver: SQL Server Native Client 10.0 is installed on the system
15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Searching for ODBC Driver: SQL Server Native Client 11.0
15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Registry Install Path: SOFTWARE\Microsoft\Microsoft SQL Server Native Client 11.0\
15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - ODBC Driver Entry Registry Path: SOFTWARE\ODBC\ODBCINST.INI\SQL Server Native Client 11.0\
15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Registry entry not found for: SOFTWARE\Microsoft\Microsoft SQL Server Native Client 11.0\
15:43:02.064 [3152.3376] <4> dbc_GetServerName: entering dbc_GetServerName.
15:43:02.064 [3152.3376] <4> getServerName: entering getServerName.
15:43:02.064 [3152.3376] <4> getServerName: Read server name from nb_master_config: MASTER01
15:43:02.064 [3152.3376] <4> CDBIniParms::CDBIniParms: INF - NT User is Admin_bcr
15:43:02.072 [3152.3376] <16> CGlobalInformation::QuerySQLServerInfo: ERR - Error in RegConnectRegistry, opening <HKEY_LOCAL_MACHINE> key on <\\>: 1707. The text follows:
15:43:02.073 [3152.3376] <1> CGlobalInformation::QuerySQLServerInfo:     CONTINUATION: - The network address is invalid.
15:43:02.073 [3152.3376] <4> CGlobalInformation::CreateDSN: INF - Using ODBC Driver <SQL Server>
15:43:02.081 [3152.3376] <4> CGlobalInformation::CreateDSN: INF - Error Creating ODBC data source name
15:43:02.081 [3152.3376] <1> CGlobalInformation::CreateDSN:     CONTINUATION: - Invalid string
15:43:02.081 [3152.3376] <1> CGlobalInformation::CreateDSN:     CONTINUATION: - Driver's ConfigDSN, ConfigDriver, or ConfigTranslator failed
15:43:04.881 [3152.3376] <4> SQLEnumerator: INF - Enumerated SQL hosts: SERVERSmiley Frustratederver={(local),VOLCANO01};UID:Login ID=?;PWDSmiley Tongueassword=?;Trusted_Connection:Use Integrated Security=?;*APP:AppName=?;*WSID:WorkStation ID=?
15:43:04.881 [3152.3376] <4> CGlobalInformation::IsDefaultInstanceInstalled: INF - Error: ERROR_FILE_NOT_FOUND
15:43:04.881 [3152.3376] <1> CGlobalInformation::IsDefaultInstanceInstalled:     CONTINUATION: - The system cannot find the file specified.
15:43:04.882 [3152.3376] <4> CGlobalInformation:Smiley FrustratedQLEnumerator: INF - Hosts and instances retrieved from host list string
15:43:04.882 [3152.3376] <4> CGlobalInformation:Smiley FrustratedQLEnumerator: INF - host: VOLCANO01
15:43:04.882 [3152.3376] <4> CGlobalInformation:Smiley FrustratedQLEnumerator: INF -      instance: <default>
15:43:04.918 [3152.3376] <4> AugmentInstanceList: INF - Cannot obtain remote access to registry on \\VOLCANO01
15:43:04.919 [3152.3376] <8> CSQLDBMSOptions:Smiley SurprisednInitDialog: WARN - Cannot expand instance list for host .
15:43:04.919 [3152.3376] <4> CSQLDBMSOptions:Smiley SurprisednInitDialog: INF - It is unknown whether NetBackup for Microsoft SQL Server is installed on host machine
15:43:16.392 [3152.3376] <4> CGlobalInformation::CreateDSN: INF - Using ODBC Driver <SQL Server>
15:43:16.418 [3152.3376] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_3152_3376_2>, SQL userid <sa> handle <0x00329810>.
15:43:33.957 [3152.3376] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_3152_3376_2>, SQL userid <sa> handle <0x0032ab60>.
15:43:51.483 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC return code <-1>, SQL State <08001>, SQL Message <17><[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.>.
15:43:51.483 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - SQL Message <2><[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).>
15:43:51.483 [3152.3376] <4> CGlobalInformation::CreateDSN: INF - Failed to connect. Attempting operation with next installed ODBC Driver <SQL Server Native Client 10.0>
15:43:51.521 [3152.3376] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_3152_3376_3>, SQL userid <sa> handle <0x0032b730>.
15:44:07.094 [3152.3376] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_3152_3376_3>, SQL userid <sa> handle <0x0032ce70>.
15:44:22.621 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC return code <-1>, SQL State <08001>, SQL Message <2><[Microsoft][SQL Server Native Client 10.0]Named Pipes Provider: Could not open a connection to SQL Server [2]. >.
15:44:22.621 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - SQL Message <2><[Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.>
15:44:22.621 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - SQL Message <0><[Microsoft][SQL Server Native Client 10.0]Login timeout expired>
15:44:22.621 [3152.3376] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x0032ce70>
15:44:22.621 [3152.3376] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_3152_3376_3>, SQL userid <sa> handle <0x0032ec20>.
15:44:38.147 [3152.3376] <4> DBConnect: INF - Failed sql connect try #1
15:44:54.691 [3152.3376] <4> DBConnect: INF - Failed sql connect try #2
15:45:11.224 [3152.3376] <4> DBConnect: INF - Failed sql connect try #3
15:45:27.736 [3152.3376] <4> DBConnect: INF - Failed sql connect try #4
15:45:44.260 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC return code <-1>, SQL State <08001>, SQL Message <2><[Microsoft][SQL Server Native Client 10.0]Named Pipes Provider: Could not open a connection to SQL Server [2]. >.
15:45:44.260 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - SQL Message <2><[Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.>
15:45:44.260 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - SQL Message <0><[Microsoft][SQL Server Native Client 10.0]Login timeout expired>
15:45:44.260 [3152.3376] <16> CGlobalInformation::QuerySQLServerInfo: ERR - Unable to login into SQL instance <VOLCANO09\> as user <sa>.
15:45:44.260 [3152.3376] <4> CGlobalInformation:Smiley Very HappyeleteDSN: INF - Using ODBC Driver <SQL Server>
15:45:44.267 [3152.3376] <16> CSQLDBMSOptions:Smiley SurprisednApply: ERR - Error 64 has been returned from QuerySQLServerInfo

I tried some suggestions in several posts regarding UAC, user permissions, etc., but the issue is still there.

Please advice.

Thank you. 

Regards, 

Rolando. 

1 Solution

Accepted Solutions
Accepted Solution!

Hi everyone, I just solved

Hi everyone,

 

I just solved the issue. This was due to a dns problem. The server was not solving the nslookup properly. We have to modify the server's DNS properties to add a specific DNS suffix.

The NetBackup MS SQL Client still doesn't show the local server name but now typing it and also typing the SQL instance name it connected without problem.

 

Thank you all for your help.

 

Regards,

Rolando.

 

View solution in original post

11 Replies

The issue seems to be with

The issue seems to be with the incorrect hostname showing up in the GUI. You will need to find out where this is coming from. Please show us output of these commands : hostname bpclntcmd -self bpclntcmd -pn

Is this a cluster? Please

Is this a cluster? Please post the outputs Marianne wanted.

 

Simple test is, the user you're logged on with, can they open SQL Management studio and login?

Hi Marianne, Yes, that's

Hi Marianne,

Yes, that's actually the problem.

Here is the output of the commands.

 

C:\Users\NetBackup_DB>hostname
VOLCANO09

C:\Users\NetBackup_DB>

--------------------------------------

E:\NetBackup\NetBackup\bin>bpclntcmd -self
gethostname() returned: volcano09
host volcano09: VOLCANO09 at ::1
host volcano09: VOLCANO09 at 192.168.200.236
aliases:     VOLCANO09     ::1     192.168.200.236
 getfqdn: No error

E:\NetBackup\NetBackup\bin>

-------------------------------------

E:\NetBackup\NetBackup\bin>bpclntcmd -pn
expecting response from server MASTER01
volcano09 *NULL* 192.168.200.236 62062

E:\NetBackup\NetBackup\bin>

--------------------------------------

 

Thank you,

Rolando.

Hi Riaan, this is a

Hi Riaan,

this is a standalone client. The user is ok. I log in to SQL Management Studio and it has the sysadmin role and is also part of the administrator group on the server. The outputs are in the reply to Marianne.

 

Thank you,

Rolando.

Think you're running into

Think you're running into issue because of mixed case.

VOLCANO09  !=  volcano09

Hi Will, I followed your

Hi Will,

 

I followed your suggestion. We changed the alias on DNS to uppercase but no success. When I open NetBackup MS SQL Client it only shows host VOLCANO01 in the SQL connection properties.

E:\NetBackup\NetBackup\bin>hostname
VOLCANO09

E:\NetBackup\NetBackup\bin>bpclntcmd -self
gethostname() returned: VOLCANO09
host VOLCANO09: VOLCANO09 at ::1
host VOLCANO09: VOLCANO09 at 192.168.200.236
aliases:     VOLCANO09     ::1     192.168.200.236
 getfqdn: No error

E:\NetBackup\NetBackup\bin>bpclntcmd -pn
expecting response from server MASTER01
VOLCANO09 *NULL* 192.168.200.236 62304

Thank you,

Rolando.

 

Is there a VOLCANO01 in your

Is there a VOLCANO01 in your environment?

Hi, maybe check the SQL

Hi,

 

maybe check the SQL ports being used, https://support.symantec.com/en_US/article.TECH155299.html

 

Longshot but you never know.

Hi Andrew, Yes, there is

Hi Andrew,

Yes, there is another server named VOLCANO01 which is in the same network zone of VOLCANO09.

 

Thank you,

Rolando.

Accepted Solution!

Hi everyone, I just solved

Hi everyone,

 

I just solved the issue. This was due to a dns problem. The server was not solving the nslookup properly. We have to modify the server's DNS properties to add a specific DNS suffix.

The NetBackup MS SQL Client still doesn't show the local server name but now typing it and also typing the SQL instance name it connected without problem.

 

Thank you all for your help.

 

Regards,

Rolando.

 

View solution in original post

Re: Is this a cluster? Please

Simple test. Smiley Happy

Tags (2)