Quantcast
Channel: Primavera Online Interaction » Event Code
Viewing all 60 articles
Browse latest View live
↧

prim20525:Error: “VTFIO-2909-5″ when deleting users from Methodology Management

August 29, 2013, 8:58 am
$
0
0
Solution ID: prim20525
Error: "VTFIO-2909-5" when deleting users from Methodology Management
Status: Reviewed
Version(s): 4.0, 4.1



Problem: Error: “VTFIO-2909-5″ when deleting users from Methodology Management


*****************************************************
*                EXCEPTION  REPORT                  *
*****************************************************
Date:          15-Feb-05


Executable:    MM.exe
Application:   Primavera Methodology Management
Event Code:    VTFIO-2909-5
Message:      
  TCVirtualTable.FieldIndexOf: Could not find field
  concurrent_user in vtable USERENG


Context:
  1: TCArcturusAssignMgr.ConfirmDeleteUsers
  2: TfrmOriUsers.cmdDeleteClick
  3: TfrmOriUsers.FormCreate
  4: TfrmOriUsers.DoPopupUsers
  5: TfrmMain.mnuAdminUsersClick
  6: TfrmMain.ResizeDirectoryToolbar
  7: TfrmMain.splitMainResize
  8:
  9:
  10:


Detail:
  Type:        EVirtualTableError
  Object Type: TCUltraButton
Cause: Users with concurrent user licenses for Methodology Management
Fix: Login to SQL plus as privuser and issue the following Query.

Update usereng set named_user_flag=’Y’
↧
Search

prim20715:Claim Digger – Unable to load the list of database instances – DCEB4AC1

August 31, 2013, 4:00 pm
$
0
0
Solution ID: prim20715
Claim Digger – Unable to load the list of database instances – DCEB4AC1
Status: Reviewed
Version(s): 4.0, 4.1, 5.0



Problem: Claim Digger -  Failed connect to Oracle database
Fact: All PMDB tables in Oracle is owned by ADMUSER.
Fact: Oracle database instance
Fact: Claim Digger or Schedule Analyzer
Fact: SQL Server connection uses “privuser”
Problem: Event Code DCEB4AC1 when launching the Claim Digger application.
Problem: Event Code DCEB4AC1
Problem: com.primavera.ServerException: Unable to load the list of database instances.  Verify that the name attribute of the “BootStrap.Configurations.BRE” element in BREBootStrap.xml lists a valid configuration.  If not, use the Database Configuration Setup utility or Administrator application to add a new configuration.

Click “More” then the following error screen will be displayed.


 


com.primavera.integration.server.ServerFacade.getDBInstances(ServerFacade.java)


com.primavera.integration.client.LocalSession.getDatabaseInstances(LocalSession.java)


sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)


sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)


java.lang.reflect.Method.invoke(Unknown Source)


com.primavera.integration.client.Session.getDatabaseInstances(Session.java)


com.primavera.integration.app.schedcomp.gui.x.<init>(LoginDlg.java)


com.primavera.integration.app.schedcomp.gui.CompareProjectsDlg.main(CompareProjectsDlg.java)
Fix: Modify the connection as follows:-

User name = admuser


Password=admuser(This is the default password; if does not work. Please check with your Oracle DBA).
Fix: How to change Claim Digger/Schedule Analyzer Database configuration? 
↧
↧

prim20783:AVAA0-2254-B event code while exporting a project using an Interbase database.

September 1, 2013, 11:11 am
$
0
0
Solution ID: prim20783
AVAA0-2254-B event code while exporting a project using an Interbase database.
Status: Reviewed
Version(s): 3.5.1, 4.0, 4.1



Problem:

AVAA0-2254-B event code while exporting a project using an Interbase database.
Problem: AVAAO errors
Problem: AVAA errors
Fix: Run the following statement from ISQL:

ALTER TABLE TASK
DROP CONSTRAINT FK_TASK_PROJECT;


DROP INDEX NDX_TASK_1;


ALTER TABLE TASK
ADD CONSTRAINT FK_TASK_PROJECT
FOREIGN KEY (PROJ_ID) REFERENCES PROJECT (PROJ_ID);


