Quantcast
Channel: Primavera Online Interaction » Exception
Viewing all 111 articles
Browse latest View live

prim10983:Received error when updating the Access Level from 0 to 1: ODBC–update on linked table ‘OAUSER_PROJECT’ failed.

$
0
0
Solution ID: prim10983
Received error when updating the Access Level from 0 to 1: ODBC–update on linked table ‘OAUSER_PROJECT’ failed.
Status: Reviewed
Version(s): 3.5.1, 4.0, 4.1, 5.0, 6.0, 6.1, 6.2, 6.2.1, 7.0

Problem: Received error when updating the Access Level from 0 to 1:

ODBC–update on linked table ‘OAUSER_PROJECT’ failed.                                                                                                                                                                                                                  [ATI][OpenRDA ODBC] Invalid statement: update statement exception.  Error returned from engine: VDB.Update; hResult=0×80040031 (PMSDK_E_READONLY: attempt to modify a read-only object); EOleSysError = SetFieldValue [PROJECT.access_level] error, field is read-only  Error number: 0×80040031 (#-2147221455)


Fix: Check the SDK user privileges.  A user must have the Global Security profile ‘View all data/project via SDK’ to log into the SDK.  If the SDK user has ‘View all data/project via SDK’ privileges, then he is only allowed to view the data and can not change the access level 1 (shared mode). 

Only an SDK user with <Admin Superuser> privileges can change the access_level, and therefore update data, through the SDK. 


prim11001:Group Server throwing error and requires restart. Event Viewer Application Log reveals errors: Exception error File:ThreadFactory.h, Line:123, Error:8000ffff, Description:EXCEPTION_ACCESS_VIOLATION …

$
0
0
Solution ID: prim11001
Group Server throwing error and requires restart. Event Viewer Application Log reveals errors: Exception error File:ThreadFactory.h, Line:123, Error:8000ffff, Description:EXCEPTION_ACCESS_VIOLATION …
Status: Reviewed
Version(s): 3.5, 3.5.1

Fact: WSAEADDRINUSE
Fact: Group Server
Problem: Group Server throwing error and requires restart. A review of the Event Viewer Application Log will reveal errors:

Exception error


File:ThreadFactory.h, Line:123, Error:8000ffff, Description:EXCEPTION_ACCESS_VIOLATION


Context:


CLicenseProcessor::MemberLicProc


Exception error


File:MessageProcessor.cpp, Line:314, Error:80072740, Description:WSAEADDRINUSE


Context:


CMessageProcessor::MemberListenerProc

Fix:

This error can occur when trying to run two of the same types of server applications on the same machine. For instance, this error will occur if you try to run two applications that have FTP servers. In this case, the 2nd application will fail with WSAEADDRINUSE.)

prim11235:Error: “Event Code: GSQLE-1358-A” / “ORA-01654: unable to extend index…”

$
0
0
Solution ID: prim11235
Error: "Event Code: GSQLE-1358-A" / "ORA-01654: unable to extend index…"
Status: Reviewed
Version(s): 3.5, 3.5.1, 4.1, 5.0, 6.0, 6.1, 6.2, 6.2.1

Problem: When copying a project, creating a baseline, entering activity codes or importing a P3 project, receive the following error:

General SQL error.  ORA-01654: unable to extend index


ADMUSER.NDX_TASKACTV_TASK by 128 in tablespace PMDB_NDX1


*****************************************************
*                EXCEPTION  REPORT                  *
*****************************************************

Executable:    PM.exe
Application:   Primavera Project Manager
Event Code:    GSQLE-1358-A
Message:      
  General SQL error.
  ORA-01654: unable to extend index
  ADMUSER.NDX_TASKACTV_TASK by 128 in tablespace
  PMDB_NDX1
 
Context:
  1: TfrmEPS.mnuOpenProjectClick
  2: TCFormManager.SetToolbar
  3: TfrmLogin.FormCreate
  4:
  5:
  6:
  7:
  8:
  9:
  10:
 
Detail:
  Type:        EDBEngineError
  Object Type: TCVirtualQueryGrid
 
