Yesterday I was able to connect Azure SQL Database - Today I am not

Hello Everyone,
I have problem with establishing connection with Azure SQL Database. I have read many articles here, tried some solutions but none worked.
0. On last Friday everything worked well - today it does not.
1. I added my public IP Address in Azure Management Portal earlier.
2. I tried different types of login-ways: login@nameserver, I used numeric addresses instead of server names, I set TCP connection manually, added encryption in one case either, tried do establish connection with particular database
3. Firewall does not block 1433 out connection
4. My IP address is static
5. I have no error message displayed using Microsoft SQL Server Management Studio - it just hangs.. - no response at all
6. I cannot ping the machine but its name is resolved correctly - maybe it does not respond using echo reply on purpose
7. Status of my database is Active - I am able to connect it and manage via browser and management portal at the moment
8. When I am trying to connect database via Visual Studio - it hangs.. - VS must be stopped manually via task manager
9. My local CloudService has problem with connection to the db either
10. Currently I am not able to deploy my CloudService because when I am trying to Publish it - VS hangs as soon as first Publish dialog window appears. Looks that I am able to deploy cloud service via Management portal only.
I am still trying to dive into the problem but at this moment I would be grateful for any clues.
Regards,

Hi Mekh, hi everyone
PROBLEM SOLVED.
Yestarday I updated Azure Firewall rule and database-level firewall rules (master, my_database). I added special input / output protocols (IP, TCP, UDP) rules to my COMODO firewall (MSSMS could send anything and receive anything using IP, TCP and UDP). Status
of my computer -> database connection was set to ESTABLISHED in netstat output but MSSMS was still unavailable (no response at all - no error message).
I DECIDED TO UNINSTALL COMODO AT ALL and then if it does not work - reinstall local SQL Server, MSSMS and finally Visual Studio. When Comodo was gone - problem was gone either. Now I have connection with my database using MSSMS and I do not have to reinstall
anything more.
Regards,

