Unable to connect to SQL 2012 on Windows VM from gallery

I had deployed new virtual machine from the gallery, windows 2012 with sql 2012 but fail to login with default authentication
I had followed the directions as in: "Provisioning a SQL Server Virtual Machine on Windows Azure" (http://www.windowsazure.com/en-us/documentation/articles/virtual-machines-provision-sql-server/)
but fail to login to SQL with the following error:
===================================
Cannot connect to R10PROJDEPLOY.
===================================
Login failed for user 'R10PROJDEPLOY\R10Admin'. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
Server Name: R10PROJDEPLOY
Error Number: 18456
Severity: 14
State: 1
Line Number: 65536
in the past I had used same procedure to work with windows Server 2008 & SQL 2008 and managed to login well, any hint could be wrong?

Hi,
To connect to the Database Engine from another computer, configure SQL Server for mixed mode authentication.
Add the port number after the server name.
Also try connecting with the IP address.
If no progress, please check the error message in ‘\Program Files\Microsoft SQL Server\MSSQL11.<instance name> \MSSQL\Log\ERRORLOG’
Hope it helps.
Tracy Cai
TechNet Community Support

Similar Messages

Connecting to SQL Server on Windows 8 from WindowsCE

Hello,
I need to make a connection to SQLServer 2008 which is on my developer machine, later it will be SQL Server on some production machine from .Net Compact Framework developed app on WindowsCE.
When I using local sdf file I use SqlCeConnection for DB connection but how to connect from same app local SQL Compact databse and SQL Server on some server.
Thanks in advance...

Related blog: How to connect to SQL Server from a Windows Mobile Emulator
Forum thread:
Windows mobile connect with sql server 2008 r2
Kalman Toth Database & OLAP Architect
Free T-SQL Scripts
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

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

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 Deskjet 3545 via Wireless Direct from Windows 8.1 laptop (Lenovo Thinkpad E530)

Hi, It's a newly bought printer. I am unable to connect to the printer via Wireless Direct from Windows 8.1 64bit laptop. I have enabled the Wireless Direct with security on the Printer. Connected to the Printer SSID from my laptop wifi. Created the new printer from Driver software. It discovers the printer with it's name,IP etc; Upon selecting the printer and click on 'Next' button on the screen, results in a 5 min search process and finally displays that it could not connect. I have tried pinging the printer and it's able to pingf the IP of the printer successfully. I have even tried disabling the Norton antivirus, but result is the same. regards,sathwik

Cluster SQL 2012 on Windows 2008 R2

Hi
Presently, i have a cluster SQL 2012 on windows 2008 R2 (2 nodes), i need to add a new server in cluster.
My question, it's possible to add WINDOWS 2012 SERVER with SQL 2012?
(2 nodes with Windows 2008 R2, 1 node with Windows 2012 and all nodes with SQL 2012)
If yes, do you have a link that
confirms this?
Thanks

No. This is not possible. Microsoft Windows Cluster required all the Member Nodes to have same OS to the Same version level. Even you cannot use Windows Server 2008 on one node with Windows Server 2008 R2 on another node.
Thanks and Regards Alankar Chakravorty MCITP Database Administrator SQL Server 2008 MCITP Database Administrator SQL Server 2005

Unable to connect to MQ7.0 in BIND mode from Weblogic10.3.4 Cluster

Unable to connect to MQ7.0 in BIND mode from Weblogic10.3.4 Cluster (Managed Servers)
Issue in brief is we are able to connect to MQ7.0 from Weblogic10.0 admin server but not able to connect to MQ7.0 from Weblogic Cluster (Managed Servers).
Below are the details:-
Environment:-
1) Weblogic 10.3.4
MQ Version: 7.0.1.4
Admin Server :- adminserver
Managed Server:- ms1
Managed Server:- ms2
Cluster:- cluster_1 (ms1,ms2)
a) Admin Server (adminserver)
When deployed the application on Admin Server (adminserver) its working fine, able to connect to MQ 7.0
b) Cluster:- cluster_1 (ms1,ms2)
When deployed the application on cluster_1(ms1,ms2) its failing with the error message:-
Error:-
####<Jan 4, 2012 3:27:39 PM CET> <Warning> <EJB> <ahuoms30> <ms2> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <guest> <> <> <1325687259034> <BEA-010061> <The Message-Driven EJB: TestMDBean is unable to connect to the JMS destination: jms/queue/external/TestResponseQueue. The Error was:
com.ibm.msg.client.jms.DetailedJMSException: JMSFMQ6312: An exception occurred in the Java(tm) MQI. The Java(tm) MQI has thrown an exception describing the problem. See the linked exception for further information.
Nested exception: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2495;AMQ8568: The native JNI library 'mqjbnd' was not found. [3=mqjbnd]
Nested exception: java.lang.UnsatisfiedLinkError: no mqjbnd in java.library.path>
Analysis:-
Error Occurs because it is not able to find the mqjbnd in java.library.path.
The JAVA_LIB_PATH="/opt/mqm/java/lib64" valus is set in the startup script for both the Admin Server (adminserver) and cluster_1 (ms1,ms2),
working fine for Admin Server (adminserver) but not for cluster_1 (ms1,ms2).
Connection towards MQ is not working for the clusters(ms1,ms2) when compared with the Admin Server (adminserver) as all the settings in scripts are same.
Does anyone have experience similar issue and solved this issue, please let me know.