CREATE INDEX NDX_TASK_1
ON TASK ( PROJ_ID );
↧

prim20901:Primavera Contractor version 4.1 Patch to correct NSIS errors due to Microsoft Security Update that was released on February 8, 2005

September 2, 2013, 4:56 pm
$
0
0
Solution ID: prim20901
Primavera Contractor version 4.1 Patch to correct NSIS errors due to Microsoft Security Update that was released on February 8, 2005
Status: Reviewed
Version(s): 4.1



Problem: Primavera Contractor version 4.1 Patch to correct NSIS errors due to Microsoft Security Update that was released on February 8, 2005
Problem: “Event code NSIS-2739-6″ when launching application.
Fix:

Please follow the instructions below to correct all problems caused by the Microsoft Security Update that was released on February 8, 2005: Download the attached Readme file for installation considerations and instructions.


Readme file


ftp://suppsaleserver.primavera.com/servicepacks/Contractor/Contractor_dhtml_Patch.zip


 


To download the latest Primavera Contractor version 4.1 Service Pack, click the following link:


Solution ID prim30003: Primavera Contractor version 4.1 Service Pack 4
↧

prim20956:Error: “Event code AVAA0-3921-5″ after opening a layout

September 3, 2013, 9:12 am
$
0
0
Solution ID: prim20956
Error: "Event code AVAA0-3921-5" after opening a layout
Status: Reviewed
Version(s): 4.0, 4.1, 5.0, 6.0, 6.1, 6.2, 6.2.1, 7.0



Problem: Error:  “Event code AVAA0-3921-5″ after opening a layout
Problem: Error:  ”Event code EECD-0641-3″ after opening a layout
Problem:
Fix: Delete this layout and recreate to correct the problem.
↧
↧

prim20967:How to control the size of the Primavera Project Management (PMDB) log file from increasing in size, disproportionately large, when using MS SQL server

September 3, 2013, 10:53 am
$
0
0
Solution ID: prim20967
How to control the size of the Primavera Project Management (PMDB) log file from increasing in size, disproportionately large, when using MS SQL server
Status: Reviewed
Version(s): 2.x, 3.x, 4.0, 4.1, 5.0



Problem: How to control the size of the Primavera Project Management (PMDB) log file from increasing in size, disproportionately large, when using MS SQL server 2005 ?
Problem: How to prevent the size of the Project Management (PMDB) log file from increasing too dramatically when using MS SQL server ?
Fact: MS SQL Server
Problem: MSSQL Log file is very large
Problem: Event Code:  GSQLE-3126-2 when logging into Project Management
Problem: General SQL error: log file for Database is full when logging into Project Management
Problem: PMDB Log File is too big
Problem: recovery model or recovery mode
Problem: Log file is growing too quickly
Problem: Database log file is much bigger than the data file
Cause: If the database log file is significantly bigger than the database data file, or the log file is growing disproportionately faster than the data file, it may be that the ‘recovery model’ specified on the database is set to ‘Full’.
Fix:

By default the ‘Recovery model’ value should be set to ‘Simple’.



  1. Launch MS SQL Server 2005 Management Studio.

  2. Right-click on the database and select ‘properties’.

  3. Select the ‘Options’ page.

  4. Select ‘Simple’ from the ‘Recovery model’ drop-down list:

         



  1. Click ’OK’.

  2. Close the Management Studio.

  3. Go to start, (Settings), Control Panel, Administrative Tools, Services

  4. Stop and Restart SQL SERVER to insure changes will take effect.

         

Fix: By default the ‘recovery model’ value should be set to ‘simple’.

  1. Launch MS SQL Server 2000, Enterprise Manager.

  2. Right-click on the database and select ‘properties’.

  3. Select the ‘Options’ tab.

  4. Select ‘Simple’ from the ‘Recovery model’ drop-down list:


     

  5. Hit ‘OK’.

  6. Close Enterprise Manager.

  7. Launch Settings, Control Panel, Administrative Tools, Services

  8. Stop and Restart MSSQLSERVER to verify settings will take effect.

        