Database Error:
1: General SQL error.
   Category:          51
   Error Code:        13059
   Sub Error Code :   3
   Server Error Code: 0
 
2: ORA-01654: unable to extend index ADMUSER.NDX_TASKACTV_TASK by 128 in tablespace PMDB_NDX1
 
   Category:          51
   Error Code:        13059
   Sub Error Code :   3
   Server Error Code: 1654

Problem: GSQLE-1789-F
Problem: General Error. GSQLE-1526-6
Problem: Event Code: SAQLE-0035-5
Problem: Event Code:  GSQLE-3539-8
Message:      
  General SQL error.
  ORA-01654: unable to extend index ADMUSER.NDX_TASKACTV_ACTVCODE by 128 in tablespace PMDB_NDX1
Problem: Event Code: GSQLE-2005-F

General SQL error.
ORA-01654: unable to extend index ADMUSER.NDX_TASK_1 by 128 in tablespace PMDB_NDX1

Problem:

Error PRMDB-1294-E when exporting a project


Executable:    PM.exe
Application:   Primavera Project Management

Event Code:    PRMDB-1294-E

Message:      

  PRM DBAccess Error: SQL Server Error:
 
ORA-01654: unable to extend index ADMUSER.NDX_UPKLIST_SESSION_PK by 128 in tablespace PMDB_NDX1

ORA-06512: at line 251

Problem: PRMDB-3920-3 and PRMDB-0623-D when copying or opening projects.

EXCEPTION REPORT – Date: 08-Aug-07 Executable: pm.exe Application: Primavera Project Management Event Code: PRMDB-0623-D Message: PRM DBAccess Error: SQL Server Error: ORA-01653: unable to extend table ADMUSER.TASKSUM by 1024 in tablespace PRTSDAT1 Context: 1: TfrmMain.actAdminUsersExecute 2: TfrmMain.actProjectsExecute 3: TfrmMain.actAdminUsersExecute 4: TCFormManager.SetToolbar 5: TfrmLogin.FormCreate 6: 7: 8: 9: 10: Detail: Type: EprmDBSQLExecutionFailure Object Type: TCVirtualQueryGrid Database Error: Error Code: 0 Components

Problem: PPUSP-2606 when attempting to add or delete baselines.
Problem:
Fix: This Oracle error means that the index tablespace PMDB_NDX1 is not large enough.

In the database creation scripts we limit extents (number of times tablespace will grow) to 121.  This is done to control disk space usage.


Increase the extents to 500 by executing the following SQL command:


alter tablespace pmdb_ndx1 default storage (maxextents 500)


Note:  This process should be completed by an Oracle DBA.

prim11639:Exception when using the Alphablox v5.5 Convert Repository with an Oracle DB

$
0
0
Solution ID: prim11639
Exception when using the Alphablox v5.5 Convert Repository with an Oracle DB
Status: Reviewed
Version(s): 8.6, 8.6 SP2, 8.6.0 SP1, 8.6.0 SP2a, 8.6.0 sp1a, 8.6.0 sp1b, 8.6.0a

Problem: Users will experience an exception when using the Alphablox v5.5 Convert Repository function against an Oracle database
Cause:

This occurs because BEA WebLogic version 8 is using JDK v1.4 and AlphaBlox is using v1.3. The next AlphaBlox release should fix this problem (as Alphablox is going to jdk 1.4).

Fix:

You can use either of the following workaround:


1. Add our Oracle driver in the last file. In /alphablox/analytics/tools/convert/ConvertRepository.lax file, edit the lax.class.path statement. Insert


“C:\\alphablox\Analytics\lib\OracleDriver.zip”


before the weblogic.jar path.



2. Or change the jdk path. In /alphablox/analytics/tools/convert/ConvertRepository.lax file, change


lax.nl.current.vm=..\\..\\jdk\\bin\\java.exe


to


lax.nl.current.vm=\\bea\\jdk141_03\\bin\\java.exe

prim11643:”Exception error: CLDML-3916-3″ when scheduling caused by too many loops

$
0
0
Solution ID: prim11643
"Exception error: CLDML-3916-3" when scheduling caused by too many loops
Status: Reviewed
Version(s): 3.5, 3.5.1