Similar Messages

  • Can I connect Azure SQL Database from Project Siena ?

    Can I connect Azure SQL Database from Project Siena ?
    I want to connect Azure SQL Database of Office 365 SharePoint's Access App from Project Siena.
    Access App's Database is Azure SQL Database.
    and can connect to Excel/PowerBI/etc.
    Access App's Database can connect from specific location / any locations.
    Access App's Database can allow read-only connection / read-write connection.
    I want to create Windows App connected to Access App's Database.
    Regards,
    Yoshihiro Kawabata.

    Hi Yoshihiro,
    Could you share more with us about the high level scenario for what you are trying to accomplish offline? We can discuss further at
    [email protected]
    Once we are done, we will definitely share our findings with the community.
    Thanks!

  • Azure SQL database working locally but not when published to Azure

    I have an
    AngularJS  solution that is connecting to a SQL Azure database.  When
    I run the solution locally, it’s configured to connect up to the SQL Azure database, the solution works fine. However,
    when I publish the solution to Azure the connection to the SQL Azure database does not work.
    When debugging with Chrome I get the error Failed to load resource: the server responded with a status of 500 (Internal Server
    Error) 
    I'm not using EF. but dapper.
    My connectionstring is as follows
    <add name="PortalConnection" providerName="System.Data.SqlClient" connectionString="Server=tcp:xxx.database.windows.net,1433;Database=xxx;User ID="xxx";Password="xxx";Trusted_Connection=False;Encrypt=True;Connection
    Timeout=30;"/>
    When I run the web solution locally from Visual Studio, my sql queries runs like it should, it's only the published version having problems. 
    Any ideas?
    Software Developer

    Hi,
    Thanks for answer.
    I had followed that step by step guide for deploying to Windows Azure. So that was not the problem.
    But I was able to get a better error message by turning off custom error in web.config.
    I got the error message: "Windows login are not supported in this version of SQL Server"
    I solved this by using the SqlConnectionStringBuilder instead of getting the connection string from 
    web.config.
    So everything works great now, just think it's strange it worked locally before..
    Regards
    -entery
    Software Developer

  • Failed to Establish Connection With SQL Database Server in Essbase studio

    I am using Essbase Studio Release 11.1.2.1.00 for developing XOLAP cubes and deploying them on to Essbase server .
    I am getting the below Error while deploying the cube onto Essbase server.
    error : Failed to deploy Essbase cube.
    Caused by: Failed to build Essbase cube dimension: (TimeHierarchy) .
    Caused by: Cannot get async process state. Essbase Error(1021001): Failed to Establish Connection With SQL Database Server.
    From Essbase Studio -> Datasources tab, I could able to connect to SQL Database server..Please let me know how to resolve this issue.
    Thanks,
    Swathi

    Thanks for the reply.
    There was a problem with my Essbase Server..so now i m pointing to other server.
    now I am getting the below Error:
    Failed to deploy Essbase cube.
    Caused by: Cannot end incremental build. Essbase Error(1025008): Join Specification near [[TIMEID]] is invalid. Please verify the Xolap Schema file.
    Please let me know how can I validate my cube and what changes might require in my Cube definitions?

  • Essbase Studio - Failed to Establish Connection With SQL Database Server

    Hi all,
    I am new to Hyperion and am having trouble deploying what seems a simple cube in Essbase Studio.
    My environment is Windows 2003, EPM 11.1.1.2, SQL Server 2000.
    I have the following two issues which may be related.
    1. The EPM System Diagnostic tool says that Hyperion Foundation cannot connect to the SQL database.
    Error:
    Failed: Connection to database
    Error: java.net.UnknownHostException: <server name: <server name>
    Recommended Action:
    Every other EPM application is able to connect to the database. I have tried re-configuring Foundation Services and checking the config files and nothing looks wrong. I would appreciate advice on how to fix this.
    2 In Essbase Studio, I was able to connect to the database where the source data is, build the minischema and create dimensions and measures. But when I run the cube deployment wizard I get the error:
    Message: Failed to deploy Essbase cube
    Caused By: Failed to build Essbase cube dimension: (Time)
    Caused By: Cannot incremental build. Essbase Error(1021001): Failed to Establish Connection With SQL Database Server. See log for more information
    …ODBC Layer Error: [08001] ==> [[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.]
    I have checked the DSN as well as the connections set up within Studio, and they are all able to connect to the database. I am using the admin user for the Essbase server and have created a different user for the databases where the data resides and the shared services database. I tried using the same user all the way through and this didn’t help.
    Can you please advise what else I can check or change to resolve this issue.
    Also, can you work in EAS with cubes that are created in Studio? I tried looking at it and I got an error that the rule file couldn’t be accessed because it was created in Studio.
    After the above failures, I tried creating a cube in EIS, with mixed success. I have been able to load the members and data without errors. But when I try to view the data in the cube, I am seeing field names for the measures instead of the data itself.
    ...Definitely more questions than answers at this stage of my learning.
    Regards
    Michelle

    Michelle,
    I don't know if you found an answer to you question after so many months but I was hoping I could be helpful.
    The issue you are experience happens often when the dimension that you are getting an error on, in this case TIME, is built from a snowflake lineage and there is a bad foreign key reference. This dimension is most like high-up in your outline build process for Essbase Studio and this prevents the build from happening usually early on.
    Check your logs also. They are in Hyperion > Products > logs > essbase > essbasestudio.
    You can also make your logs more verbose by setting a configuration variable in the essbase studio server.properties file but that should only be used for debugging as it really saps performance.
    And, yes, you can of course edit an Essbase Studio deployed cube in EAS. However, any changes you make to the cube in EAS are subject to being wiped-out upon the next Essbase Studio deployment of that Applicaion/Database combo.
    If you want to provide more detail, screenshots, etc. I would be glad to help where I can.
    Cheers,
    Christian
    http://www.artofbi.com

  • Cannot Connect to Azure SQL Database in Visual Studio 2013

    Beyond Frustrated here.
    I am trying to connect to an Azure SQL database - it has been created, has tables etc. I am trying to create a new Data Connection from within Visual Studio 2013, latest release for VS and Azure. I continue to receive 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
    I have ensured that TCP is allowed and above Named Pipes in the Configuration Manager. The associated IP address is allowed on Azure Firewall. Certificate has been added to VS etc. But still no connection. I can see the database in the Azure section in Server
    Explorer, but cannot add a Data Connection. What is equally as frustrating is I have a MacBook Pro running Win 7 sitting right next to my office computer and it can access Azure fine, not problems.
    If anyone has any other ideas on how I might be able to solve this I would love to hear them. Thanks in advance.
    Jeff

    Hi,
     The Error message "   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: 53) "
    The issue comes up mainly because the application is not able to connect to the server.
    To resolve this issue, try the following steps (in that order):
     Make sure that TCP IP is enabled as a client protocol on the application server. For more information on how to do this, see
    Configure client protocols. On application servers where you do not have SQL Server tools installed, you can check this by running cliconfg.exe (SQL Server Client Network Utility).              
     2.  Check the application’s connection string to make sure that it is correctly configured. For example, make sure that the connection string specifies the correct port (1433) and the fully qualified server name.                
    Note You can follow these steps to obtain the connection string from the Azure Management Portal:                  
                          Log on to the
    Azure Management Portal.                    
                          In the left navigation pane, click
    SQL Databases.                    
                          Select your Azure SQL Database server.                    
                          Click
    Dashboard.                    
                          On the right side, go to the
    quick glance section, and then click Show connection strings.                    
    Test the connectivity between the application server and the Azure SQL database by using a UDL file, ping, and telnet. For more information about how to do this, see
    Azure SQL Database connectivity troubleshooting guide and
    Troubleshooting SQL Server connectivity issues.                
    Note As a troubleshooting step, you can also try to test the connectivity on a different client computer.                
    Try increasing the connection timeout. Microsoft recommends using a connection timeout of at least 30 seconds.              
    As a best practice ensure retry logic is in place. For more information about the retry logic, see
    Azure SQL Database best practices to prevent request denials or connection termination.              
          If these  steps do not resolve your problem, follow the below steps to collect more data and contact support:              
       If your application is a cloud service, enable the logging. This step returns a UTC time stamp of the failure. Additionally, SQL Azure returns the tracing ID.
    Microsoft Customer Support Services can use this information.                   
       For more information about how to enable the logging, see
    how to enable diagnostic logging for Azure Web sites and Developing SQL Database Applications section in
    Azure SQL Database Development Considerations.                
      Check out
    the list of best practices for Connecting to Windows Azure SQL Database.
    Regards,
    Shirisha Paderu.

  • Dispatcher stopped and not able to connect with sql server

    Hi ,
                       In one of test system disp+work is started and then within no time its stopped.
    I am able to connect with  sql server 2005 database but while starting sap  dispatcher is stopping.
    Here is the log of  dev_wo
    trc file: "dev_w0", trc level: 1, release: "700"
    ACTIVE TRACE LEVEL           1
    ACTIVE TRACE COMPONENTS      all, MJ

    B Thu Jan 05 07:24:02 2012
    B  create_con (con_name=R/3)
    B  Loading DB library 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll' ...
    B  Library 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll' loaded
    B  Version of 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll' is "700.08", patchlevel (0.72)
    B  New connection 0 created
    M sysno      11
    M sid        DE1
    M systemid   560 (PC with Windows NT)
    M relno      7000
    M patchlevel 0
    M patchno    75
    M intno      20050900
    M make:      multithreaded, Unicode, optimized
    M pid        988
    M
    M  kernel runs with dp version 217000(ext=109000) (@(#) DPLIB-INT-VERSION-217000-UC)
    M  length of sys_adm_ext is 572 bytes
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 988) [dpxxdisp.c   1299]
    I  MtxInit: 30000 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
    M  DpShMCreate: sizeof(wp_adm)          23936     (1408)
    M  DpShMCreate: sizeof(tm_adm)          3994272     (19872)
    M  DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
    M  DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
    M  DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
    M  DpShMCreate: sizeof(comm_adm)          528064     (1048)
    M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    M  DpShMCreate: sizeof(file_adm)          0     (72)
    M  DpShMCreate: sizeof(vmc_adm)          0     (1440)
    M  DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
    M  DpShMCreate: sizeof(gw_adm)     48
    M  DpShMCreate: SHM_DP_ADM_KEY          (addr: 07F90040, size: 4659000)
    M  DpShMCreate: allocated sys_adm at 07F90040
    M  DpShMCreate: allocated wp_adm at 07F91E40
    M  DpShMCreate: allocated tm_adm_list at 07F97BC0
    M  DpShMCreate: allocated tm_adm at 07F97BF0
    M  DpShMCreate: allocated wp_ca_adm at 08366E90
    M  DpShMCreate: allocated appc_ca_adm at 0836CC50
    M  DpShMCreate: allocated comm_adm at 0836EB90
    M  DpShMCreate: system runs without file table
    M  DpShMCreate: allocated vmc_adm_list at 083EFA50
    M  DpShMCreate: allocated gw_adm at 083EFA90
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated ca_info at 083EFAC0
    M  DpShMCreate: allocated wall_adm at 083EFAC8
    X  EmInit: MmSetImplementation( 2 ).
    X  MM global diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  Using implementation flat
    M  <EsNT> Memory Reset disabled as NT default
    X  ES initialized.

    M Thu Jan 05 07:24:03 2012
    M  ThInit: running on host sugarland

    M Thu Jan 05 07:24:04 2012
    M  calling db_connect ...
    C  Warning: Env(MSSQL_SERVER) [SUGARLAND\DE1] <> Prof(dbs/mss/server) [SUGARLAND]. Profile value will be used.
    C  Thread ID:708
    C  Thank You for using the SLOLEDB-interface
    C  Using dynamic link library 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll'
    C  dbmssslib.dll patch info
    C    patchlevel   0
    C    patchno      72
    C    patchcomment MSSQL: Thread check in DbSlDisconnect (969143)
    C  np:(local) connection used on SUGARLAND
    C  CopyLocalParameters: dbuser is 'de1'
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.

    C Thu Jan 05 07:24:19 2012
    C  OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), 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.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.

    C Thu Jan 05 07:24:34 2012
    C  OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), 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.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.

    C Thu Jan 05 07:24:49 2012
    C  OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), 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.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  failed to establish conn to np:(local).
    C  Retrying without protocol specifier: (local)
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.

    C Thu Jan 05 07:25:05 2012
    C  OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), 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.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.

    C Thu Jan 05 07:25:21 2012
    C  OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), 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.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.

    C Thu Jan 05 07:25:37 2012
    C  OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), 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.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  failed to establish conn. 0
    B  ***LOG BY2=> sql error 0      performing CON [dbsh#2 @ 1204] [dbsh    1204 ]
    B  ***LOG BY0=> <message text not available> [dbsh#2 @ 1204] [dbsh    1204 ]
    B  ***LOG BY2=> sql error 0      performing CON [dblink#3 @ 431] [dblink  0431 ]
    B  ***LOG BY0=> <message text not available> [dblink#3 @ 431] [dblink  0431 ]
    M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1411]
    M  in_ThErrHandle: 1
    M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10156]

    M  Info for wp 0

    M    stat = 4
    M    reqtype = 1
    M    act_reqtype = -1
    M    rq_info = 0
    M    tid = -1
    M    mode = 255
    M    len = -1
    M    rq_id = 65535
    M    rq_source = 255
    M    last_tid = 0
    M    last_mode = 0
    M    semaphore = 0
    M    act_cs_count = 0
    M    control_flag = 0
    M    int_checked_resource(RFC) = 0
    M    ext_checked_resource(RFC) = 0
    M    int_checked_resource(HTTP) = 0
    M    ext_checked_resource(HTTP) = 0
    M    report = >                                        <
    M    action = 0
    M    tab_name = >                              <
    M    vm = V-1

    M  *****************************************************************************
    M  *
    M  *  LOCATION    SAP-Server sugarland_DE1_11 on host sugarland (wp 0)
    M  *  ERROR       ThInit: db_connect
    M  *
    M  *  TIME        Thu Jan 05 07:25:37 2012
    M  *  RELEASE     700
    M  *  COMPONENT   Taskhandler
    M  *  VERSION     1
    M  *  RC          13
    M  *  MODULE      thxxhead.c
    M  *  LINE        10354
    M  *  COUNTER     1
    M  *
    M  *****************************************************************************

    M  PfStatDisconnect: disconnect statistics
    M  Entering TH_CALLHOOKS
    M  ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
    M  *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   720]
    M  *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c  260]
    M  Entering ThSetStatError
    M  ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
    M  Entering ThReadDetachMode
    M  call ThrShutDown (1)...
    M  ***LOG Q02=> wp_halt, WPStop (Workproc 0 988) [dpnttool.c   327]
    Please help me on this
    Thanks
    Srikanth

    Hi Amit, 
                 I restarted the system but dispatcher still in same stage.
    Here is the log for dev_w0
    ========================================
    Fri Jan 06 03:41:06 2012
    C  OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), 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.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  failed to establish conn. 0
    B  ***LOG BY2=> sql error 0      performing CON [dbsh#2 @ 1204] [dbsh    1204 ]
    B  ***LOG BY0=> <message text not available> [dbsh#2 @ 1204] [dbsh    1204 ]
    B  ***LOG BY2=> sql error 0      performing CON [dblink#3 @ 431] [dblink  0431 ]
    B  ***LOG BY0=> <message text not available> [dblink#3 @ 431] [dblink  0431 ]
    M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1411]
    M  in_ThErrHandle: 1
    M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10156]

    M  Info for wp 0

    M    stat = 4
    M    reqtype = 1
    M    act_reqtype = -1
    M    rq_info = 0
    M    tid = -1
    M    mode = 255
    M    len = -1
    M    rq_id = 65535
    M    rq_source = 255
    M    last_tid = 0
    M    last_mode = 0
    M    semaphore = 0
    M    act_cs_count = 0
    M    control_flag = 0
    M    int_checked_resource(RFC) = 0
    M    ext_checked_resource(RFC) = 0
    M    int_checked_resource(HTTP) = 0
    M    ext_checked_resource(HTTP) = 0
    M    report = >                                        <
    M    action = 0
    M    tab_name = >                              <
    M    vm = V-1

    M  *****************************************************************************
    M  *
    M  *  LOCATION    SAP-Server sugarland_DE1_11 on host sugarland (wp 0)
    M  *  ERROR       ThInit: db_connect
    M  *
    M  *  TIME        Fri Jan 06 03:41:06 2012
    M  *  RELEASE     700
    M  *  COMPONENT   Taskhandler
    M  *  VERSION     1
    M  *  RC          13
    M  *  MODULE      thxxhead.c
    M  *  LINE        10354
    M  *  COUNTER     1
    M  *
    M  *****************************************************************************

    M  PfStatDisconnect: disconnect statistics
    M  Entering TH_CALLHOOKS
    M  ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
    M  *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   720]
    M  *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c  260]
    M  Entering ThSetStatError
    M  ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
    M  Entering ThReadDetachMode
    M  call ThrShutDown (1)...
    M  ***LOG Q02=> wp_halt, WPStop (Workproc 0 3632) [dpnttool.c   327]

  • Consistently getting "The wait operation timed out" when connecting to Azure SQL Database from a virtual instance...

    I have a web app that is backed by a an Azure SQL Database. The problem is that I had multiple issues when connecting to the database mainly when trying to establish a connection, or timeouts. This is the log I just encountered when trying to use the web
    app.
    [Win32Exception (0x80004005): The wait operation timed out]
    [SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=21970; handshake=1; ]
    System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) +671
    System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +116
    System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +1012
    System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) +6712291
    System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) +152
    System.Data.SqlClient.SqlConnection.Open() +229
    System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure) +102

    Hi Affar2k,
    According to your description, we need to verify if there is no network issue and the Sqlclient version is older than .NET 4.5.  You can try to connect to the Windows Azure SQL database via SSMS and check if it can run well. When you
    connect to the SQL Azure database via ADO.NET, you need to verify that the server name and passwords are right in the connection string.
    For more information, you can review the following article about how to connect to Windows Azure SQL Database using ADO.NET.
    http://msdn.microsoft.com/en-us/library/windowsazure/ee336243.aspx
    Thanks,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Connecting to Azure SQL database in Access 2010

    I've recently purchased a new computer and I had an OBDC connection set up to link to a sql database in azure through access. I am trying to set it up on my new computer but I'm unable to define the specific database. I'm able to make the connection but
    it only allows me into the master database. I've added my IP address in the configure servers but still can't get things to work. Any help would be greatly appreciated.
    thanks
    Lynn

    Hi,
    The following guidelines apply to SQL Database connections using ODBC:
    • When using SQL Server Native Client from SQL Server 2008 R2 or SQL Server 2008, the connection string must include the server name as part of the user name (user@server).
    • You must use TCP/IP as the protocol when connecting to an Azure SQL Database.
    • You cannot create a table in the master database, so therefore you must create a user database to create a table.
    • You cannot execute a use database command to switch to your user database. You must disconnect and connect directly to the user database.
    • You must have a primary key or clustered index on your table to be able to insert data.
    Ref:
    https://msdn.microsoft.com/en-us/library/azure/hh974312.aspx?f=255&MSPPError=-2147217396
    http://blogs.office.com/2010/06/07/access-2010-and-sql-azure/
    https://support.microsoft.com/en-us/kb/2028911/
    Hope this helps you.
    Girish Prajwal

  • Can No Longer Connect to Azure SQL Databases

    As of this morning, I am no longer to connect to any of my Azure SQL databases by any (apparent) means. I checked the configuration in the azure portal and my IP address is listed as an allowed IP, however:
    I am unable to connect via SQL Server Management Studio
    My request times out when attempting to visit https://{server_name}.database.windows.net
    What might have caused this?

    Hi ,
    Thanks for posting here.
    To resolve the issue you can try the following steps (in that order):
                    Check the application’s connection string to make sure that it is correctly configured. For example, make sure that the connection string specifies the correct port
    (1433) and the fully qualified server name.                
    Note You can follow these steps to obtain the connection string from the Azure Management Portal:                  
                          Log on to the
    Azure Management Portal.                    
                          In the left navigation pane, click
    SQL Databases.                    
                          Select your Azure SQL Database server.                    
                          Click
    Dashboard.                    
                          On the right side, go to the
    quick glance section, and then click Show connection strings.                    
                    Make sure that TCP IP is enabled as a client protocol on the application server. For more information on how to do this, see
    Configure client protocols. On application servers where you do not have SQL Server tools installed, you can check this by running cliconfg.exe (SQL Server Client Network Utility).              
                    Test the connectivity between the application server and the Azure SQL database by using a UDL file, ping, and telnet. For more information about how to do this,
    see
    Azure SQL Database connectivity troubleshooting guide and
    Troubleshooting SQL Server connectivity issues.                
    Note As a troubleshooting step, you can also try to test the connectivity on a different client computer.                
                    Try increasing the connection
    timeout. Microsoft recommends using a connection timeout of at least 30 seconds.              
                    As a best practice ensure retry logic is in place. For more information about the retry logic, see
    Azure SQL Database best practices to prevent request denials or connection termination.              
                  If the previous steps do not resolve your problem, follow these steps to collect more data and contact support:              
                      If your application is a cloud service, enable the logging. This step returns a UTC time stamp of the failure. Additionally, SQL Azure returns the tracing
    ID.
    Microsoft Customer Support Services can use this information.                
                      For more information about how to enable the logging, see
    how to enable diagnostic logging for Azure Web sites and Developing SQL Database Applications section in
    Azure SQL Database Development Considerations.
    Please write back with the exact Error message/ Error Code if this doesn't help.
    Regards,
    Shirisha Paderu.

  • Not able to connect with Sql Server Database

    Hi,
    I'm not able to connect with Sql Server database.during making connection I'm getting the following error:
    "Status : Failure -I/O Error: SSO Failed: Native SSPI library not loaded. Check the java.library.path system property."
    Please help
    Regards,
    Neeraj Goel

    Hi,
    I'm using Sql Server 2000.
    I downloaded the driver from the given site and still having the same problem. Do I need to copy the driver file in some specific folder.
    Regards,
    Neeraj Goel

  • Yesterday I was able to take photos but around 9pm last night my rear camera stop working. I have reseted my phone and have also restored it and the camera still is not working. Also I have deleted all apps that can have access to the camera.

    Yesterday I was able to take photos but around 9pm last night my rear camera stop working. I have reseted my phone and have also restored it and the camera still is not working. Also I have deleted all apps that can have access to the camera and i have updated the new IOS.What else should I do ? Is this a hardware problem?

    Looks like a hardware issue that will have to be taken to a store

  • Hello friends..i m not able to connect MS SQL SERVER 2005 FROM cmd prompt

    dear friends,
    i m not able to connect MS SQL SERVER from command prompt..
    do you know how to connect from command prompt or any other ways to connect to database only for delete SAP* user purpose.
    thanks
    zaheer

    Hi,
    you can use the SQLCMD tool:
    Microsoft (R) SQL Server Command Line Tool
    Version 10.50.1600.1 NT x64
    Copyright (c) Microsoft Corporation.  All rights reserved.
    usage: Sqlcmd            [-U login id]          [-P password]
      [-S server]            [-H hostname]          [-E trusted connection]
      [-N Encrypt Connection][-C Trust Server Certificate]
      [-d use database name] [-l login timeout]     [-t query timeout]
      [-h headers]           [-s colseparator]      [-w screen width]
      [-a packetsize]        [-e echo input]        [-I Enable Quoted Identifiers]
      [-c cmdend]            [-L[c] list servers[clean output]]
      [-q "cmdline query"]   [-Q "cmdline query" and exit]
      [-m errorlevel]        [-V severitylevel]     [-W remove trailing spaces]
      [-u unicode output]    [-r[0|1] msgs to stderr]
      [-i inputfile]         [-o outputfile]        [-z new password]
      [-f <codepage> | i:<codepage>[,o:<codepage>]] [-Z new password and exit]
      [-k[1|2] remove[replace] control characters]
      [-y variable length type display width]
      [-Y fixed length type display width]
      [-p[1] print statistics[colon format]]
      [-R use client regional setting]
      [-b On error batch abort]
      [-v var = "value"...]  [-A dedicated admin connection]
      [-X[1] disable commands, startup script, enviroment variables [and exit]]
      [-x disable variable substitution]
      [-? show syntax summary]
    You have to have the SQL Server tools installed on the box, to get sqlcmd.
    You then can connect with SQL authentication
    sqlcmd -S <Servername\Instancename> -U user -P password                          
    or with windows authentication
    sqlcmd -S <Servername\Instancename> -E
    Best regards
      Clas

  • Connection ... able to connect using sql developer, but not sqlplus or toad too

    Hi folks, having this issue, with only one of my so many databases, what might be the reason and how to fix/correct this, please assist.
    Able to connect using sql developer, but not sqlplus or toad too; sqlplus error: ORA-12154: TNS:could not resolve the connect identifier specified
    thanks in advance.

    SQLDEVELOPER works since it use JDBC Thin & does not use tnsnames.ora
    ORA-12154 ALWAYS only occurs on SQL Client & no SQL*Net packets ever leave client system
    ORA-12154 [B]NEVER[/B] involves the listener, the database itself or anything on the DB Server.
    ORA-12154 occurs when client requests a connection to some DB server system using some connection string.
    TNS-03505 is thrown by tnsping & is same error as ORA-12154 thrown by sqlplus or others.
    The lookup operation fails because the name provided can [B]NOT[/B] be resolved to any remote DB.
    The analogous operation would be when you wanted to call somebody, but could not find their name in any phonebook.
    The most frequent cause for the ORA-12154  error is when the connection alias can not be found in tnsnames.ora.
    The lookup operation of the alias can be impacted by the contents of the sqlnet.ora file; specifically DOMAIN entry.
    TROUBLESHOOTING GUIDE: ORA-12154 & TNS-12154 TNS:could not resolve service name [ID 114085.1]
    http://edstevensdba.wordpress.com/2011/02/26/ora-12154tns-03505/

  • I get a "Connection Failed" message when I try to connect to a Windows 7 computer that I was able to connect to before.

    I was able to connect to this Windows 7 computer before, I don't think anything happened, and then suddenly I couldn't.  I turned the firewall off and enabled everything that I could for sharing on the PC.  I can connect to the other PC on the network fine.  I have tried using the connect to server and all of the different ways to enter the address in.  When I ping the PC all of the responses are completely normal.  I'm on OS X 10.8.3 and the PC I'm connecting to is Windows 7 Ultimate x64 SP1.  If you need any more details I'll try to provide them, that's all I can think of right now.

    I called Apple today... It turned out to be my modem/router.

