Troubleshooting Powermanager

The following section describes how to handle common import error conditions.

Message

Situation

Do the following...

“Issue found during the import” error loading the CSV import file.

The selected CSV import file cannot be loaded by the Desigo CC importer.

Verify that the CSV file uses a comma (,) character as separator. Any other character will result in an invalid file format. Refer the sample CSV file provided.

There are warnings or errors, look at the log file.

The configuration file selected for the import is invalid.

In the Import tab, click Analysis Log and check the pre-import log.

Try again using another configuration file.

Error in report, check configuration.

The default Tomcat memory of 2500 MB is insufficient to generate cache for a system with more than 500 managed meters configured. In such situations you must set the Tomcat memory to a higher limit, for example, 6000 MB.

From the Services dialogbox, stop the Tomcat service.

Navigate to the following path:
\Program Files\Apache Software Foundation\Tomcat 9.0\bin and double-click Tomcat9w.exe file.

Select the Java tab and navigate to the Maximum memory pool field.

Set the memory to higher value and click Apply and OK.

Now re-start the Tomcat service and try again.

Empty Dashboard
(Tiles inside Charts tab doesn’t load any content)

This is due to the cache of the web browser content of the charts which has not loaded

Close powermanager and powermanager SMC(do not stop the applications, just close them)
Goto Temp folder
cmd>” %temp%”

Delete
eo.Webbrowser.cache folder as mentioned in SC1

Could not load report and gives the message that “A connection attempt was refused”

Tomcat is not installed or has stopped

1)Check if Tomcat is installed. If not installed, install and place the report files and start Apache Tomcat from Services.msc

2)If already installed,start Apache Tomcat from Services.msc

After loading report and executing params “"Error while fetching data from WSI due to token expiration.",”

WSI has stopped working

Start WSI from Console

After scheduling reports, Report is not available in the location

The password has been changed

Enter the correct credentials to edit the selected report definitions.

System goes into emergency mode

There is no sufficient C drive space and memory and many devices are connected.

Increase system C drive space and memory

HDB Writer goes to Overload state

Too many measurement points, connected to Powermanager, are archived

Unselect some of the archived measurement points and continue

Report definition shows blank

When create report definition is clicked, a blank page is displayed.

Exit the application and re login

Application Viewer shows blank

Switch between report definition and application viewer

Click on the report and click on application viewer

Read function failed error pop up

Occurs when the object models in the libraries are corrupt

Create the new project through template.

#COM is displayed in overview, Operations and Extended Operation pane of Application view

The device is flickering and there is a communication error. Hence, the data is not polled.

Check the device communication and try connecting again

Configuration is not allowed based on the user's scopes and permissions

The device is flickering and there is a communication error. Hence, the data is not polled.

Contact the system administrator to grant extended permissions.

Service not available error in the splash screen of application

This could happen if the WCCOAGmsCoHoMngr in the WinCCOA console would have stopped

Check if it is stopped and try restarting the control, then try logging in to application

Client license unavailable

When GMS_Licensing is stopped, this error is displayed in the splash screen of the application

Try restarting GMS_Licensing.ctc manager in WinCCOA console and logging in to application

powermanager cannot be installed. Powershell 5.1 is not installed in this PC. Kindly install Powershell 5.1 and retry the installation.

Powermanager 4.1 requires powershell 5.1 or higher for all the steps to be completed successfully.

Install powershell 5.1 from the microsoft website.

The system is found to contain WinCC OA licenses. You can transfer the licenses or delete in case of trial licenses and start the installation again. Refer the product manual for more details

There is a license in the SYSTEMDRIVE\AX NF ZZ folder

Delete the license in case of trail license or transfer the license

powermanager installation is not compatible with the Versions of Visual C++ redistributables found in the PC. Kindly refer the product manual for more details and contact your system administrator for technical assistance.

If any version of Visual C++ redistributable higher than 14.0.24213 is found in the PC.

Uninstall the Visual C++ redistributable higher than 14.0.213, note that few versions will not have an uninstall option in control panel.
In this case please contact IT support for further assistance.

Project name is not as per standards, refer the manual for more details

In the entry fields of the platform:

You can use UTF-8 characters and 7-bit ASCII characters in the file or project names and paths. However, blank spaces and special characters including \\, :, /, \, :, ,, =, ^, &, *, ?, “, <, >, |, @, [, ], {, }, $, !, %, ., (, ), ‘ “ ‘, \t are not permitted.

