Getting Frequent time out while Connecting to SQL server 2008 Instance installed on VmWare

Hi,
I have a production SQL server Database with default instance. when I connect this instance from 10 attempts it get connected only 5-6 times. I connect this through SSMS. Some of jobs also getting failed due to login time out expired. please help in this.
Product is SQL server 2008 Enterprise Edition
Thank You
Yogesh Arora

Yogesh Arora
Have you checked Event Viewer and ERROR.LOG?
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

Similar Messages

Trouble shooting while connecting Ms SQL Server 2008

hi everyone i ve a trouble shooting while connecting to sql server. my whole sql connection code is here. i m using windows 7 64bit. i ve download jdk for 64bit and download jdbc driver too. in the jdbc driver folder i ve copied sqljdbc.jar file in to C:\Program Files\Java\jre6\lib\ext then i ve copied to C:\Program Files\Java\jdk1.6.0_19\jre\lib\ext then C:\Program Files (x86)\Java\jre6\lib\ext. i m not sure to where to copy. also finally i ve copied sqljdbc_auth.dll file in to C:\Windows\System32. there r two sqljdbc_auth.dll files one is 32bit other one is 64bit i checked to c folder and i see there r two microsoft sql server folders one is under program files one is under programfiles(x86). i just copied sqljdbc_auth.dll 64bit version in to system32 folder. i just found these infos from internet. i m new in java. when i run the program i get an error message which is :
java.sql.SQLException: No suitable driver found for JDBC:sqlserver://localhost;java_data
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at ClientQuery.<init>(ClientQuery.java:31)
at TicketSale.<init>(TicketSale.java:68)
at TicketSale.main(TicketSale.java:409)
the name of the database i want to connect is java_data which i made in sql server. can anyone tell me where did i made wrong?
import java.sql.Connection; import java.sql.DriverManager; import java.sql.PreparedStatement; import java.sql.ResultSet; import java.sql.SQLException; import java.util.List; import java.util.ArrayList; public class ClientQuery { // class begin private static final String URL ="JDBC:sqlserver://localhost;java_data"; private static final String USERNAME ="root"; private static final String PASSWORD = " "; private Connection connection = null; private PreparedStatement selectAllClient = null; private PreparedStatement selectClientbyAirline = null; private PreparedStatement insertNewClient = null; // person query constructor begin public ClientQuery (){ try { try { Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver"); } catch (ClassNotFoundException e) { e.printStackTrace(); } connection = DriverManager.getConnection( URL, USERNAME, PASSWORD ); selectAllClient = connection.prepareStatement("SELECT * FROM Ticket"); selectClientbyAirline = connection.prepareStatement("SELECT * FROM Ticket WHERE airline = ?"); insertNewClient = connection.prepareStatement("INSERT INTO Ticket "+ "(name,surname,airline,flight_no,departure_date,departure_city,arrival_city,departure_time,arrival_time,gate,price)" + "VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)"); } // end try catch (SQLException sqlException) { sqlException.printStackTrace(); System.exit(1); } // end catch } // person query constructor end // select all client in database public List <Client> getAllClient() { List<Client> results = null; ResultSet resultSet = null; try { resultSet = selectAllClient.executeQuery(); results = new ArrayList<Client>(); while (resultSet.next()) { results.add(new Client( resultSet.getString("name"), resultSet.getString("surname"), resultSet.getString("airline"), resultSet.getString("flight_no"), resultSet.getString("departure_date"), resultSet.getString("departure_city"), resultSet.getString("arrival_city"), resultSet.getString("departure_time"), resultSet.getString("arrival_time"), resultSet.getString("gate"), resultSet.getString("price"))); } // end while } // end try catch (SQLException sqlException ) { sqlException.printStackTrace(); } // end catch finally { try{ resultSet.close(); } // end try catch (SQLException sqlException) { sqlException.printStackTrace(); close(); } // end catch } //end finally return results; } // end of get all client method // select Client by Airline public List <Client> getClientbyAirline(String name ) { List<Client> results = null; ResultSet resultSet = null; try { selectClientbyAirline.setString(1, name); resultSet = selectClientbyAirline.executeQuery(); results = new ArrayList<Client>(); while (resultSet.next()) { results.add(new Client( resultSet.getString("name"), resultSet.getString("surname"), resultSet.getString("airline"), resultSet.getString("flight_no"), resultSet.getString("departure_date"), resultSet.getString("departure_city"), resultSet.getString("arrival_city"), resultSet.getString("departure_time"), resultSet.getString("arrival_time"), resultSet.getString("gate"), resultSet.getString("price"))); } // end while } // end try catch (SQLException sqlException) { sqlException.printStackTrace(); } // end catch finally { try{ resultSet.close(); } // end try catch (SQLException sqlException) { sqlException.printStackTrace(); close(); } // end catch } //end finally return results; } // end of select by airline method public int addClient(String name, String surname, String airline, String flight_no, String departure_date, String departure_city, String arrival_city, String departure_time, String arrival_time, String gate, String price) { int result = 0; try { insertNewClient.setString(1, name); insertNewClient.setString(2, surname); insertNewClient.setString(3, airline); insertNewClient.setString(4, flight_no); insertNewClient.setString(5, departure_date); insertNewClient.setString(6, departure_city); insertNewClient.setString(7, arrival_city); insertNewClient.setString(8, departure_time); insertNewClient.setString(9, arrival_time); insertNewClient.setString(10, gate); insertNewClient.setString(11, price); result = insertNewClient.executeUpdate(); } // end try catch (SQLException sqlException) { sqlException.printStackTrace(); close(); } // end catch return result; } // end of add Client method public void close () { try { connection.close(); } // end try catch (SQLException sqlException) { sqlException.printStackTrace(); } // end catch } // end close method } // class end

Your URL string is, apparantly, incorrect. See the driver documentation.

Issues installing SQL Server 2008 instance - Install fails

Hi there,
I have a server windows server 2008 R2 standard.
While doing an Enterprise to Standard downgrade, I have removed enterprise edition of SQL Server 2008, rebooted and while installing standard edition, I get the below error saying "You
SQL server 2008 installation completed with failures. Some or all identity references could not be translated"
Bit of background. This server has another express instance of SQL Server 2008. I have used local system account, network service as well as our general SQL service account, but I get the error
towards the end of the installation and it fails saying “Some or all identity references could not be translated.”
I am installing a named instance with the same name as before but fails. I have tried creating a test instance that fails too. Any ideas? I have also run the clean up utility but no joy.
Cheers
Faltaf

Hi FAltafB,
According to your description, you come across the error that some or all identity references could not be translated. Please help to post SQL Server setup error log for analysis. By default, SQL Server setup summary and detail logs located in C:\Program
Files\Microsoft SQL Server\100\Setup Bootstrap\Log.
Based on my research, this issue could be due to the incomplete uninstallation for previous installation. Another cause could be that you are installing SQL Server after your machine becomes a domain controller.
To troubleshoot the issue, please pay attention to the points below.
1. Make sure you have administrative rights on the computer, uninstall all the components related with SQL Server 2008 enterprise from the control panel and delete registry keys mentioned in the article:
http://blogs.msdn.com/b/sreekarm/archive/2010/03/15/sql-express-is-not-installed-properly-steps-to-be-taken-before-reinstall-again.aspx
2. Use
SQL Server 2008 R2 Best Practice Analyzer to detect if SQL Server is installed on a domain controller. If SQL Server is installed on a domain controller, please demote your machine from being a domain controller and install the SQL Server again since it
is not recommended to install SQL Server on a domain controller.
Regards,
Michelle Li

Cannot connect to SQL Server 2008 Express

I install SQL Server 2008 Express on Windows 7 and make sure SQL Server(SQLEXPRESS) service is running. Then I write a program via Visual C++ & ADO, and try to connect to the local SQL Service instance by using the following SQL connection string:
“Provider=sqloledb;Data Source=(local);Integrated Security=SSPI;”
But the connection fails. I try the same code on a computer with SQL Server 2008 Professional installed and it works without problems.
Please advise. Thanks.

Hi chcw,
Are you got any error message/information while connect to SQL Server express instance faild via VC++ & ADO? If so, please post them for further investigation.
Please also check the windows firewall. Firewall systems help prevent unauthorized access to computer resources. If a firewall is turned on but not correctly configured, attempts to connect to SQL Server might be blocked. For more information, please see:
http://technet.microsoft.com/en-us/library/cc646023.aspx
If you have any feedback on our support, please click
here.
Regards,
Elvis Long
TechNet Community Support

Error while connecting to SQL SERVER from OWB

HI All,
I got the following error while connecting to SQL SERVER from OWB(10gR2).
1). Created DSN with (GMSCADA)
2). tnsnames file is updated with the following information
GMSCADA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 172.16.60.29)(PORT = 1433))
(CONNECT_DATA =
(SERVICE_NAME = SA)
3). Tried to connect to SQL SERVER frm OWB
Username: sa
password: sa
host: 172.16.60.29
port: 1433
service name: GMSCADA
schema: sa
I got the following error, when I click Test Connection:
ORA-28545: error diagnosed by Net8 when connecting to an agent
Unable to retrieve text of NETWORK/NCR message 65535
ORA-02063: preceding 2 lines from OWB_3095
Regards,
Kumar.