Note:  It is acceptable for the Database Administrator to change this to ‘full’ recovery, as long as a plan to deal with the expanding log file is also implemented.


For information on how to shrink the LOG file, see:


Solution ID: 200363104250 ”How to shrink the SQL log file for Project Management?”
↧

prim21129:Application error AVAA0-0252-6 when printing to a HP 1055CM plotter

September 5, 2013, 3:49 pm
$
0
0
Solution ID: prim21129
Application error AVAA0-0252-6 when printing to a HP 1055CM plotter
Status: Reviewed
Version(s): 4.0, 4.1



Problem:

Receive an Application error when printing to a HP 1055CM plotter:


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





* EXCEPTION REPORT *


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


Executable: PM.exe


Application: Primavera Project Management


Event Code: AVAA0-0252-6


Message:


Access violation at address 005BA9E6 in module ‘PM.exe’.


Read of address 00000004


Context:


1: TCFormManager.SetToolbar


2: TfrmLogin.FormCreate


3:


4:


5:


6:


7:


8:


9:


10:


Detail:


Type: EAccessViolation


Object Type: TCVirtualQueryGantt
Problem: AVAA0 error when trying to print to an HP LaserJet 5550HDN printer after changing the Timescale to Day/Week.
Problem: AVAA0 errors
Problem: AVAAO errors
Problem: AVAA errors
Cause: This error is caused by a corrupted layout.
Fix: Create a new layout.
↧

prim21184:Event code AVAA0-0240-4 or AVAA0-1788-0 when assigning resource by role

September 7, 2013, 4:55 pm
$
0
0
Solution ID: prim21184
Event code AVAA0-0240-4 or AVAA0-1788-0 when assigning resource by role
Status: Reviewed
Version(s): 4.0, 4.1, 5.0, 6.0



Problem:

Event code AVAA0-0240-4 or AVAA0-1788-0 when assigning resource by role.


Steps to duplicate issue:



  1. Display Resource Profile

  2. Applying the “Current Project’s Resources” filter

  3. Select to display “Open project Only”

  4. Check “Display Activities for the select  ”Resources” option

  5. Clicking “Assign Rsrc by Role” from the command bar
Problem: AVAAO errors
Problem: AVAA errors
Problem: Application Event Code: AVAA0-3049-4
Problem: Application Event Code AVAA0-0352-1
Problem: Application Event Code: AVAA0-1006-F
Problem: Application Event Code: AVAA0-0587-A
Fix: This known problem in Project Manager / Project Management will be corrected in a future release.
↧
Search

prim21279:Claim Digger hangs when comparing Relationships.

September 8, 2013, 1:41 pm
$
0
0
Solution ID: prim21279
Claim Digger hangs when comparing Relationships.
Status: Reviewed
Version(s): 5.0, 6.0



Problem: Claim Digger hangs when comparing Relationships.
Problem: Claim Digger and Memory Settings
Problem: Schedule Comparison and Memory Settings
Problem: Claim Digger Out of Memory
Problem: Schedule Comparison Out of Memory
Problem: java heap size registry entry for claim digger, update baselines, schedule comparison
Problem: Event code 80C6CE70
Problem: [Class=java.lang.OutOfMemoryError] Java heap space.
Problem: Claim Digger never gets past 80% when comparing Relationships.
Fix: Specify the initial heap size in the registry:

Note: Always backup the registry before making any edits in case the wrong entries are modified/deleted.  By exporting the registry first, you will have a back up to restore.  Open the Registry by going to Start, Run and typing “REGEDIT”.  Go to File, Export… and select a filename and location.



  1. Go to start, run and type: regedit.  Click ok

  2. Browse to HKEY_LOCAL_MACHINE\Software\Primavera\Shared\External Applications\Claim Digger

  3. Right-click on parameters and choose modify

  4. Add -Xms256m -Xmx256m to the beginning of the string.  Be sure to include a space after -Xmx256m.

      


     5.  Click ok and re-run the Claim Digger Report.