Problem:

Executable:PM.exe


Application:Primavera Project Manager


Event Code:CLDML-3916-3


Message:


TCCheckLoopDepend.MakeLoopReport.FindLoopForRow:


Too many levels of recursion


Context:


1: TfrmMain.actToolsSchedulingExecute


2: TfrmMain.actProjectActivitiesExecute


3: TCFormManager.SetToolbar

Cause: This message occurs when there are too many activities within the schedule loop for the report to be generated.
Fix: To resolve the error remove the activity relationships which are causing the loop.

prim12209:Primavision hangs when trying to login.

$
0
0
Solution ID: prim12209
Primavision hangs when trying to login.
Status: Reviewed
Version(s): 2.x, 3.x, 4.0, 4.1

Problem: Primavision hangs when trying to login.
Problem: Primavision error log is reporting:






error Exception(All licenses are currently being used, try again later.) [Class=com.primavera.PhoenixException] The encryption used for this blob uses an incompatible version.
at com.primavera.infr.services.utils.b.t(Unknown Source)
at com.primavera.infr.services.utils.g.(Unknown Source)
at com.primavera.infr.services.srvcs.c$a.gp(Unknown Source)
at com.primavera.infr.services.srvcs.c$a.execute(Unknown Source)
at com.primavera.infr.services.threadpool.c.run(Unknown Source)
at java.lang.Thread.run(Thread.java:536)
Cause: License file has become damaged or corrupt.
Fix: Re-administer the application license file, into the database, using the DB Config.

You may need to remove the current license from the database before re-administering.  For more information on how to remove a license file, please view the following: Solution 20021127134548:  How to remove a license file


Instruction for administering/loading license file: How do I configure a license file?

prim12335:Weblogic does not startup after installing AlphaBlox

$
0
0
Solution ID: prim12335
Weblogic does not startup after installing AlphaBlox
Status: Reviewed
Version(s): 7.0

Problem: An exception similar to the following occurs during the Weblogic startup :

java.lang.ClassNotFoundException: com.alphablox.server.webapps.server.ServerStartup.>
####<Aug 5, 2004 4:43:34 PM PDT> <Error> <HTTP> <techsupp02> <myserver> <main> <<WLS Kernel>> <> <BEA-101216> <Servlet: “AlphabloxServerStartup” failed to preload on startup in Web application: “AlphabloxServer”.
javax.servlet.ServletException: [HTTP:101249][ServletContext(id=12254630,name=AlphabloxServer,context-path=/AlphabloxServer)]: Servlet class com.alphablox.server.webapps.server.ServerStartup for Servlet AlphabloxServerStartup could not be loaded because the requested class was not found in the classpath d:\alphablox\analytics\system\AlphabloxPlatform\AlphabloxServer\WEB-INF\classes;d:\BEA\user_projects\domains\mydomain\.\myserver\.wlnotdelete\extract\myserver_AlphabloxPlatform_AlphabloxServer\jarfiles\WEB-INF\lib\taglibs-i18n379.jar.
java.lang.ClassNotFoundException: com.alphablox.server.webapps.server.ServerStartup.
 at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:799)
 at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3252)
 at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3197)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3174)
 at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:688)
 at weblogic.servlet.internal.WebService.preloadResources(WebService.java:483)
 at weblogic.servlet.internal.ServletInitService.resume(ServletInitService.java:30)
 at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
 at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
 at weblogic.Server.main(Server.java:32)

Problem: Error : “AlphabloxServerStartup” failed to preload on startup in Web application: “AlphabloxServer”.
Fix: During the installation of alphablox, you must change the Weblogic Server Start File. Change it from the default startManagedWebLogic.cmd to startWebLogic.cmd

If necessary, uninstall and reinstall Alphablox to reach this screen.


Make the change at the Configure Weblogic screen shown below :


prim12417:Error opening Project Management : “Exception EVirtualTableError in module PM.EXE at XXXXXXXX. TCVirtualTable.OptFieldIndexOf: VTable is not loaded – PROJECT.

