P6 Professional XML Import Results In "Prism.Modularity.ModuleInitializeException: An exception occurred while initializing module 'CommandLineModule'" Error
(Doc ID 2493210.1)
Last updated on APRIL 07, 2023
Applies to:
Primavera P6 Professional Project Management - Version 18.8.1.0 and laterInformation in this document applies to any platform.
Symptoms
When attempting to import a large XML file, via P6 Professional, the following error occurs:
ERROR
Prism.Modularity.ModuleInitializeException: An exception occurred while initializing module 'CommandLineModule'.
- The exception message was: One or more errors occurred.
- The Assembly that the module was trying to be loaded from was:Primavera.Mercury.CommandLineModule, Version=18.8.0.29254, 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.AggregateException: One or more errors occurred. ---> System.InvalidOperationException: This SqlTransaction has completed; it is no longer usable.
at System.Data.SqlClient.SqlTransaction.ZombieCheck()
at System.Data.SqlClient.SqlTransaction.Rollback()
at Primavera.Venus.Data.DbStore.BaseSqlHydrator.RollbackTransaction(CommandSource cmdSource)
at Primavera.Venus.Data.DataStore.d__30.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Primavera.Venus.DataRepository.DataServiceContext.d__33.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Primavera.Mercury.CommandLineModule.ExecuteImportExport.d__67.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Primavera.Mercury.CommandLineModule.ExecuteImportExport.d__63.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at Primavera.Mercury.CommandLineModule.CommandLineModule.Initialize()
at 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: One or more errors occurred.
- The Assembly that the module was trying to be loaded from was:Primavera.Mercury.CommandLineModule, Version=18.8.0.29254, 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.
Steps to Duplicate:
The issue can be reproduced at will with the following steps:
1. Login to P6 Professional
2. Attempt to import XML file.
3. Select all 13 baselines available to import (if any)
4. Observe the import fails with the reported error in the XXX.xml.SummaryImportLog.txt
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |