IBM Support

PJ34783: CUBE PROCESSING FAILS: "A CONNECTION CANNOT BE MADE" - PA.AMO.P ROCESSANALYZERAMO.CONNECT()

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • ***PLEASE PROVIDE THE FOLLOWING INFORMATION
    THIS FIELD IS REQUIRED.***
    Description of Problem (full details)
    Customer installed PA 4.0.1-001 on 64-bit Windows. Whne they
    try to run cube processing, they get the following errrors in
    palogtxt:
    008/10/06 16:37:57 [filenet.pa.main.DTSRunner$WIPProcessor]
    SEVERE main  Error while processing WIP cubes: {0}
    java.lang.Exception: A connection cannot be made. Ensure that
    the server is running.
       at
    Microsoft.AnalysisServices.XmlaClient.Connect(ConnectionInfo
    connectionInfo, Boolean beginSession)
       at Microsoft.AnalysisServices.Server.Connect(String
    connectionString, String sessionId)
       at pa.amo.ProcessAnalyzerAMO.connect()
       at pa.amo.ProcessAnalyzerAMO.Main(String[] argv)
    Error while processing WIP cubes: {0}
    And these:
    2008/10/06 16:37:40 [filenet.pa.publisher.PublisherManager]
    INFO  publisher  Committing published events to the database.
    2008/10/06 16:37:40 [filenet.pa.publisher.PublisherManager]
    SEVERE publisher  Database error:
    com.microsoft.sqlserver.jdbc.SQLServerException: The INSERT
    statement conflicted with the FOREIGN KEY constraint
    "FK_F_DMWorkflowWIP_D_DMWorkflow". The conflict occurred in
    database "VMAEDM", table "dbo.D_DMWorkflow".
     at
    com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabas
    eError(Unknown Source)
     at
    com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(U
    nknown Source)
     at
    com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecu
    tePreparedStatement(Unknown Source)
     at
    com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStm
    tExecCmd.doExecute(Unknown Source)
     at
    com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
     at
    com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand
    (Unknown Source)
     at
    com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(
    Unknown Source)
     at
    com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatemen
    t(Unknown Source)
     at
    com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.execute
    (Unknown Source)
     at
    filenet.pa.sql.PADataEnvironmentBase.factInsert_WorkflowWIP(Unk
    nown Source)
     at
    filenet.pa.publisher.fact.FactDataEnvironment.paFactInsert(Unkn
    own Source)
     at
    filenet.pa.publisher.fact.NonBulkFactTable.update(Unknown
    Source)
     at
    filenet.pa.publisher.fact.FactManager.performNonBulkUpdate(Unkn
    own Source)
     at
    filenet.pa.publisher.Publisher.performNonBulkUpdate(Unknown
    Source)
     at
    filenet.pa.publisher.PublisherManager.updateDatabase(Unknown
    Source)
     at filenet.pa.publisher.PublisherManager.start(Unknown
    Source)
     at filenet.pa.main.PARunnable.run(Unknown Source)
     at java.lang.Thread.run(Thread.java:570)
    The had a similar issue with installing the OLAP db during PA
    installation  on 64-bit Windows in defect 774052. It is not
    clear if this is a related issue, or how to apply a similar
    workaround in this scenario. On the system in defect 774052,
    after successfully installing the OLAP DB, cube processing
    worked successfully without this error.
    We also tried to recreate the PA databases because of the
    second exception above about the foreign key contraints (the PA
    database may be corrupt). We tried running cscript setupdb.wsf
    in the ...jpa\scripts\sqlserver folder. It gave an error about
    creating an OLAP object.
    This installation does not have production data yet, so the PA
    database can be recreated if necessary.
    TC wanted to see if CSS/Engineering has any suggestions to try
    before trying to reinstall PA.
    How long has the problem been occurring (recent changes)? :
    This is the first time they tried processing the cubes on this
    system.
    Does this occur on more than one station / server? :  no.
    Is there a workaround? : no
    What is the impact to the customer/system? : cannot use PA
    Can the problem be replicated on an internal system?  Y or N
    By Who (L3, Support, etc..) no
    Steps to Reproduce:
    1
    2
    3
    Actual Results: exceptions above when trying to process cubes
    Expected Results: processing the cubes should be successful
    Are there any similar or related Defects? If Y provide ECMDB #s
    774052
    What logs were collected and where are they located?
    palog.txt, attached to the defect
    Configuration/Environment :
    Server OS : Windows 2003 R2
    Client OS :
    Database : MS SQL 2005
    Network:
    App Server :
    Browser :
    Note if non US Language:
    Other Product Component Versions: P8 PA 4.0.1-001
    Non Web Environment  Y or N
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Cube Processing fails: "A connection cannot be made"  -      *
    * pa.amo.ProcessAnalyzerAMO.connect()                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Customer installed PA 4.0.1-001 on 64-bit Windows. Whne they *
    * try to run cube processing, they get the following errrors   *
    * in palogtxt:                                                 *
    * 008/10/06 16:37:57 [filenet.pa.main.DTSRunner$WIPProcessor]  *
    * SEVERE main  Error while processing WIP cubes: {0}           *
    * java.lang.Exception: A connection cannot be made. Ensure     *
    * that the server is running.                                  *
    *    at                                                        *
    * Microsoft.AnalysisServices.XmlaClient.Connect(ConnectionInfo *
    * connectionInfo, Boolean beginSession)                        *
    *    at Microsoft.AnalysisServices.Server.Connect(String       *
    * connectionString, String sessionId)                          *
    *    at pa.amo.ProcessAnalyzerAMO.connect()                    *
    *    at pa.amo.ProcessAnalyzerAMO.Main(String[] argv)          *
    * Error while processing WIP cubes: {0}                        *
    * And these:                                                   *
    * 2008/10/06 16:37:40 [filenet.pa.publisher.PublisherManager]  *
    * INFO  publisher  Committing published events to the          *
    * database.                                                    *
    * 2008/10/06 16:37:40 [filenet.pa.publisher.PublisherManager]  *
    * SEVERE publisher  Database error:                            *
    * com.microsoft.sqlserver.jdbc.SQLServerException: The INSERT  *
    * statement conflicted with the FOREIGN KEY constraint         *
    * "FK_F_DMWorkflowWIP_D_DMWorkflow". The conflict occurred in  *
    * database "VMAEDM", table "dbo.D_DMWorkflow".                 *
    *  at                                                          *
    * com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDataba
    * Source)                                                      *
    *  at                                                          *
    * com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(
    * Source)                                                      *
    *  at                                                          *
    * com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExec
    * Source)                                                      *
    *  at                                                          *
    * com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepSt
    * Source)                                                      *
    *  at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown  *
    * Source)                                                      *
    *  at                                                          *
    * com.microsoft.sqlserver.jdbc.SQLServerConnection.executeComman
    * Source)                                                      *
    *  at                                                          *
    * com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand
    * Source)                                                      *
    *  at                                                          *
    * com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStateme
    * Source)                                                      *
    *  at                                                          *
    * com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.execut
    * Source)                                                      *
    *  at                                                          *
    * filenet.pa.sql.PADataEnvironmentBase.factInsert_WorkflowWIP(Un
    * Source)                                                      *
    *  at                                                          *
    * filenet.pa.publisher.fact.FactDataEnvironment.paFactInsert(Unk
    * Source)                                                      *
    *  at                                                          *
    * filenet.pa.publisher.fact.NonBulkFactTable.update(Unknown    *
    * Source)                                                      *
    *  at                                                          *
    * filenet.pa.publisher.fact.FactManager.performNonBulkUpdate(Unk
    * Source)                                                      *
    *  at                                                          *
    * filenet.pa.publisher.Publisher.performNonBulkUpdate(Unknown  *
    * Source)                                                      *
    *  at                                                          *
    * filenet.pa.publisher.PublisherManager.updateDatabase(Unknown *
    * Source)                                                      *
    *  at filenet.pa.publisher.PublisherManager.start(Unknown      *
    * Source)                                                      *
    *  at filenet.pa.main.PARunnable.run(Unknown Source)           *
    *  at java.lang.Thread.run(Thread.java:570)                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * apply to PA401.002                                           *
    ****************************************************************
    

Problem conclusion

  • The fix build is PA401.002
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ34783

  • Reported component name

    P8 TOOLKIT

  • Reported component ID

    5724R9900

  • Reported release

    401

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-10-09

  • Closed date

    2009-06-16

  • Last modified date

    2009-06-16

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    PROCESS ANALYZE

  • Fixed component ID

    5724R7603

Applicable component levels

  • R401 PSY

       UP



Document information

More support for: Case Foundation
Case Analyzer

Software version: 4.0.1

Reference #: PJ34783

Modified date: 16 June 2009