$
0
0
Solution ID: prim12417
Error opening Project Management : "Exception EVirtualTableError in module PM.EXE at XXXXXXXX. TCVirtualTable.OptFieldIndexOf: VTable is not loaded – PROJECT.
Status: Reviewed
Version(s): 3.x, 4.0, 5.0, 6.0

Problem:

Error opening Project Manager after upgrading Oracle database:


Exception EVirtualTableError in module PM.EXE at XXXXXXXX.


TCVirtualTable.OptFieldIndexOf: VTable is not loaded – PROJECT.



Problem: Error opening Project Management after restoring SQL 2005 database.
Cause: Oracle:  This error will occur if selecting ‘admuser’ as the Privileged Database Username:

Fix: Go through upgrade again and:

Oracle:  Select ’PRIVUSER’ as the Privileged Database Username:


Fix: Use DBCONFIG to Administer Private Database Login.  “How to administer the private database logins username and password”

prim12472:Error: “Event Code UCVFR-2024-2″ or “Event Code CVRJC-2104-4″ when importing XER file

$
0
0
Solution ID: prim12472
Error: "Event Code UCVFR-2024-2" or "Event Code CVRJC-2104-4" when importing XER file
Status: Reviewed
Version(s): 3.5.1, 4.0, 4.1

Problem:

*****************************************************
*                EXCEPTION  REPORT                  *
*****************************************************
Date:          11-Aug-2004 05:15 PM


Executable:    PM.exe
Application:   Primavera Project Management
Event Code:    UCVFR-2024-2
Message:      
  Unique Constraint violated. Field rsrc_id is null.


Context:
  1: TfrmWizImport.wizImportFinish
  2: TfrmWizImport.RunImportWizard
  3: TfrmMain.actProjectsExecute
  4: TfrmMain.actFileImportExecute
  5: TCFormManager.SetToolbar
  6: TfrmLogin.FormCreate
  7:
  8:
  9:
  10:


Detail:
  Type:        Exception
  Object Type: TCUltraButton



Components
==========
ORI: ORI Win32 #
ORI/DB: PMDB,0350.0005.0004.0002
IMG: IMG Win32 #1000
DLL: (failed to query D:/PRIMAVERA ENTERPRISE 3.5.1/PROJECT MANAGER/../COMMON/BIN/DBCFGLIB.DLL)


System Info
===========
Username: Stuartw   Hostname: STUARTWILLIAMS
OS Version: Windows NT ver 5.1, build 2600, Service Pack 1 (Intel Pentium)
BDE Version: 500 (1901-5-11) OTHER
BDE Ini file: C:\Program Files\Borland\Common Files\BDE\IDAPI32.CFG

Problem: Error: “Event Code CVRJC-2104-4 with orphaned rows in the TASKRSRC table” when importing XER file
Cause: Resource references in tables such as TASKRSRC do not exist in the RSRC (Resource) table.
Fix: The resource assignments without a reference to the Resource table need to be removed from the XER file.  To find the problematic rows, open the XER file in notepad or Excel.  The error references the rsrc_id and checks all joins that use this id.  For example, below is an extract of TASKRSRC from the sample project AUTO.

%T TASKRSRC
%F taskrsrc_id  task_id  proj_id  work_flag  cost_qty_link_flag  role_id  acct_id  rsrc_id 
%R 7014           33521    278       Y                Y                            337       1179     3 


This row references rsrc_id 3.  Compare that to an extract of the table RSRC.


F rsrc_id parent_rsrc_id clndr_id
%R 1169   1209                 590  
%R 1170   1222                 597  
%R 1171   1208                 597  
%R 1172   1221                 597 


However, resource with an ID of 3 does not exist in the RSRC table.


So the row:


%T TASKRSRC
%F taskrsrc_id  task_id  proj_id  work_flag  cost_qty_link_flag  role_id  acct_id  rsrc_id 
%R 7014           33521    278       Y                Y                            337       1179     3 


Would need to be removed from the XER file.

prim12574:Exception occurred while attempting to connect to collaboration server

$
0
0
Solution ID: prim12574
Exception occurred while attempting to connect to collaboration server
Status: Reviewed
Version(s): 4.1

