C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Resolving Process Object View Error 300 - 14 Database Disconnection in SIMATIC PCS 7

Resolving Process Object View Error 300 - 14 Database Disconnection in SIMATIC PCS 7

In SIMATIC PCS 7 (V9.0 SP3 / V9.1), opening or browsing the Process Object View (POV) that aborts with Error (300:14) 'The application has no connection to the database' is caused by desynchronized IPC pipe connections or broken socket handles between STEP 7 and the underlying Sybase SQL Anywhere database engine. This condition frequently occurs after resuming suspended virtual machines (VMware/Hyper-V) or following sudden network disconnects. To resolve this, terminate orphaned database processes ('s7ussapx.exe', 'dbeng*.exe'), perform a full computer restart, and execute 'Save As... with Reorganization (slow)' on the multiproject.

Table of Contents

Executive Summary

Process Object View (POV) is the central engineering workbench in SIMATIC PCS 7 for bulk parameterization, signal interconnection, and hierarchy management across large multiprojects. During engineering sessions, particularly on virtualized engineering stations (e.g., VMware Workstation, ESXi, or Microsoft Hyper-V), engineers occasionally encounter a sudden failure: selecting a chart, hierarchy folder, or parameter tab halts with the error dialog: Process Object View (300:14): The application has no connection to the database.

This error occurs because STEP 7 relies on an embedded Sybase SQL Anywhere database server engine to manage the engineering data dictionary. When a host virtual machine is suspended (paused) and later resumed, or when network shares experience temporary dropouts, the active inter-process communication (IPC) pipe between the SIMATIC Manager front-end and the local database server breaks. The client process cannot re-establish authentication against the existing database session, locking out the project. This guide outlines the immediate recovery steps, process termination rules, and project reorganization procedures required to eliminate Error 300:14.

Architecture and Fundamental Mechanics

The STEP 7 and Process Object View architecture utilizes a client-server relational database model behind the graphical interface:

  1. The Sybase SQL Anywhere Relational Engine:
    - Behind the STEP 7 project directory structure (*.s7p, *.mcp), project cross-references, block parameters, and hierarchy definitions are stored in Sybase SQL Anywhere databases (.db and transaction log .log files).
    - The database server executable (dbeng*.exe or dbsrv*.exe) runs locally or as a background service.
    - Communication between the engineering application (s7tgtopx.exe, s7ussapx.exe) and the database engine occurs via local Named Pipes or loopback TCP sockets.

  2. The Suspension / Resumption Disconnect Trap:
    - When a virtual machine hosting PCS 7 is suspended, the OS kernel freezes memory state and CPU execution.
    - Upon resuming the VM, Windows network sockets and local IPC pipe handles frequently experience desynchronization: the database server process registers an abandoned client connection, while the client application attempts to reuse stale socket handles.
    - When Process Object View executes a SQL query to load block instances, the request fails, triggering exception code (300:14): The application has no connection to the database.

  3. Database Locking and Stale Lock Files:
    - If SIMATIC Manager is forcibly closed while the database connection is broken, lock files (e.g., temporary .ldf, .dcf, or Sybase lock structures) remain on disk.
    - Subsequent attempts to reopen the project encounter locked tables, perpetuating the disconnection error until the database engine is completely restarted and caches are purged.

Step-by-Step Implementation Procedure

Follow these steps to recover from Error (300:14) and restore Process Object View access:

  1. Close SIMATIC Applications:
    - Close Process Object View, CFC Editor, SFC Editor, and SIMATIC Manager.
    - If any window hangs or refuses to close, use Task Manager to terminate the unresponsive applications.

  2. Terminate Orphaned Database and STEP 7 Processes:
    - Press Ctrl + Shift + Esc to open Windows Task Manager.
    - Switch to the 'Details' tab.
    - Look for and terminate any lingering instances of the following processes:

    • s7ussapx.exe (Process Object View server)
    • s7tgtopx.exe (AS-OS / CFC compiler engine)
    • dbeng*.exe / dbsrv*.exe (Sybase SQL Anywhere database engine)
    • CCDataMgr.exe / WinCC* (if WinCC components were active)
    • Right-click each process and select 'End task'.

  3. Restart the Operating System:
    - Perform a complete, clean restart of Windows (do NOT use suspend, hibernate, or fast startup).
    - Rebooting releases all locked file handles, resets named pipes, and guarantees a pristine network socket environment.

  4. Reopen and Reorganize the Multiproject:
    - After rebooting, launch SIMATIC Manager.
    - Open the multiproject.
    - Select 'File > Save As...'.
    - In the 'Save As' dialog, check the radio button 'with Reorganization (slow)'.
    - Specify a new project target directory and click 'OK'.
    - Allow the reorganization to sweep the Sybase database tables, rebuild indices, and remove corrupted cross-reference pointers.

  5. Verify Process Object View Functionality:
    - Open the newly reorganized project.
    - Navigate to 'View > Process Object View' (or press Ctrl + Alt + P).
    - Browse through the plant hierarchy, CFC charts, and parameters to confirm that data loads without error.

Verification

  1. In SIMATIC Manager, open Process Object View: verify that all tabs ('General', 'Blocks', 'Parameters', 'Signals', 'Messages') load data seamlessly.
  2. Filter by hierarchy folder: confirm that charts and blocks populate without delay.
  3. Make a test parameter change in POV (e.g., modify an alarm limit comment) and click 'Save': verify that the change commits cleanly to the database.
  4. Perform a consistency check ('Options > Plant Hierarchy > Check Consistency'): confirm zero database connectivity errors.

Limitations and Operational Precautions

Never suspend or pause virtual machines running SIMATIC PCS 7 while online monitoring, AS-OS compiling, or database editing is active; always shut down the guest operating system cleanly. In VMware environments, disable VMware Shared Folders on project directories to avoid file-locking conflicts. System licenses and engineering station configurations should be verified through an authorized Siemens distributor or the Siemens Industry Mall.

Engineer FAQ

What causes Error (300:14) in Process Object View?

Broken IPC named pipes or socket communication between the STEP 7 engineering interface and the local Sybase SQL Anywhere database engine.

Why does this error frequently occur after resuming a VMware virtual machine?

Suspending and resuming freezes and unfreezes the OS, causing network socket timeouts and broken inter-process database handles.

Does 'Save As with Reorganization (slow)' repair the database?

Yes. It rebuilds internal Sybase database pages, purges obsolete cross-reference records, and repairs index tables.

Can I prevent this error on virtualized engineering stations?

Yes, by always cleanly shutting down the guest OS instead of suspending the VM, and avoiding dynamic network adapter changes while STEP 7 is open.

What background process manages Process Object View?

s7ussapx.exe manages Process Object View application services.

Technical References

Related Articles

Related Tags

  • Process Object View
  • Error 300:14
  • Database Connection
  • Sybase SQL
  • VMware
  • PCS 7 V9.0 SP3
20 respuestas