Shared Services Connection to SQL Server Failed

Hi all
Am trying to configure an SQL Server 2005 user directory in Hyperion
Shared Services and have got to the screen where I need to type in
all of the database details (i.e. Type, Name, Server, Port, etc) and
a username/password but I keep getting the message:
Connection Failed. Not enough privileges to connect to the directory
server...
I'm trying to connect to the "hypdb" database I've set up in SQL and
have tried the username "hypuser" which is set as the database owner
and another login which I've called "SysAdmin" and has system
administrator priviliges.
Have also tried the system generated used ID "sa" but again no luck.
Am I missing a setting for these logins in SQL which is stopping
Shared Services being able to log in as them?
Also, for the "Name" box on this Shared Services window do I just
come up with my own unique name for the server or does it have to be
something that has already been defined?

Hi,
The first things to know when you connect to MS SQL SERVER is the host or ip address and the port.
If these are correct when you click on RETRIEVE DATABASE, you are able to see all database on the server you specified.
So that means connection is ok, but of course user and password may be incorrect at this level.
If no database are retrieved, that means the host or/and port are not correct.
So before click on TEST, are you able to retrieve the database with RETRIEVE DATABASE button?
Are you able to ping the remote machine (SQL SERVER) with ip address or hostname?
Are you sure about the port for the SQL Server?
Regards,
Mireille