Problem: When logging into Primavision, all of the collaboration related windows give the following error message:

An error has occurred
Exception occurred while attempting to connect to collaboration server: server name

Problem: Within the log file there is a warning: WARN [Session-145] warn: exception=com.imanage.cms.exceptions.base.ProtocolNotSupportedException: Client protocol version is 1.9, Server protocol version is 1.7
Cause: The section in the instructions in the admin guide called “Applying the Collaboration update for compatibility with myPrimavera 4.1″ was not completed.
Fix:

Complete the section in the instructions in the admin guide called “Applying the Collaboration update for compatibility with myPrimavera 4.1″ described below.


1. Stop the iManage Process Manager (impm or impm.exe).


If you installed the Process Manager as a service on Windows, open the Services applet, locate the iManage PM service, and stop it.


NOTE: Stopping the iManage Process Manager will also stop the Indexer and CMS services.


2. If necessary, insert/mount the myPrimavera web applications CD.


3. Launch the installer according to the collaboration server operating system:


Windows: <CD>:\collab\31HFB5\instdata\windows\vm\svr31b5.exe


Solaris: <CD>/collab/31/instdata/solaris/vm/svr31b5.bin


4. Select the installation language and review the introduction.


5. Accept the license agreement.


6. When prompted for the existing installation directory, verify that the path listed is correct.  If not, click Choose… and select the base installation directory (this directory contains the “worksiteserver” directory).


7. When prompted for a backup directory, you can leave the default directory, type the path to a new directory, or click Choose… and select a backup directory.


8. When the installer is finished, click Done to quit.


9. Delete any temporary files (all files) in the \fxfer directory of your Worksite MP installation. The default location of this directory is


                      c:\worksitemp\<library_name>\fxfer\.


10. Restart the iManage Process Manager (or restart the service on Windows).  If CMS and Indexer are not set to Auto-Start, restart them from the Configuration Manager.


11. To verify the upgrade, launch the Configuration Manager, click Help, About…, and scroll to the bottom of the window.  The current version should be 3.1.6.2.5.


 

prim12935:Error: AWPCF-1727-7 when exporting an XER file

$
0
0
Solution ID: prim12935
Error: AWPCF-1727-7 when exporting an XER file
Status: Reviewed
Version(s): 4.0, 4.1, 5.0, 6.0, 6.1, 6.2, 6.2.1

Problem: When exporting to an XER file, the following error appears:

Error: AWPCF-1727-7


*****************************************************
*                EXCEPTION  REPORT                  *
*****************************************************
Date:          19-Aug-04 02:36 PM


Executable:    PM.exe

Event Code:    AWPCF-1727-7
Message:      
  TCAwk.WritePChar: failed to write 2 bytes to file:



 

Problem: *****************************************************
*                EXCEPTION  REPORT                  *
*****************************************************
Date:          27-Nov-07

Executable:    PM.exe
Application:   Primavera Project Management
Event Code:    AWPCF-2731-5
Message:      
  TCAwk.WritePChar: failed to write 6 bytes to file:

Context:
  1: TfrmWizExport.wizExportFinish
  2: TfrmWizExport.RunExportWizard
  3: TfrmMain.actHomeExecute
  4: TfrmEPS.mnuOpenProjectClick
  5: TfrmMain.actProjectsExecute
  6: TCFormManager.SetToolbar
  7: TfrmLogin.FormCreate

Problem: *****************************************************
*                EXCEPTION  REPORT               *
*****************************************************
Date:          11-Jan-08

Executable:    PM.exe
Application:   Primavera Project Management
Event Code:    AWPCF-1444-5


Message:      
  TCAwk.WritePChar: failed to write 5 bytes to file:

Fix: Ensure that the destination folder for the XER file has adequate disk space.

prim13002:Error : The James email server’s domain name is missing a top level domain specified in the property infra.kc.service.james.domainName

