Fix MTP700 Unified Comfort Panel Reporting Initialization Failures

SIMATIC WinCC Unified Comfort Panels (MTP700 through MTP2200) ship with a built-in report engine that produces PDF, CSV, and XLSX reports from runtime tag values, alarms, and historical archives. The engine works reliably in PLCSIM/PLCSIM Advanced and in WinCC Unified Runtime simulation on the engineering station, but field engineers commonly encounter two related failures after the project has been compiled and downloaded to the physical panel:

• "Service or database initialization failed" shown in the status bar of the configured Report Control on the HMI.
• "No connection to the server" returned by the Excel Add-In when the connection target is changed from the engineering station name to the panel's IP address.

Both symptoms are almost always symptoms of the same root cause: the runtime report database has not been initialized on the panel, the SIMATIC Edge container for reporting is not deployed, or the WinCC Unified certificate is not trusted on the Excel host. This guide covers the diagnostic path and the four canonical fixes for these errors on MTP700 Unified Comfort Panels running TIA Portal V17, V18, V19, and V20 projects.

1. Affected Hardware and Runtime Versions

The reporting subsystem on Unified Comfort Panels is implemented as a containerized Edge application. The panel device and image version determines whether reporting is enabled by default and which TIA Portal / Engineering Framework version can administer it.

The behavior described in the official documentation is that Unified Comfort Panels with a device version lower than V18 always have reporting enabled and the storage locations are predefined in the runtime settings. From V18 forward, reporting is built on top of the SIMATIC Edge runtime and the container must be deployed. See the official TIA Portal help under Reporting (Unified Comfort Panel) (RT Unified) - WinCC Unified.

2. Root Cause Analysis

The two visible errors collapse to four distinct underlying causes. Identifying which one applies is a three-step process: check the panel image version, check the Control Center status of the reporting service, and check the Excel host's trust store.

2.1 Empty or non-initialized SQLite database on the panel

The WinCC Unified report engine persists queued jobs, layouts, and triggers in a local SQLite database under /home/industrial/Siemens/Automation/Reports/. After a fresh image, factory reset, or firmware update, this directory may exist but the database file report.db is empty. The service refuses to start, surfaces Service or database initialization failed in the Report Control status bar, and the Excel Add-In subsequently cannot bind to the RPC endpoint on TCP 4433 (or the configured HTTPS port).

2.2 SIMATIC Edge runtime not licensed or not deployed

From TIA Portal V18, the report application is delivered as the report-unified Edge application on the Industrial Edge Marketplace. If the Edge runtime is enabled on the panel but the report-unified app is not deployed (or the app is deployed but the underlying Edge is not licensed with a valid Edge Device License Manager entitlement), the report service will not start. The control's status bar again shows the initialization failure with no further detail.

2.3 Self-signed WinCC Unified certificate not trusted on the Excel host

The Excel Add-In uses OPC UA-style reverse HTTPS and authenticates the panel by its X.509 certificate. Unified Comfort Panels generate a self-signed certificate per device. If the certificate is not in the Trusted Root Certification Authorities store of the Windows host running Excel, the Add-In receives a TLS handshake failure that is reported as No connection to the server. The connection works against the engineering station because the host's own certificate chain is trusted by default.

2.4 Offline configuration export mismatch

If the project was authored on TIA Portal V19 or V20 but the panel still runs the V17 image, exporting an offline configuration from the Report Control's configuration tab produces a schema that the panel's older engine cannot import. The result is An error occurred while importing the configuration and the runtime is left in a half-initialized state.

3. Prerequisites

Before applying the fixes below, confirm the following items are available on the engineering workstation and the panel:

• Engineering workstation running TIA Portal V18, V19, or V20 with the matching WinCC Unified Comfort Panel HSP installed.
• SIMATIC WinCC Unified Excel Add-In (delivered with TIA Portal under Siemens/Automation/PLCSIM/Add-Ins or downloaded from the SIOS support entry 109828694).
• Panel admin password (default for Unified Comfort Panels is 1234; if the project was compiled with a custom password it must be retrieved from the TIA Portal project under HMI\_RT > Security > User management).
• Network reachability: HTTPS port 443/tcp and the report RPC port 4433/tcp (default) between the Excel host and the panel, verified with Test-NetConnection <panel-IP> -Port 4433 on Windows PowerShell.
• Panel image version equal to or newer than the TIA Portal project's device version. Verify on the panel under Control Panel > System > Device info.

4. Solution Path A: Rebuild the Runtime Database

Use this path when the panel image is correct and Edge is licensed, but the Service or database initialization failed string is visible in the Report Control status bar.

1. Open the TIA Portal project and the device view of the Unified Comfort Panel.
2. Open the Runtime settings editor and navigate to Reports.
3. Note the configured Storage location paths (network share, local SD card, or /home/industrial/). The default on pre-V18 panels is /home/industrial/Siemens/Automation/Reports per the Reporting (Unified Comfort Panel) help page.
4. Recompile only the HMI (right-click the device → Compile > Software (rebuild all)).
5. Download the rebuilt project to the panel. During the download, the runtime will recreate the database and storage folders.
6. After the panel reboots, open a browser to https://<panel-IP>/reports (if exposed) or check the Control Center for the report service state.

