EcoStruxure Power Monitoring Expert
Enter the EcoStruxure Power Monitoring community of experts and find answers to your questions about the EcoStruxure Power Monitoring Expert software. From IoT implementation to sensor integration and more, get support from experts and share your experiences by subscribing to the Schneider Electric Exchange forum today.
Posted: 2019-12-16 05:00 AM . Last Modified: 2023-08-18 05:37 AM
Link copied. Please paste this link to share this article on your social media post.
I want to restore a backup, but the Configuration Management Tool has the following error:
An error accurred while initializing the system. Please see log for more details. The Configation Manager will now shut down.
I'm using an PME 7.2.2
Windows Server 2012 R2
Link copied. Please paste this link to share this article on your social media post.
Hello @Eliezer95 ,
Looks like the bug is from the CM tool trying to get SQL registry information that does not exist. This is most likely because SQL 2012 version is keeping this information in a registry that is slightly named differently or in a different location.
I've attached a hotfix for the CM tool that you can apply to see if it fixes the issue.
1) The attached file "FA374630_Error_Opening_Application_Hotfix.zip" contains the dll you need and the instructions on where to place it.
Steps to deploy the hotfix (Hotfix will only work in CM tool Build 18241.1 and will not work in other versions)
If the hotfix does not work there are a couple of other things you can try.
2) Make sure that FIPs is disabled
Disable FIPS (Federal Information Processing Standard) setting in windows group policy. CM Tool 9 using some third party libraries to get around windows not handling Long Paths.
Can turn it off in Group Policy
Run -> GPEdit.msc -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing
Disable the rule.
https://social.msdn.microsoft.com/Forums/vstudio/en-US/209e25be-0925-484e-ac10-736823e2b9f3/fips-iss...
3) Make sure that MD5 Hashes are allowed on the machine.
https://support.microsoft.com/en-us/help/922574/the-microsoft-extensible-authentication-protocol-mes...
4) If the error is only in the 'Operating System Information' section then it can usually be safely ignored and the CAB file created should still be fine.
If that doesn't work then I would contact Tech support to log a ticket so we can investigate the issue in more detail.
Thanks,
Link copied. Please paste this link to share this article on your social media post.
Hello @Eliezer95 , thanks for your question.
You asked this at the right time, I would recommend you to participate tomorrow to our webinar focused on Power Management systems to get the opportunity to interact in live with our experts and get your issue solved. Register here!
If you have other questions as well, it will be the occasion to ask them all 😉
Link copied. Please paste this link to share this article on your social media post.
Hello Eliezer95,
When did you encounter this error? (Opening the tool? Save to Archive? Write to System?)
If you upload the Configuration Management Tool log file (should be found in the "\PME 9.0 Configuration Management Tool\Logs\" folder) we can take a quick look to see if there a specific error that we have run into before.
There might be a quick fix if it is something we have encountered before, otherwise you might have to open a Tech support ticket.
Let's take a quick look first to see if we can get some more details on this issue.
Thanks,
Link copied. Please paste this link to share this article on your social media post.
@Calvin_HopWo This error is when opening the tool.
This is the log text:
16:50:07:040||Error||High||Configuration Manager||System.NullReferenceException: Referência de objeto não definida para uma instância de um objeto.
em ConfigurationManager.Business.Utilities.ProductIdentifier.GetSqlInfoFromRegistry(String sqlInfoName)
em ConfigurationManager.Business.Utilities.ProductIdentifier.GetSystemInformation()
em ConfigurationManager.Helper.UiStateManager.SetUiStateForReadFromSystem()
em ConfigurationManager.Helper.UiStateManager.SetUiStates()
em ConfigurationManager.Helper.UiStateManager..ctor(ISupportedVersionManager supportedVersionManager, IDistributedSystemManager distributedSystemManager, IZipHelper zipHelper, ILogger logger, IConfigurationManager configManager)
em ConfigurationManager.ViewModels.ConfigurationManagerVM.Initialize()||UI
Link copied. Please paste this link to share this article on your social media post.
Hello @Eliezer95 ,
Looks like the bug is from the CM tool trying to get SQL registry information that does not exist. This is most likely because SQL 2012 version is keeping this information in a registry that is slightly named differently or in a different location.
I've attached a hotfix for the CM tool that you can apply to see if it fixes the issue.
1) The attached file "FA374630_Error_Opening_Application_Hotfix.zip" contains the dll you need and the instructions on where to place it.
Steps to deploy the hotfix (Hotfix will only work in CM tool Build 18241.1 and will not work in other versions)
If the hotfix does not work there are a couple of other things you can try.
2) Make sure that FIPs is disabled
Disable FIPS (Federal Information Processing Standard) setting in windows group policy. CM Tool 9 using some third party libraries to get around windows not handling Long Paths.
Can turn it off in Group Policy
Run -> GPEdit.msc -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing
Disable the rule.
https://social.msdn.microsoft.com/Forums/vstudio/en-US/209e25be-0925-484e-ac10-736823e2b9f3/fips-iss...
3) Make sure that MD5 Hashes are allowed on the machine.
https://support.microsoft.com/en-us/help/922574/the-microsoft-extensible-authentication-protocol-mes...
4) If the error is only in the 'Operating System Information' section then it can usually be safely ignored and the CAB file created should still be fine.
If that doesn't work then I would contact Tech support to log a ticket so we can investigate the issue in more detail.
Thanks,
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.