A login timeout error in ODI

Hi ,
I have been facing following issue since some days of  "A login timeout occured while connecting to the database".
Although this is not occuring daily in scheduled executions but its been there say 2-3 days apart.
Error given is as
ODI-1228: Task SrcSet0 (Loading) fails on the target ORACLE connection OMP.
Caused By: oracle.odi.jdbc.datasource.ConnectionTimeoutException: A login timeout occured while connecting to the database
    at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.doGetConnection(LoginTimeoutDatasourceAdapter.java:117)
    at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.getConnection(LoginTimeoutDatasourceAdapter.java:62)
    at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:113)
    at com.sunopsis.sql.SnpsConnection.createConnection(SnpsConnection.java:380)
    at com.sunopsis.sql.SnpsConnection.connect(SnpsConnection.java:338)
    at com.sunopsis.sql.SnpsQuery.updateExecStatement(SnpsQuery.java:1842)
    at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java:628)
    at com.sunopsis.dwg.dbobj.SnpSessTaskSql.executeUpdate(SnpSessTaskSql.java:3218)
    at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execStdOrders(SnpSessTaskSql.java:1785)
    at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java:2805)
    at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2515)
    at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:534)
    at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:449)
As stated in some forums i have done changes in User Parameters and set same to 180 but still error persists.
now I also tried to find file USERPREF.XML but i was unable find the file.
My ODI installation directory path is "D:\oracle\product\11.1.1\Oracle_ODI_1"
I wanted to know if any solutions for sam problem are there and any inputs regarding same would appreciated.
Thanks,
Mahesh

Hi,
Can this be resolved by upgrading ODI?
My ODI version details are:
About
Oracle Data Integrator 11g 11.1.1
Standalone Edition Version 11.1.1
Build ODI_11.1.1.3.0_GENERIC_100623.1635 Copyright © 1997, 2010
Oracle.  All Rights Reserved.
IDE Version: 11.1.1.3.37.56.60
Product ID: oracle.odi
Product Version: 11.1.1.0.0.0.0
Version
Component       Version
=========       =======
Java(TM) Platform           1.6.0_23
Oracle IDE           11.1.1.3.0
Do i have to update all the 11g patches to get rid of this issue?
Thanks,
Shilpa