Hi David,
What is Gateway, How I have to setup, Please let me know.
I tried according to the Demo, But still I am facing the same problem. Which system IP I have to put in the host details.
Can u please let me know.
Regards,
Kumar.

Cannot connect to SQL Server 2008 R2 Express

I have a database application that connects to the Northwind sample db in MS Access and lets the user perform CRUD operations.
Now I want to add the same for MS SQL Server, however, I have trouble connecting to it using this connection string:
I changed the server properties in SQL Server Management Studio to allow windows and SQL Server authentication, yet, I still get this exception when trying to open the connection:
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)
I thought it might be because the server is not allowing remote connections and followed this guide to allow remote connections:
http://www.linglom.com/2009/03/28/enable-remote-connection-on-sql-server-2008-express/
But the SQL Server windows service won't start. The Browser works fine, but the server doesn't do anything.
When trying to start it I get this error:
The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details.
The event log says:
2011-07-07 17:02:55.35 spid51 Starting up database 'Northwind'.
2011-07-07 17:02:59.98 spid51 Starting up database 'Northwind'.
2011-07-07 17:03:03.68 spid53 Starting up database 'Northwind'.
2011-07-07 17:03:07.01 spid55 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2011-07-07 17:03:07.30 spid55 Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2011-07-07 17:03:07.76 spid55 Starting up database 'pubs'.
2011-07-07 17:03:08.89 spid55 Starting up database 'pubs'.
2011-07-07 17:03:09.30 spid55 Starting up database 'pubs'.
2011-07-07 17:04:11.37 spid55 Starting up database 'pubs'.
2011-07-07 17:08:17.28 spid52 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2011-07-07 17:08:17.35 spid52 Using 'xplog70.dll' version '2009.100.1600' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
However, when starting SQL Server Management Studio, I can normally work with the databases, perform CRUD operations, etc.
I was wondering if it might be a connection string issue.
I'm using this string:
@"Server=lolcalhost;Database=Northwind;User ID=BEN-A350C47E32F;Password=;Trusted_Connection=False;";
I added the Northwind database as data source to the project and the connection string is in the app.config:
<connectionStrings>
<add name="NwindConnectionString" connectionString="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=|DataDirectory|\Nwind.mdb" providerName="System.Data.OleDb"/>
</connectionStrings>
using this code to access it:
constringServer = ConfigurationManager.ConnectionStrings["NwindConnectionString"].ToString();
but when using this string I get an ArgumentException:
Keyword not supported: 'provider'.
I'd appreciate any help that would let me connect to the server from a program.

