Resolving PCS 7 New Project Wizard Error 'Object View Could Not Be Created in WinCC'

During project creation using the PCS 7 New Project Wizard, the error 'Object view could not be created in WinCC' occurs when the wizard fails to initialize the Technological Hierarchy (TH) plant view in the underlying WinCC project database. This failure is caused by missing Windows security group memberships (SIMATIC HMI, Siemens TIA Engineer), SQL Server instance permission conflicts, or corrupted Engineering System installation components, and is resolved via the SIMATIC Security Controller.

Role of the PCS 7 New Project Wizard in Multiproject Initialization

The SIMATIC PCS 7 New Project Wizard (PCS 7 Wizard) automates the creation of a standardized process control multiproject:
* It generates the central multiproject container, the Automation Station (AS), the Operator Station (OS), and the Master Data Library (MDL).
* Plant Hierarchy Creation: Crucially, the wizard structures the Technological Hierarchy (TH), establishing plant sections, units, and equipment phases.
* It initializes the corresponding WinCC OS database, creating the internal Object View and picture hierarchy (@Overview.pdl, @Area.pdl) that binds the STEP 7 plant view to the supervisory graphics engine.

Mechanism of the Error: WinCC Database and Plant Hierarchy Failure

When the wizard reaches the final step and attempts to synthesize the OS project structure, the operation halts with dialog:

Object view could not be created in WinCC.

The failure indicates that the wizard:
1. Created the STEP 7 multiproject files and HW Config structure successfully.
2. Initialized the WinCC project directory and launched the Microsoft SQL Server database creation script.
3. Failed when executing the inter-process COM command that binds the Technological Hierarchy COM server (s7hpshax.dll / s7whtaax.dll) to the WinCC CS database, resulting in an unpopulated, corrupted OS project object.

Root Causes: Windows Security Groups and SQL Server Rights

Field diagnostics establish three primary causes for this initialization fault:
* Missing User Group Memberships: The active Windows user account logged into the Engineering Station is not an explicit member of the mandatory Siemens local security groups:
* SIMATIC HMI
* Siemens TIA Engineer
* Administrators
* SQL Server Instance Permissions: The WinCC SQL Server service instance was started with restricted account permissions or lacks access to the Windows temporary folder (C:/Users/<User>/AppData/Local/Temp/), preventing the execution of temporary database attach scripts.
* Corrupted COM Registration: Following a Windows cumulative update or interrupted software installation, the Technological Hierarchy ActiveX/COM DLLs failed to register properly.

Step-by-Step Resolution: Security Controller, Rights Audit, and Re-Registration

To repair the engineering environment and allow the wizard to complete successfully:
1. Audit Windows User Security Groups:
* Open Computer Management -> Local Users and Groups -> Groups.
* Open SIMATIC HMI: verify that the current Windows user account is listed as a member.
* Open Siemens TIA Engineer: verify that the current user account is listed.
* If missing, add the user and log off and log back into Windows to apply group token changes.
2. Execute SIMATIC Security Controller:
* Open the Windows Start menu and launch SIMATIC Security Controller as Administrator.
* Click Repeat Settings.
* The utility scans all registry keys, DCOM endpoints, SQL Server permissions, and folder ACLs, restoring certified factory defaults.
3. Re-register Technological Hierarchy DLLs:
* Open Windows Command Prompt as Administrator.
* Execute manual registration commands:
cmd cd "C:\Program Files (x86)\Common Files\Siemens\Ace" regsvr32 s7hpshax.dll regsvr32 s7whtaax.dll
* Confirm that each component returns "DllRegisterServer succeeded".
4. Restart Workstation: Reboot the Engineering Station to ensure all COM handles and SQL services initialize cleanly.

Verification

Launch SIMATIC Manager as Administrator.
Select File -> 'New Project' Wizard....
Select the default CPU 410-5H or S7-400, select an OS Single Station or Server, and specify 3 plant hierarchy levels.
Click Finish: verify that the wizard runs smoothly to 100% completion without warning dialogs.
Open the created project in SIMATIC Manager: verify that the Plant View displays the configured hierarchy folders and that the OS project opens cleanly in WinCC Explorer.

Limitations and Operational Precautions

Always install SIMATIC PCS 7 software with Windows User Account Control (UAC) set to default and real-time antivirus scanning temporarily disabled.
Never create PCS 7 projects on unmapped cloud-sync folders (e.g., OneDrive, Dropbox) or network paths with latency, as SQL file locking will corrupt database generation.
If repairing security settings does not resolve the error, repair the installation using the official PCS 7 DVD setup.

Engineer FAQ

What does 'Object view could not be created in WinCC' specifically mean?
The wizard failed to initialize the Technological Hierarchy database link within the WinCC project.
Which Windows user groups are mandatory for PCS 7 engineering?
The active user must belong to SIMATIC HMI, Siemens TIA Engineer, and local Administrators.
What utility automatically restores Siemens registry, DCOM, and folder permissions?
The SIMATIC Security Controller application.
Can I create the project manually without using the wizard if it fails?
Yes, by creating a blank Multiproject in SIMATIC Manager, manually inserting an S7-400 station, and inserting a WinCC OS station.
Why is SQL Server involved in creating a new PCS 7 project?
Because WinCC uses Microsoft SQL Server for project configuration databases (CC_xxx.mdf), initialized during project creation.
Does this error affect existing projects, or only new project creation?
It affects new project initialization and opening the Plant View on newly generated stations; existing projects may also fail to compile OS.
Where is the SIMATIC Security Controller located?
Under Windows Start Menu -> Siemens Automation -> SIMATIC Security Controller.
Can running SIMATIC Manager as a standard user cause this error?
Yes, engineering tasks require administrative rights to execute DCOM calls to the WinCC SQL engine.
What S7 software component manages the Plant View in SIMATIC Manager?
The Technological Hierarchy (TH) component of PCS 7 Engineering.
Does this error indicate a damaged controller CPU?
No, this error is 100% localized to software configuration and user rights on the Engineering Station.

Technical References

SIMATIC PCS 7 Engineering System Configuration Manual (V9.0 / V9.1)
SIMATIC PCS 7 PC Configuration and Installation Manual
Siemens Industry Online Support Entry: Troubleshooting PCS 7 Wizard Project Creation (Entry ID 299527)
SIMATIC Security Controller User Guide