DataSource Fails to Connect After SQL Server Reboots
I have a SQL Server which is rebooted once every week. I also have a small daemon thread running on Tomcat 4.1 that checks a database every 60 seconds for a specific setting. When something changes it sends an email to the required email address. The connection object the daemon uses is created from a datasource configured in Tomcat's server.xml specific to the daemon's application. After the reboot of the SQL Server I receive this error message "[Microsoft][SQLServer 2000 Driver for JDBC]Connection reset by peer: socket write error" ever time the daemon tries to connect to the datasource.
Anybody have any ideas as to where the problem may lie?
Any suggestions as to a work around?
Thanks
jmorrison42
Thanks for your response 8233. Below is the Context tag of Tomcat's server.xml file...
<Context className="org.apache.catalina.core.StandardContext" cachingAllowed="true"
charsetMapperClass="org.apache.catalina.util.CharsetMapper" cookies="true"
crossContext="false" debug="0" displayName="Forecast" docBase="forecast"
mapperClass="org.apache.catalina.core.StandardContextMapper" path="/forecast"
privileged="false" reloadable="true" swallowOutput="false" useNaming="true"
wrapperClass="org.apache.catalina.core.StandardWrapper">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_forecast_log." suffix=".txt"
timestamp="true"/>
<Resource name="jdbc/DEVSERVER" auth="Container"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/DEVSERVER">
<parameter>
<name>username</name>
<value>JAVA_USER</value>
</parameter>
<parameter>
<name>password</name>
<value>JAVA_USER</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>com.microsoft.jdbc.sqlserver.SQLServerDriver</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:microsoft:sqlserver://DEVSERVER:1433</value>
</parameter>
<parameter>
<name>removeAbandoned</name>
<value>true</value>
</parameter>
<parameter>
<name>removeAbandonedTimeout</name>
<value>60</value>
</parameter>
<parameter>
<name>logAbandoned</name>
<value>true</value>
</parameter>
<parameter>
<name>maxWait</name>
<value>5000</value>
</parameter>
<parameter>
<name>maxActive</name>
<value>10</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>5</value>
</parameter>
</ResourceParams>
<ResourceLink global="mail/Session" name="mail/Session" type="javax.mail.Session"/>
</Context>
After my last post, I changed the Context paramater reloadable from false to true. All other tags have not been modified. (I haven't had the opportunity to test this change because my SQL Server doesn't reboot until Sunday.) Does that parameter affect the datasource's availability after a disconnect such as this?
Thanks again for your help
jmorrison42
Similar Messages
-
UDL failed to connect to SQL server
I have been using UDL as the means to connect to SQL server in Windows XP. But after upgraded to Window 7, UDL cannot connect any more. I still can connect to SQL database through the means of ODBC.
UDL itself connects successfully. I know it is something about Windows 7. What is exactly the problem here?Where is the SQL Server? I assume its on a remote machine?
Did you try using an IP address instead of host name?
In your UDL, you you are using Windows Authentication. Did you happen to install the SQL Server in mixed mode? If so, you could try specifying a known username/password instead of using Windows Authentication.
Turn off your firewall to see if that is the problem. -
Login fails when connecting to SQL Server 2008
There were 3 databases and a report server database on sql server 2008 r2. All were renamed. Now, when trying to connect to sql server I am getting a login failed error for default database. I'm guessing because the default db name was changed. How
can I fix this so that I can connect to the db server\instance?
ThanksHi ,
According to your description, I do a test in SQL Server 2008R2. If you use windows system admin account to log in the instance via Windows authentication, even if you change all use database name, you can still log in successfully. However, if you create
a SQL Server login name to connect to instance via SQL Server authentication, when you change the default database name, it will
occur the error which just like at follows .
//Cannot open user default database. Login failed.
Login failed for user '***'. (.Net SqlClient Data Provider), Error Number: 4064//
I recommend you change the default database any existing database on your server like master via clicking on Option , or you can run following statement for username
to replace your original database name with master.
ALTER LOGIN [login name] WITH DEFAULT_DATABASE = master
GO
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support -
Outlook 2010 doesn't automatically re-connect after Exchange Server reboot - help
We have recently upgraded from Exch 2003 to Exch 2010. We also upgraded our users Outlook client from 2003 to 2010. Now when an Exch 2010 server is rebooted Outlook does not re-connect automatically. You have to close Outlook and re-open
it and it starts working again. Others have reported the same issue. Outlooks shows the status in the status bar area as password is required. I have read an article in the forums about it being an authentication problem. What
changes can I make in Outlook or to Exchange 2010 to make Outlook automatically reconnect after an Exchange server reboot. thanksThey connect internally in the LAN with their domain credentials.
I haven't noticed any errors in the Exchange server related to this issue but I have not really looked in the logs right after this happens.
I guess I just don't understand how when we were running Exch2003 with Outlook2003 we did not have this problem. Now that we have spent all this money and upgraded to bigger, better, smarter software we are having a problem like this. It seems like
if Outlook senses the lost connection and transfers to Offline that it would keep periodically to see if the email server is back up and reconnect.
Sorry for the delay response.
I would suggestyou create a new Windows profile and test it again. Some times the windows profile curropted and woithout being able to provide credentials.
Hope it is helpful.
Fiona Liao
TechNet Community Support -
BI JDBC Connection fails to connect to SQL Server 2000
Hello SDNs,
I have configured my JDBC connector to connect to MS SQL Server 2000(Third party in my case) using the document How to Configure UD connect on the J2EE server for JDBC Access to External Drivers.
I have given the following properties for my JDBC connector:
Driver Name : com.microsoft.jdbc.sqlserver.SQLServerDriver
URL : jdbc:microsoft:sqlserver://servername:1433;database=<databasename>
When i test the connection using the url: http://hostname:50000/TestJDBC_Web/TestJDBCPage.jsp
Here is the Error:
<b>Details:
com.sap.ip.bi.sdk.exception.BIConnectionFailedException: Cannot open the connection at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcConnectionFactory.getConnectionEx(JdbcConnectionFactory.java:238) at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getConnection(JDBCModel.java:797) at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getTables(JDBCModel.java:132) at
com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnection.(JdbcManagedConnection.java:118) ... 23 more Caused by: java.lang.ClassNotFoundException: com.microsoft.jdbc.sqlserver.SQLServerDriver Found in negative cache -
Loader Info -
ClassLoader name: [connector:default] Parent loader name: [Frame ClassLoader] References: common:service:http;service:servlet_jsp service:ejb common:service:iiop;service:naming;service:p4;service:ts service:jmsconnector library:jsse library:servlet common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl library:ejb20 library:j2eeca library:jms library:opensql common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore interface:resourcecontext_api interface:webservices interface:cross interface:ejbserialization common:library:bimmrcore;library:bimmrdb sap.com/cafcore sap.com/cafruntimeear library:tcconnconnectorframework library:sapxmltoolkit sap.com/com.sap.ip.bi.sdk.dac.connector.xmla.x library:com.sap.mw.jco library:com.sap.aii.proxy.framework library:com.sap.aii.util.misc library:com.sap.ip.bi.sdk.dac.connector.odbodll library:BI_JDBC library:bimmrcwm_1.0_library library:bimmrjmi library:com.sap.ip.bi.sdk library:MSSQL Resources: H:\usr\sap\BD2\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.ip.bi.sdk.dac.connector.xmla\connector\connectors\bi_sdk_xmla.rar\bi_sdk_xmla.jar H:\usr\sap\BD2\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\cafbwadapterassembly\connector\connectors\sap.com_cafbwadapterassembly.rar\lib\java\sap.comcafbwadapter~caf.bw.adapter.jar H:\usr\sap\BD2\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.ip.bi.sdk.dac.connector.sapq\connector\connectors\bi_sdk_sapq.rar\bi_sdk_sapq.jar H:\usr\sap\BD2\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.ip.bi.sdk.dac.connector.jdbc\connector\connectors\bi_sdk_jdbc.rar\bi_sdk_jdbc.jar Loading model: {parent,references,local} -
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:141) at com.sap.ip.bi.sdk.dac.connector.jdbc.impl.Connection.connectDB(Connection.java:365) ... 25 more</b>
Please let me know if any changes are required in Driver name and URL.
Your inputs will be highly appreciated.
Thanks,
Sireesha.B
Message was edited by:
sireesha BorraHi Sireesha,
Some insights.....while using JDBC connector .
For JDK 1.1 environments, access to the "current working directory" mustbe granted.
For Java 2 environments, access to the temporary directory specified by the VM configuration must be granted. The following is an example of permissions being granted in the file java.security.policy for the C:\TEMP directory:
// permissions granted to all domains grant { // Permission to create and delete temporary files. // Adjust the temporary directory for your environment. permission java.io.FilePermission "C:
TEMP
-", "read,write,delete"; };
Note 777304 - Problems with JDBC drivers when using BI UDI
Related notes -
834385 - 'Invalid operation: result set closed' Exception
834384 - Problems with selection in InfoPackage in UD Connect
777306 - MSSQL problem when using BI UDI
777305 - Problems with Unicode when using BI UDI
Fyi-
http://dev.mysql.com/downloads/index.html
Regards,
Anil -
SCCM Install fails. cannot connect to SQL server. "the network was not found"
Hi,
I'm installing SCCM 2012. i have a 2 server boxes. 1x sccm and 1x dedicated SQL. sccm installation is stuck @ connecting to DB.
SQL server is 2012 with SP2, static 1433 port used.installation account used is already sysadmin, sccm computer account also added into SQL local admins. ports 1433, 4022, 445 are already FW open in between SCCM box and SQL Box?
error pop up" "the network was not found"
Pls advise.if MS is really doing good job then such things (scCm on remote sql) should be easy for us with proper docs. Cheers!
The docs are "proper". They give you all the technical details needed. They assume however that you know how to translate the stated requirements, like the ports necessary (as documented at
http://technet.microsoft.com/en-us/library/hh427328.aspx ), into the environment you are working in. They cannot give you a click by click guide because that would only be applicable to
generic lab environments.
Sorry that that may sound a bit harsh, but it is reality. They simply have no idea what customer networking environments actually look like as the possibilities are simply unbounded. They must rely on the implementer being able to take the core technical
requirements and implement them for the uniqueness of the environment they are working in. In most cases, this is generally straight-forward, but there is a great deal of variety in the real-world.
Jason | http://blog.configmgrftw.com | @jasonsandys -
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 incorrectThe 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 -
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
PaulHi 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 -
Linked Server "Could not open a connection to SQL Server [1909]" after reboot
We have two production servers, with RCP [out] enabled linked servers set up back and forth between them. When they are rebooted at the same time one of the linked servers will throw this error:
Named Pipes Provider: Could not open a connection to SQL Server [1909]. 767462021 OLE DB provider "SQLNCLI10" for linked server "server3" returned message "Login timeout expired".
OLE DB provider "SQLNCLI10" for linked server "server3" returned message "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.".
I've been fixing it by dropping and re-creating the linked server. It's completely identical as before (in sp_linkedservers), so I'm thinking this shouldn't be necessary. My guess is it's only happening because during startup the other server was not available.
If this is true, can I force a reset of the linked server, without having to restart the server instance, or recreate the linked server?Hi Chuck, thanks for the reply. Both servers were already set to 20. I think this might work if in the ensuing 10 seconds the other server happened to come on line. I could also set it to 60, but then production queries would be waiting 60 seconds
for timeout. I'm really after a cause and solution. It's as though the server tries once, sees that the other server is unavailable, and henceforth refuses to try again. I'd like it to try again. Really, it should try every time.
Could it be that upon startup SQL Server looks for all its linked servers and marks ones it can't reach in that moment as forever invalid? I'm sure this doesn't happen after startup, only during. -
hi ,
when generate the schema , i got the below error, please any one put your inputs:
Connecting to the LOB system has failed. 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server).thaks shanky,
but facing another , after generate schema from WCF_SQL, im unable get elements in my schema.
this is schema generate from storeprocduer , but thru WCF-sql im unable get the elements like
id, name
<xsd:schema targetNamespace="urn:schemas-microsoft-com:sql:SqlRowSet2" xmlns:schema="urn:schemas-microsoft-com:sql:SqlRowSet2" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sqltypes="http://schemas.microsoft.com/sqlserver/2004/sqltypes" elementFormDefault="qualified">
<xsd:import namespace="http://schemas.microsoft.com/sqlserver/2004/sqltypes" schemaLocation="http://schemas.microsoft.com/sqlserver/2004/sqltypes/sqltypes.xsd" />
<xsd:element name="Test.dbo.sample">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="id" type="sqltypes:int" minOccurs="0" />
<xsd:element name="name" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="sqltypes:nvarchar" sqltypes:localeId="1033" sqltypes:sqlCompareOptions="IgnoreCase IgnoreKanaType IgnoreWidth" sqltypes:sqlSortId="52">
<xsd:maxLength value="1000" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<Test.dbo.sample xmlns="urn:schemas-microsoft-com:sql:SqlRowSet2">
<id>18</id>
<name>BIRADAR</name>
</Test.dbo.sample>
<Test.dbo.sample xmlns="urn:schemas-microsoft-com:sql:SqlRowSet2">
<id>18</id>
<name>BIRADAR</name>
</Test.dbo.sample>
<Test.dbo.sample xmlns="urn:schemas-microsoft-com:sql:SqlRowSet2">
<id>19</id>
<name>sw</name>
</Test.dbo.sample>
<Test.dbo.sample xmlns="urn:schemas-microsoft-com:sql:SqlRowSet2">
<id>18</id>
<name>BIRADAR</name>
</Test.dbo.sample>
<Test.dbo.sample xmlns="urn:schemas-microsoft-com:sql:SqlRowSet2">
<id>14</id>
<name>swe</name>
</Test.dbo.sample>
<Test.dbo.sample xmlns="urn:schemas-microsoft-com:sql:SqlRowSet2">
<id>13</id>
<name>se</name>
</Test.dbo.sample> -
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. MAfter 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 -
Hi there,
I am having a serious issue with The Power BI Data Management Gateway which I am hoping that someone can help me with.
Basically I am setting a connection between a Power BI demo site and a SQL 2012 Database based on Azure. The Data Management Gateway and is up and running, and Power BI has managed to connect to it successfuly.
By following the tutorials at
here I was able to successful create my Data Connection Gateway with a self-signed certificate.
However, when trying to create the data source I come into problems. The Data Source Manager manages to successfully resolve the hostname, as per the screenshot below:
Bear in mind that I exposed the require ports in Azure as endpoints and I managed to modify my hosts file on my local machine so I could access the SQL server hosted in Azure using its internal name -- otherwise I would not be able to get this far.
However the creation of the data source also fails when trying to created it whilst logged in the SQL server in question:
The Data Source Manager returns the error when using the Microsoft OLE DB Provider for SQL Server:
Failed to test connection. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
I tried using the SQL Server Native Client 11.0 instead but I also get an error. This time the error is:
Failed to test connection. Login timeout expiredA 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.Named Pipes Provider: Could not open a connection to SQL Server [53].
Some considerations
If I provide an invalid username/password, the Data Source Manager does say that the username and password is incorrect.
Firewall is turned off in the SQL Server (either way, this error also happens if I try top use the Data Source Manager whilst logged in the SQL Server itself).
SQL Profiler does not show any attempt of connection.
The SQL server instance in question is the default one.
The error happens regardless if I select the option to encrypt connection or not.
In SQL Configuration manager I can see that all protocols are enabled (TCP/IP, Named Pipes and Shared Memory.
The Event Viewer does not provide any further errors than the one I have copied in this post.
I'm at a loss here. Could someone please advise what might I be doing wrong?
Regards,
P.Here is what I had to do to solve this issue:
Basically I had to add the MSSQL TCP/IP port as an end-point in Azure. After I did that, then I was able to create the data-source. However, I was only able to authenticate with a SQL account, as any domain account would return me an error saying that the
domain isn't trusted.
What puzzles me here is how come the Data Source Manager would inform me that an account username/password was invalid, but it would fail/timeout if I provided valid credentials (!?!?!!?) -
Failed to Establish connection with SQL Server
hi I have configured odbc settings and when i connect the sql from essbase i got the error :Failed to Establish connection with SQL Server .please hepl me on this
and please give me step by step process for how to resolve thi issue.and give me detail step by step from starting onwards.
appreciate your Help,
Thank u
Subbu.Steps:
1. Test database connection from Essbase server through SQL Command. This gives you whether you are able to connect to Database from Essbase server.
2. Create ODBC Connection: System DSN>Add>Select correct driver (Oracle in ...) >give Datasource (any name), Description (Any), TNS Service Name (user SID name), User name (Database user name)
3. Test Connection. if successful, you can use this ODBC to get the data.
4. Open rules file, go to FILE>Open SQL
5. Provide Essbase server, Application, Database names
6. Select SQL Data Source from the list (ODBC defined in step2)
7. Enter tested SQL Query(which is tested at SQL command or "sysdate from dual" ) in select box. NOTE: Remove select word from query. You can ignore from and where clauses, all you can include in select block.
8.Click OK/Reteive data
Rao -
Establishing connection to SQL server suddenly failed
Hi,
I had a working SQL connection before, but today i've tried to connect and got this message:
TITLE: Connect to Server
Cannot connect to User-PC\SQLEXPRESS.
ADDITIONAL INFORMATION:
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: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
BUTTONS:
OK
p.s. I'm novice to SQL ssms.
with regards,
yaron H.1. Make sure SQL Server Service is running
2. If a named instance, make sure SQL Server browser service is running
3. Make sure SQL Server is configured to allow remote connections
4. Examine the SQL Server error log for messages confirming that SQL is listening on the expected network interfaces and ports
5. Test server connectivity with PING from the client machine
6. Test port connectivity using TELNET or PowerShell to the server and port (from step 4) from the client machine. For example
a. TELNET <server-name> 1433
b. PowerShell: 1433 | % { echo ((new-object Net.Sockets.TcpClient).Connect("YourServerName",$_)) "server listening on TCP port $_" }
7. Check firewall settings if step 5 or 6 connectivity test fails
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence -
Hi!
I'm using consume adapter service> sqlbinding > to connect to sql database in order to generate sql schemas.
I'm getting below error:
Connecting to the LOB system has failed.
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: 26 - Error Locating Server/Instance Specified).
ChristianeHi,
As suggested earlier this seems to be a DTC related issue. It can only occur if the DTC settings are not proper or if firewalls don't allow the default ports to communicate.
Check DTC settings on both SQL and BizTalk Box and also check if MSDTC service is up and running.
Go to Start
à Run
à (type in) Dcomcnfg. You should be inside Component Services MMC.
Expand Component Services
à Computers
à My Computer (right click)
à Properties
à MSDTC tab
à Security Configuration button.
Select the checkboxes as following :
Check the below article from Microsoft Support Team, they have listed all the errors which may come during setting up a new system. They also have your MSDTC error listed.
Resolving the issues you may face during BizTalk Runtime Configuration
Thanks,
Prashant
Please mark this post accordingly if it answers your query or is helpful.
Maybe you are looking for
-
What OS will my MacBook 2,1 support?
Apparently I need to repair my start up disk but I don't have a OS bootable disk! What will my MacBook support that I can get from the apple store?
-
I updated my safari till 7.1.5. After this I cant open safari. Why?
-
IMPDP take too much time at TABLE STATISTICS
Hi experts. on of my database is taking taking to much time during IMPDP at TABLE STATISTICS. it take alomost 20 mints to import TABLE STATISTICS while on the other hand all other objects are imported within 5 to 7 minits. my database version is 10.2
-
Hi Not sure whether its right forum to post this, I'm using server for long time and its performance is getting bad, Can somebody suggest how I can speed up its performance? Any suggestions Thanks in advance Srikant
-
Re:Cloning Oracle Applications with Discoverer .
HI , We have configured Discoverer 11.1.1.4.0 on R12.1.3. Request to kindly provide the document id to clone R12.1.3 including 11.1.1.4.0 Regards .