Error: "PM Information Exception Exception while reading bootstrap file: System.Globalization.CultureNotFoundException: Culture is not supported. Parameter name: name Dutch is an invalid culture identifier."

(Doc ID 2074835.1)

Last updated on SEPTEMBER 06, 2017

Applies to:

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

Symptoms

Scenario 1: When attempting to log in to Visualizer, the following error occurs:

ERROR
-----------------------
Unable to connect to the database. Please run the Database Configuration tool or contact your administrator.


Visualizer log (visualizer.log found in %TEMP%) displays the following error:
PM Information Exception Exception while reading bootstrap file: System.Globalization.CultureNotFoundException: Culture is not supported.
Parameter name: name
Dutch is an invalid culture identifier.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Log in to Visualizer
2. Note the reported error which occurs

 

Scenario 2: When attempting to import an XML file, the following error occurs:

ERROR
-----------------------

Process Completed with Errors

Log File: Exception while reading bootstrap file: System.Globalization.CultureNotFoundException: Culture is not supported.
Parameter name: name
Dutch is an invalid culture identifier.

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.6.18611, 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
-----------------------
1. Log in to P6
2. Select File > Import...
3. Select "XML" for the file type, browse to the .xml file and select it, click Import and follow the prompts
4. Message "Process completed with errors" displays, with a link to the log file

 

Scenario 3: When running Schedule Comparison or launching Visualizer in 16.1.x

ERROR

-----------------------

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.Venus.CommandLineModule, Version=16.1.0.18077, 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
-----------------------
1. Log in to P6
2. Select Schedule Comparison
3. See error when Visualizer launches
4. Or, launch Visualizer and see error.

 

 

Changes

 

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