Dupremove.ncf unable to connect to SQL DB instance

I have ZDM7SP1_IR3a, my inventory database is running as a named instance on SQL2005. I am unable to get the dupremove module to connect to the data base. I keep getting a message:
Trying to (re)connect to the database -> mw_dba
Jdbc:sqlserver://10.10.11.55:1433;selectMethod=cursor
Com.microsoft.sqlserver.jdbc.SQLServerException: The TCP?IP connection to the host
Has failed. Java.net.ConnectException: Connection refused
at com.microsoft.sqlserver.jdbc.SQLServer Connection.connect(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServer Connection.connect(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.conne ct(Unknown Source)
at java.sql.DrierManager.getConnection(DriverManager. java:512)
at java.sql.DrierManager.getConnection(DriverManager. java:140)
at com.novell.zenworks.desktop.inventory.storer.Datab aseOperator.create(DatabaseOperator.jav:830)
at com.novell.zenworks.desktop.inventory.storer.Datab aseOperator<init>(DatabaseOperator.jav:589)
at com.novell.zenworks.desktop.inventory.storer.Datab aseOperator.main(DatabaseOperator.jav:7162)
Could not connect to database.
My dupremove.ncp is as follows:
java -ns -sn"ZENworks Inventory Dupremove utility" -neh -mx128m -classpath $tmppath;"$classpath" -Djava.compiler= com.novell.zenworks.desktop.inventory.storer.Datab aseOperator -host=10.10.11.55 -listwsdup -dbtype=2 -sid=mgmtdb -port=3855
It appears that this module is ignoring the port number provided. Is there a way to get it to accept the port given so that the connection to the database can be made?
I appreciate any and all suggestions.

DMPotter,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Similar Messages

Unable to Connect to SQL 2000 Instance from Windows Server 2012 environment

We have a windows server (TEST) 2012 environment , where our test SQL Server 2012 instance is hosted.
We have a different (DEV) Server (windows 2000) where a SQL Server 2000 instance is present.
When I RDP to our Windows Server 2012 box, I cannot connect to the SQL 2000 server instance from SQL Management Studio. (whereas I can connect to
the same server from my local machine which has windows 7 and SQL 2012 installed).
This is the error i see -
"A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name
is no longer available.) (.Net SqlClient Data Provider)"
When run from SQL Agent Service from TEST (A Job which tries to connect to that SQL 2000 instance to read some data using SSIS) , we get the following
error -
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005 Description: "[DBNETLIB][ConnectionRead
(recv()).]General network error. Check your network documentation.".
The same SSIS package runs successfully from my local machine.
Please, could someone advice how to resolve this situation?

Thanks Olaf.
Its just that we have legacy systems here in our company, who, for some reason haven't upgraded their older infrastructure, whereas they have set up new Windows 2012/SQL 2012 environments for the newer sql instances where they want to transition to !
Not sure what the solution is honestly. It is affecting our timelines now. The infrastructure team needs to take a decision now, as to what to do.
I do have to add, we were able to connect to these "older" servers from our Windows 7 client machines which have SQL 2012 - both from SQL management studio & SSIS (using OLE-DB Provider for SQL Server).

Unable to connect to SQL Server 2008 from OBIEE 11G(on 64 bit Linux box)

