Cannot Import eAM (EBS) XML and MSP 2013 XML into P6 15.2.0.0 SQLite Standalone Version.

(Doc ID 2131764.1)

Last updated on APRIL 17, 2017

Applies to:

Primavera P6 Enterprise Project Portfolio Management - Version 15.2.0.0 and later
Primavera P6 Professional Project Management - Version 15.2.0.0 and later
Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 15.2.0.0 and later
Information in this document applies to any platform.

Symptoms

When importing into P6 using SQLite Standalone version with a) P6 XML file exported by Enterprise Asset Management (eAM) or b) MS Project 2013 XML exported file by MS Project 2013 the import run is unsuccessful and the error message "Process did not complete successfully...  See log file.." displays on the completed run dialog.

 

Steps:

1. From P6, select File > Import
2. Select Primavera XML option
3. Select Primavera XML file that was generated from eAM module of EBS
4. Result: At the end of importing the message "Process did not complete successfully...  See log file.." is displayed.

 

Import Run Log File Results:

Microsoft.Practices.Prism.Modularity.ModuleInitializeException: An exception occurred while initializing module 'CommandLineModule'.
    - The exception message was: Object reference not set to an instance of an object.
    - The Assembly that the module was trying to be loaded from was:Primavera.Mercury.CommandLineModule, Version=15.2.2.16346, Culture=neutral, PublicKeyToken=null
    Check the InnerException property of the exception for more information. If the exception occurred while creating an object in a DI container, you can exception.GetRootException() to help locate the root cause of the problem.
   ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at Primavera.Mercury.Importer.ImportCleaner.CleanupActivities(EntityContext sourceContext)
   at Primavera.Mercury.Importer.ImportCleaner.CleanSourceContext(EntityContext sourceContext, IVenusDataServiceContext targetContext, ILoggerFacade logger, ImportProjectSettings importProjectSettings, Dictionary`2 initialKeyDictionary)
   at Primavera.Mercury.CommandLineModule.ExecuteImportExport.DoImport()
   at Microsoft.Practices.Prism.Modularity.ModuleInitializer.Initialize(ModuleInfo moduleInfo)
   --- End of inner exception stack trace ---
Failed to load type for module CommandLineModule.
Error was: An exception occurred while initializing module 'CommandLineModule'.
    - The exception message was: Object reference not set to an instance of an object.
    - The Assembly that the module was trying to be loaded from was:Primavera.Mercury.CommandLineModule, Version=15.2.2.16346, Culture=neutral, PublicKeyToken=null
    Check the InnerException property of the exception for more information. If the exception occurred while creating an object in a DI container, you can exception.GetRootException() to help locate the root cause of the problem.

 

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms