Fixing WinCC V7.0 SP3 "No or invalid Project Context" ASO Error on SIMATIC IPC 227D with Windows Embedded Standard SP3

When SIMATIC WinCC V7.0 SP3 Runtime is installed on a SIMATIC BOX PC IPC 227D running Windows Embedded Standard SP3, two related symptoms are typically reported: an interactive launch failure of project.mcp with the dialog "No or invalid Project Context, ASO cannot work correct", and an AutoStart failure that delays roughly 30 minutes before reporting "Error open the project C:\…\project.MCP. AutoStart imposible" (sic). The same project file opens and runs without fault on a standard Windows XP Professional SP3 workstation. This reference isolates the root cause, the affected platform combinations, and the only configurations that Siemens officially supports for WinCC on embedded hardware.

1. Problem Statement

1.1 Error 1 — Interactive launch from Explorer

User double-clicks project.mcp on the IPC 227D desktop. WinCC initialization begins, then the dialog "No or invalid Project Context, ASO cannot work correct" is displayed and the runtime is terminated. The same .mcp file on Windows XP Professional SP3 starts normally within seconds.

1.2 Error 2 — WinCC AutoStart

When the project is configured in the WinCC AutoStart list and the runtime is started without an interactive logon, the system hangs for approximately 30 minutes and then logs the message "Error open the project C:\…\project.MCP. AutoStart imposible". The 30-minute delay is the system service-start timeout chain cascading through dependent WinCC services.

1.3 Operating environment

• Runtime: SIMATIC WinCC V7.0 SP3 (single-station or client)
• Hardware: SIMATIC BOX PC IPC 227D (Intel Atom / Celeron class)
• Operating system: Windows Embedded Standard SP3 (WES, 32-bit, NT 6.0 base, XP-look)
• Comparison baseline: Windows XP Professional SP3 (full-fat desktop SKU) — works

2. Siemens Official Support Position

Siemens documents that WinCC V7.0 SP3 Runtime is only released for the SIMATIC IPC 477C Panel PC family in the embedded segment. The IPC 227D (BOX PC) is not a released target for WinCC embedded configurations. The official support entry documenting the released embedded combination is Siemens Support entry 48189693 — "WinCC on Windows Embedded Standard / Embedded Standard 2009".

3. Root Cause Analysis

3.1 Component-level cause — Windows Message Queuing

The WinCC V7.0 SP3 runtime depends on the Windows Message Queuing (MSMQ) service. On Windows XP Professional SP3, MSMQ is part of the default install media and is enabled through Add/Remove Windows Components. On Windows Embedded Standard SP3, MSMQ is an optional component that must be explicitly selected at image-build time using the Windows Embedded Standard - Image Configuration Editor (ICE) or ICE2. If MSMQ is not in the deployed WES image, the WinCC project context handler cannot resolve its queue bindings, and the ASO (Alarm/System Objects) layer reports an invalid project context.

Diagnostic confirmation path on the failing IPC 227D:

1. Open services.msc and look for Message Queuing and Message Queuing Triggers.
2. If only the Triggers entry exists and the main service is missing, MSMQ is not installed.
3. Run sc query msmq from an elevated command prompt — expected return is STATE: 4 RUNNING; on the failing unit the service is reported as 1060 (the service does not exist as an installed service).

3.2 Component-level cause — PDLRT.exe and ASO binding

WinCC V7.0 SP3 launches the runtime process PDLRT.exe from C:\Program Files\Siemens\WinCC\bin. PDLRT initializes the Alarm Logging subsystem (the ASO referenced in the error text), which subscribes to project-internal message queues backed by MSMQ. When MSMQ is missing, the ASO initialization callback returns a null context, the project is loaded into memory but the alarm channel cannot bind, and the runtime is terminated before any process window is opened.

3.3 Why the 30-minute AutoStart delay

The 30-minute wall-clock is the cumulative result of three serial waits inside the WinCC service-start chain. Each step polls the dependency for up to 10 minutes (the Windows service default), and there are three steps in series:

1. WinCC CCStartService waits on the MSMQ-dependent WinCC internal channel service (10 min).
2. The internal channel service waits on the OS MSMQ dispatcher (10 min).
3. PDLRT.exe waits on the alarm logging queue with a 10-minute retry window before logging the final AutoStart imposible message and exiting.

4. Diagnostic Procedure

Run the following checks in order on the failing IPC 227D. Each step produces a go/no-go that isolates one variable.

1. Confirm hardware and image. In the registry, navigate to HKLM\Software\Microsoft\Windows NT\CurrentVersion and read ProductName. Confirm Windows Embedded Standard with SP3. Confirm device under System Information is SIMATIC IPC227D.
2. Confirm MSMQ presence. Run sc query msmq and sc query MSMQTriggers. Both must report STATE: 4 RUNNING. If MSMQ is missing, stop here — this is the proximate cause.
3. Confirm WinCC installation integrity. Open Control Panel → Programs and Features and verify SIMATIC WinCC V7.0 SP3 is installed with no yellow warning icons. Re-run the installer in Repair mode if necessary.
4. Confirm project file permissions. The user account that runs the WinCC service must have Modify rights on the project directory and on C:\Program Files\Siemens\WinCC. The AutoStart impossible error can also be triggered by ACLs blocking the service from reading project.mcp.
5. Capture the WinCC startup log. Open C:\Program Files\Siemens\WinCC\diagnose (or \Diagnose on newer SPs) and read WinCC_SStart_<timestamp>.log and PDLRT_<timestamp>.log. Look for the string ASO, MSMQ, or queue. The presence of any of these confirms the MSMQ failure path described in Section 3.
6. Reproduce on a known-good OS. Copy the project to a workstation running Windows XP Professional SP3, install WinCC V7.0 SP3, and verify the project opens cleanly. If it does, the IPC 227D image is the variable — not the project.