$
0
0
Solution ID: prim13002
Error : The James email server’s domain name is missing a top level domain specified in the property infra.kc.service.james.domainName
Status: Reviewed
Version(s): 8.01c, 8.6, 8.6 SP2, 8.6.0 SP1, 8.6.0 SP2a, 8.6.0 sp1a, 8.6.0 sp1b, 8.6.0a, 8.9, 8.9.0a, 8.9.0b, 8.9.0c, 8.9.0d, 8.9.0sp1, 9.0, 9.0.0a, 9.0SP1

Problem: Error : The James email server’s domain name is missing a top level domain specified in the property infra.kc.service.james.domainName
Problem: The Primavera Server fails to boot up and reports the following Java exception :

Aug-19-20:06:13-ERROR-S:-1:1 – “default” – C-111 : See exception message.
evolve.services.kc.exception.KcActionFailedException: The James email server’s domain name is missing a top level domain specified in the property Infra.kc.service.james.domainName.
 at evolve.services.kc.impl.KcServiceImpl.setupBaseData(KcServiceImpl.java:921)
 at evolve.pts.server.server.PtsServer.bootApplication(PtsServer.java:772)
 at evolve.pts.infra.server.AppServer.boot(AppServer.java:1434)
 at evolve.pts.infra.server.AppServer.run(AppServer.java:771)
 at java.lang.Thread.run(Thread.java:536)

Fix: This error occurs when implementing Worksite MP. 

When specifying the James server, use the fully qualified machine name.


1. To correct this locate  the AppServerConfig.properties file on the Primavera host.


              By default this file is located in Primavera\cfg\AppServerConfig.properties


2. Open with a text editor, such as Notepad


3. Locate the following section : Knowledge Collaboration parameters – START


4. Edit the following line : infra.kc.service.james.domainName=<fully qualified machine name>


For example : infra.kc.service.james.domainName=james.primavera.com

prim13751:CollabLibrary disappears after rebooting the Collaboration server

$
0
0
Solution ID: prim13751
CollabLibrary disappears after rebooting the Collaboration server
Status: Reviewed
Version(s): 4.0, 4.1

Problem: CollabLibrary disappears after rebooting the Collaboration server
Problem: Exception occurred while attempting to connect to collaboration server
Cause: The configuration was not saved during or after setup.
Fix: You will need to:

  • Recreate the Collaboration configuration

  • Re-add the existing Library

  • Re-add the authentication Library

  • Recreate the Indexer Service

prim14080:Error: “CmsConnection Pool Not Available” when the Collaboration components start in MyPrimavera

$
0
0
Solution ID: prim14080
Error: "CmsConnection Pool Not Available" when the Collaboration components start in MyPrimavera
Status: Reviewed
Version(s): 4.1

Problem: Error: “CmsConnection Pool Not Available” when the Collaboration components start in MyPrimavera
Problem:

Exception Error:


com.imanage.cms.exceptions.cmsconnection.CmsConnectionPoolNotAvailableException: CmsConnection pool is not available
at com.imanage.cms.fc.cmsconnection.CmsConnectionPool.getConnectionOnce(CmsConnectionPool.java:856)
at com.imanage.cms.fc.cmsconnection.CmsConnectionPool.getConnectionViaVirtualConnection(CmsConnectionPool.java:792)
at com.imanage.cms.fc.cmsconnection.UserConnection.getConnectionImpl(UserConnection.java:45)
at com.imanage.cms.fc.cmsconnection.CmsConnectionVirtual.getConnection(CmsConnectionVirtual.java:264)
at com.imanage.cms.fc.cmsconnection.CmsConnectionVirtual.validateConnection(CmsConnectionVirtual.java:97)
at com.imanage.cms.fc.cmsconnection.UserConnection.(UserConnection.java:36)
at com.imanage.cms.fc.cmsconnection.CmsConnectionPool.getConnection(CmsConnectionPool.java:743)
at com.imanage.cms.t2.jom.impl.PoolManager.getLoggedOnLibraryFor(PoolManager.java:212)
at com.imanage.cms.t2.jom.impl.DefaultReconnector.getLibraryByName(DefaultReconnector.java:28)
at com.imanage.cms.t2.jom.impl.LibrarySessionImpl.getLoggedOnTrustee(LibrarySessionImpl.java:70)
at com.imanage.cms.t2.jom.impl.SessionImpl.logonImpl(SessionImpl.java:87)
at com.imanage.cms.t2.jom.impl.LibrarySessionImpl.logon(LibrarySessionImpl.java:33)
at com.imanage.cms.api.workteam.impl.LibrarySessionImpl.logon(LibrarySessionImpl.java:39)
at com.primavera.oriweb.collaboration.cal.imanageImpl.WOMHelper.a(Unknown Source)
at com.primavera.oriweb.collaboration.cal.imanageImpl.WOMHelper.ensureIManageUserExists(Unknown Source)
at com.primavera.oriweb.collaboration.session.sessionFactory.ensureCollabUserExists(Unknown Source)
at com.primavera.oriweb.collaboration.initiation.engine.InitiationConnectionEngine.getWorksiteMPSession(Unknown Source)
at com.primavera.oriweb.collaboration.initiation.engine.InitiationEngine.a(Unknown Source)
at com.primavera.oriweb.collaboration.initiation.engine.InitiationEngine.getMyReviews(Unknown Source)
at com.primavera.oriweb.preshelpers.pm.ProjectInitiationBIC_data.loadData(Unknown Source)
at com.primavera.oriweb.preshelpers.AbstractRootServlet.doPresentation(Unknown Source)
at com.primavera.oriweb.preshelpers.AbstractRootServlet.doGet(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:536)

Fix: 1. Stop the iManage Service and run the service pack for the Collaboration server.  Browse the myPrimavera CD for the file svr31b5.exe in the following location: 

Windows: collab\31HFB5\InstData\Windows\VM
Solaris: collab\31HFB5\InstData\Solaris\VM for Solaris


2. Reboot the Collaboration server.


3. Verify the upgrade via Help, About in the Configuration Manager.  Scrolling to the bottom of the window should show the version to be 3.1.6.2.5


 

prim15232:Installation error: Run-Time 217 at 41c6806. The exception cannot continue.

$
0
0
Solution ID: prim15232
Installation error: Run-Time 217 at 41c6806. The exception cannot continue.
Status: Reviewed
Version(s): 3.x, 4.0, 4.1

Fact: Windows XP Home
Fact: Laptop
Problem: Installation error: Run-Time 217 at 41c6806. The exception cannot continue.

This happens when the CD is inserted or if you try to launch the Setup.exe. After that error message the the Setup never starts.

Fix: To resolve this installation error re-boot the laptop to Safe-Mode(F8) and the Setup will now start.

To access Safe-Mode, restart the laptop and upon the machine restarting, tap the F8 key until you are prompted for the Safe-Mode install options. To install using the Primavera CD please choose Safe-Mode with Networking.


prim15912:Floating point division by Zero when Print Previewing an Activity Layout.

$
0
0
Solution ID: prim15912
Floating point division by Zero when Print Previewing an Activity Layout.
Status: Reviewed
Version(s): 4.0, 4.1, 5.0



Problem: Floating point division by Zero when Print Previewing an Activity Layout.
Problem: When Printing a Layout in Project Management, the following error occurs:

*****************************************************
*                EXCEPTION  REPORT                  *
*****************************************************
Executable:    PM.exe
Application:   Primavera Project Management
Event Code:    FPDBZ-3853-D
Message:      
  Floating point division by zero



 

Cause: This error is generated because the Timescale Start and Timescale Finish in Page Setup are identical.

Example:


Fix: Set the Timescale Finish to a date that is greater than the Timescale Start
Fix: The layout is corrupt.  Try a different layout.

prim16528:Error: “Event Code GSQLE-2504-4: ORA-01401: inserted value too large for column” when importing MPP project into an Oracle database

$
0
0
Solution ID: prim16528
Error: "Event Code GSQLE-2504-4: ORA-01401: inserted value too large for column" when importing MPP project into an Oracle database
Status: Reviewed
Version(s): 4.1, 5.0