↧
↧

prim21568:Error: “Event Code: LIOOB-3801-6: List index out of bounds” when replacing resource assignments

September 12, 2013, 12:29 pm
$
0
0
Solution ID: prim21568
Error: "Event Code: LIOOB-3801-6: List index out of bounds" when replacing resource assignments
Status: Reviewed
Version(s): 4.0, 4.1, 5.0, 6.0, 6.1, 6.2, 6.2.1, 7.0



Problem: Error: “Event Code: LIOOB-3801-6: List index out of bounds” when replacing resource assignments
Problem: Error: “Event Code: LIOOB-2102-5: List index out of bounds (14) when replacing resource assignments
Cause: Replacing assignments from one resource to another in activity view.
Fix: This known problem in Project Management will be corrected in a future release.
↧

prim21681:Application Event GSQLE-1009-D when importing XER in Interbase.

September 13, 2013, 7:52 am
$
0
0
Solution ID: prim21681
Application Event GSQLE-1009-D when importing XER in Interbase.
Status: Reviewed
Version(s): 4.0, 4.1



Problem: Application Event GSQLE-1009-D when importing XER in Interbase.

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


*EXCEPTIONREPORT*


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


Date:21-Mar-05


 


Executable:PM.exe


Application:Primavera Project Management


Event Code:GSQLE-1009-D


Message:


General SQL error.


internal error


 


Context:


1: TfrmWizImport.wizImportFinish


2: TfrmWizImport.wizImportBeforeShowPage


3: TfrmWizImport.RunImportWizard


4: TfrmMain.actHomeExecute


5: TfrmMain.actFileImportExecute


6: TfrmMain.actProjectsExecute


7: TCFormManager.SetToolbar


8:


9:


10:


 


Detail:


Type:EDBEngineError


Object Type:TCUltraButton


 


Database Error:


1: General SQL error.


Category:51


Error Code:13059


Sub Error Code :3


Server Error Code: 0


 


2: internal error


 


Category:51


Error Code:13059


Sub Error Code :3


Server Error Code: -303


 


 


Components


==========


ORI: ORI Win32 #


ORI/DB: PMDB,0410.0001.0001.0002


IMG: IMG Win32 #1000


 


System Info


===========


Username: DominicHostname: DGILLESPIEXP


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
Cause: Documents section of the XER having documents dealing with Collaboration.
Fix: This known problem in Project Management / Project Manager will be corrected in a future release.

Workaround:


Remove the Documents section of the XER that deals with Collaboration, save the XER and then the XER will import in to Interbase.
↧

prim21717:Troubleshooting AVAA Event Code errors

September 13, 2013, 2:06 pm
$
0
0
Solution ID: prim21717
Troubleshooting AVAA Event Code errors
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: Troubleshooting AVAA0 Event Code errors
Problem: Troubleshooting AVAA Event Code errors
Problem: Event Code: AVAA0-1352-3
Message: Access violation at address 005975EB in module ‘PM.exe’.  Read of address 09599000
Problem: AVAAO errors
Cause: AVAA Errors, or “Access Violation” errors are generated by the operating system and they happen when an application tries to access an area of memory that is not designated for that application’s use.

If an application were able to write outside of its assigned storage area, it could overwrite another applications’, or even Windows’, instructions or data.  Rather than allow this (which could result in a loss of data or in a more serious crash), Windows generates an error.  “Access Violation” errors are the same things as “Invalid Page Faults” and “General Protection Faults” and all three are simply the symptoms of a computer ‘crash’.


Access Violation errors are rarely an indication of a major problem with the software and the difficulty in tracing the source of Access Violation errors lies in the fact that they are generic.  There isn’t a common way to fix all Access Violation errors because there are so many different (and unpredictable) situations which can cause them.
Fix: See also, Access Violation errors when accessing the Activities view in Project Management 

AVAA errors have also been observed to be a symptom of corrupt layouts, particularly if they occur mostly while working with layouts, e.g.



  • Opening or saving layouts

  • Adding or removing columns

  • Changing bar definitions

  • Applying filters

