Error connection to sql server files (*.mdf)

please tell me how i resolve this error
"error connection to sql server files (*.mdf) require SQL Server Express 2005 to function properly. Please verify the installation of the component or download from the URL: http://go.microsoft.com/fwlink/?LinkId=49251"
whenever i tried to make database i got this error.
please help me

please tell me how i resolve this error
"error connection to sql server files (*.mdf) require SQL Server Express 2005 to function properly. Please verify the installation of the component or download from the URL: http://go.microsoft.com/fwlink/?LinkId=49251"
whenever i tried to make database i got this error.
please help me
Hello,
After googling I found below
http://forums.asp.net/t/1120411.aspx?connection+to+SQL+Server+files+mdf+require+SQL+server+express+2005+to+function+properly+ 
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Similar Messages

  • Connecting to sql server database mdf file without installing sql server on client machine?

    I am creating a window application that need to use sql server database. I want to install this application to client machine without installing sql server so that my application can still connect to a database i.e mdf file that i will be providing at client
    system.
    How can i connect to a database(mdf) on client machine through my window application without installing sql server. ? I dont know is it possible or not.
    If possible what will be the connection string in that case. Database need not be used in network.

    you cant connect and view the internals of mdf file unless it being attached to a sql server instance as a database.
    The sql server instance can be installed in any box which is in the same domain and then you can connect from your application to it.
    Please Mark This As Answer if it solved your issue
    Please Mark This As Helpful if it helps to solve your issue
    Visakh
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • Error connecting to SQL  server 2005 from Dreamweaver 8

    Hi I have a database in SQL server 2005.I just started using
    dreamweaver's server behaviours.When I use the "log in" behaviour I
    get the following error.
    Microsoft VBScript compilation (0x800A0401)
    Expected end of statement
    /MyBlog/Connections/connBlog.asp, line 9, column 38
    MM_connBlog_STRING = Provider=SQLOLEDB;workstation
    id="FAZ-F6EE655890B";integrated security=SSPI;data
    source="FAZ-F6EE655890B\SQLEXPRESS";persist security
    info=False;initial catalog=MyBlog;
    -------------------------------------^
    First thing that came to my mind was obviously my database
    conn isnot right but when I define a conn using the built in
    dreamweaver's dialogue and test it, it says that the test
    succeeded.Also in the dialogue for the "login page" it shows the
    values of fields from the database, so it is definitely connecting
    to the database.So I don't know why am i getting this error.Please
    someone help!

    See if this TechNote helps:
    ASP error "VBScript compilation error '800a0401' "
    http://www.adobe.com/go/15717
    Are you using the ASP VBScript server model?
    Try creating a simple recordset that displays all records
    from a table and
    see if you can get that to work. It's less complex code than
    the user
    authentication server behavior and might help to isolate the
    problem.
    David Alcala
    Adobe Product Support

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

    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)(Microsoft SQL Server, Error: 2)
    The system cannot find the file specified
    Cannot connect to COWBOYS.
    Here are the technical details===================================
    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) (.Net SqlClient Data Provider)
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
    Error Number: 2
    Severity: 20
    State: 0
    Program Location:
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
       at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer
    timeout)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance,
    SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
       at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
    ===================================
    The system cannot find the file specified
    I have tried from so many forms. This is so frustrating. Thank for everyone/anyone who wants to help. So this is what happened: I had to uninstall my previous sqlserver 2012(which worked great) for some reason, and I uninstalled everything from that download.
    Then I installed the trial edition of sql server 2012 (64 Bit) and It wouldn't connect to the database. (Error mentioned above.) My local DB is COWBOYS. (COWBOYS is also my computer name.) After this, I have tried downloading sqlexpress and sqlserver 64bit
    many times and cannot connect to my local DB. 
    How do I connect to my Local DB? 
    Also, I think this might help: (When I run sqlserve.exe, which I was able to find in C:\Program Files\Microsoft SQL Server\110\LocalDB\Binn, I get an error: Your SQL server installation is either corrupt or has been tampered with(Error getting
    instance ID from name). Please uninstall then re-run setup to correct this problem.
    I would happily re install it, if it wasn't my 20th time.
    I don't have any remote connections, I don't use username/password, only window authentication. I work mostly on visual studio, but without able to store /retrieve data, I don't know how to survive.
    May be the solution is very simple, but I am too frustrated. 
    Some of the things I have tried:
    From a command prompt, enter one of the following commands:
    net start "SQL Server Agent (MSSQLSERVER)" OR 
    net start "SQL Server Agent(instancename)"(for instance)
    on my sql configuration, I cannot start anything because there is nothing there to start. I can post more details, if that would help. Also, some more details about the error:
    Details
    Product:
    SQL Server
    ID:
    2
    Source:
    MSSQLServer
    Version:
    10.0
    Component:
    SQLEngine
    Message:
    An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error:
    40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
    Explanation
    SQL Server did not respond to the client request because the server is probably not started.
    User Action
    Make sure that the server is started.
    Version:
    9.0
    Component:
    SQLEngine
    Message:
    An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error:
    40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
    Explanation
    SQL Server did not respond to the client request because the server is probably not started.
    User Action
    Make sure that the server is started.
    Any one that can help me, I will be greatful. Thank you so much. p.s. please ask me anything if you have any questions.

    It sounds like there are a couple things going on here.  First check if you have a successful install of SQL Server, then we'll figure out the connection issues.
    Can you launch SQL Server Configuration Manager and check for SQL Server (MSSQLSERVER) if default instance or SQL Server (other name) if you've configured your instance as a named instance.  Once you find this, make sure the service is started. 
    If not started, try to start it and see if it throws an error.  If you get an error, post the error message your hitting.  If the service starts, you can then launch SSMS and try to connect.  If you have a default instance, you can use the machine
    name in the connection dialog.  Ex:  "COWBOYS" where Cowboys is the machine name.  However, if you named the SQL Server instance during install, you'll need to connect using the machine\instance format.  Ex:  COWBOYS\Romo (where Romo
    is the instance name you set during install).
    You can also look at the summary.txt file in the SQL Server setup error logs to see what happened on the most recent install.  Past install history is archived in the log folder if you need to dig those up to help troubleshoot, but the most
    recent one may help get to the bottom of it if there is an issue with setup detecting a prior instance that needs to be repaired.
    Thanks,
    Sam Lester (MSFT)
    http://blogs.msdn.com/b/samlester
    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
    "Mark as Answer" and
    "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

  • Re: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

    Hi,
    I'm encountering an issue with "Named Pipes Provider, error: 40 windows" and am having problems determining how to fix it due to the environment I'm using.  I have two SQL Servers installed on two separate Win2K3 Server boxes, one is SQL Server 2000 and the other is SQL Server 2005.  The SQL Server 2000 contains the actual application data.  The 2005 database is used only for Reporting Services.  I've set up the reports on SSRS such that their datasources hit the 2000 server.  This is using SQL Server authentication.
    When testing the reports via SSRS (in Visual Studio 2005), the connection to the data works and the reports are generated fine.  When I deploy them to the reporting server and launch IE to test locally (still on the 2005 box), I get this "Named Pipes Provider, error 40" issue.  I made sure that Named Pipes and TCP were enabled and the port set at 1433 (to match that on the 2000 box). 
    Now I changed the datasource's authentication from SQL Server to Windows authentication.  I tested this in SSRS and this works too.  When I redeployed the reports with this authentication change, testing the reports via IE locally (on the 2005 box) worked.  Great.  Now when I open IE on an external box, i.e. on the 2000 box, and try to test the reports, I get this same error 40 issue.  I've been through a few threads describing the error 40, fiddling around with the SQL Server configuration as well as SSRS, to no avail.  I have a feeling this error 40 issue has to due with permissions/authentication between the SQL Server boxes but I can't really be sure.  Anyone have any ideas on how to troubleshoot my situation.  Thanks.
    larry

    Named Pipes Provider, error: 40 - Could not open a connection to SQL Server :
    I.   Incorrect connection string, such as using SqlExpress.
    Check out: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=558456&SiteID=17
                    https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1245564&SiteID=1
    The typical error when dealing with Express includes:
    a.  User is not aware of SqlExpress was installed as a named instance, consequently, in his/her connection string, he/she only specify ".","localhost" etc instead of ".\SqlExpress" or "<machinename>\Sqlexpress".
    b. Np was disabld by default after installing SqlExpress.
    c. If Sqlexpress was installed on the remote box, you need to enable remote connection for Express.
    Please read the following blog for best practice of connecting to SqlExpress.
    http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx
    II. Named Pipes(NP) was not enabled on the SQL instance.
    Check out: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=136253&SiteID=1
    Oppose to SQL 2000 which turn on all protocols, SQL 2005 SKUs turn off NP by default. So, when you see this error, please check:
    1) Go to SQL Server Configuration Manager, See Server has NP enabled.
    2) %windir%\program files\microsoft sql server\mssql.1\mssql\log, notepad ERRORLOG, see whether Server is listening on NP.  You should see "Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ] or [\\.\pipe\mssql$<InstanceName>\sql\query]"
    3) Notice that "sql\query" is the default pipe name, so you need to know server is listening on which pipe name. eg: if you specify server pipe name is "sql\query1", then you would see in the errorlog that server listening on [ \\.\pipe\sql\query1 ], and go to SQL Server Configuration Manager, click client Named Pipe properties, see whether the pipe name is same with the one server listening on.
    4) If you are using SQL Native Client ODBC/OLEDB provider({SQL Native Client} or SQLNCLI), go to SQL Configuration Manager, click client protocols, make sure NP and TCP are both enabled. Right click properties of NP, make sure client is using the same pipe name as server for connection.
    5) If you are using MDAC ODBC/OLEDB({SQL Server} or SQLOLEDB) provider, in command line, launch "cliconfg.exe" and make sure NP enabled and right pipe name specified.
    III. Remote connection was not enabled. 
    Check out: when you right click on the Server in SQL Server Management Studio, in Connections, the Remote server connections part, you have enabled the "Allow remote connections to this server" check box
    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=322792&SiteID=1
    https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=763875&SiteID=1
    If you are making a remote connection, namely, your target SQL Server is on the different box as client application, you might need to check whether:
    a. "File and Printer Sharing" was opened in Firewall exception list.
    b. Please see the blog for enabling remote connection for express and troubleshooting tips of remote connection.
    http://blogs.msdn.com/sql_protocols/archive/2005/11/14/492616.aspx
    http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx
    IV. Server not started, or point to not a real server in your connection string.
    Check out: Open SQL Server Surface Area Configuration and ensure all the required services are started, Remote Connections are configured.
    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=348662&SiteID=1
    a. use "sc query mssqlserver" for default instance or "sc query mssql$<instancename>" to make sure SQL Server was started. Sometimes, reseason behind the broken of your client application w/ this error:40 might be SQL server restarted and failed, so, it'd better for you to double check.
    b. User specified wrong server in their connection string, as described in the forum discussion, "MSSQLSERVER" is an invalid instance name. Remember, when you connect to default instance, <machinename> could be best representitive for the instance, when you connect to a named instance such as sqlexpress, you should specify <machinename>\<instancename> as data source in your connection string.
     V. Other reasons such as incorrect security context.
    Check out: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=192622&SiteID=1
    Such error also occured during user operation such as moving database or db mirroring or cluster, any DB OP that might invovle different sql instances, namely, the destination database is located in another sql instance and user is not aware of the state of the destination. I recommend you first isolate whether this fail is during connection stage or data operation stage.
    a. During data operation, you are normally asked to type in the destination server name whether it is default to "(local)" or another server "<remotemachinename>". So, remember the exact string that represent the target instance, then when the error repros, open command line, use "sqlcmd -S<representitive> -E" ,see what happens, if the connection fail, please follow up above I - IV troubleshooting lists. otherwise continue.
    b. If you can make basic conection, but still face the error, then there must be something that server reject the connection or client close the connection for some reason.
    VI. Please try basic connectivity tests between the two mahcines you are working on. One simple way to verifty connectivity is to use command line tools, such as osql.exe. For example, osql -E -Stcpervername\instancename. If it connects cross-machine successfully, please also verify that your connection string in your scenario is correct.
    Here are some blogs which could be helpful: just follow the basic connectivity troubleshooting guidelines on the SQL Protocols blog, see:
    SQL Server 2005 Connectivity Issue Troubleshoot - Part I
    http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx
    and
    SQL Server 2005 Connectivity Issue Troubleshoot - Part II
    http://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx
    Hope this helps.

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

  • Entity bean connection with SQL Server Error! urgent

    Hi,
    I am working with J2EE tutorial and when i tried SavingsAccount Entity bean to connect with SQL Server 2000(other than default Cloudscape)and I'm also having SQL Server 2K JDBC Driver installed. I also made entries in Server Configuration menu of J2EE deployment tool for this MS JDBC Driver for SQL Server 2K,I will enclose my dbName and connection method in the entity bean , but i am getting error like this.
    my data base name in SQL Server 2K is 'rajeshrNew'.
    private String dbName="java:comp/env/jdbc/rajeshrNew"; //dbName
    private void makeConnection() throws NamingException, SQLException {
    InitialContext ic = new InitialContext();
    DataSource ds = (DataSource) ic.lookup(dbName);
    con = ds.getConnection();
    and errors receiving are:
    java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
    java.rmi.RemoteException: nested exception is: javax.ejb.EJBException: Unable to connect to database. No suitable driver; nested exception is:
    javax.ejb.EJBException: Unable to connect to database. No suitable driver
    java.rmi.RemoteException: nested exception is: javax.ejb.EJBException: Unable to connect to database. No suitable driver; nested exception is:
    javax.ejb.EJBException: Unable to connect to database. No suitable driver
    javax.ejb.EJBException: Unable to connect to database. No suitable driver <<no stack trace available>>
    Please help me to resolve this problem!!
    Regards
    Rajesh R

    yes i do create System DSN with rajeshrNew and my default.properties file look like this..
    # maximum size of message driven bean instance
    # pool per mdb type
    messagebean.pool.size=3
    # maximum size of a "bulk" message bean delivery
    messagebean.max.serversessionmsgs=1
    # message-bean container resource cleanup interval
    messagebean.cleanup.interval=600
    passivation.threshold.memory=128000000
    idle.resource.threshold=600
    log.directory=logs
    log.output.file=output.log
    log.error.file=error.log
    log.event.file=event.log
    distributed.transaction.recovery=false
    transaction.timeout=0
    transaction.nonXA.optimization=true
    sessionbean.timeout=0
    # validating parser values
    # validating.perser is used when archive file are loaded by
    # any of the J2EE Reference Implementation tools.
    # deployment.validating.parser is used when deploying an
    # archive on the J2EE AppServer.
    validating.parser=false
    deployment.validating.parser=true
    now u tell me what i have to change..
    with regards
    Rajesh

  • Azure Webjobs with EF DB - A network-related or instance-specific error occurred while establishing a connection to SQL Server

    Hi,
    I have been trying to get a very simple WebJob developed and deployed onto Azure with little to no luck.  I have a MVC Website which has a common project which handles my Data Access Layer with Entity Framework.  I have created a WebJob project
    using Visual Studio and added the following lines of code to the Manual Trigger Function
    [NoAutomaticTrigger]
    public static void ManualTrigger(TextWriter log, int value, [Queue("queue")] out string message)
    RitualDBEntities db = new RitualDBEntities();
    log.WriteLine("Function is invoked with value={0}", value);
    List<Location> locations = db.Locations.ToList();
    string msg = string.Empty;
    foreach (Location location in locations)
    msg += location.Name;
    message = msg;
    log.WriteLine("Following message will be written on the Queue={0}", message);
    In my app.config of my WebJob i have the following connection strings:
    <add name="RitualDBEntities" connectionString="metadata=res://*/RitualDBEntities.csdl|res://*/RitualDBEntities.ssdl|res://*/RitualDBEntities.msl;provider=System.Data.SqlClient;provider connection string=&quot;data source=ritual-pc\sqlexpress;initial catalog=RitualDB;integrated security=True;persist security info=False;MultipleActiveResultSets=True;App=EntityFramework&quot;" providerName="System.Data.EntityClient" />
    <add name="RitualContext" connectionString="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=RitualDB;Data Source=ritual-pc\sqlexpress" providerName="System.Data.SqlClient" />
    <add name="AzureWebJobsDashboard" connectionString="DefaultEndpointsProtocol=https;AccountName=ritual***;AccountKey=tQAP0gyMYKtWPJeIbsqk2iT2k69gyd1FwcyRf3+5Mc9b9EdYzpj0Dq8X2VHUmF*****"/>
    <add name="AzureWebJobsStorage" connectionString="DefaultEndpointsProtocol=https;AccountName=ritual***;AccountKey=tQAP0gyMYKtWPJeIbsqk2iT2k69gyd1FwcyRf3+5Mc9b9EdYzpj0Dq8X2VHUmF*****" />
    When i test locally (F5 Debugging) the webjob runs successfully and does the loop of the objects returned from the database.  When i deploy this Azure the WebJob fails with the following error:
    [03/29/2015 22:07:39 > 6ca05b: SYS INFO] Status changed to Initializing
    [03/29/2015 22:07:41 > 6ca05b: SYS INFO] Run script 'Ritual.WebJobs.Members.exe' with script host - 'WindowsScriptHost'
    [03/29/2015 22:07:41 > 6ca05b: SYS INFO] Status changed to Running
    [03/29/2015 22:07:44 > 6ca05b: INFO] Found the following functions:
    [03/29/2015 22:07:44 > 6ca05b: INFO] Ritual.WebJobs.Members.Functions.ManualTrigger
    [03/29/2015 22:07:44 > 6ca05b: INFO] Executing: 'Functions.ManualTrigger' because This was function was programmatically called via the host APIs.
    [03/29/2015 22:08:01 > 6ca05b: INFO] Function had errors. See Azure WebJobs SDK dashboard for details. Instance id is e99d7205-3ca0-4674-9414-f0381d5c2316
    [03/29/2015 22:08:01 > 6ca05b: ERR ]
    [03/29/2015 22:08:01 > 6ca05b: ERR ] Unhandled Exception: System.Data.Entity.Core.EntityException: The underlying provider failed on Open. ---> System.Data.SqlClient.SqlException: 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)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlConnection.Open()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Infrastructure.Interception.DbConnectionDispatcher.<Open>b__36(DbConnection t, DbConnectionInterceptionContext c)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext](TTarget target, Action`2 operation, TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Infrastructure.Interception.DbConnectionDispatcher.Open(DbConnection connection, DbInterceptionContext interceptionContext)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.EntityClient.EntityConnection.<Open>b__2()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.<>c__DisplayClass1.<Execute>b__0()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute(Action operation)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.EntityClient.EntityConnection.Open()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] --- End of inner exception stack trace ---
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.EntityClient.EntityConnection.Open()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.Objects.ObjectContext.EnsureConnection(Boolean shouldMonitorTransactions)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__5()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.Objects.ObjectQuery`1.<System.Collections.Generic.IEnumerable<T>.GetEnumerator>b__0()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at Ritual.WebJobs.Members.Functions.ManualTrigger(TextWriter log, Int32 value, String& message)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at lambda_method(Closure , Object[] )
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.Host.Executors.VoidInvoker.InvokeAsync(Object[] arguments)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.<ExecuteWithWatchersAsync>d__23.MoveNext()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] --- End of stack trace from previous location where exception was thrown ---
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.<ExecuteWithOutputLogsAsync>d__1c.MoveNext()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] --- End of stack trace from previous location where exception was thrown ---
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.<ExecuteWithLogMessageAsync>d__c.MoveNext()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] --- End of stack trace from previous location where exception was thrown ---
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.<ExecuteWithLogMessageAsync>d__c.MoveNext()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] --- End of stack trace from previous location where exception was thrown ---
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.<TryExecuteAsync>d__1.MoveNext()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] --- End of stack trace from previous location where exception was thrown ---
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.Host.Executors.ExceptionDispatchInfoDelayedException.Throw()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.JobHost.<CallAsyncCore>d__7.MoveNext()
    [03/29/2015 22:08:01 > 6ca05b: ERR ] --- End of stack trace from previous location where exception was thrown ---
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.JobHost.Call(MethodInfo method, Object arguments)
    [03/29/2015 22:08:01 > 6ca05b: ERR ] at Ritual.WebJobs.Members.Program.Main()
    [03/29/2015 22:08:01 > 6ca05b: SYS INFO] Status changed to Failed
    [03/29/2015 22:08:01 > 6ca05b: SYS ERR ] Job failed due to exit code -532462766
    If i remove any of my database code and use just the basic Stub code my webjob will run successfully so i know that my connection strings (outside of the DB ones) are correct.  My MVC web application also runs perfectly using the same connection strings
    in Azure so i also know that they have also been configured.  
    I am now lost and need some guidance, so if someone is able to assist me that would be much appreciated.
    Thanks
    Ritual.

    Can you try to log the connection string you are using in both cases to make sure they are the same?
    Also can you share your site name, either directly or indirectly?
    This will help us investigate.
    Thanks,
    Amit

  • A network-related or instance-specific error occurred while establishing a connection to SQL Server.

    Dear all,
    I know that this topic may be a bit old school; but it really make me mad as I tried all solutions i found and it still cant be resolved....please give a hand...
    The situation is like this,my company divided different platform as a status of project, like DEV, SIT and UAT. I got a project that require me to upgrade an vs2003 project to vs2005. I upgraded it completely and
     successfully, it works fine in development and UAT platform; EXCEPT, the SIT platform.
    The situation is very strange that, once I move the source to SIT, it return the following error:
    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)
    but it never happen in either DEV or UAT platform and even do I copy the workable web.config from DEV or UAT platform to SIT, the error still here and unable to resolve it.
    I search a lot in the internet by Google, but solution suggested are not suitable or fail in my case. Most answer suggest that "enable remote control", "check fire wall", "check server" etc......But as I can connect well the
    DBServer in DEV and UAT properly, I dont think those are the cause(but still, I check them all, and all are enabled properly, except my firewall setting is OFF, so adding port is ignored).
    After all the searching and testing, I believed and have reason to believe that, the cause is inside my web.config:
      <appSettings>
        <!--   User application and configured property settings go here.-->
        <!--   Example: <add key="settingName" value="settingValue"/> -->
    <clear/>
        <add key="Environment" value="UAT v1.31"/>
        <add key="DBServer" value="DB_UAT"/>
        <add key="cnBPSS.ConnectionString" value="data source=DB_UAT\BPSS;persist security info=True;user id=theloginid;workstation id=RP_UAT;packet size=4096;pwd=theloginpwd"/>
        <add key="UTBPSSConn.ConnectionString" value="data source=DB_UAT\BPSS;persist security info=False;user id=theloginid;workstation id=RP_UAT;packet size=4096;pwd=theloginpwd"/>
        <add key="UTDSBDBConn.ConnectionString" value="workstation id=RP_UAT;packet size=4096;user id=theloginid;data source=DB_UAT\DSBDB;persist security info=False;password=theloginpwd"/>
        <add key="cnDSBDB.ConnectionString" value="workstation id=RP_UAT;packet size=4096;user id=theloginid;data source=DB_UAT\DSBDB;persist security info=False;password=theloginpwd"/>
        <add key="Timer1.Enabled" value="True"/>
        <add key="Timer1.AutoReset" value="True"/>
        <add key="cnbpss.ConnectionString" value="data source=DB_UAT\BPSS;password=theloginpwd;persist security info=True;user id=theloginid;workstation id=RP_UAT;packet size=4096"/>
        <add key="cnbpss1.ConnectionString" value="data source=DB_UAT\BPSS;password=theloginpwd;persist security info=True;user id=theloginid;workstation id=RP_UAT;packet size=4096"/> 
    </appSettings>
    </configuration>
    I know such kind of setting is old school; But due to this program runs for few years from tons of ppl...I dont dare to modify it unless I am very sure they are the cause.....
    May I ask if anyone cna give me some advice and help in this issue please? I already tried for weeks and turning mad....Please I really need some help...
    Many thanks.
    Ksun Chan

    Checklist of possible reason of this error
    1. Check SQL services are running
    2. Check SQL Browser service is running
    3. Check remote connections are enabled
    4. Network connectivity between database & application servers by TRACERT command
    5. Check TCP/IP protocol enabled at SQL server
    6. Check talent connectivity – telnet <IP address> <port no on SQL server running>
    7. Check UDP port 1434 is open or not on SQL Server
    8. Check firewall is running or not Check
    9. If firewall running, SQL Server & UDP port must be added in exception in firewall
    Regards,
    Rohit Garg
    (My Blog)
    This posting is provided with no warranties and confers no rights.
    Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.

  • A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.

    Server Error in '/' Application.
    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)
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
    Exception Details: System.Data.SqlClient.SqlException: 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)
    Source Error:
    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
    Stack Trace:
    [SqlException (0x80131904): 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)]
    System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +4846887
    System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +194
    System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +4860189
    System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +90
    System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +342
    System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +221
    System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +189
    System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +185
    System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +31
    System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +433
    System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66
    System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +499
    System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +65
    System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +117
    System.Data.SqlClient.SqlConnection.Open() +122
    System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState) +31
    System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +112
    System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +287
    System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +92
    System.Web.UI.WebControls.SqlDataSourceView.ExecuteSelect(DataSourceSelectArguments arguments) +1297
    System.Web.UI.DataSourceView.Select(DataSourceSelectArguments arguments, DataSourceViewSelectCallback callback) +19
    System.Web.UI.WebControls.DataBoundControl.PerformSelect() +142
    System.Web.UI.WebControls.BaseDataBoundControl.DataBind() +73
    System.Web.UI.WebControls.GridView.DataBind() +4
    System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound() +82
    System.Web.UI.WebControls.CompositeDataBoundControl.CreateChildControls() +72
    System.Web.UI.Control.EnsureChildControls() +87
    System.Web.UI.Control.PreRenderRecursiveInternal() +44
    System.Web.UI.Control.PreRenderRecursiveInternal() +171
    System.Web.UI.Control.PreRenderRecursiveInternal() +171
    System.Web.UI.Control.PreRenderRecursiveInternal() +171
    System.Web.UI.Control.PreRenderRecursiveInternal() +171
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +842
    Version Information: Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082

    On what website/link did you received this error message ??

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

  • Response Group: A network-related or instance-specific error occurred while establishing a connection to SQL Server.

    Hi all,
    I have three central sites with each having a Front End server pool (standard).
    Site A and Site B are paired for resiliency. Site C is on its own.
    On two of my Front Ends (Site A and Site B), when I click on response group tab i get the following warning on the top of the page:
    "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)"
    I have check out the following articles about dont think they apply to me:
    http://unifiedme.co.uk/2014/01/network-related-instance-specific-error-occurred-accessing-lync-control-panel-response-group-tab/
    I dont see any Event logs that would direct me to a cause. 
    Which database it is complaining about? RGSDYN and RGSCONFIG are local databases as it is an standard installation. What could be the possible cause for this issue?
    Thanks in advance.

    My latest change was the addition of Site C. 
    Going through logs (i must have missed it the first time, with all the noisy EWS errors), i found event ID 31147. I am investigating network issues although I have MPLS running to that location.
    Does Lync set up open correct ports on the machine itself?

  • SQL Server Agent Log showing errors [298] SQLServer Error: 10061, 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

    Hi All,
    I have started receiving this error in the logs for the last 10 days and the Schedules Jobs for the database have stopped running. My MS CRM application is working fine.
    Can anyone guide me what could be the problem.
    Date                      17/4/2014 2:04:20 PM
    Log                         SQL Server Agent (Current - 17/4/2014 2:01:00 PM)
    Message
    [298] SQLServer Error: 10061,
    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. [SQLSTATE 08001]
    Date                      17/4/2014 2:11:55 PM
    Log                         SQL Server Agent (Current - 17/4/2014 2:01:00 PM)
    Message
    [298] SQLServer Error: 10061,
    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. [SQLSTATE 08001]
    Date                      7/4/2014 11:00:31 AM
    Log                         SQL Server Agent (Current - 17/4/2014 2:01:00 PM)
    Message
    [298] SQLServer Error: 10061,
    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. [SQLSTATE 08001]

    Check this link
    http://social.msdn.microsoft.com/Forums/en-US/906da9b5-2482-468c-a424-ae099da2d96b/sql-server-agent-service-account-error?forum=sqlsetupandupgrade
    Regards, RSingh

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

  • Network related or instance specific error occurred while establishing a connection to sql server

    Hi all,
    I am getting  a SQL error - 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).
    Problem is when a user tries to connect with remote SQL Server
    through VPN from Domain, it throws this error, and when the same machine tries to connect with Remote SQL Server through VPN as a standlone machine, it is getting connected.
    I checked all the settings but ....... There is no any policies deployed in Active Directory.
    Any suggetion?
    Rajneesh
    Rajneesh Kumar MCITP - SA, MCSE, CNA

    check these
    1) Make sure your server name is correct, e.g., no typo on the name.
    2) Make sure your instance name is correct and there is actually such an instance on your target machine.
    [Update: Some application converts \\ to \. If you are not sure about your application, please try both Server\Instance and Server\\Instance in your connection string]
    3) Make sure the server machine is reachable, e.g, DNS can be resolve correctly, you are able to ping the server (not always true).
    4) Make sure SQL Browser service is running on the server.
    5) If firewall is enabled on the server, you need to put sqlbrowser.exe and/or UDP port 1434 into exception.
    http://uk.linkedin.com/in/ramjaddu

