Resolving PCS7 V8.0 SP1 Error 1230:2001 WinCC Insert Failure

Problem Overview

On a SIMATIC PCS 7 V8.0 SP1 (Update 1) Engineering Station, an engineer attempts to build a Multi-project and insert a WinCC Application into the HW-Config of a PC station. The SIMATIC Manager dialog terminates with the message:

Insert(1230:2001) – Unable to insert the object.

The error appears immediately on the Insert WinCC Application action, before any object picker dialog is presented. The WinCC Application object is never placed in the PC station slot, and the station remains incomplete in the Multi-project. Because the operator station depends on this object, the entire project cannot be downloaded or commissioned until the failure is cleared.

The 1230:2001 identifier is a SIMATIC Manager object-model error reported by the COM/OLE insertion layer. The first four digits (1230) indicate the OLE insertion error class, and the suffix (:2001) names the specific failure code returned by the WinCC Application COM server. The text "Unable to insert the object" is the localized string for HRESULT failure of the COM call. The same class of error can also surface in unrelated Office automation scenarios; see Microsoft Q&A: cannot insert object in Excel and Microsoft Support: "Cannot insert object" error after MS14-082 for the general failure pattern.

Affected Environment

The error has been observed on Engineering Stations that already host a working WinCC runtime elsewhere on the machine, so a missing installation is not a precondition. The same Multi-project can be opened and modified on a second Engineering Station and the insert succeeds, which proves the issue is local to the original ES rather than to the project object itself.

Root Cause Analysis

The 1230:2001 error has three observed root-cause families on PCS 7 V8.0 SP1 Update 1:

1. Missing or stopped SQL Server (WINCC) service. SIMATIC Manager and HW-Config depend on the WinCC instance of SQL Server to register and instantiate the WinCC Application COM class. If the service is set to Manual and is stopped (typical after a reboot, after a service-pack install, or after the SQL Server agent is changed), the insert fails with 1230:2001 because the COM server cannot bind to its database.
2. Corrupt Multi-project state. The Multi-project container can become inconsistent (stale references, broken inter-project links, locked handles in the project database) such that the insert call into the PC station times out or refuses the object. Copying the project to a second ES and successfully inserting the same WinCC Application on that ES, then archiving/restoring back to the original ES and observing the same failure, points strongly to a corrupt local view rather than a corrupt project file.
3. Installation defect on the Engineering Station. A subset of WinCC components installed with warnings or errors leaves the WinCC Application COM class partially registered. The SIMATIC Manager installer log should show non-zero error entries for WinCC components on affected machines; on a healthy ES every WinCC component shows status OK.

A network/ethernet cable absence is sometimes cited as a contributing cause. SIMATIC Manager performs a station-name resolution at insert time; without a working adapter, the PC station cannot be bound to a target and the COM call may fail. Always verify a network adapter is enabled and connected before proceeding.

Pre-Diagnostic Checklist

Before applying fixes, capture the following state so you can compare before/after:

1. Open Start → Control Panel → Administrative Tools → Services on the Engineering Station.
2. Locate the service SQL Server (WINCC). Record its Startup Type, current Status, and the path of the executable.
3. Open Start → All Programs → Siemens Automation → SIMATIC → SIMATIC Manager and confirm the installed version is exactly PCS 7 V8.0 SP1 Update 1 via Help → About.
4. In Start → Control Panel → Programs and Features, locate SIMATIC WinCC entries and confirm none show Error in the install status column.
5. Open Start → Run → eventvwr.msc and inspect Windows Logs → Application for the last 24 hours; filter on source SQLWRITER, MSSQL$WINCC, and SIMATIC.
6. Confirm the Ethernet adapter is connected and has a link light; record IP address and subnet mask.

Resolution Path A — Start SQL Server (WINCC) Service

This is the fastest path and the one that resolved the original incident. The WinCC Application COM class is hosted by the WinCC instance of SQL Server; if that instance is stopped, the COM class cannot be instantiated and the SIMATIC Manager insert call returns 1230:2001.

1. Press Win + R, type services.msc, press Enter.
2. Scroll to SQL Server (WINCC). The service display name is SQL Server (WINCC) and the service name is typically MSSQL$WINCC.
3. Right-click → Properties. Set Startup type to Automatic (or Automatic (Delayed Start) if the ES boots slowly).
4. Click Start. The Service status should change to Running. Confirm via Start → Run → sqlcmd -S .\WINCC -E; the prompt 1> confirms the instance accepts queries.
5. Close Services. Re-open SIMATIC Manager, navigate to the PC station inside the Multi-project, and retry Insert → WinCC Application.

Resolution Path B — Rebuild the Multi-project

If Path A does not clear the error, the Multi-project state on the local Engineering Station is inconsistent. The project file itself is healthy, as proven by the successful insert on a second ES. Rebuild the container on the local ES:

1. In SIMATIC Manager, close the Multi-project without saving (if there are unsaved changes, save them to a separate S7 project first).
2. Use File → Multi-project → Remove from Multi-project on each sub-project to detach them.
3. Use File → Multi-project → New to create a fresh Multi-project container with the same name.
4. Re-insert each sub-project via File → Multi-project → Insert Sub-project.
5. Open the PC station → HW-Config and retry the WinCC Application insert.