Here is an active Sql connection string we use currently from our app.config file:
<connectionStrings>
<clear/>
<add name="ServerConnectionString" connectionString="Data Source=SqlBox;Initial Catalog=YourCatalog;User Id=Username; Password=password;" providerName="System.Data.SqlClient"/><br/> </connectionStrings>
here is one for Sql Express:
<add name="LocalConnectionString" connectionString="Data Source=MachineName\SqlExpress;Initial Catalog=YourCatalog;Integrated Security= true;" providerName="System.Data.SqlClient"/>

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

How to secure connection in sql server 2008? my main problem is which certificate should i add in mmc

i'm recently working on hardening of sql server 2008. now i face with a problem. my problem is how to secure connection in sql server 2008? my main problem is which certificate should i add in mmc? what are these certificates about?and guide
me in choosing the appropriate certificate.
and how should i know that the connection in sql server is secured?
plz guide me from the beginning cause i'm rookie in this subject.
thanks in advance.

Hi sqlfan,
Question 1: my problem is how to secure connection in sql server 2008?
Microsoft SQL Server can use Secure Sockets Layer (SSL) to encrypt data that is transmitted across a network between an instance of SQL Server and a client application. For more information about Encrypting Connections to SQL Server, please refer to the following
article:
http://technet.microsoft.com/en-us/library/ms189067(v=sql.105).aspx
Question 2: my main problem is which certificate should i add in mmc? what are these certificates about?and guide me in choosing the appropriate certificate.
To install a certificate in the Windows certificate store of the server computer, you will need to purchase/provision a certificate from a certificate authority first. So please go to a certificate authority to choose the appropriate certificate.
For SQL Server to load a SSL certificate, the certificate must meet the following conditions:
The certificate must be in either the local computer certificate store or the current user certificate store.
The current system time must be after the Valid from property of the certificate and before the Valid to property of the certificate.
The certificate must be meant for server authentication. This requires the Enhanced Key Usage property of the certificate to specify Server Authentication (1.3.6.1.5.5.7.3.1).
The certificate must be created by using the KeySpec option of AT_KEYEXCHANGE. Usually, the certificate's key usage property (KEY_USAGE) will also include key encipherment (CERT_KEY_ENCIPHERMENT_KEY_USAGE).
The Subject property of the certificate must indicate that the common name (CN) is the same as the host name or fully qualified domain name (FQDN) of the server computer. If SQL Server is running on a failover cluster, the common name must match the host
name or FQDN of the virtual server and the certificates must be provisioned on all nodes in the failover cluster.
Question 3: how should i know that the connection in sql server is secured?
If the certificate is configured to be used, and the value of the ForceEncryption option is set to Yes, all data transmitted across a network between SQL Server and the client application will be encrypted using the certificate. For more detail about this,
please refer to Configuring SSL for SQL Server in the following article:
http://technet.microsoft.com/en-us/library/ms189067(v=sql.105).aspx
If you have any question, please feel free to let me know.
Regards,
Donghui Li