A corrupt layout may also be the cause of AVAA errors when opening the software (for example, if the user has disabled the welcome screen and set the software up to open the last project – this will also open the most recently used layout).


It is not possible to ‘fix’ a corrupt layout and if it is suspected that a layout has become corrupt, a new, clean layout should be created.  Because corruption can potentially be copied across if a corrupt layout is saved to create a new layout, it is best to open a layout which is rarely or never used and save this as the new layout.


For further information about how data can become corrupt, please see the following knowledgebase solution:


prim29241 ”Why data may become corrupted”
Fix: Possible fixes for AVAA0 errors include:

Client PC:


1. Closing down other programs or processes to free up resources for Project Manager.  Click Ctrl, Alt + Delete and choose Task Manager, Performance.  Compare Physical Total Memory to Available Memory.  AVAA0 errors may occur when less than 25% of total memory is available.



2. Log completely out of Project Manager/Project Management and then log back in.  Try running the process again.


3. Reboot the computer.


Database:


1. Restore a previous clean Backup of the Project or Database to determine if the Error still occurs. The problem could be data integrity related.
↧

prim22299:Error: “Event Code AVAA0-0974-F” when modifying a filter

October 3, 2013, 8:02 am
$
0
0
Solution ID: prim22299
Error: "Event Code AVAA0-0974-F" when modifying a filter
Status: Reviewed
Version(s): 4.0, 4.1, 5.0, 6.0, 6.1, 6.2, 6.2.1, 7.0



Problem: Error: “Event Code AVAA0-0974-F” when modifying a filter
Problem: AVAAO errors
Problem: AVAA errors
Fix:

  1. Replace the current layout with the Classic WBS Layout.  If this corrects the issue, delete the offending layout and recreate it.

  2. If the error still persists after switching layouts, create a new user account and recreate the filter.
↧
↧

prim22467:Event Code Error: ‘CVRJC-3802-1′ when importing an XER

October 6, 2013, 10:49 am
$
0
0
Solution ID: prim22467
Event Code Error: ‘CVRJC-3802-1′ when importing an XER
Status: Reviewed
Version(s): 4.0, 4.1, 5.0



Problem: “Event Code Error: ‘CVRJC-3802-1′ when importing an XER”
Problem:

Event Code Error: ‘CVRJC-3802-1: TCCustomVirtualRow.getJoinedColItems: UDFVALUE row has blank fk_id’ when importing an XER
Cause: This is caused by orphaned records in the database being extracted into the XER file during export, then the error is received when importing an XER file that contains these orphaned records.  Orphaned records can happen for a variety of reasons. 

Note: 
- One known cause is if multiple users are in a project and user 1 runs a global change or fill down for a user defined field and user 2 is deleting an activity at the same time.  The activity is successfully deleted but leaves an orphaned UDF value. (Note:  Primavera recommends running these type of changes in “Exclusive mode”. )
- This particular cause  of orphaned records has been fixed in Project Management 5.0 SP1 and 4.1 SP4.  Applying these releases will not fix pre-existing orphaned records in databases or XER files but will prevent new orphaned records from being created by this scenario.  Therefore, the error will continue to happen if the XER being imported contains orphaned UDFs. (see the delete_orphaned_UDFVALUE scripts below for database cleanup of orphaned records.)

** Other scenarios that cause orphaned records may still exist. **

Fix: This known problem in Project Management has been corrected in version 5.0 Service Pack 2.  

To download the latest Service Pack, see:


Solution ID: prim29265 揥hat are the latest Service Packs for Primavera version 5.0??/A>
Fix: Workaround:

Run database queries/scripts on the source database (the database where the XER was exported from).  See steps below.


PROJECT MANAGEMENT FIX:


Run the appropriate script below on the database that the XER was exported from
     – For Microsoft SQL Server, run the script as PRIVUSER
     – For Oracle , run the script as ADMUSER
     - For MSDE Primavera 5.0 Standalone installation, save the appropriate script to the root of the C:\ drive and run the following from a DOS command prompt:
       (Start > Run > type ‘cmd’ and click OK):  osql -U sa -P prima -S localhost\primavera -d pmdb$primavera -i c:\delete_orphaned_UDFVALUE_##.sql