Similar Messages

  • Login timeouts

    Guys,
    Iam getting login timeout error sometimes when  we tried to connect to AS/400 from ORACLE.
    I have checked in the designer/ user parameters /ORACLE DATA INTEGRATOR Timeout and it is 30 there.
    Do we need to change that value? or anything we need to change on ther server side agent file i.e odiparams.sh file?
    Cheers

    Hi
    When we run 10 interfaces using same connection string  all in 2 mnts intevals,all of them went through well apart from 2.
    Those 2 failed saying login timeouts and when i ran them again immediatly they went through well.
    So clealy something with timeout waiting side of issue?
    Cheers

  • A login time out error in ODI

    Hi,
    I have been facing following issue since few days of  "A login timeout occured while connecting to the database".
    Although this is not occuring daily in scheduled executions but its been there say 2-3 days apart.
    Error given is as :
    ODI-1228: Task SrcSet0 (Loading) fails on the target ORACLE connection OMPTBR.
    Caused By: oracle.odi.jdbc.datasource.ConnectionTimeoutException: A login timeout occured while connecting to the database
    at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.doGetConnection(LoginTimeoutDatasourceAdapter.java:117)
    at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.getConnection(LoginTimeoutDatasourceAdapter.java:62)
    at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:113)
    at com.sunopsis.sql.SnpsConnection.createConnection(SnpsConnection.java:380)
    After doing research on this, i found in some forums to modify the timeout value in userpref.xml file. But, i am unable to locate the file userpref.xml.
    Any inputs/pointers would be of great help.
    Thanks,
    Shilpa

    Hi,
    Can this be resolved by upgrading ODI?
    My ODI version details are:
    About
    Oracle Data Integrator 11g 11.1.1
    Standalone Edition Version 11.1.1
    Build ODI_11.1.1.3.0_GENERIC_100623.1635 Copyright © 1997, 2010
    Oracle.  All Rights Reserved.
    IDE Version: 11.1.1.3.37.56.60
    Product ID: oracle.odi
    Product Version: 11.1.1.0.0.0.0
    Version
    Component       Version
    =========       =======
    Java(TM) Platform           1.6.0_23
    Oracle IDE           11.1.1.3.0
    Do i have to update all the 11g patches to get rid of this issue?
    Thanks,
    Shilpa

  • 2008 r2 Copy Database Wizard Error code 0x80004005 (login timeout expired).

    While on copy database wizard, step Configure the package I
    get this error:
    while trying to find a folder on sql an ole db error was encountered with error code 0x80004005 (login timeout expired).
    If I try to run it any way, I got the following in the Execute stage:
    the job failed. check the event log on the destination server for details
    In the destination server, job history:
    Message
    Executed as user: WORKGROUP\servername$. Microsoft (R) SQL Server Execute Package Utility  Version 10.50.1600.1
    for 64-bit  Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started:  3:26:57 PM  Could not load package "package name omitted" because of error 0xC0014062.  Description: The LoadFromSQLServer method
    has encountered OLE DB error code 0x80004005 (Login timeout expired).  The SQL statement that was issued has failed.  Source:   Started:  3:26:57 PM  Finished: 3:27:44 PM  Elapsed:  47.83 seconds.  The package could
    not be loaded.  The step failed.
    I check the job permission with the integration service connection. try with default and with db_ssisadmin. 
    other info:
    Source: Other SQL Server Version, Microsoft SQL Server Enterprise Edition , Build 1617, Microsoft Windows NT 6.0 (6002) NT INTEL X86
    Destination:  Other SQL Server Version, Microsoft SQL Server Data Center Edition (64-bit) , Build 1600, Microsoft Windows NT 6.1 (7601) NT
    x64 Using SMO online transfer

    Hi kexinger,
    This issue might be caused by the insufficient permission for the SQL Agent account, please check the SQL Agent service account has sufficient permissions to the various folders. For detail information, please take a look at the following article:
    http://mattsql.wordpress.com/2014/01/06/quick-tip-could-not-load-package-xxx-because-of-error-0xc0014062/
    If you have any feedback on our support, please click
    here.
    Elvis Long
    TechNet Community Support

  • The adapter "SQL" raised an error message. Details "Login timeout expired".

    Hi All
    Please help me to understand "Login timeout". All feedback is welcome.
    BizTalk Server 2009 on Windows Server 2008 R2 64 bit
    SQL Server 2008 SP1 64 bit
    BizTalk Adapter Pack 2.0
    Event Viewer -> Windows Logs -> Application
    The adapter "SQL" raised an error message. Details "Login timeout expired".
    The adapter failed to transmit message going to send port "ALL.Exceptions" with URL "SQL://xxxxxxxxx/EsbExceptionDb/". It will be retransmitted after the retry interval specified for this Send Port. Details:"Login timeout expired".
    Regards
    Steve

    Hi Abhishek,
    Thank you for your input.
    I found errors in the Table [EsbExceptionDb].[dbo].[Fault] relating to the write to the target Oracle database
    Microsoft.ServiceModel.Channels.Common.MetadataException: Metadata resolution failed for OperationId:ATHENA/Table/WO_ADDITIONAL/Delete ---> System.TimeoutException: Timeout Expired     at
    The BizTalk send port timeout has been increased from 1 minute to 30 minute and all is well
    Regards
    Steve

  • Error code 80004005 login timeout

    Getting an intermittent error when trying to access a database on my SQL 2008 server.

    This thread should help you resolve the issue:
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/8575e9ff-3acc-4b44-8907-dbe225fcb738/login-timeout-expired-in-ssis-pack?forum=sqlintegrationservices
    In short: replace the OLE DB Destination with a OLE DB Command
    Arthur
    MyBlog
    Twitter

  • SQL Server Expres 2008R2 on Windows 7 peer to peer network using MS Access to connect - ODBC Login Timeout

    Hello,
    I have had a Microsoft Access database that was running on Windows XP against a SQL Server 2000 database.  We are running on a peer to peer network.  This all worked fine.  Recently I upgraded all the systems to Windows 7 and the Access database
    to Office 2013 and setup SQL Server Express 2008R2.  I am running into strange problems trying to connect the access database to SQL Server Express.
    SQL Server Express was setup with mixed authentication mode. 
    What is strange to me is that if I run the Access database on the same server as SQL Server Express 2008R2, everything works fine. However, if I run the Access database from a separate system (Windows usernames and passwords are identical on all systems
    for all accounts).  I get a spinning circle, then after 5 minutes or so I get an error box that says "Connection Failed SQL State S1-T00 - ODBC Login Timeout Expired.
    I click OK and then there is a ODBC login box,  It has trusted connection  box checked.  So, I just click ok and everything runs fine.
    I have checked with the Access database the ODBC connection string (How do you change this to imbed a username and pwd?) and the connection specifies that trustedconnection = yes.
    I have tried setting the odbc connection up to use a SQL Account, I have setup all of the security in SQL so that Windows accounts have access and either works on the system that is hosting the SQL database.  But when I try to connect from a separate
    machine we have to wait with the timeout and then click okay.
    Any Ideas.
    Thank you!!!

    I have TCP/IP and named pipes.
    I will take a look at the kb article.
    What puzzles me is that odbc connection is set for trusted connection, the access database is set for trusted connection.  But yet it seems that it wants to do a SQL authentication.  Then it fails, and then if you simply hit okay to do the Trusted
    Connection then it is fine.
    I will read about setting the UID and PWD in code.  Been a long time since I have done that, but very doable.  Then see if the Access DB is setup with the UID and Pwd in the odbc connection string, then switch the odbc connection to be a SQL Server
    connect, then maybe it will work..  Crossing my fingers.
    I will be back on site next week and will give it a try then.
    I will check the ports, but suspect they are fine as it works fine after it has it timed out and you hit okay to connect with a trusted connection.
    Thanks for your ideas.

  • Sapinst login timeout during installation of NetWeaver 2004s

    Hello,
    I want to install a new NetWeaver 2004s system using sapinst.
    The Gui starts but after some seconds the connection breaks with the following error.
    Starting GuiServer using:
    /opt/IBMJava2-amd64-142/bin/java -cp /usr/sap/put/Install_/sapinst_exe.1789.1199282891/JAR/instgui.jar:/usr/sap/put/Install/sapinst_exe.1789.1199282891/JAR/inqmyxml.jar -Djava.security.egd=file:/dev/urandom SDTServer config=jar:sdtserver.xml guiport=21212 sapinsthost=localhost sapinstport=21200 guistart=true
    load resource pool /usr/sap/stage/PORTAL/BS_2005_SR2_SAP_Installation_Master/IM_LINUX_X86_64/resourcepool.xml
    guiengine: no GUI connected; waiting for a connection on host , port 21200 to continue with the installation
    guiengine: login in process.
    guiengine: login timeout; the client was unable to establish a valid connection
    I used an other port but I got the same error. The only thing which helps is a reboot of the server.
    The operating system is LINUX.
    Any ideas?
    Thank you.
    Best Regards
    Ines

    Hi Ines,
    I think you're missing the DISPLAY environment variable.
    set DISPLAY <IP_of_your_pc>:0.0
    make sure your Xserver is up and running.
    That should solve your problem
    Regards
    Juan

  • Increasing the timeout parameter in ODI

    Hi,
    I have got 7000 error code in a step while executing the scenario.
    I have found out it may be time out error and it can be resolved by changing the timeout parameter in ODI(File->Userparameter->Oracle Data Integrator Timeout)
    Is there any maximum limit for this timeout parameter? After changing this, should i restart the ODI server?
    Can anyone suggest me quicly please?
    Am i proceeding correctly for this 7000 error code?

    Hi,
    Please post this question in the ODI forum:
    Data Integrator
    Thanks, Mark

  • Login timeout expired-2EETW169 no connect possible:"DBMS = MSSQL" DBNAME=""

    Hi, SDN fellows.
    I finished applying SPs for Solman Manager 7.0 (updated to Solman 7.1 EHP1 - just the Java Stack with JSPM). Then, I decided to start install SAP ECC 6.0 IDES in D drive (solman currently installed in C drive). When I ran the SAP ECC installer till the screen where it require Solution Key, I stopped the process due to invalid solution key provided. 
    After that, my Solman system became not able to connect to MS SQL server anymore. Here is the trans messages I got from "R3Trans -d".
    Not sure what isthe root cause, but I found couple messages maybe the leads to root cause.
    I wonder why the DBNAME become empty on this line: 2EETW169 no connect possible: "DBMS = MSSQL                            ---  SERVER = 'MYSERVER101' DBNAME = ''".
    These message also shown that this maybe login related issue:
    4 ETW000  [     dev trc,00000]  CopyLocalParameters: dbuser is 'dbo'                                      19  0.004714
    4 ETW000  [     dev trc,00000]  OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
    4 ETW000                                                                               
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: 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.
    4 ETW000
    LOG BY0=>Login timeout expired [dblink#4 @ 433]  
    Thanks for advices,
    KC

    4 ETW000                                                                                45  30.272192
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 17  30.272209
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: 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.
    4 ETW000                                                                                63  30.272272
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 20  30.272292
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    4 ETW000                                                                                42  30.272334
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 17  30.272351
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    4 ETW000                                                                                38  30.272389
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 17  30.272406
    4 ETW000  [     dev trc,00000]  Using Provider SQLNCLI                                                 10214  30.282620
    4 ETW000  [     dev trc,00000]  OpenOledbConnection: MARS property was set successfully.                  75  30.282695
    4 ETW000  [     dev trc,00000]  Sun Jul 24 07:23:58 2011                                             15172939  45.455634
    4 ETW000  [     dev trc,00000]  OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
    4 ETW000                                                                                41  45.455675
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Login timeout expired
    4 ETW000                                                                                43  45.455718
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 17  45.455735
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: 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.
    4 ETW000                                                                                75  45.455810
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 27  45.455837
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    4 ETW000                                                                                43  45.455880
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 16  45.455896
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    4 ETW000                                                                                38  45.455934
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 17  45.455951
    4 ETW000  [     dev trc,00000]  failed to establish conn to np:(local).                                 6519  45.462470
    4 ETW000  [     dev trc,00000]  Retrying without protocol specifier: (local)                              30  45.462500
    4 ETW000  [     dev trc,00000]  Using Provider SQLNCLI                                                    60  45.462560
    4 ETW000  [     dev trc,00000]  OpenOledbConnection: MARS property was set successfully.                  57  45.462617
    4 ETW000  [     dev trc,00000]  Sun Jul 24 07:24:14 2011                                             15636603  61.099220
    4 ETW000  [     dev trc,00000]  OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
    4 ETW000                                                                                51  61.099271
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Login timeout expired
    4 ETW000                                                                                45  61.099316
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 17  61.099333
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: 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.
    4 ETW000                                                                                60  61.099393
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 17  61.099410
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    4 ETW000                                                                                41  61.099451
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 17  61.099468
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    4 ETW000                                                                                37  61.099505
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 17  61.099522
    4 ETW000  [     dev trc,00000]  Using Provider SQLNCLI                                                  5453  61.104975
    4 ETW000  [     dev trc,00000]  OpenOledbConnection: MARS property was set successfully.                  59  61.105034
    4 ETW000  [     dev trc,00000]  Sun Jul 24 07:24:29 2011                                             15620154  76.725188
    4 ETW000  [     dev trc,00000]  OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
    4 ETW000                                                                                43  76.725231
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Login timeout expired
    4 ETW000                                                                                45  76.725276
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 18  76.725294
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: 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.
    4 ETW000                                                                                79  76.725373
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 17  76.725390
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    4 ETW000                                                                                42  76.725432
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 17  76.725449
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    4 ETW000                                                                                103  76.725552
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 25  76.725577
    4 ETW000  [     dev trc,00000]  Using Provider SQLNCLI                                                  5413  76.730990
    4 ETW000  [     dev trc,00000]  OpenOledbConnection: MARS property was set successfully.                  78  76.731068
    4 ETW000  [     dev trc,00000]  Sun Jul 24 07:24:45 2011                                             15600542  92.331610
    4 ETW000  [     dev trc,00000]  OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
    4 ETW000                                                                                42  92.331652
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Login timeout expired
    4 ETW000                                                                                45  92.331697
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 17  92.331714
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: 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.
    4 ETW000                                                                                60  92.331774
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 16  92.331790
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    4 ETW000                                                                                42  92.331832
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 16  92.331848
    4 ETW000  [     dev trc,00000]  sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    4 ETW000                                                                                38  92.331886
    4 ETW000  [     dev trc,00000]  Procname: [OpenOledbConnection - no proc]                                 17  92.331903
    4 ETW000  [     dev trc,00000]  failed to establish conn. 0                                             5491  92.337394
    4 ETW000  [    dblink  ,00433]  ***LOG BY2=>sql error -1     performing CON [dblink#4 @ 433]             119  92.337513
    4 ETW000  [    dblink  ,00433]  ***LOG BY0=>Login timeout expired [dblink#4 @ 433]                        27  92.337540
    2EETW169 no connect possible: "DBMS = MSSQL                            ---  SERVER = 'MYSERVER101' DBNAME = ''"

  • Returned message login timeout expired linked server

    OLE DB provider "SQLNCLI" for linked server "SERVER" returned message "Login timeout expired".
    OLE DB provider "SQLNCLI" for linked server "SERVER" returned 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.".
    Msg 53, Level 16, State 1, Line 0
    Named Pipes Provider: Could not open a connection to SQL Server [53].

    Hi Lukesh,
    According to your description, you cannot connect to one of your linked servers with the error "Login timeout expired", right?
    If in this case, please follow the troubleshooting methods below on the linked server.
    Select "Using both TCP/IP and named pipes" in SQL Server 2005 Surface Area Configuration.
    In SQL Server Configuration Manager, make sure that TCP/IP is enabled for the Network protocol.
    If you turn on the Firewall, make sure the TCP port 1433 is in the Firewall exception list.
    Reference
    http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/
    If the issue persists, please provide us more information, so that we can make further analysis.
    Regards,
    Charlie Liao
    TechNet Community Support

  • Installer Timeout error

    Hi,
    I have created an AddOn installer following the AddOnInstaller project. Everything goes allright when I create and install it, but when the AddOn must be started, gives me a timeout error. Which makes no sense, becouse the AddOn is executing (I can see it executing and it changes some forms as it should do).
    Any idea about what am I doing wrong?
    Thanks in advance,
    Ibai Peñ

    Hi Ibai
    Edit:
    I'm posting very slowly, I didn't see you second posting.
    I suppose you successfully created an *.ard-file using AddOnRegDataGen.exe, you pass the installation without any error.
    As far as I know, for an UI-Addon a valid license for the named user is required, which allows the user to run an addon. It also works with the 30-Day test version.
    When you login with this named user (and the addon is installed for this user/company), SBO will call your addon:
    x:\youraddonlocation\youaddon.exe theConnectionString
    You simply have to connect to the SBO Application using this supplied connection string like it's done in almost every SBO vb6 sample. After the connection is established, SBO should recognize the addon as connected (well, at least it does that for me).
    You checked wheter you connect using the supplied connection string? Maybe you mess it up somehow when parsing it as a command line argument or something?
    Message was edited by: Florian Zeller

  • I am using the mac QQ and when I login it said login timeout.

    I am using the mac QQ and when I login it said login timeout.

    If you are missing using google maps - try the Nokia map app called "here"

  • TimeOut error while running a report on the report server

    Hi,
    One of my report is taking 30 minutes to generate the output. It works fine when I run it locally, but when I run it on report server I encounter the following error message. Its a timeout error. Any solution other than tuning the query, please.
    500 Internal Server Error
    org.omg.CORBA.OBJECT_NOT_EXIST: minor code: 0 completed: No
         at java.lang.Class.newInstance0(Native Method)
         at java.lang.Class.newInstance(Class.java:237)
         at com.inprise.vbroker.orb.SE.read(SE.java:28)
         at com.inprise.vbroker.orb.DelegateImpl.handleReply(DelegateImpl.java:711)
         at com.inprise.vbroker.orb.DelegateImpl.invoke(DelegateImpl.java:606)
         at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:459)
         at oracle.reports.server._ConnectionStub.getMainFile(_ConnectionStub.java:1283)
         at oracle.reports.client.ReportRunner.getMainFile(ReportRunner.java:488)
         at oracle.reports.rwclient.RWReportRunner.getMainFile(RWReportRunner.java:121)
         at oracle.reports.rwclient.RWReportRunner.getMainFile(RWReportRunner.java:95)
         at oracle.reports.rwclient.RWClient.runReport(RWClient.java:1322)
         at oracle.reports.rwclient.RWClient.processRequest(RWClient.java:1139)
         at oracle.reports.rwclient.RWClient.doPost(RWClient.java:328)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:283)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
         at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:59)
         at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
         at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:523)
         at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:269)
         at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:735)
         at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.AJPRequestHandler.run(AJPRequestHandler.java:151)
         at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].util.ThreadPoolThread.run(ThreadPoolThread.java:64)

    Hi Bhasker
    Try setting idleTimeOut under connection element in server configuration file to a large value.
    Regards
    Sripathy

  • Getting timeout error while updating a record from c#

    Hi,
    I have around 30k records in a tables. When I update that record inside the Transaction (Enterprise Data Library, c#) , it takes long time and throws timeout error.
    But I am able to update the same record via Toad.
    In the morning I tried same updating the record, it works without any change in the code or script.+
    is it due table lock or db related issue? please adivse, how to resolve if occurs again.
    anand

    Code:
    private static void Save()
    using (DBTransactionManager dbTransactionManager = new DBTransactionManager())
    try
    DataTableDAL.Instance.ExecuteDML("Update Voyage SET BallastBonus = 30000 WHERE ID = 'AE53B610BEA743EC8AFBAED0C8349BF8';");
    //commit database
    dbTransactionManager.Commit();
    catch
    dbTransactionManager.RollBack();
    throw;
    Table
    Column Name     ID     Pk     Null?     Data Type     Default     Histogram     Encryption Alg     Salt
    ID     1     1     N     NVARCHAR2 (32)          None          
    CALCNUMBER     2          N     NUMBER (10)          None          
    CURRENCYID     3          N     NVARCHAR2 (32)          Frequency          
    CALCTYPE     4          N     NUMBER (5)          Frequency          
    ESTIMATEDESCRIPTION     5          Y     NVARCHAR2 (200)          None          
    ESTIMATEGROUPDESCRIPTION     6          Y     NVARCHAR2 (200)          None          
    BALLASTBONUS     7          Y     NUMBER (12,2)          None          
    BALLASTBONUSCOMMPCT     8          Y     NUMBER (6,3)          None          
    ISESTIMATE     9          N     NUMBER (1)          None          
    ADDITIONALSTEAMVALUE     10          Y     NUMBER (8,4)          None          
    ISADDITIONALSTEAMPCT     11          Y     NUMBER (1)          None          
    ADDITIONALPORTVALUE     12          Y     NUMBER (8,4)          None          
    ISADDITIONALPORTPCT     13          Y     NUMBER (1)          None          
    CREATEDBY     14          N     NVARCHAR2 (32)          Frequency          
    CREATEDDATE     15          N     DATE          None          
    UPDATEDBY     16          Y     NVARCHAR2 (32)          None          
    UPDATEDDATE     17          Y     DATE          None          
    LUMPSUMCARGOCOST     18          Y     NUMBER (1)          None          
    BUNKERPRICEMETHOD     19          Y     VARCHAR2 (30 Byte)          None          
    INCCONTCALCRESULT     20          Y     NUMBER (1)          None          
    FINAL_EST     21          Y     NUMBER          None          
    SPOT_VOYAGE     22          Y     NUMBER (1)          None          
    ISRUNCOSTEDIT     23          Y     NUMBER (1)          None          
    Index
    Table doesnt have any index, except primary key index.
    Total Records
    35,000
    Hope this input might sufficient to help me.

Maybe you are looking for