5. Workarounds

The following are field-proven mitigations ordered from least to most invasive. None of them convert the IPC 227D into a Siemens-supported WinCC V7.0 SP3 target — see Section 6 for the supported path.

5.1 Workaround A — Add Message Queuing to the WES image

The proper engineering fix on the embedded image side. Re-author the WES image:

1. On the engineering workstation, open the WES SP3 image in Image Configuration Editor.
2. Under Components → Windows Components → Application Server enable Message Queuing and the Message Queuing Triggers sub-feature.
3. Also enable SNMP and WMI Scripting if they are not already present — WinCC telemetry depends on both.
4. Re-deploy the image to the IPC 227D using the Siemens SIMATIC IPC Image Creator or a bootable PE stick.
5. Boot, run sc query msmq, and confirm RUNNING.
6. Re-launch the WinCC project. The ASO error should no longer appear.

5.2 Workaround B — Manual launch from the Windows startup folder

If the embedded image cannot be re-authored (e.g. the unit is already at a customer site):

1. Create a shortcut to "C:\Program Files\Siemens\WinCC\bin\PDLRT.exe" with the appropriate project switch.
2. Place the shortcut in C:\Documents and Settings\All Users\Start Menu\Programs\Startup (or the equivalent path on the WES profile that the runtime user logs into).
3. Configure the WES auto-logon policy so the runtime user is logged in at boot.
4. Disable the WinCC AutoStart service so it does not race the manual launch.

This approach starts PDLRT.exe after a user session is established, which sidesteps the service-start dependency chain. It is not equivalent to a real AutoStart, and it does not survive a sudden power loss with the same recovery characteristics as a service-based start.

5.3 Workaround C — Scheduled task wrapper

A more deterministic version of Workaround B:

1. Open taskschd.msc and create a task named WinCC_RT_Start.
2. Trigger: At system startup, with Delay task for set to 2 minutes (give the OS time to bring up MSMQ, networking, and the SQL Anywhere engine used by WinCC).
3. Action: Start a program, with Program/script set to "C:\Program Files\Siemens\WinCC\bin\PDLRT.exe" and Add arguments set to the project path.
4. Conditions: clear Start only if on AC power; set Start only if the following network connection is available to Any connection.
5. General: select Run with highest privileges and the runtime service account.

This is the recommended interim measure when the WES image cannot be rebuilt — it survives a restart and provides a deterministic 2-minute boot delay rather than the 30-minute cascade seen with a broken AutoStart service.

6. Permanent Solution — Migrate to a Supported Platform

If the application is in design or commissioning, the cleanest path is to retarget the runtime to a supported combination:

Option A is the least disruptive: the existing .mcp project loads on an IPC 477C without changes, and the unit benefits from Siemens support coverage for the combination.

7. Comparison: Windows XP Pro SP3 vs Windows Embedded Standard SP3 for WinCC V7.0 SP3

The right column explains the symptom: a default WES SP3 image is missing multiple components WinCC V7.0 SP3 assumes are present. The MSMQ absence is the one that produces the specific ASO error text quoted above.

8. Error-Code Map

9. Verification

After applying Workaround A (preferred) or A combined with B/C, confirm the fix with the following checks:

1. sc query msmq returns STATE: 4 RUNNING.
2. services.msc shows SIMATIC WinCC CCStartService, SIMATIC WinCC Alarm Logging, and SIMATIC WinCC Runtime all in Started state.
3. Double-clicking project.mcp opens the runtime within 30 seconds with no ASO dialog.
4. WinCC startup log WinCC_SStart_<timestamp>.log contains no line with ASO or queue.
5. Reboot the IPC 227D. AutoStart should bring the runtime online in under 2 minutes (no 30-minute wait).
6. Trigger a test alarm in the project and confirm the entry appears in the WinCC alarm window and is written to the configured archive.

10. Preventive Checklist for New IPC 227D + WES SP3 Deployments

• Do not plan to run WinCC V7.0 SP3 Runtime on IPC 227D. Select IPC 477C or a TIA-based runtime.
• If a legacy WinCC V7.0 SP3 must be deployed on an embedded device, confirm with Siemens support (entry 48189693) that the specific IPC catalog number is on the released list.
• For any WES SP3 image that will host a WinCC runtime, use the Image Configuration Editor template that includes MSMQ, SNMP, WMI Scripting, DCOM, and SQL Anywhere runtime dependencies up front.
• Document the runtime start method (service, scheduled task, or startup folder) in the project Functional Design Specification so the maintenance crew knows the intended recovery path after a power loss.
• Always include a Windows XP Professional SP3 test workstation in the FAT (Factory Acceptance Test) rig so a project file that fails on a deployed panel can be validated on a known-good OS in under five minutes.