In case this happens to anyone in the future, you may also need to add '/opt/mqm/java/lib64' to the LD_LIBRARY_PATH env variable.

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).

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 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

SQL 2005 will not connect in SQL 2012 profiler

We have a few SQL 2005 databases that we manage. I went to do a trace on them(recently upgraded to 2012) and it gives me the error, "SQL Server Native Client 11.0 does not support connections to SQL Server 2000 and earlier versions".
According to MSDN it does. https://msdn.microsoft.com/en-us/library/cc280356(v=SQL.110).aspx
"SQL Server Native Client 11.0 supports connections to SQL Server 2005, SQL Server 2008, SQL Server 2008
R2, SQL Server 2012, and Windows Azure SQL Database."
Any clue why it wouldn't let me connect?

Can you specify the following parameter in the "connect to server" dialog when you load the Profiler --> click on "options" button and go to "Additional Connection Parameters" tab and paste the following?
DataTypeCompatibility=80
Satish Kartan www.sqlfood.com

Remote Desktop Connection Client 9.3.9600 unable to connect to Server 2012 RDS via Gateway

Hi,
I have a Windows Sever 2012 R2 RDS environment with two Gateways servers configured in high availability mode (RD Web Access, RD Gateway, RD Connection Broker roles installed) and four Windows Server 2012 R2 RDS Session Hosts. The servers are all running
the most recent public server updates. With this configuration I when connecting externally using a Windows 7 computer with the older Remote Desktop Connection client (6.1.7601) I am able to connect without any problems however when I try connecting with a
newer client from a computer running Windows 8.1 and the 9.3.9600 client I am unable to connect.
At the moment a NAT rule is configured to pass 80/443 traffic to only one of the RDS gateway servers, I've removed our load balancer from the configuration for the moment to reduce the complexity.
No error is generated by the client when it tries to connect it just stops trying to connect after a while.
On the Gateways servers event logs for
Things I have looked into so far.
- I've double and triple checked the RDS configuration and checked it against one of my other clients configurations that is working and they are identical.
- Connecting from an older client version works fine.
I'm not sure what else can be checked does anyone have any ideas?

Hi,
1. What entries are you seeing in the RD Gateway's log? Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-Gateway
2. How come you are not forwarding UDP port 3391 in addition to TCP port 443? It should work without UDP, but you will not have UDP support which is one of the benefits of RDP 8.0/8.1.
3. Are there any non-default group policy settings being applied to the servers and/or client PCs? To be clear, I'm asking if any changes have been made to the default local and domain security policies, group policy objects, new GPOs that may have
been added, etc., that are applicable to the servers and or client PCs.
-TP

SQL 2000 LINKED SERVER ERROR 7303 WITH SQL 2012 ON WINDOWS SERVER 2012 R2

Hi all,
I have a problem with SQL Server 2012 and a linked server for SQL 2000 database.
System specification:
Windows server 2012 64 bit
SQL SERVER 2012 64 bit
REMOTE SERVER SQL 2000 32 bit
I've installed sql native client 32bit,create a SYSTEM DSN odbc connection with "SQL Server" driver named "MYSERVER".
Create a linked server with the query below in SQL 2012:
EXEC master.dbo.sp_addlinkedserver @server =N'MYSERVER', @srvproduct=N'MYSERVER', @provider=N'MSDASQL', @datasrc =N'MYSERVER', @location=N'System';
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'MySERVER',@useself=N'True',@locallogin=NULL,@rmtuser=NULL,@rmtpassword=NULL
GO
but when i browse the linked server i receved error 7303.

You need 64-bit MSDASQL. It is the bitness of the server you are connecting from that matters. 64-bit executables cannot hook into 32-bit DLL.
However, I suspect that you will not get things to work anyway. At least I have not seen anyone this far who has been able to set up a linked server from SQL 2012 to SQL 2000. I know that when I tried this, the following providers had this result:
SQLNCLI11 - does not support connections to SQL 2000.
SQLNCLI10 - failed with some obscure message that I don't recall.
SQLNCLI - Don't recall that the problem was here.
SQLOLEDB - SQLOLEDB is always replaced with the most recent version of SQLNCLI, so this fails because of lack of support.
I don't think I got through all version of the ODBC drivers, though.
Erland Sommarskog, SQL Server MVP, [email protected]

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.

Unable to connect to SQL 2012 on Windows VM from gallery

Similar Messages

Maybe you are looking for