BO Login token expire problem

Hi,
We have few dashboards developed in Xcelsius which we need to run 24/7. We use jsp to create login token and pass the login token to the .swf file. The problem is, the login token expires after 24 hour and the dashboards give error message "Invalid login token". In that case, we have to close the dashbaords and start again.
Is there anyway to automatically extend the lifetime of the login tokens? Please share your knowledge.
Regards,
Tanveer.

There is a setting in the infoview web.xml for logontoken and value of true will cause the logon token to auto renew.
If you are looking for a solution in the SDK then you may want to ask this question in the SDK forums. Let me know and I can move the post there.
Regards,
Tim

Similar Messages

  • Login Token Expired Error on FolderManager.getFolderByPath

    Hello,
    We have two applications that are both making a call to FolderManager.getFolderByPath().  When this call is made, we receive a ContentException from the PTCS, and the error message indicates that the Login Token has expired.  We are sending the login token (in fact, all of our web service settings are identical to another set of servers that do work), and we are completely stumped.  We don't see any exceptions in the logs for the PTCS.  Anyone have a clue as to what might be wrong?
    Thanks,
    Eric

    Did you ever figure this one out? I am having the same problem.

  • Public Caching Problem with Login Token

    Hi All,
    I am trying to publicly cache a Portlet on a community (at community level) when using a login token. From my initial testing it looks like any Portlet which has a login token passed (through the webservice) can only exhibit PRIVATE caching and is cached on a per user basis not a per community basis.Can you please advise if it is possible (and if so how) to cache at a public level when using a login token.A speedy response is appreciated as I have a Tuesday deadline to meet (that's right tomorrow)

    And here is the code for the database connection
    import java.sql.*;
    import java.util.*;
    public class TryConnect_10g
            public static void main(String abc[])
        String cs = "jdbc:oracle:thin:@255.255.255.255:1234:a000studs";
    //    String cs = "jdbc:oracle:thin:@255.255.255.255:1234:a000studs";
             String user = "123456";
             String pass = "123456";
             try
                   Class.forName("oracle.jdbc.driver.OracleDriver");
                   //Connection conn = DriverManager.getConnection("jdbc:odbc:myOracle");
                   Connection conn = DriverManager.getConnection(cs,user,pass);
                   Statement stmt = conn.createStatement();
                   String query = "SELECT * FROM members";
                   ResultSet rs = stmt.executeQuery(query);
                 // ResultSet rs = stmt.executeQuery("SELECT * FROM members WHERE member_id = 'M0001'");
                   while(rs.next())
                         String s = rs.getString("member_id");
                         System.out.println("\n Member ID. : " + s);
                   System.out.println("\nOracle10g at 255.255.255.255  is working!");
              catch(SQLException e)
                   System.out.println("\n\nException Occured " +
                             "(Incorrect IP address, Server may be down, or SQL Exception)");
                   e.printStackTrace();
              catch(ClassNotFoundException e)
                   System.out.println("\n\nException Occured (CLASSNOTFOUND Exception)");
    }

  • Having Problems with Login Token

    I'm constructing a search method.This is my code:
    //Get portlet context object IPortletContext portletContext = PortletContextFactory.createPortletContext(request,response); IPortletRequest portletRequest = portletContext.getRequest(); IPortletUser portletUser = portletContext.getUser(); // Use PRC URL urlEndPoint = portletRequest.getRemoteAPIEndpoint(); String strToken = portletRequest.getLoginToken().toString(); IRemoteSession Session = portletContext.getRemotePortalSession(); Session = RemoteSessionFactory.getTokenContext(urlEndPoint, strToken);
    I'm getting this exception:
    com.plumtree.remote.portlet.NotInRequestException: The Login Token was not configured to be sent to this portlet.
    It points to this line of code:
    String strToken = portletRequest.getLoginToken().toString();
    What am I missing?

    In the web service object -> advanced settings page
    you have to check mark "send login token"

  • When I add an opendocument login token, it wipes out my parameter/prompt response in the Redirect URL

    I am having this issue and I wonder if anyone has any pointers?
    When I send the URL with the single prompt response &lsSPrompt0=1234567 it works fine but I have to login to InfoView.
    So I created a login token .jsp and that took care of the login for InfoView, but it also killed my prompt value.
    The code that I got from another site that does the same thing I WANT to do seems to create a cookie to store the passed prompt value in, then it creates a login token, then it assembles it all in the redirect URL and sends it to the openDocument.jsp.
    The login token works like a champ, but the prompt value (initially passed in to the cookie as "Prompt0") ends up passing from the Redirect URL to the openDocument.jsp with a value of NULL (lsSPrompt0=NULL).
    In my lack of knowledge, I am thinking maybe it has something to do either with how the cookie is being created, how it is being passed, or how/if it is getting stored at the target.  The cookie/token.jsp and the openDocument.jsp are in different folders on the same domain.
    So, I pass this URL:
    http://server:8080/InfoViewApp/token.jsp?&lsSPrompt0=1234567
    The token.jsp that it hits looks like this:
    So, the redirect winds up hitting the target looking like this:
    http://server:8080/OpenDocument/opendoc/openDocument.jsp?token=logonToken&iDocID=45227708&sKind=FullClient&lsSPrompt0=NULL&NAII=N&buttonrefresh=hide&buttonexport=hide
    Obviously, my problem is this:  lsSPrompt0=NULL
    Any pointers or nuggets of wisdom are GREATLY appreciated?
    Also of note, I wasn't sure if I needed to publish this token.jsp as a Webapp to Tomcat.
    I just placed the .jsp file in the folderTomcat5.5/webapps/InfoViewApp (same location as the client who has it working).
    Do I need to publish it?  Is that part of the problem?
    I am a little out of my realm here but trying to learn!
    We are on BOXI R2, Tomcat 5.5, JAVA, and I am having the same behavior on my personal XI 3.0 server too
    Thanks in advance,
    Randy

    I believe it's storing the info in a cookie so that it can be used later.  You don't mention which version of BO you're using, but I've sometimes found that the logon tokens created in 4.x contain special characters and may need to be URL encoded.  Also, I've found that it helps to put the logon token at the end of the URL after any parameters instead of in the middle before the parameters.
    -Dell

  • 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

  • Call into WS Portal to authorize login token Failed

    I have a portlet that allows a user to upload documents to a document folder in a Collaboration project. I have the Login Token set for 30 minutes in the portlets Advanced Admin. However, the function still appears to fail too quickly with the following error.
    An Exception has ocurred during InsertNewDocument()Call into WS Portal to authorize login token 8370|1137526646|h2EZdnRKV bmNS2pEP/avpiz Pw= failed. Details: com.plumtree.remote.prc.PortalException:null; nested exception is: java.rmi.RemoteException: -2147024809 - Error in function PTSession.Reconnect (strToken == '8370|1137526646|h2EZdnRKV bmNS2pEP/avpiz Pw='): -2147024809 - InternalSession.Reconnect(): Invalid token.An Exception has ocurred during InsertNewDocumentCall into WS Portal to authorize login token 8370|1137526646|h2EZdnRKV bmNS2pEP/avpiz Pw= failed. Details: com.plumtree.remote.prc.PortalException:null; nested exception is: java.rmi.RemoteException: -2147024809 - Error in function PTSession.Reconnect (strToken == '8370|1137526646|h2EZdnRKV bmNS2pEP/avpiz Pw='): -2147024809 - InternalSession.Reconnect(): Invalid token.
    How can I Reconnect if the token is no longer valid? Does the user have to refresh the page ?
    Paul
    =http://cgi-clay01.clayton.com/imageserver/plumtree/common/public/css/mainstyle19-en.css]

    I have a portlet that allows a user to upload documents to a document folder in a Collaboration project. I have the Login Token set for 30 minutes in the portlets Advanced Admin. However, the function still appears to fail too quickly with the following error.
    An Exception has ocurred during InsertNewDocument()Call into WS Portal to authorize login token 8370|1137526646|h2EZdnRKV bmNS2pEP/avpiz Pw= failed. Details: com.plumtree.remote.prc.PortalException:null; nested exception is: java.rmi.RemoteException: -2147024809 - Error in function PTSession.Reconnect (strToken == '8370|1137526646|h2EZdnRKV bmNS2pEP/avpiz Pw='): -2147024809 - InternalSession.Reconnect(): Invalid token.An Exception has ocurred during InsertNewDocumentCall into WS Portal to authorize login token 8370|1137526646|h2EZdnRKV bmNS2pEP/avpiz Pw= failed. Details: com.plumtree.remote.prc.PortalException:null; nested exception is: java.rmi.RemoteException: -2147024809 - Error in function PTSession.Reconnect (strToken == '8370|1137526646|h2EZdnRKV bmNS2pEP/avpiz Pw='): -2147024809 - InternalSession.Reconnect(): Invalid token.
    How can I Reconnect if the token is no longer valid? Does the user have to refresh the page ?
    Paul
    =http://cgi-clay01.clayton.com/imageserver/plumtree/common/public/css/mainstyle19-en.css]

  • 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

  • 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 = ''"

  • Expiration problem in other packages?

    Do anybody know whether other java extension packages will have the same expiration problem as in JCE1.2.1 or not?

    Your classpath needs to include both "work" (its full path) and also "work/pack1"
    The syntax for setting the classpath environment variable will depend on what shell you're using. But you can use the "-classpath <path>" command line option when compiling and running your application.

  • 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

  • Need Extended Version of JCO Pool Viewer Tool for SSO Expiration Problem

    Hi, SDN Fellow.
    When we are running some of our Web Dynpro application, it ran into this error". Cannot create JCOClientConnection for Logical System XXXXX_WD_MODELDATA_DEST - Model class xxxxx. The SSO ticket needed for authentication to  XXXXX_WD_MODELDATA_DEST has expired. Close all applications and lofon anew!"
    We have researched on this error, and find that the optimal fix is to upgrade to SP12, then use the Assertion Ticket. But we are currently not ready to apply SP12 from SP11 yet.
    I have read about SAP Note 1130191 - JCO Pool Viewer Tool for SSO Expiration Problem.
    For workaround fix, we decided to try out Extended Version of JCO Pool Viewer Tool to clear the cache when this error occurs.
    The note did not mention where can I get the tool. I remembered I read a blog on this tool too, but could not recall the blog link. Can anyone guide me where can I get this tool?
    Thanks,
    Kent

    Hi Cui,
    Navigate to Content Admin-> Web Dynpro-> SAP.COM space in left navigation area.
    There you can find the EAR/WAR file for this tool, open it and click on run.
    Now it will show you list of threads which are faulty, you can remove the faulty thread from this list.
    So no server restart is needed in case of one thread failure.
    If you are not able to get this tool, I will mail it to your ID.
    regards
    Kedar Kulkarni
    Reward points for useful answers
    Edited by: Kedar Kulkarni on Jun 18, 2008 2:58 PM

  • Session Expired Problem on OAS

    Hi,
    I often got the error message "Session Expired" displayed on my HTML page that serves Java Servlet output after some time.
    I attempted to look through my Servlet source codes but it has no problem. In fact, it runs perfectly well on JavaWebServer2.0.
    This seems to be a OAS problem. I'm using Oracle Application Server 4.0.8.1. I attempted changing the Servlet Cartridge's "Max session idle time" and observe the behaviour. It appears that when "Session Expired" problem happened, my servlet class never get called. OAS simply display a "Session Expired" message on the web page.
    How can I avoid this? How can ask OAS to call my servlet's doGet() to create a new session when it expired?
    Anyone knows how?
    null

    Hi,
    OAS has a limitation of 300 seconds. This value cannot be changed. See the release notes.
    One possible way to get around this is to use the Oracle Supplied Session class and use the time feature in that.
    This a big limitation and I am not sure why Oracle designed the product this way.
    null

  • E6 Certificate Expired Problem

    I tried to install some dictionary software....it is showing the Certificate expired problem.
    I tried to search on internet for other options provided by 3rd parties...they are not working.
    what the use of using this mobile if cannot install softwares....

    > it is not that easy if you operator supports NITZ
    Do you mean "automatic time update"? If it is on, it will be automatically set to off when you manually change phone's date.
    I never had problem to change date for fooling expired certificates on my E72. I also never removed the SIM.
    bbao
    * If this post helped you, please click the white Kudo star.
    * If this post has solved your issue, please click Accept as Solution.

  • "undefined user or missing login token"

    Hi
    I've installed Oracle Secure Backup 10.2 on a RHEL 5 system, on which I'm running Oracle 11g R1. I think I've set things up correctly, including adding preauthorized access in OSB to the 'oracle' user, and creating a storage selector. When I use EM to run a test tape backup, I do see a job get started in the OSB web interface's Home page under Active Jobs.
    But the job reports many instances of:
    "undefined user or missing login token'
    and the rest of the error message is unhelpful jibberish. This message isn't mentioned in the documentation, and the documentation doesn't help me understand what/where the user is missing from.
    Help, please!
    Thanks
    tl

    Hi
    Thanks for the help! As requested:
    11g:[oracle@tivo7 ~]$ obtool lsuser -l
    admin:
    Password: (set)
    User class: admin
    Given name: [none]
    UNIX name: root
    UNIX group: root
    Windows domain/acct: [none]
    NDMP server user: no
    Email address: [none]
    UUID: f8c9258a-cbb9-102b-9b72-000423cc7906
    Preauthorized access: [none]
    oracle:
    Password: (set)
    User class: oracle
    Given name: [none]
    UNIX name: oracle
    UNIX group: dba
    Windows domain/acct: [all] Administrator
    NDMP server user: no
    Email address: [none]
    UUID: f8c9305c-cbb9-102b-9b72-000423cc7906
    Preauthorized access:
    Hostname: [all]
    Username: [all]
    Windows domain: [all]
    RMAN enabled: yes
    Cmdline enabled: yes
    11g:[oracle@tivo7 ~]$

Maybe you are looking for