You must not use any characters other than A through Z, numbers 0 through 9, and a hyphen (-).

Forward and backward slashes (\ and /) can only be used to separate the names of directories.

According to WinCC OA 3.16 Help: Umalaut (“ä”, “ö”, “ü”) – cause problems during online backup.

Change the project name and retry.

JDK 11.0.2 is not present in the PC. Refer the powermanager Help for further information.

JDK 11.0.2 is neccasary for installation of few components of powermanager , hence this warning appears.

Download Open JDK 11.0.2 from the below link

https://jdk.java.net/archive/

Extract the contents and place the jdk-11.0.2 folder in C:\Siemens\Java\

Website name is not as per standards, refer the manual for more details

The website name must be a unique name. You cannot have sites in IIS with the same name. Following special characters are not permitted in the website name: \\’, ‘/’, ‘?’, ‘;’, ‘:’, ‘@’, ‘&’, ‘=’, ‘+’, ‘$’, ‘,’, ‘|’, ‘ “ ‘, ‘<’, ‘>’.

Change the website name and retry.

A certificate error occurred. Please handle CertificateError event.

To access WSI from a remote machine, WEB server communication has to be secure.

Both the root and host certificates have to be created from server and same to be imported in Client.

powermanager runs in demo/courtesy mode

You in to the application and the courtesy/demo mode appears in summary bar

Check if customer has proper license in LMU(License management utility)

Check the license platform version

Check if license related services are running properly

Make sure user has purchased enough number of licenses

“No License…” in WinCCOA console

Issue may occur in virtual box machine when license in pointed from host machine.

 

You get this error when you try to open winccoa console. But you will able to login to powermanager and to switch to engineering mode

Restart the following licensing services and restart WinCCOA:

FlexNet Licensing services

Automation License manager service

BT Licensing server

Remote pointing license does not work- test connection fails in LMU application

Issue may occur in virtual box machine when license in pointed from host machine

Add two programs(LMS Imgrd & LMS siembt) in firewall exception; make sure test connection is successful from VM’s LMU

Also, make sure that ports are open from firewall to communicate to host machine

In SMC, project HDB is in not reachable state

Issue may happen when SQL server service stops

Make sure SQL Server(GMS_HDB_Express) service runs properly

powermanager dashbaord does not load. Dashboard remains blank

Website and its application is not configured properly

OR

Application is running for few days and kept idle

OR

The dashboard does not load after right dashboard configuration

Make sure website is up and running in SMC

Make sure that proper configuration is done for websites in powermanager

Exit the application and login again

Converted units from powermanager do not get refreshed in device graphics(default tab in operating mode)

This can happen if the converted unit from the device is changed and user moves to default tab in operating mode

Click on graphics page and press Alt+Ctrl+Shift+O from keyboard

Click on – Clear symbol cache in the new window

Navigate to graphics node in system tree

Navigate back to device node

Powermanager login screen does not load

This may happen if project is not running properly or closed mode service is not running

Make sure that project and Siemens GMS closed mode service runs properly

Certificate error when trying to launch web application in IE remote machine

This may appear when you try to open powermanager as client in browser

Make sure that certificates are configured properly in client machine

Managers do not run properly in the installed client machine

This may happen if powermanager is installed as client but there is a time difference between server and client

Synchronize the system time of client and server

Filed system alarms do not load (High, Low)

Right communication parameters should be used when PAC4200 device is created and started. Also, this could happen when the alarms are not loaded in the alarm bar of powermanager application

Check if the alarms are present in the PAC4200 device HMI

If they are present in device and not listed in the application, stop the device and start it again

If there is a mismatch in count of high and low alarms field of PAC4200 device

Right communication parameters should be used when PAC4200 device is created and started. This may happen if the High and low alarm counts (in alarm bar of powermanager application) are not same as compared to alarm count in device HMI

Check if the alarms are present in the PAC4200 device HMI

Count the number of High and Low alarms in the device HMI

If there is a mismatch in powermanager application, stop the device and start it again

If there is a mismatch in alarm classes or alarm type of alarm in PAC4200 device

Right communication parameters should be used when PAC4200 device is created and started. This may happen if there is a mismatch in the alarm configuration like alarm classes or alarm type (High or Low) in alarm bar of powermanager application when compared to the device HMI

Check if the alarm class in the device HMI is same as per the configuration

Check if the alarm type in the device HMI is same as per the configuration

If there is a mismatch in powermanager application, stop the device and start it again