Maybe you are looking for

  • Create Credit Memo using B1if

    Hello Experts, Have anyone tried to create service Credit Memo using B1if when an AP Invoice is posted by a user for a specific vendor? or Any similar scenario? I am new to B1if , looking into the recordings now. Can anyone advise steps or process to

  • Using Datasource location

    Hello, I am trying to change the tables used in a specific report.  Table "Customers" is currently being used in the report.  I have made a copy of this table in my MS SQL DB and called it "Customers_2011".  Using 'Set Datasource Location" I am tryin

  • OBIEE & 2 x Essbase hypercubes

    Hi all, I'm still wrestling with my federation of Essbase cubes and need some advice. I have 2 cubes with the same data facts, but one cube has less dimensions that the other: Summary cube: date dimension 1 fact - number of sales Detailed cube: date

  • I need to run internet explorer for a program I use.But can't access it is this due to running Firefox

    I noticed that when I went to use Internet Explorer a few weeks ago it would say it stopped running. I thought that it was just a fluke. But when I try to download things in my MTC program they will start to download then just stop.MTC needs Internet

  • Took pictures on new ipod.  Did restore - lost all current pictures.  Any way to get the others back? :(

    Took pictures on new ipod.  Did restore - lost all current pictures.  Any way to get the others back? Had Christmas pictures of family and friends.  I'll be so sad if I can't them back.