We are unable to connect to connect to SQL Server 2008 from OBIEE 11G which is on 64 bit Red Hat Enterprise Linux.
Infrastructure: OBIEE 11.1.1.5 64bit, on 64 bit Red Hat Linux Enterprise Linux 5.6 , MS SQL Server 2008 on 64 bit Microsoft Windows Server
Issue Description: Unable to connect to SQL Server 2008 from OBIEE11G RPD
Details: We are unable to connect to SQL Server 2008 from OBIEE which is on a 64 bit Linux box. We created the ODBC connection on Linux box to the SQL server. Whenever we try to import metadata it throws an error that says ‘Connection Failed’.
Here are the steps we followed to setup the ODBC connection on Linux box.
1) We updated the user.sh file with the LD_LIBRARY_PATH and LD_LIBRARY_PATH_64 values that point to $ORACLE_HOME/bifoundation/odbc/lib
This is where we found the driver for SQL server SEmsss23.so.
2) We updated the odbc.ini file with the entry for SQL server with the connection details
SI_SQL_Server_DEV = SQL Server
[SI_SQL_Server_DEV]
Driver=/u001_OAS/Oracle/Middleware/Oracle_BI1/bifoundation/odbc/lib/SEmsss23.so
Description=DataDirect 5.1 SQL Server Wire Protocol
Address=10.230.216.52,54970
AlternateServers=
AnsiNPW=Yes
ConnectionRetryCount=0
ConnectionRetryDelay=3
Database=SVBDW_NEW
LoadBalancing=0
LogonID=SIDatavalidation
Password=~~~Password123
QuoteID=No
ReportCodePageConversionErrors=0
3) We updated the IDENTIFIER_QUOTE_CHAR with single quotes instead of double quotes in the DB features of the RPD
4) We updated the bash_profile file to point the ODBCINI variable to the path where the OBIEE odbc.ini file is present.
Export ODBCINI=/u001_OAS/Oracle/Middleware/instances/instance1/bifoundation/OracleBIApplication/coreapplication/setup/odbc.ini
The error in nqsserver.log file says “[nQSError: 16001] ODBC error state: IM002 code: 0 message: [DataDirect][ODBC lib] Data source name not found and no default driver specified.”

Hi,
Make sure SQL Configuration Manager make sure the TCP/IP enabled. please try below method
Method 1
Re Create a new ODBC & Oracle Bi Server DSN Configuration test it and use it in the connection pools.
define your ODBC data source in your server where the BI Server is installed. Check your DB connections in your physical layer and make they are defined on your BI Server as well.
Method 2:
try using the complete TNS in below format in the datasource name section:
(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST =DB IP)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = ORCL) ) and provide the credentials.
Method 3:
To use the OCI call interface you need to have oracle client DB to be installed so that you can establish a connection using that DB credentials and connect to the remote dB and then import the tables.....this is the rule of thumb.
hope helps you.
Thanks
Deva

Unable to connect to sql server database