Could not connect to sql server 2008 R2

TITLE: Connect to Server
Cannot connect to SURENDRA-PC\MSSQLSERVER.
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: 25 - Connection string is not valid) (Microsoft SQL Server, Error: 87)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=87&LinkId=20476
BUTTONS:
OK

Hi Shravan,
According to my research, besides the causes from SQL Server services, firewall, protocol according to other people’s posts, the issue could also be due to the wrong server name, or the remote connections are not allowed. To work around your issue, please
pay attention to the points below.
Firstly, for the local connection to SQL Server default instance, please just type [.] dot or 'localhost','(local)' in server name field according to Shashikant’s post.
Secondly, for the remote connection to SQL Server default instance, please make sure that 'Allow remote connections to this server' is checked in Server Connections properties in SQL Server Management Studio referring to the
article. And just type the computer name in server name field, like SURENDRA-PC.
Regards,
Michelle Li

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

How to enable remote connections in SQL Server 2008

I'm trying to enable remote connections in SQL Server 2008 R2 as described in the following article. I see the error message at the top of the article.
http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx
One step in the article describes how to enable TCP/IP in Configuration Manager.  Specifically it says that
'SQL Server NETWORK Configuration' should have TCP/IP enabled.
The issue I've encountered is that my Configuration Manager
is different than what appears in the article. My Configuration Manager shows the following:
SQL Server 2005 Services
SQL Server 2005 Network Configuration (32 bit)
      - Protocols for SQLExpress
