Resolving Greyed Out Message Configuration in OS Project Editor
In SIMATIC PCS 7, the message configuration fields and column width editors in the WinCC OS Project Editor appear greyed out and read-only for two distinct reasons: either the project editor activity is set to 'Only configurations capable of online change download' under the General tab, or the alarm system has been managed using the central tool 'Options -> PCS 7 message system -> Configure...' in SIMATIC Manager. When central message configuration has been used, message blocks in the SQL database receive an author lock (CREAT_ID = 10210) to preserve central consistency. To adjust column widths, configure them directly in SIMATIC Manager under Options -> PCS 7 message system.
Table of Contents
- Author Locking and Central Administration in PCS 7 Alarming
- Why OS Project Editor Message Fields Become Read-Only
- The Role of the Central PCS 7 Message System Configuration Tool
- Comparison of Alarm Block Authorization States in SQL
- Step-by-Step Procedure to Regain Message Configuration Control
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Author Locking and Central Administration in PCS 7 Alarming
In SIMATIC PCS 7, the alarm logging database must remain consistent across redundant OS servers, engineering stations, and distributed OS clients. To prevent conflicting edits, Siemens implements an author locking mechanism inside the WinCC Microsoft SQL Server database (dbo.MSBlock table).
When a control engineer opens the WinCC OS Project Editor and navigates to the Message configuration (Melde-Projektierung) tab to adjust column formats, widths, or message classes, they often discover that the entire left-hand column list is disabled and unclickable. Understanding how PCS 7 enforces database ownership explains why this protection occurs and how to configure columns correctly.
Why OS Project Editor Message Fields Become Read-Only
Two distinct technical factors cause message configuration to lock:
-
OS Project Editor Run Setting: In the
Generaltab of the OS Project Editor, there is a setting for 'Activities during project editor run'. If this is set to 'Only configurations capable of online change download', structural message block edits are disabled because modifying message definitions requires a full runtime reactivation, which is incompatible with online delta changes. -
Central Tool Precedence (
CREAT_ID = 10210): If any engineer has ever executedOptions -> PCS 7 message system -> Configure...from SIMATIC Manager, the system assigns a global author ID (CREAT_ID = 10210) to all message blocks. This permanently locks the OS Project Editor and WinCC Alarm Logging from local modification.
The Role of the Central PCS 7 Message System Configuration Tool
When the OS Project Editor fields are greyed out due to central ownership, attempting to bypass the lock inside WinCC is the wrong approach. The system is functioning exactly as designed:
-
Global Master Location: In PCS 7, message lists must be administered from SIMATIC Manager via
Options -> PCS 7 message system -> Configure.... -
Unified Deployment: Defining column widths, hidden fields, and priorities in SIMATIC Manager updates the master project database. The OS Project Editor then reads these master definitions during its next execution, applying them without manual local intervention.
Comparison of Alarm Block Authorization States in SQL
The table below details author IDs (CREAT_ID) in the WinCC SQL database (dbo.MSBlock) and their corresponding editing states.
CREAT_ID)010210SIMATIC Manager -> Options -> Message SystemStep-by-Step Procedure to Regain Message Configuration Control
Follow this procedure to properly configure message columns when fields are greyed out in the OS Project Editor:
Method A: Administer Centrally from SIMATIC Manager (Recommended)
- Close WinCC Explorer on the Operator Station.
- In SIMATIC Manager, open menu
Options -> PCS 7 message system -> Configure.... - In the
Configure message liststab, select the target alarm list and clickConfigure. - Modify column widths, add/remove columns, and click
OK. - Ensure the
Activatecheckbox is selected, clickOK, and reopen the OS Project Editor to deploy.
Method B: Change OS Project Editor Run Activity (If not managed centrally)
- Open the OS Project Editor in WinCC Explorer.
- Switch to the
Generaltab. - Under 'Activities during project editor run', change the selection from 'Only configurations capable of online change download' to 'Complete configuration (loss of online delta download capability)'.
- Switch to the
Message configurationtab: verify that column editing is now active.
Verification
Verify message configuration restoration through the following checks:
1. In SIMATIC Manager or OS Project Editor, confirm that column modifications are accepted and saved without error popups.
2. Run the OS Project Editor: verify that generation finishes with status 'Configuration completed successfully'.
3. Launch WinCC Runtime: confirm that the alarm banner and message windows reflect the customized column widths and arrangements.
4. Open WinCC Explorer Alarm Logging: confirm that message blocks display normal consistent statuses.
Limitations and Operational Precautions
Never use direct SQL commands (such as UPDATE dbo.MSBlock SET CREAT_ID = 0) on an active production PCS 7 database. Resetting the author ID breaks synchronization between the STEP 7 multiproject and the WinCC runtime database, causing subsequent OS compilations to create duplicate message blocks or trigger database foreign key violations. Always use official Siemens menu dialogs.
Engineer FAQ
Why does setting 'Complete configuration' disable online delta download capability?
Complete configuration regenerates system screens and re-indexes message databases. Because running OS servers cannot dynamically reload core database schemas while operating, a full OS download and runtime restart is required.
Can I configure column widths per OS Client?
Yes, if the client has an independent local project and central PCS 7 message inheritance is decoupled. However, maintaining central consistency is the standard best practice.
What is the author ID 10210 in the WinCC database?
Author ID 10210 is the proprietary Siemens author stamp indicating that the message block was generated by the PCS 7 system tools, protecting it from accidental manual alteration.
Technical References
- SIMATIC Process Control System PCS 7 Operator Station Manual - OS Project Editor
- SIMATIC PCS 7 Compendium Part A - Handling the Message System V9.0
- Siemens Technical Support: Message Blocks Write Protection in WinCC (SIOS Entry ID 109756485)
Related Articles
- Configuring Permanent Column Widths in PCS 7 WinCC AlarmControl
- Deactivating Batch Name and Custom Columns in PCS 7 Message Lists
- Resolving WinCC API Error 4029 (PutSingleMessageProperties) During OS Compilation
Related Tags
- OS Project Editor
- Message Configuration
- CREAT_ID
- dbo.MSBlock
- WinCC AlarmControl
- SIMATIC Manager