i run on CMD:
aspnet_regsql -C "Data Source =Davidchamoun/sqlexpress : intergrated security= true" -ssadd -sstype p
i got
a network-related or instance-specific error occurred while establishing a connection to sql server. the server
was not found or was not accessible. verify that the instance name is correct and that sql server is configured to allow remote connections. (provider: SQL Network interfaces . error: 25 – connection string is not valid
unable to connect to sql server database.
im using sql sever 2012 express, microsoft visual studio web 2008 express.
please help me.

i run it as :
aspnet_regsql -C "Data Source =Davidchamoun\sqlexpress : integrated security= true" -ssadd -sstype p
i got the same error :
an error has occurred . details of the exception:
a
network-related or instance-specific error occurred while establishing a connection to sql server. the server was not found or was not accessible. verify that the instance name is correct and that sql server is configured to allow remote connections. (provider:
SQL Network interfaces . error: 25 – connection string is not valid
unable to connect to sql server database.
im using also windows 8.1
pls help me
ty for ur reply

DPM unable to connect to SQL Rreporting during install

I'm attempting to install System Center 2012 R2 Data Protection Manager on the same machine I installed SQL Server 2014.
I configured the default instance of SQL Server with the database engine and Reporting Services - Native, the database was created for reporting and the reporting website comes up. I configured TCP/IP for all enabled and listening, removed the dynamic port
0 from the network devices and specified 1433 under IPAll. The firewall is turned off, the user is a domain admin and sysadmin, the SQL Browser service is running.
When I attempt to install DPM and connect to the local instance it keeps giving me the same error no matter what I try. "DPM setup is unable to connect to the specified instance of SQL Server Reporting Service. (ID: 33431)"
Has anyone gotten this to work yet? I see that SC DPM 2012 r2 and sql 2014 are compatible.

Hi,
DPM 2012 R2 does not support using SQL 2014 for database.
Please see
Preparing your environment for System Center 2012 R2 Data Protection Manager (DPM)
SQL Server Database
SQL Server 2012 with SP2 Standard or Enterprise 64-bit
SQL Server 2012 with SP1 Standard or Enterprise 64-bit
SQL Server 2012 Standard or Enterprise 64-bit
SQL Server 2008 R2 with SP2 Standard or Enterprise 64-bit
SQL Server 2008 R2 with SP1 2012 Standard or Enterprise 64-bit
However after you install
KB3009516 Update Rollup 4 (UR4) DPM 2012 R2 can protect SQL 2014 databases.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Cannot not connect to SQL Server instance.

Hello,
I have SQL Server 2012 installed and when I run this command:
sc query mssql$MSSQLSERVER
I get this error:
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:
The specified service does not exist as an installed service.
I run this command on the same server where SQL Server is installed. Databases are on the same server too. TCP/IP is enabled for the instance and port 1433 is open on the server's firewall. SQL Server Browser is running.
Many errors in the SQL Server error logs like:
SQLServer Error: 11001, 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.
SQLServer Error: 11001, TCP Provider: No such host is known. [SQLSTATE 08001]
Any ideas what could have gone wrong?
Thanks,
Paul
Paul

Hi Paul,
According to your description, you fail to connect to SQL Server 2012 instance. According to the SQL Server error log, based on my research, your issue could be due to that
the client cannot resolve the name of the SQL Server instance.
Are the errors from the SQL Server error log solved? If the errors are not solved, please follow the steps below to troubleshoot the issue.
1. Make sure you are able to ping the physical server where SQL Server is installed from the client machine. If not, you can try to connect to the SQL Server using an IP Address (for default instance) or IP Address\Instance Name
for a named instance.
2. Make sure you are using the correct instance name. When you connect to a default instance, machine name is the best representative for the instance name and when you connect to a named instance such as sqlexpress, you should
specify machinename\instancename according to
Niting123’s post. And you could verify if you use the right instance name in SQL Server configuration manager according to
Niting123’s post.
3. Check that SQL Server is in the network. You can use the SQLCMD -L command to retrieve the list of SQL Server installed in the network. Note that this will only return SQL Servers if the SQL Server Browser service is running.
4. Make sure that you enable Named Pipes besides TCP/IP protocol.
5. Check to see if remote connections is enabled. Right click on the server name in SSMS and select Properties. Go to the Connections tab and make sure Allow remote connection to this server is checked.
6. Locally connect to SQL Server and check the error log for the port entry.
7. To connect to SQL Server instance using TCP/IP from another computer, on the SQL Server computer, you must configure the firewall to allow connections to the TCP port used by the Database Engine. If you are connecting to a named
instance or a port other than TCP port 1433, you must also open the UDP port 1434 for the SQL Server Browser service according to pasquale’s post.
For step by step instruction on opening a port in the Windows firewall, see
How to: Configure a Windows Firewall for Database Engine Access
For more information about the process, please refer to the article:
http://www.mssqltips.com/sqlservertip/2340/resolving-could-not-open-a-connection-to-sql-server-errors/
In addition, you mention that there are many other errors, so please provide the SQL Server error log for analysis.
Regards,
Michelle Li

Able to connect from SQL-Assistant BUT unable to connect from Sql Developer

Hello,
I have been troubling with this issue for the last two weeks...tried so much, but could not able to resolve....
sqlplus username/password@IPAddress:port/ServiceName
I am able to connect to DATABASE from SQLAssistant only when I provide string like ABOVE........If I dont mention the SERVICE, m unable to connect to DB...
Now the biggest issue is with SQL Developer.....m not at all able to connect to DB using SQL Developer....I tried all options...but no use...
waiting for your reply......
Thanks Much in Advance.....

What have you tried, and what error messages are you getting?
When you create a connection in SQL Developer, you should specify IPAddress,port,ServiceName as in your sqlplus connect string.

Unable to connect to sql server 2008

i have windows 8 64-bit on my system, i installed sql server 2008 it installed successfully, but now i'm unable to open server management studio, it is showing error like "provider:named pipes provider, error:40-
could not open a connection to sql server microsoft sql
server, error:2" and in configuration manager there is nothing under "sql server services and sql server network configuration"kindly help me to fix this problem

Hello,
Please run the Discovery Report as shown in the following resource and make sure the Database Engine Services is listed
on the report.
http://blogs.msdn.com/b/petersad/archive/2009/11/13/sql-server-2008-discovery-report.aspx
If the Database Engine Services is listed on the report, please apply SP3 for SQL Server 2008 since SQL Server is not compatible with Windows 8 without that service pack.
http://support.microsoft.com/kb/2681562
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Windows 7 clients suddenly unable to connect to SQL database

Our environment in a nutshell:
Server1: Small Business Server 2003 R2 (Active Directory domain, it is the sole domain controller [DC])
Server2: Dedicated to SQL Server 2005 and the SAP Business One database
Server3: Windows Server 2003 R2 Standard Terminal Server. This provides user sessions that are the equivalent of Windows XP SP3.
Two Windows 7 workstations: 1x 64-bit, 1x 32-bit. Both are domain joined.
All above computers on a gigabit LAN.
Client product is SAP Business One 2007 A (8.00.181) SP:00 PL:49
SQL Native Client is 9.00.5000.00
SQL Server is mixed-mode authentication, however all users use trusted Windows connections. All users with access to the product are members of an "SAP Users" domain security group.
Normal operation is:
Local Win7 workstations have client installed and connect over the LAN to the SQL Server instance on Server2
Remote users log on to the Server3 Terminal Server, fire up sessions and connect to the SQL Server instance
Up to and including Thursday, March 12 everything was working fine for all users. As of Friday, March 13 the Terminal Server users/sessions are still working perfectly but the Windows 7 workstations can no longer connect to the SQL Server instance with trusted connections. They are still able to connect if they switch to a SQL Server logon and use the "sa" user account and its password.
Also, the users normally using the Win7 workstations can log on to the Terminal Server with their usual domain accounts, and run SAP from there, which works perfectly.
The error the Windows 7 users are seeing:
Connection failed:
SQL State: 28000
SQL Server Error: 18452
[Microsoft][SQL Native Client][SQL Server]Login failed for user ". The user is not associated with a trusted SQL Server connection.
Prior to each logon attempt above, the Server2 SQL Server machine logs another event to its Application Event Log:
SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: xx.xx.xx.xx]
Source: SQL Server instance, event 17806. From SQL Server log, Severity 20, State 2
What I've tried so far:
All servers have been restarted in correct order
Running the client in Windows XP SP3 compatibility mode. No difference
Running the client as Administrator. No difference
Upgrading to SQL Server Native Client 11.0 via:
Uninstall B1 client
Uninstall v9.00 Native Client
Install v11.00 Native Client
Install B1 client
Net effect is no difference
Googling the event IDs that are being logged seems to point to:
Expired domain account. Manually checked that the 2 users accounts are not expired and they belong to the "SAP Users" group. Furthermore, the domain accounts are still working when used in Terminal Server sessions.
Problem with Service Primary Names (SPNs). This seems to be Active Directory-related. Again, the domain accounts normally used on the Win7 workstations work fine on the Terminal Server so I'm inclined to think AD is OK
Other information that may be useful:
No Windows updates applied between March 12 and 13 on either Win7 workstation
Both Win7 workstations running Microsoft Security Essentials and the native Windows 7 firewall
All servers running Trend Worry Free Business Security suite
Sorry about the length of the post but hopefully it will reduce wild goose chases. Any troubleshooting ideas greatly appreciated.

Problem found!
It turns out it was some sort of subtle problem with Trend antivirus running on the servers.
On all 3 servers there are 3 main protection components that are enabled by default:
Antivirus/Anti-spyware
Web Reputation
URL Filtering
What I did was to turn off all 3 components for all the servers. With Trend this can be done from the central management console. SAP then worked on one of the Win7 clients using Trusted Connection (i.e. Windows Authentication).
Then I turned the Trend components back on, on all servers, one at a time (to try to find which component was the culprit). Here’s the funny part: I turned all 3 back on, and SAP still works on the Win7 client using Windows Authentication! I even restarted it to make sure that state of affairs persists across a restart, and it’s still OK.
It's worth noting the problem was not solved shortly after it appeared by restarting all 3 servers. There was even a scheduled installation of Windows updates a couple of hours ago, which restarted all 3 servers again, and the problem still persisted. It was not fixed until the Trend components were globally disabled (on all 3 servers), then re-enabled.
Trend WBFS is version 9.0, pre SP1.

Linked Server unable to Connect in SQL Server 2012 after Restarting SQL Server Service it works fine. Why?

I have created a Linked Server to Access Database of 64 MB in Size located in Remote System to SQL Server 2012.In Start for Some time it works fine and after it is giving the Error
OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.".
Msg 7303, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
Previously I thought it as Permission Issue. By trying some fixes proposed in forums it not fixed. But, after restarting the SQL Server Services without changes to the linked Server it works perfectly. How could i fix it. I don't want restart the SQL Server
Service it leads to Some other process failures.
RehaanKhan. M

After all the Errors, When I am restarting the SQL Server its working correctly.
Whats the problem it is clearing itself after restarting of SQL Server. Why ?. I can't find anything regarding this in SQL Server .
The following are the Errors i got connecting to SQl Server.
OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.".
Msg 7303, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
Error-2:
Executed as user: RMS\Administrator. Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST". [SQLSTATE 42000] (Error 7303) OLE DB provider
"Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.". [SQLSTATE 01000] (Error 7412). The step failed.
After unchecking the Allow In Process in OLEDB.ACE Provider Properties.
Msg 7399, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
The OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" reported an error. Access denied.
Msg 7301, Level 16, State 2, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
for to fix above error i have followed the instructions in the following link,
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2010/08/19/permissions-needed-to-set-up-linked-server-with-out-of-process-provider.aspx
This also failed to work. I Restarted SQL Server and make the Linked Server Properties Default to my Configuration and it works fine.
Can you suggest me a solution for this issue. Every time i don't want to restart SQL Server Services as it effects other jobs and Processes.
Thank you.
RehaanKhan. M

Unable to connect using SQL Developer.

Hi,
I am having a hard time connecting to the database instance using "Cloud Connections," in SQL Developer.
I am using the information found in here: http://docs.oracle.com/cloud/CSDBU/develop.htm#BABDBHJA to connect to my cloud-service, but all I get is an error:
"Authentication Failed Invalid resource owner credentials."
I am positive that I am using the same username and password as when logging in to could.oracle.com.
Can anybody help me?

Apologies for any difficulty you have been having.
I would start by reviewing the white paper on data movement. My guess is that you have not defined an APEX user with SQL Developer privileges (yes, I know the process could be more clear - it's getting there.)
You can find the white paper here - http://www.oracle.com/technetwork/database/database-cloud/public/data-movement-wp-1844121.pdf. Please make sure you follow all the steps properly, for both initialization and the actual connection.
Hope this helps.
- Rick Greenwald, Product Management, Database Cloud Service

Unable to connect to sql server 2008 r2 after upgrading from framework 4.0 to 4.5.2 in windows 7 environment

Hi All,
BackGround
I used to connect to database with Encrypt set true in sql connection which helps established encrypted data base connection . I verified that created certificate in order
to provide Encrypted connection to database for client is valid.
Issue :Issue
is un-able to connect to sql sever2008 r2 from vs2013 by enforcing encryption to true.
while trying to test the connection from vs2013 error log getting recorded as well as error notification is getting populated as below .
Step1 :
from Vs2013 trying to connect to sql server 2008 r2
step 2: on Click test Connection . getting below mentioned error notification
Event Viewer Log:<o:p></o:p>
<o:p></o:p>
(Process Id: 7472)
<o:p></o:p>
.Net SqlClient Data Provider:<o:p></o:p>
A connection was successfully established with the server, but then an error
occurred during the login process. (provider: SSL Provider, error: 0 - The
target principal name is incorrect.)<o:p></o:p>
   at
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception,
Boolean breakConnection, Action`1 wrapCloseInAction)<o:p></o:p>
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)<o:p></o:p>
   at
System.Data.SqlClient.TdsParserStateObject.SNIWritePacket(SNIHandle handle,
SNIPacket packet, UInt32& sniError, Boolean canAccumulate, Boolean
callerHasConnectionLock)<o:p></o:p>
   at System.Data.SqlClient.TdsParserStateObject.WriteSni(Boolean
canAccumulate)<o:p></o:p>
   at System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte
flushMode, Boolean canAccumulate)<o:p></o:p>
   at System.Data.SqlClient.TdsParser.TdsLogin(SqlLogin rec,
FeatureExtension requestedFeatures, SessionData recoverySessionData)<o:p></o:p>
   at
System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo
serverInfo, String newPassword, SecureString newSecurePassword, Boolean
ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)<o:p></o:p>
   at
System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo
serverInfo, String newPassword, SecureString newSecurePassword, Boolean
redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential
credential, TimeoutTimer timeout)<o:p></o:p>
   at
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer
timeout, SqlConnectionString connectionOptions, SqlCredential credential,
String newPassword, SecureString newSecurePassword, Boolean
redirectedUserInstance)<o:p></o:p>
   at
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, SqlCredential credential,
Object providerInfo, String newPassword, SecureString newSecurePassword,
Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions,
SessionData reconnectSessionData)<o:p></o:p>
   at
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo,
DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions
userOptions)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool
pool, DbConnection owningObject, DbConnectionOptions options,
DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
owningObject, DbConnectionOptions userOptions, DbConnectionInternal
oldConnection)<o:p></o:p>
   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
owningObject, DbConnectionOptions userOptions, DbConnectionInternal
oldConnection)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection
owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate,
Boolean onlyOneCheckConnection, DbConnectionOptions userOptions,
DbConnectionInternal& connection)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection
owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions,
DbConnectionInternal& connection)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection
owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions
userOptions, DbConnectionInternal oldConnection, DbConnectionInternal&
connection)<o:p></o:p>
   at
System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection
outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1
retry, DbConnectionOptions userOptions)<o:p></o:p>
   at
System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)<o:p></o:p>
   at
System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)<o:p></o:p>
   at System.Data.SqlClient.SqlConnection.Open()<o:p></o:p>
Inner Exception:<o:p></o:p>
:<o:p></o:p>
The target principal name is incorrect

The target principal name is incorrect
Hi Rahul.U,
Are you able to connect to SQL Server successfully from SQL Server Management Studio (SSMS) when enforcing encryption?
According to above error message, it could be caused by the inappropriate server name or incorrect TrustServerCertificate configuration in the connection string from Visual Studio. There are some proposals for you troubleshooting this error.
1. Make sure that you connect to the SQL server using the fully qualified domain name (FQDN).
2. When connecting to a SQL Server instance with a valid certificate, please add the
TrustServerCertificate
parameter and set it to true in the connection string. For more details, please review this
article.
However, if you can successfully connect to SQL Server via SSMS, but still fail to connect to SQL Server from Visual Studio, I would like to recommend you post the question in the .Net Framework forum at
https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?category=netdevelopment . It is appropriate and more experts will assist you.
There are similar articles about error “The target principal name is incorrect” for your reference.
http://serverfault.com/questions/458935/aws-rds-sql-server-ssl-connection-the-target-principal-name-is-incorrect
http://www.derekseaman.com/2013/09/sql-2012-failover-cluster-pt-12-kerberos-n.html
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Unable to connect to SQL database through ODBC calls

I have been looking around for an answer to this, but haven't found the exact issue I'm seeing.
I have several Excel spreadsheets which have been working until recently, which use an ODBC call to a remote SQL database. The database is running, remote connections are allowed. The SQL server is in a domain which has no external trusts. Users with accounts
in this domain can remotely access the SQl databases through ODBC just fine. Users who do not have domain accounts in this domain are being denied access by their domain account, and the SQL authentication is not passed through, even though remote access is
set to allow "everyone", and the database is set to Windows authentication and SQL authentication. This worked until early this week (the spreadsheet was created in 2010), and I have been looking fruitlessly for a fix ever since. As far as I know,
no changes were made to group policy on this domain, and no changes were made to the server or database recently, except Microsoft patches. None of the patches this month looked like they would affect this.

It works locally on the server and remotely for users in the same domain. I am trying to use the SQL account and password to connect to the database, but users from outside this domain fail to reach the SQL database for authentication. It looks like Windows
authentication is not passing the SQL credentials on if the windows authentication fails. I don't know how to resolve this. The only options in SQL are "Windows authentication and SQL authentication" or "Windows authentication only". The database is already
set to the first option. Somehow, I need to set the server to allow the SQL authentication even if the Windows authentication fails.
Hi pkuti01,
SQL Server mixed mode is "Windows Authentication and SQL Server Authentication", we have to restart SQL Server service after change the authentication to mixed mode.
In your case, have you got any error message/information if you faild connect to SQL Server via ODBC? If so, please post them to us for further investigation. Furthermore, here is an article regarding steps to troubleshooting SQL connectivity issues for
your reference. Please see:
http://blogs.msdn.com/b/sql_protocols/archive/2008/04/30/steps-to-troubleshoot-connectivity-issues.aspx
If you have any feedback on our support, please click
here.
Regards,
Elvis Long
TechNet Community Support

Unable to connect to the database instance using Enterprise Manager.

I just install Oracle 10gr2 in my computer and after successful installation created a database instance which also install successfully. I then configure the listener using Net Manager and then start the database instance, the listener and dbconsole, everything seems to work fine and checking the status of this services from the command prompt indicates everything started successfully. But when I try to use Enterprise Manager I was directed to the Database Down Page with a message unable to connect to database instance. I try to use startup and perform recovery but every time I log-in to the database an error message comes out:
SQLEXCEPTION
ORA-00604: error occurred at recursive SQL level 1
ORA-12705: Cannot access NLS data files or invalid environment specified.
It seems for Enterprise Manager to connect to the database it needs to access this NLS(National Language Support) data files or specify an environment variable to point to this data files. I am just new to Oracle and I am having difficulty solving this particular problem. Where is this data files located and how do I configure Enterprise Manager to access this NLS data Files?
Any help however small will be highly appreciated.

Are you able to connect to the database via SQLPlus?
What Operating System are you using?
Assuming Windows, can you RUN regedit to open Windows Registry and check the value or NLS_LANG when you select
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_<your_oracle_home>
Examples of vaules you may find:
1. ENGLISH_UNITED KINGDOM.WE8MSWIN1252
2. AMERICAN_AMERICA.US7ASCII
3. AMERICAN_AMERICA.WE8MSWIN1252
4. FRENCH_FRANCE.WE8MSWIN1252
5. GERMAN_GERMANY.WE8MSWIN1252
If you are not able to connect to SQLPlus, from the command prompt try setting one of the above:
e.g.
D:\>set NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252
D:\>sqlplus /nolog
SQL>connect sysman/password

Required Ports to connect remote SQL named Instance for SCCM 2012 R2

Hi,
I have allowed the TCP 1433,1434,135 and 80 but still unable to connect the remote SQL named instance DB for the SCCM 2012 R2... and getting below error..can you please suggest if any other port required for the same, i have turned off the windows
firewall and RPC service is running ob Remote SQL and SCCM 2012 R2 server..
CCMsetuplog
Shailendra Dev

During the installation you need more ports. You would also need the (dynamic) RPC ports. See for a complete list (section Site Server --> SQL Server):
https://technet.microsoft.com/en-us/library/hh427328.aspx
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Dupremove.ncf unable to connect to SQL DB instance

Similar Messages

Maybe you are looking for