SQL Native Client Configuration (32 bit)
       - Client protocols
       - Aliases
Note that I see 'SQL Server 2005 Network Configuration'
rather than that for 2008. When 'Protocols for SQLExpress'
is expanded, there is a TCP/IP setting, but it's disabled and I see an
Access Denied message if I try to enable this.
I also see a TCP/IP setting under Client protocols and successfully enabled this. This uses port 1433 and I configured my firewall to accomodate this port as suggested in the article.
I also followed the other steps in the article, but still don't have remote access to SQL Server 2008 R2. (I can access it from the office.) I'm wondering if this remote access issue is because SQL Server
2008 Network Configuration does not appear in Configuration Manager
and if so, I'm interested in how this might be resolved. (I'm running Windows 7 - 64 bit.)
I'd appreciate any ideas on this. Thanks.

Hello,
Please refer to the following resource.
http://support.microsoft.com/kb/KbView/914277
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

-net.sourceforge.jtds.jdbc.Driver ERROR WHILE CONNECTING TO SQL SERVER

Hi,
While making a new connection to Sql Server Express Edition Database, through Oracle Sql Developer i am getting a problem when retrieving the database.The error is "-net.sourceforge.jtds.jdbc.Driver" .I have downloaded the "jTDS - SQL Server and Sybase JDBC driver " from sourceforge website, but i am confused about where to paste it.
thanks.

I'm not sure why you are having the error but I am sure of the following:
1. This forum is not appropriate for SQL*Developer questions.
2. Or questions about code from SourceForge
3. Or Microsoft products.
It seems unlikely this has anything to do with Oracle so I would recommend you find a forum related to the driver if one exists. Otherwise you can try the SQL*Developer forum but I would be there aren't more than a dozen other people on the product trying to do this.

Having problem while connecting to SQL Server through a application

hi guys ,
having one problem while connecting to the SQL SERVER 2008 R2 through a application (Dynamics NAV), by using the concept of Linked Server.
But one more thing , i am able to access that very SQL server through my app , when i am working locally , i mean to say that when i am working on the machine itself on which the server is installed then its working fine .
But when i am working on another system the query doesn't work.

by using the concept of Linked Server.
Why through a linked server and not directly as a simple remote connection? I don't think you app is aware of linked server.
Olaf Helper
[ Blog] [ Xing] [ MVP]

How to Configure Remote Connections To SQL Server 2008 R2 Express