Fact: Importing the same MPP project into an SQL database is successful and without any errors
Problem: An XER file originating from a SQL database gives the error, “Event Code: PRMDB-1832-E” when trying to import into an Oracle database.
Problem: Error: “Event Code GSQLE-2504-4: ORA-01401: inserted value too large for column” when importing MPP project into an Oracle database
Problem: The import stops and the following error appears:

*****************************************************


*EXCEPTIONREPORT*


*****************************************************


 


Executable:PM.exe


Application:Primavera Project Management


Event Code:GSQLE-2504-4


Message:


General SQL error.


ORA-01401: inserted value too large for column

Cause: Field(s) in the project may exist with too many characters for the corresponding field in the Oracle database.  Some fields are too long to be stored in the Oracle database, but can be stored in SQL.  For example, Activity Names have a 54 character limit in Oracle, but more in SQL.
Fix: Check and shorten the length of any long fields that exist in the database and reimport.

prim16911:Exception error when creating a calendar

$
0
0
Solution ID: prim16911
Exception error when creating a calendar
Status: Reviewed
Version(s): 3.x, 4.0, 4.1, 5.0



Problem:

When creating any type of calendar, the following error occurs:


 *****************************************************


* EXCEPTION REPORT *


*****************************************************


Date: 27-Oct-04


Executable: PM.exe


Application: Primavera Project Management


Event Code: VTFRN-0683-B


Message:


TCVirtualTable.FindRowNewIndex: Adding row


(CALENDAR – Calendar: 4078 – ZOU YANPING


.) conflicts with existing unique key: (XXXX).


Context:


1: TCArcturusAssignMgr.AssignAndAddNewRowToVDBE


2: TCArcturusAssignMgr.InsertClndrRow


3: TfrmBaseCalendar.cmdAddClick


4: TfrmMain.actConfigureCalendarsExecute


5: TfrmMain.actConfigureResourcesExecute


6: TfrmMain.actReportsReportsExecute


7: TfrmMain.actProjectsExecute


8:


9:


10:


Detail:


Type: Exception


Object Type: TCUltraButton


Components


==========


ORI: ORI Win32 #


ORI/DB: PMDB,0410.0001.0001.0002


IMG: IMG Win32 #1000

Cause: The next calendar incremental number in the NEXTKEY table is lower than the highest calendar ID in the calendar table.
Fix:

Run the following queries against the database:


select max(clndr_id) from calendar;


select key_seq_num from nextkey where key_name=’calendar_clndr_id’;


You will see that the first query returns a number that is higher than the second query. Run the following query to correct this.


NOTE: Replace XXXX to be a higher value than the first query returned.


update nextkey set key_seq_num=XXXX where key_name=’calendar_clndr_id’;

prim17241:Exception. Unknown software exception 0x0eedfade occurred in the application at location …

$
0
0
Solution ID: prim17241
Exception. Unknown software exception 0x0eedfade occurred in the application at location …
Status: Reviewed
Version(s): 4.1, 5.0, 6.0, 6.1



Problem: When attempting to install the software, before the splash screen, the customer sees the following error message:

“Exception. Unknown software exception 0x0eedfade occurred in the application at location …”


 This also occurs with Primavera Contractor installation.

Cause: The computer displaying this behavior had a network printer defined and mapped as default printer.  If the network printer was turned off, setup crashed immediately.
Fix: Select a default printer which is powered on and working. 

Note: Can also set Microsoft Fax as the default printer.

Fix:

May indicate a network problem (may be a flaky connection). 



Check event viewer for any errors. 


Have user reboot and re-launch PM.

prim17416:”error” creating or deleting projects

$
0
0
Solution ID: prim17416
"error" creating or deleting projects
Status: Reviewed
Version(s): 9.1



Problem: Create or Delete project
Problem: “error”
Problem: server.log records java exception:

ERROR – DatabaseMgrSessionBean.executeUpdate Exception while executeUpdate :
com.sybase.jdbc2.jdbc.SybSQLException: ASA Error -143: Column ‘copy_cf_between_phases’ not found

Change: Applied service pack to 9.1
Cause: Service pack was applied to web server but not databases.
Fix: Apply service pack (TRG scripts) to databases.
Viewing all 111 articles
Browse latest View live