Resolving SIMATIC PDM Project Converter Freezes and Database Lockups During Project Upgrades

When the SIMATIC PDM Project Converter freezes or stops responding during project migration in SIMATIC PCS 7, the failure is typically caused by missing Electronic Device Descriptions (EDD) in the local device catalog, corrupted device database indices, or active SQL database locks. To resolve the freeze, terminate hung PDM background processes via Task Manager, open the Device Integration Manager (DIM) as an administrator to reinstall missing EDDs, re-catalog the device library, and ensure the project path does not exceed Windows path limitations. Re-running the conversion on an unlocked project completes the migration cleanly.

SIMATIC PDM Project Migration Architecture and Converter Mechanics

SIMATIC Process Device Manager (PDM) integrates intelligent field instrumentation—such as HART, PROFIBUS DP/PA, and PROFINET devices—into the SIMATIC PCS 7 engineering environment. When upgrading a project from an earlier PCS 7 release (e.g., PCS 7 V7.1 or V8.0 to V8.2/V9.0), the project's field device data structure must be transformed to match the newer PDM database schema.

The SIMATIC PDM Project Converter automatically initiates upon opening a legacy project. It scans the hardware configuration (HW Config), locates each field instrument instance, and matches its parameters against the Electronic Device Description (EDD) library registered in the local Device Catalog. If a referenced device descriptor cannot be resolved or if database handles collide, the converter enters an infinite wait state.

Root Causes of Converter Freezes and Process Lockups

Field analysis indicates four primary failure mechanisms during PDM project conversion:

Missing EDDs in Device Catalog: If a legacy transmitter (e.g., SITRANS P DS III or a third-party HART flowmeter) has no matching device description installed in the new PDM catalog, the converter queries missing dependencies without timing out.
Orphaned Background Processes: Background services such as pdmserver.exe, pdmstarter.exe, or s7wsvaps.exe from prior failed attempts retain shared locks on the project's PDM database files.
Path Length and Special Characters: STEP 7 and PDM struggle with folder paths exceeding 260 characters or directory names containing non-ASCII characters or spaces.
Database Index Corruption: Abrupt shutdowns or incomplete earlier migrations can corrupt the local PDM repository index, causing SQL Server Express (the PDM database backend) to dead-lock during transaction replay.

Device Integration Manager (DIM) and EDD Device Catalog Synchronization

The Device Integration Manager (DIM) is the authoritative utility responsible for importing, updating, and compiling device descriptions:

Always open DIM from the Windows Start menu under Siemens Automation -> SIMATIC -> PDM -> Device Integration Manager with elevated administrator privileges.
Point the source directory to the latest SIMATIC PDM Device Library DVD (Device Library 1#YYYY or 2#YYYY) or manufacturer-supplied EDD archives.
Perform a complete catalog update. DIM compiles the XML/EDD structures into the binary catalog cache, ensuring that the Project Converter can instantly resolve hardware device IDs without hanging.

Resolving SQL Database Locks and Stale Background Processes

When the converter locks up:

Open Windows Task Manager -> Details tab.
Terminate all instances of pdmserver.exe, pdmstarter.exe, pdmadmin.exe, and s7epa64x.exe.
Verify that the Microsoft SQL Server instance used by WinCC and PDM (WINCC or SIMATIC_PDM) is running normally without excessive CPU throttling.
Clear temporary conversion scratch files located in C:\ProgramData\Siemens\Automation\SIMATIC PDM\Temp or the project subfolder \pdm\.

Comparative Diagnostic Matrix: PDM Conversion Faults and Resolutions

The following table categorizes common PDM conversion failure symptoms and their direct remedies:

Failure SymptomUnderlying MechanismPrimary IndicatorRemediation ActionConverter hangs at 0% or initial scanMissing EDD or obsolete device catalogCPU usage at 0%, no disk activityRun Device Integration Manager; install latest Device Library DVDError: Database locked by another processOrphaned PDM background servicesFile lock on <Project>\pdm\*.dbTerminate pdmserver.exe in Task Manager; restart SIMATIC ManagerConverter crashes midway with memory exceptionCorrupted project temporary cacheEvent Viewer application error 1000Clear C:\ProgramData\Siemens\...\Temp; execute project reorganizationDevice appears with red cross in HW ConfigDevice description version mismatch'Device description not found' in PDMManually re-assign device object in PDM Network ViewAccess Denied during catalog compileInsufficient Windows user permissionsDIM reports 'Write error on catalog'Run DIM as Administrator; verify user is in SIMATIC HMI group

Step-by-Step Recovery and Migration Workflow

Execute the following recovery workflow to convert stalled PDM projects successfully:

Kill Hung Processes: Close SIMATIC Manager and kill any lingering pdm*.exe processes via Task Manager.
Backup Project: Create a zip archive of the unconverted legacy project folder.
Update Device Catalog via DIM: Launch Device Integration Manager as Administrator. Insert the latest PDM Device Library media. Select all relevant manufacturer folders (Siemens, Endress+Hauser, Emerson, ABB, Yokogawa) and execute Catalog Update.
Reorganize STEP 7 Project: Open SIMATIC Manager. Navigate to File -> Save As... with the checkbox 'With Reorganization (Slow)' enabled. Save to a short local directory path (e.g., C:\Projects\Prj_Reorg).
Initiate PDM Conversion: Open the reorganized project in SIMATIC Manager. When prompted to convert the PDM database, click OK.
Observe Completion: Allow the conversion progress bar to finish. Verify that all field instruments appear healthy in the Process Device Plant View.

Verification

Verify successful PDM migration through these validation checks:

Process Device Plant View: In SIMATIC Manager, switch to the Process Device Plant View. Confirm all instruments are listed without warning flags.
Online Device Communication: Open PDM on a test instrument (e.g. pressure transmitter). Execute Device -> Upload to PG/PC. Confirm parameter upload completes without communication timeouts.
Device Diagnostics: Confirm that PDM diagnostic views display online status, sensor health, and maintenance flags.
HW Config Consistency: Open HW Config. Perform Station -> Check Consistency. Ensure zero errors regarding missing slave descriptions.

Limitations and Operational Precautions

Observe the following technical constraints:

Version Support Boundaries: Very old PDM versions (PDM V5.x) cannot be converted directly to PDM V9.0. An intermediate migration step via PDM V6.0 or V8.0 is strictly required by Siemens migration specifications.
Catalog Immutability During Conversion: Never open or modify the PDM Device Integration Manager while a project conversion is actively executing.
Commercial Accuracy Disclaimer: Software order numbers (MLFBs), package structures, and hardware capacity prerequisites vary across PCS 7 versions and hardware platforms. System integrators must confirm exact software entitlements and licensing requirements against the official Siemens Catalog CA 01 and obtain an authorized Siemens distributor quotation prior to purchasing.

Engineer FAQ

What processes should I kill if PDM Project Converter hangs indefinitely?

Kill pdmserver.exe, pdmstarter.exe, and pdmadmin.exe in Windows Task Manager, then restart SIMATIC Manager.

Does PDM conversion alter my PLC logic or CFC charts?

No. PDM conversion updates the field device parameterization database and HW Config device associations; it does not alter CFC algorithm logic or function blocks.

Where are missing EDDs obtained if they are not on the Siemens Device Library DVD?

Missing EDDs must be downloaded directly from the field instrument manufacturer's official support portal and imported into PDM via Device Integration Manager.