Maybe you are looking for

  • The keyboard of my computer doesn't work

    **** apple community, i have a very serius problem with my macbook. Today, i iniciated my computer to start working as usual, but i discovered that my computer do not recognize the keyboard or the trackapd that are attached to it. These are not exter

  • QHD+ Resolution Scaling Issues Windows 8

    I've read that QHD+ resolution monitors like the Dell Precision m3800 with a 3200x1800 resolution screen are having scaling issues with Windows 8, and even 8.1. Some programs scale correctly, but I have specifically heard Adobe programs including Ado

  • Polling SAP directories

    Hello, I am hoping someone will be able to help me with my query. I am trying to write an ABAP program which poll a SAP directory and then process the files within this directory. I am using FM SUBST_GET_FILE_LIST to get the files from the directory

  • Blocking AR Down Payments Requests

    Is there any way to stop an open AR Down Payment Request from appearing on the Incoming Payments screen? I want to use AR Down Payment Request as a means of printing a document that is linked to a sales order, so I have no interest in the DPR as a fi

  • Am I the oddball Mac Pro buyer?

    I ordered a Mac Pro not for professional applications not for video editing but for games. I love gaming on a mac. I think its fun to head to a lan party and bring along my mac. Right now I have a MacBook Pro I got in Feb (replaced my PowerBook G4) W