Post written June 10, 2010 and pertains to:
SQL Server 2008 R2 Express on both my server and local machines: SQLX_SRV,
SQLX_LOC
SQL Server 2008 R2 Management Studio on both my server and local machines:
MS_SRV, MS_LOC
Windows Server 2008 R2 Enterprise installed on a Hyper-V VPS: WS
SQL Server Configuration Manager on both my server and local machines:
CMGR_SRV, CMGR_LOC
Server Manager: SMGR
I am connecting to my hosting server via Remote Desktop Connection: RDC
I installed SQLX_SRV and MS_SRV on my hosting server and SQLX_LOC and MS_LOC on my local development machine. I am able to use MS_LOC to connect to SQLX_LOC and to use MS_SRV to connect to SQLX_SRV. However I am not able to use MS_LOC to connect
with SQLX_SRV. Here's what I have done so far:
SMGR -> Configuration -> Windows Firewall to turn off the Windows Firewall for Domain, Private and Public profiles. Obviously I'll change this later, but until I can connect I want to remove as many variables as possible.
CMGR_SRV -> SQL Server Services to confirm that both SQL Server (SQLEXPRESS) and SQL Server Browser services were running.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS to ENABLE the Shared Memory, Named Pipes, and TCP/IP protocols and DISABLE the deprecated VIA protocol.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS -> double click TCP/IP to open the TCP/IP properties dialogue. On the Protocol tab Enabled: Yes, Keep Alive: 30000, changed Listen All to No. I've tried it both
ways, but I've got six IP addresses on my server and I wanted to configure SQLEXPRESS to listen to only the first and primary IP. On the IP Addresses tab went to IPALL and cleared the TCP Dynamic Ports field and entered 1433 in the TCP Port field.
For my first and primary IP Address I made sure that Enabled was Yes, I cleared the TCP Dynamic Ports field, and entered 1433 in the TCP Port field. For all other IP Addresses Enabled was set to No and I cleared both the TCP Dynamic Ports and TCP Port
fields.
CMGR_SRV -> SQL Server Services -> SQL Server (SQLEXPRESS) right click and Restart. This of course stopped and restarted my instance of SQLX_SRV enabling the TCP/IP configuration in the previous step to take effect.
On my server, SQLX_SRV is the only instance of SQL Server running and so it's easy to hard wire it to the default port 1433.
The instance name for both SQLX_SRV and SQLX_LOC is the default "SQLEXPRESS". My server machine name is "SERVER1" on the EnglishBrains.com domain. So the proper local name (local within the context of my remote server as connected via RDC) for
my instance of SQLX_SRV would be:
SERVER1\SQLEXPRESS
Note the use of a backslash NOT a forward slash.
Of course to connect remotely from my development machine, which is not on the same domain as my hosting server, I would need to specify the domain as well, so the SQL Server name becomes:
SERVER1.EnglishBrains.com\SQLEXPRESS
I must also use SQL Server Authentication. Before I can use such a remote connection, however, there are still several configuration steps required. So on my server (connected via RDC) I used MS_SRV to connect to SQLX_SRV using SERVER1\SQLEXPRESS
for the server name and Windows Authentication. Once connected I performed the following steps:
MS_SRV -> right click the connected parent SERVER1\SQLEXPRESS instance node at the top -> Properties -> Security -> Server authentication: select "SQL Server and Windows Authentication mode". This will enable connections using either type
of authentication.
Next, leaving the Server Properties dialogue open, Connections -> check "Allow remote connections to this server" box.
Click OK to save these changes and close the Server Properties dialogue.
MS_SRV -> Security -> right click Logins and select "New Login...", the Login - New dialogue opens.
On the General page Enter a name for your new login
Select SQL Server Authorization
Enter and confirm a password
Uncheck Enforce password expiration
Select the default Database and Language
On the ServerRoles page Public will be checked, also check SysAdmin. This is probably not a good idea and I'll uncheck this as soon as I can connect to the SQLX_SRV.
On the User Mapping page select the databases you want your new Login to access and enter the Default Schema of "dbo".
At the bottom of the User Mapping page you'll see the Database Roles table. Public will be selected by default. Also select db_Owner. Again this is probably not a good idea, and I'll refine this once I can connect.
On the Status page confirm that "Grant" is checked under "Permission to connect to database engine" and "Enable" is checked under "Login".
Click OK to save all changes and close the Login - New dialogue.
With these steps completed you should now be able to use MS_SRV to connect to SQLX_SRV using SQL Server Authentication by supplying the name and password for your new Login. I tried this and it worked fine. Next I tried to use this same login
remotely, that is I went to my local development machine and used MS_LOC to try and connect to SQLX_SRV by using
SERVER1.EnglishBrains.com\SQLEXPRESS
and opting for SQL Server Authentication and supplying the name and password of my new login.
THIS DID NOT WORK?? Instead I get the following error message:
Cannot connect to SERVER1.EnglishBrains.com\SQLEXPRESS.
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://www.microsoft.com/products/ee/transform.aspx?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1
If you follow the suggested help link, you are told:
The SQL Server client cannot connect to the server. This error could be caused by one of the following reasons:
A specified SQL Server instance name is not valid.
The TCP, or named pipes protocols are not enabled.
The firewall on the server has refused the connection.
The SQL Server Browser service (sqlbrowser) is not started.
WRONG on all 4 counts! The instance name IS valid. Both TCP/IP and Named Pipes protocols are enabled. The firewall has been shut down, so it is not relevant. Finally the SQL Server Browser IS started.
The next thing I tried was to circumvent discovery by the SQL Browser service by using the following syntax to specify the IP address and port directly when specifying the SQL Server name.
tcp:68.71.134.186,1433
Using this in the Server Name field I was able to use MS_SRV to successfully connect to SQLX_SRV (using SQL Server Authentication of course) with or without the SQL Browser service running.
However when I tried to connect from MS_LOC to SQLX_SRV using this same login (WITH SQL Browser service running just for good measure) it does not work?? I get the following error message:
Cannot connect to tcp:68.71.134.186,1433.
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:
TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
If you follow the help link you are told:
"The SQL Server client cannot connect to the server. This error could occur because either the firewall on the server has refused the connection or the server is not configured to accept remote connections."
However, the firewall has been shut down and the server HAS been configured to accept remote connections!
I confirmed that i could indeed Ping to 68.71.134.186 and running NetStat -a |find /i "listening" on the server shows that the server is indeed listening at 68.71.134.186 Port 1433 -- which is why I was able to connect to SQLX_SRV using MS_SRV with
tcp:68.71.134.186,1433 .
IN SUMMARY: Even though I can connect to my SQLEXPRESS instance multiple ways from the server itself, I cannot connect remotely from my development machine!
If anyone can help me figure out why I would be very, very grateful!