Similar Messages

  • Sharepoint 2013 SSRS Interaction with Sql Server 2012 Reporting Services connecting to Sql Server 2008 R2 database

    Hi
    I'm working on upgrading sharepoint 2010 to sharepoint 2013 with sql server 2008 r2. I've ran into some problems but have been able to get a test farm upgraded. However to run SSRS 2013 it seems Sql Server 2012 Reporting Services are required. Upgrading
    to a full sql server 2012 database isn't an option. I know that sql server 2012 reporting services can use sql server 2008 r2 as a catalog and content database so I was wondering could this be a workaround? Importantly would I need a separate machine/virtual
    machine to host sql server 2012 reporting services? or could it live on the sql server 2008 r2 machine? Any pointers appreciated. Thanks Dan

    Remember that SSRS must be deployed on the SharePoint server. Having said that, yes you can install SSRS 2012 SP1 on a server running SQL 2008 R2. And yes, you can use 2008 R2 as your Database Engine server while SSRS 2012 SP1 runs on the SharePoint server.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Database adapter service connecting to SQL server

    I need to connect to our SQL server db and create a db adapter service. I am getting an error message that "connection is busy with results from another command". What do I need to do to resolve this? I tested the jdbc-odbc connection and it connected successfully. Please advise.

    Can someone help me figure out what I need for this error message now? It is from a db adapter to SQL Server.
    <messages><input><invokeICFEES_dbadapterICFEES_InputVariable><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="dbadapterICFEESInput_msg"><dbadapterICFEESInput xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/dbadapterICFEES">begin</dbadapterICFEESInput>
    </part></invokeICFEES_dbadapterICFEES_InputVariable></input><fault><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>null</code>
    </part><part name="summary"><summary>file:/u01/app/oracle/product/10.1.3.1/OracleAS_soa/bpel/domains/default/tmp/.bpel_SIPAFeeExtract_1.2_03419ae821e14ce186f5e40ee5ff1c24.tmp/dbadapterICFEES.wsdl [ dbadapterICFEES_ptt::dbadapterICFEES(dbadapterICFEESInput_msg,dbadapterICFEESOutputCollection) ] - WSIF JCA Execute of operation 'dbadapterICFEES' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    ; nested exception is:
         ORABPEL-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the server. Caused by Exception [TOPLINK-4003] (Oracle TopLink - 10g Release 3 (10.1.3.1.0) (Build 061004)): oracle.toplink.exceptions.DatabaseException
    Exception Description: Configuration error. Class [com.microsoft.jdbc.sqlserver.SQLServerDriver] not found..
    </summary>
    </part><part name="detail"><detail>
    Exception Description: Configuration error. Class [com.microsoft.jdbc.sqlserver.SQLServerDriver] not found.</detail>
    </part></bindingFault></fault></messages>

  • .Using Oracle Heterogeneous Services Connectivity to SQL Server :ORA-02068

    Hi,
    I using oracle HS to connect sql server but error ora-02068: following server from HSSQL and ORA-03135 connection lost contact.
    step by step
    1. Create the init.ora file = initHSSQL.ora
    HS_FDS_CONNECT_INFO = HSSQL
    HS_FDS_TRACE_LEVEL = OFF
    2. modified listener.ora file
    SID_LIST_LISTENERHSSQL =
    (SID_LIST =
    (SID_DESC=
    (SID_NAME=HSSQL)
    (ORACLE_HOME = C:\oraclexe\app\oracle\product\10.2.0\server)
    (PROGRAM=hsodbc)
    LISTENERHSSQL =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
    (ADDRESS = (PROTOCOL = TCP)(HOST = CEPITA1403.siam.local)(PORT = 1521))
    and start listernerHSSQL = pass
    3.modified tnsname.ora :
    HSSQL =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = CEPITA1403.siam.local)(PORT = 1521))
    (CONNECT_DATA =
    (SID = HSSQL)
    (HS = OK)
    and test by tnsping HSSQL = OK
    4.setup ODBC SQL Server
    Start --> Control Panel --> Administrative Tools --> Data Sources (ODBC)
    Click on the ‘System DSN’ tab.
    Click ‘Add’.
    Name HSSQL
    Click ‘Test Data Source…’.--> Pass
    5
    create public database link HSSQL
    connect to sa
    identified by xxxxxxxx
    using 'HSSQL';
    Database Link created.
    6. select * from ACCOUNT_CODE@HSSQL;
    show error message : ora-02068: following server from HSSQL and ORA-03135 connection lost contact.
    Please let me know.
    rose
    Edited by: user7218901 on Mar 25, 2009 12:39 AM

    Do you have all of your parameter files set up correctly?
    You need to have a hsora file in the hs/admin directory for ioi for instance, initioiDB.ora. In this file you need to set up your hs init parameters. This is an example of what's in one of mine:
    HS_FDS_CONNECT_INFO = Mapics
    HS_DB_NAME = MAPICS
    HS_DB_DOMAIN = WORLD
    HS_FDS_TRACE_LEVEL = ON
    The you need to have an entry in the tnsnames.ora file in the network/admin directory for hsodbcxtrad. The sid should be set to ioiDB.
    You can find documentation on how to manage heterogenous services in the online documentation.
    Managing Heterogenous Services Using Generic Connectivity
    Hope this helps
    Eric
    I have been trying to set up a database link between Oracle and SQL Server, currently both on the same Windows NT machine.
    I managed to create the link as follows:
    CREATE PUBLIC DATABASE LINK ioi
    CONNECT TO IOItest IDENTIFIED BY mba
    USING 'hsodbcxtrad';
    The link is created successfully.
    I then try to run a query and get the following error :
    select * from dealer@ioi
    ERROR at line 1:
    ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
    [Generic Connectivity Using ODBC]DRV_InitTdp: [Microsoft][ODBC SQL Server
    Driver][SQL Server]Login failed for user '\'. (SQL State: 28000; SQL Code:
    18456)
    ORA-02063: preceding 2 lines from IOI
    I have added a UID and PWD to the registry settings for the SQL Server DSN but this makes no difference. Do I need to specify a username and password somewhere else ?
    Thanks
    Hugh

  • ODBC connectivity to SQL-Server fails

    Oracle 11.2.0.2 on Enterprise Linux Enterprise Linux Server release 5.4 (Carthage).
    Using FreeTDS unixODBC Driver to connect to a MS SQL-Server 2008 R2 SP1database. (RPM package freetds-0.64-1.el5.rf.x86_64 reported by yum whatprovides for ODBC FreeTDS .so).
    ODBC isql connectivity works and SQL select Col1 from Schema.Table is successfully executed against DSN, and returns rows/data (not real names).
    Same SQL in Oracle, select "Col1" from "Schema"."Table"@dblink fails (using the same ODBC DSN as isql test cor connectivity), via sqlplus.
    Debug trace (HS_FDS_TRACE_LEVEL=debug) reports:
    Exiting hgopars, rc=28500 at 2013/06/19-14:12:08 with error ptr FILE:hgopars.c LINE:570 FUNCTION:hgopars() ID:SELECT list of size 0 is not valid
    Have enabled/disabled numerous combinations of odbc.ini and init.ora parameters such QuotedId,  HS_FDS_SQLLEN_INTERPRETATION, HS_FDS_SUPPORT_STATISTICS and so on. Also tried using DBMS_HS_PASSTHROUGH, instead of native SQL via sqlplus. Same error, consistently.
    Interestingly, the desc "Schema"."Table"@dblink call works fine in sqlplus - but according to the debug trace it lets the ODBC driver deal with it - it does not craft a SQL and pass this to the ODBC driver, according to the debug trace. Instead an ODBC interface call is used to describe the object.
    So, ODBC driver seems  perfectly fine. Oracle can successfully use it as the desc command proved. Except that SQL statements (from Oracle) via the driver fails.
    Any ideas as to what the problem can be?

    Yes, thanks Mike.
    Ran into a brick wall troubleshooting, have developers and project managers doing what seems to be an ugly dance (think that is what they are doing with the up and down jumping movements).
    With no responses to my posting here, and my dislike of bad dancing, went the SR route instead.
    Appreciate you looking at the posting though. Makes me feel less alone in a world of bad dancers...

  • 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

  • Connecting to the LOB system has failed. A network-related or instance-specific error occurred while establishing a connection to SQL Serve

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

    Hi, 
    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.

  • 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

  • Can't Create a Data Source - Failed to test connection. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied

    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

  • 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

    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>

  • Reporting Services 2008 R2 configuration error: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

    Hi, I am using SQL Server 2008 R2 and on one of our dev boxes I am trying to setup ReportServer using ReportingServices Configuration manager. This is was installed longtime back and during installation they created a service account for reporting services.
    When I try to configure the service account I do not get the service account created during the installation in the pull down and if I were to use something different I get this "Named Pipes Provider, error: 40 - Could not open a connection to SQL Server"
    error.
    Thanks in advance...........
    Ione

    Hi,
    Take a look at this blog - http://blogs.msdn.com/b/sql_protocols/archive/2007/03/31/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server.aspx
    I hope it will help.

  • 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?
    Thanks

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

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

  • 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

Maybe you are looking for