Rebuilding the Multi-project regenerates the project database, the cross-project links, and the S7 program container references without touching the individual sub-projects. The same technique resolved the original incident after Path A and Path C both failed.

Resolution Path C — Verify Installation Integrity

If both Path A and Path B fail, the Engineering Station installation itself is suspect. PCS 7 installation is sensitive: a partial install (e.g., a reboot during setup) leaves the WinCC Application COM class partially registered. The correct verification procedure is:

1. Open Start → Control Panel → Programs and Features.
2. Select SIMATIC PCS 7. Click Uninstall/Change.
3. Choose Modify. The installer displays the component tree; expand every WinCC component.
4. Confirm that no row shows the status Error or a red marker. On a healthy install, every component reads Will be installed or Installed (OK).
5. If any WinCC component is marked Error, complete the Modify wizard to reinstall the affected component. A reboot is typically required at the end.
6. After reboot, re-run the Pre-Diagnostic Checklist and retry the WinCC Application insert.

Resolution Path D — Network and PC Station Hygiene

SIMATIC Manager performs a PC station binding step at insert time. If the binding fails, the insert can return 1230:2001 even when the SQL Server is running. Apply the following checks:

1. Confirm an Ethernet adapter is connected, with link LEDs active, and a valid IP address in the same subnet as the target AS.
2. In SIMATIC Manager, right-click the PC station → Object Properties → Target Computer. Confirm the configured PC station name resolves via Start → Run → ping <name>.
3. If the PC station name is localhost or unset, set it to the Engineering Station's actual hostname.
4. Recompile the PC station via Station → Compile before retrying the insert.

Diagnostic Procedure — Wizard-Based Isolation

To distinguish a corrupt project from a corrupt installation, use the SIMATIC Manager project wizard:

1. Select File → New Project → Wizard.
2. Choose a project template that includes a PC station with WinCC Application (for example, the PCS 7 OS single-station template).
3. Complete the wizard and let SIMATIC Manager open the resulting project.
4. Open the PC station → HW-Config and try to insert the WinCC Application.

Interpretation:

Project Archive and Restore Procedure

When the issue appears to be project-side and you want to migrate to a clean state on the same ES:

1. In SIMATIC Manager, open the Multi-project and select File → Archive.
2. Choose the Multi-project entry (not just the sub-project) and specify a destination .zip archive.
3. Copy the archive to a second Engineering Station or to a folder on the same machine, then run File → Retrieve to extract it.
4. Open the retrieved project on a different ES; if the WinCC Application inserts there, the project file is intact.
5. Delete the original Multi-project on the original ES, then re-retrieve the archive on the original ES and rebuild the Multi-project structure.

The original incident showed that retrieving the archive on the same ES, without deleting the local Multi-project, leaves the same corrupt state behind. Always delete the original Multi-project before re-retrieving.

Verification

After applying any of the four resolution paths, verify the fix with the following checks:

1. In SIMATIC Manager, open the PC station in HW-Config. The WinCC Application slot should now show a populated object with a green check on the station-level consistency check (Station → Consistency Check).
2. Compile the PC station via Station → Save and Compile. The compile log should report 0 errors.
3. Right-click the Multi-project → Multi-project → Check Consistency. The dialog should report no cross-project inconsistencies.
4. Open WinCC Explorer from the PC station and confirm the project loads. This proves the WinCC Application object is bound to the live project database.
5. Reboot the Engineering Station and confirm that SQL Server (WINCC) comes up automatically and the WinCC Application can still be inserted into a fresh PC station.

Troubleshooting Matrix

Prevention and Best Practices

• Set the SQL Server (WINCC) service to Automatic startup on every Engineering Station so reboots do not strand the instance.
• Keep a baseline of the original install media for SIMATIC PCS 7 V8.0 SP1 Update 1 so the Modify workflow can be re-run without network access.
• Maintain a regular Multi-project archive cadence. Use the File → Multi-project → Archive command, not the sub-project archive, to capture the cross-project links.
• After any Windows security update, retest the WinCC Application insert on a non-production Engineering Station before the production ES is patched.
• Document the Engineering Station hostname and PC station name in the project header; mismatches between the SIMATIC Manager binding and the Windows hostname are a recurring root cause.

Related Error Patterns

The 1230:2001 identifier is one of a family of OLE/COM insertion errors reported by SIMATIC Manager. The general class of "Cannot insert object" failure has been observed in other COM-based hosts as well, including Microsoft Office. The behavior — a COM class that fails to instantiate on one machine while working on another — is the same. For general context on the error class, see:

• Microsoft Q&A — cannot insert object in Excel
• Microsoft Support — "Cannot insert object" error after MS14-082

For PCS 7-specific errors, the official support portal is Siemens Industry Online Support. Search the document ID for "PCS 7 V8.0 SP1" to retrieve the installation manual, the WinCC Configuration Manual, and the release notes that match this version.

FAQ