My two cents to help you out on c# code example to configure the remote sql server express.
Hope it helps. It works, but you have to be extra carefull to read it all and setup the server configuration and netsh commands; also the port fowarding on the router.
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Data.SqlClient;
namespace sqlremoteconnection
class Program
static void Main(string[] args)
// this is the local sql server connection
// 192.168.1.101\SQLEXPRESS
// now, the configuration for remote access:
// activate SQL SERVER BROWSER - set it to start "automatic"; then START UP
// SQL Server Configuration Manager
// --> SQL SERVER BROWSER -> properties -> Service -> Start Mode -> automatic -> apply
// --> Log On -> Start -> Ok
            // netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = all profile = CURRENT
            // netsh firewall set portopening protocol = UDP port = 1434 name = SQLPort mode = ENABLE scope = all profile = CURRENT
            // netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = any profile = PUBLIC
            // netsh advfirewall firewall add rule name = SQLPort dir = in protocol = udp action = allow localport = 1434 remoteip = any profile = PUBLIC
// VERY IMPORTANT FOR REMOTE ACCESS: you have to add the rules on port fowarding
// on the router!!!
// TCP: 1433
// UDP: 1434
// or just a personal port like TCP 31433/UDP 31434
// read carefully the netsh commands above
// server name: 123.132.24.177\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,1433 <<-- regular port
// server name: anyurl.myftp.org\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,31433 <<-- WOW different PORT here!!!
SqlConnection myConnection = new SqlConnection(
"user id=sa;" +
"password=password_goes_here!;" +
"server=anyurl.myftp.org\\SQLEXPRESS,31433;" +
//"Trusted_Connection=no;" +
"database=database_name_here; " +
"connection timeout=30");
try
myConnection.Open();
catch (Exception e)
Console.WriteLine(e.ToString());
try
SqlDataReader myReader = null;
SqlCommand myCommand = new SqlCommand("select * from mytable", myConnection);
myReader = myCommand.ExecuteReader();
while (myReader.Read())
Console.WriteLine(myReader["tab01_name"].ToString());
Console.WriteLine(myReader["tab01_age"].ToString());
catch (Exception e)
Console.WriteLine(e.ToString());
try
myConnection.Close();
catch (Exception e)
Console.WriteLine(e.ToString());
Adelino Araujo

Getting Frequent time out while Connecting to SQL server 2008 Instance installed on VmWare

Similar Messages

Maybe you are looking for