CONTRACTOR FIX:

      - For Contractor 5.0, save the delete_orphaned_UDFVALUE_50 script to the root of the C:\ drive and run this from the DOS command prompt:
       (Start > Run > type ‘cmd’ and click OK):  osql -U sa -P prima -S localhost\primavera -d PCONDB -i c:\delete_orphaned_UDFVALUE_50.sql


Note:  RUN THIS SCRIPT ON A BACKUP OF THE DATABASE FIRST!


For Project Management 4.1 databases:  delete_orphaned_UDFVALUE_41.sql


For Project Management 5.0 databases: delete_orphaned_UDFVALUE_50.sql


 If the script seems to hang at the section where the script attempts to delete UDF data which has no corresponding entry in the TASK table, please replace it for:


delete from udfvalue a


where exists (

select 1 from udftype b


where b.udf_type_id = a.udf_type_id


and b.table_name = ‘TASK’


)

and not exists (

select 1 from task c


where c.task_id = a.fk_id


);
Fix:

Workaround 2:


If the source database is not accessible, the XER file can be fixed.  Please see:


 PRIM16871: Receiving Event Code:  CVRJC-3802-1 while importing a project with orphaned rows in UDFVALUE table


 
Fix: Workaround 3:

If a 5.0 SP2 or higher implementation is available (both client application and database patched) the project may be imported and then re-exported to XER format to remove the Orphaned Records causing this problem.  It may then be imported into a pre SP2 database.
↧

prim22485:Event code RECFT – 1417 – 8 when leveling resources

October 6, 2013, 2:57 pm
$
0
0
Solution ID: prim22485
Event code RECFT – 1417 – 8 when leveling resources
Status: Reviewed
Version(s): 4.0, 4.1, 5.0



Problem: When leveling resources receive an event code: RECFT-1417-8
Problem:
Cause: This error will occur when there are completed resources assignments with negative units/time.
Cause: This has occurred in the past when project data has been imported in from other project management software.
Fix: Running project integrity should highlight the guilty assignments by giving the following error: Check Project for: Planned Start Date > earliest activity Actual Start Date
>>>Warnings:
 Project:  ******** - Not Fixed: Please examine and correct the data manually.  It will name the activity (*****) with the negative resource and once they are deleted and reassigned, the levelling should run without error.
↧
Search

prim22594:Event Code Error: “GSQLE-1534-A”

October 8, 2013, 5:02 pm
$
0
0
Solution ID: prim22594
Event Code Error: "GSQLE-1534-A"
Status: Reviewed
Version(s): 3.5, 3.5.01, 3.5.1, 3.5.2, 4.0, 4.1, 5.0, 6.0, 6.1, 6.2, 6.2.1, 7.0



Problem: Event Code Error: “GSQLE-1534-A” when working in Project Manager / Management connected to an Oracle database


*****************************************************
*                EXCEPTION  REPORT                  *
*****************************************************
Date:          04/15/2005


Executable:    PM.exe
Application:   Primavera Project Management
Event Code:    VTDCF-1615-F
Message:      
  TCVirtualTable.DoCalcField:
  PROJECT.other_user_exclusive: General SQL error.
  ORA-00028: your session has been killed


Context:
  1: TfrmEPS.FormReloadData
  2: TfrmMain.actProjectsExecute
  3: TfrmMain.actProjectActivitiesExecute
  4: TCFormManager.SetToolbar
  5: TfrmLogin.FormCreate
  6:
  7:
  8:
  9:
  10:


Detail:
  Type:        Exception
  Object Type: TCUltraButton



Components
==========
ORI: ORI Win32 #
ORI/DB: PMDB,0410.0001.0001.0002
IMG: IMG Win32 #1000


System Info
===========
Username: Jerry   Hostname: JERRYWXP
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: This error can be caused by terminating an Oracle session at the database level.  This can be done from the Oracle Enterprise Manager Console.
Fix: Close Project Manager / Management, then re-launch and log in again.  If you cannot log in contact your DBA.
↧