If the report service still does not start, manually clear the corrupted state by SSHing into the panel (admin mode via the diagnostic interface) and removing the database file:

rm -f /home/industrial/Siemens/Automation/Reports/report.db
systemctl restart siemens-rtm-report.service

5. Solution Path B: Deploy the SIMATIC Edge report-unified App

Use this path on V18+ panels where the report service is part of the Industrial Edge runtime.

1. Open the panel's SIMATIC Edge Management page by entering https://<panel-IP> in a browser on the engineering network.
2. Log in with the Edge admin credentials (default: admin / the panel admin password).
3. Under System > Licenses, confirm that at least one Edge Device License Manager entitlement is active. Without a valid entitlement, Edge apps will not start.
4. Navigate to Apps > Catalog and install the report-unified application from the Industrial Edge Marketplace. The app is published at the SiemensIndustrialEdgeITA/report-unified repository and is required to enable SIMATIC Edge functionality on Unified Comfort Panels.
5. Assign the app to the local Edge runtime on the panel and provide the report storage location (must match the path configured in TIA Portal).
6. Start the app and wait for the status to read Running. The first start may take up to 90 seconds while the SQLite schema is initialized.
7. Return to the HMI project and reload the runtime to re-bind the Report Control to the now-running service.

6. Solution Path C: Install the Panel Certificate on the Excel Host

Use this path when simulation connects to the engineering station by name, but the Excel Add-In fails to connect to the panel by IP with No connection to the server.

1. On the engineering workstation, open a browser and navigate to https://<panel-IP>.
2. Click the padlock icon in the address bar, choose Connection is not secure, and then Certificate is not valid. Export the certificate in Base-64 X.509 format to a file named mtp700.cer.
3. Open certlm.msc (Local Machine certificates) on the Windows host running Excel.
4. Right-click Trusted Root Certification Authorities > Certificates and choose All Tasks > Import. Import mtp700.cer and place it in the Trusted Root Certification Authorities store.
5. Close all Excel instances and reopen the Add-In.
6. In the Excel Add-In connection dialog, enter the panel IP and the HTTPS port (default 443), then click Test connection. The status should now read Secured in the URL bar and the binding should succeed.

7. Solution Path D: Export and Import the Offline Configuration

Use this path when the Report Control's Export offline configuration button appears to do nothing, or when re-importing returns An error occurred while importing the configuration.

1. In TIA Portal, open the Report Control editor and switch to the Configuration tab. Do not confuse this with the Backup tab above it.
2. Set a file name, choose a target folder on the engineering station, and click Export offline configuration. The export must be done with the same TIA Portal version that authored the project.
3. If the export appears to do nothing, check the Windows event log under Applications and Services Logs > Siemens TIA Portal for a ReportExportFailed event. The most common reason is a read-only network share or a OneDrive-synced folder.
4. To import on the panel, copy the exported file to a USB stick or to /home/industrial/Siemens/Automation/Reports/import/ via the panel's file browser.
5. Restart the report service using the System > Services > Restart entry in the Control Center. The service will pick up the imported configuration on the next start.

8. Verification Steps

After applying one of the four solution paths, verify success with the following checks. All four must pass before the report is considered operational.

1. Service status check. On the panel, open Control Panel > System > Services and confirm Report Service is in state Running with a non-zero uptime. A service that is in state Stopped after a restart indicates a database write error in the diagnostic log.
2. Control status bar check. Open a screen containing the Report Control. The status bar should read Ready instead of Service or database initialization failed.
3. Excel Add-In connection check. In the Add-In, enter the panel IP and click Test connection. A green checkmark confirms the TLS handshake and the RPC binding are both healthy.
4. End-to-end report generation. Trigger a report manually from the HMI screen, then open the configured storage path. A new PDF or XLSX file must appear within 10 seconds. File size must be greater than 0 bytes; a zero-byte file indicates a layout template error.
5. Edge app status check (V18+). In the Edge management UI, confirm the report-unified app is in state Running and its CPU/memory utilization is non-zero during report generation.

9. Diagnostic Matrix

Use this matrix to map the observed symptom to the appropriate solution path and to the diagnostic command that confirms the root cause.

10. Field-Proven Caveats

The following points are derived from recurring commissioning observations and should be verified on every MTP700 deployment that uses reporting.

• The MTP700 is a 7" panel with limited internal flash. Heavy report workloads with continuous triggers can fill the storage location within days if the report destination is set to the panel's internal flash. Always configure a network share or a USB-attached SD card as the storage location on MTP700 and MTP1000 panels.
• The Excel Add-In uses the Windows user certificate store, not the Excel user store. The certificate import must be done in certlm.msc (local machine) for system-wide Excel, or in certmgr.msc (current user) for the current account only.
• If the panel is behind a NAT router (common on machine-level networks), the Excel Add-In must use the panel's NAT-visible IP and not the engineering station's host name. The default port 4433 must also be port-forwarded.
• Reports generated from the Engineering Framework (EF) simulation can be opened with the Add-In against the engineering station, but cannot be regenerated against the panel until Path C is completed. The Add-In's error message is intentionally generic.
• The report-unified Edge app consumes one Edge Device License Manager entitlement. Plants that share a single Edge license across multiple panels will see the report service stop when the license is reassigned. Always dedicate a license per reporting panel.

11. Frequently Asked Questions