prim22869:Event code FVRVE-3317-2 or GSQLE-4064-1 importing MPX file

October 22, 2013, 12:26 pm
$
0
0
Solution ID: prim22869
Event code FVRVE-3317-2 or GSQLE-4064-1 importing MPX file
Status: Reviewed
Version(s): 4.0, 4.1



Problem: Event code FVRVE-3317-2 or GSQLE-4064-1 importing MPX file
Problem: PRED_TASK_ID value “*** null ***” importing MPX file
Cause: In Microsoft Project, there were relationships going to/from the summary tasks.  When those tasks are imported as WBS, the relationships on the normal tasks are left with null predecessor information.
Fix: During import wizard, modify the import template and on the WBS tab, select to import summary tasks as activities instead.
↧
↧

prim23074:Event Code: VTDCF-2269-5 TASKRSRC.live_cost_per_qty when importing an xer file

October 27, 2013, 12:48 pm
$
0
0
Solution ID: prim23074
Event Code: VTDCF-2269-5 TASKRSRC.live_cost_per_qty when importing an xer file
Status: Reviewed
Version(s): 4.0, 4.1, 5.0, 6.0, 6.1, 6.2, 6.2.1, 7.0



Problem: Importing an XER file and receive Event Code: VTDCF-2269-5

TCVirtualTable.DoCalcField: TASKRSRC.live_cost_per_qty:
  TCOrionRateObj.GetShiftPeriodInfo: ShiftPeriodRow not
  found


 
Cause:

Cause 1:


SHIFTPER table content in the XER file.


Shift_start_hr_num is not a whole number.
Cause: Cause 2:

A record in the RSRCRATE table is referencing a shift_period_id that is not defined in the SHIFTPER table.
Fix:

Solution 1:


Check the shift calendars to correct, and/or delete any value that is not a whole number, this should resolve the problem. 


Once the shift calendar is corrected, a new XER file will need to be created.

Fix: Solution 2:

Either delete the orphaned shift_period_id record in the RSRCRATE table or change the orphaned shift_period_id to one that is defined in the SHIFTPER table.
↧

prim23199:Event Code LCWSQ-3428-9 Lost Connection With SQL server

October 29, 2013, 4:44 am
$
0
0
Solution ID: prim23199
Event Code LCWSQ-3428-9

Lost Connection With SQL server
Status: Reviewed
Version(s): 4.0, 4.1



Problem: Event Code LCWSQ-3428-9

Lost Connection With SQL server
Fix: This event code is normally returned when the connection to the server has been lost.  Check with the Network Administrators to determine if there have been connection problems during the time that the event code was returned.
↧

prim23362:Event Code: GSQLE-0147-2 when importing Microsoft Project data

October 30, 2013, 6:22 am
$
0
0
Solution ID: prim23362
Event Code: GSQLE-0147-2 when importing Microsoft Project data
Status: Reviewed
Version(s): 4.0, 4.1



Problem: Received the following errors when importing mpp file

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


*EXCEPTIONREPORT*


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


Date:12-May-2005 11:51


Executable:PM.exe


Application:Primavera Project Management


Event Code:GSQLE-0147-2


Message:


General SQL error.


Line 1: Incorrect syntax near ‘CA_Rsrc’.


Unclosed quotation mark before the character string ‘)


‘.


Context:


1: TfrmWizImport.RunImportWizard


2: TfrmMain.actHomeExecute


3: TfrmMain.actFileImportExecute


4: TCFormManager.SetToolbar


5: TfrmLogin.FormCreate


6:


7:


8:


9:


10:


Detail:


Type:EDBEngineError


Object Type: TCUltraButton


 
Problem: The  error screen capture as following:-

 
Fix: The Microsoft Project file is corrupted.  Open the Microsoft Project file in Microsoft Project .   Remove the resources in the resource dictionary; save it.   Then the Microsoft Project data can be imported to Project Management module.
↧
Viewing all 60 articles
Browse latest View live
Search