S7-400 Station Configuration Editor Import Resource Error Fix

The "resource lack in the system" message emitted by the SIMATIC NET Station Configuration Editor (SCE) when importing an .xdb file for an S7-400 PC station is one of the most common commissioning blockers for STEP 7 V5.x projects that mix PROFIBUS and Industrial Ethernet on a single SIMATIC PC Station. The fault almost never originates inside SCE itself; it is a downstream symptom of (a) a Simatic Net Application/Driver version mismatch in HW Config, (b) a SOFTNET licensing ceiling that prohibits more than one CP of a given bus family, or (c) corruption of the previous station configuration on the PC. This reference walks through the precise diagnostic path Siemens support uses to clear the error and return the PC station to a usable state, including the exact HW Config slot, the version strings to read, the order numbers for the SOFTNET vs. HardNet CPs that govern the limit, and a rebuild procedure when the configuration database is unrecoverable.

1. Problem Overview

The Station Configuration Editor ships with the SIMATIC NET PC software and acts as the runtime manager for any SIMATIC PC Station configured in STEP 7 / HW Config. When you right-click a PC Station in the SCE and select Import Station…, SCE parses an XML-derived .xdb file (the export of an HW Config station) and reconciles it against the installed CP drivers, OPC server instances, S7 protocol stacks, and Application slots. If the reconciler cannot bind every configured Application (e.g., Application SW V6.3) to a matching runtime DLL, or if the configuration exceeds what the active SOFTNET license permits, SCE aborts the import with the dialog shown in the field reports:

"Error importing station configuration. The configuration could not be installed. There is a resource lack in the system."

The same dialog appears when the imported station declares a CP that is not physically present (or not licensed) on the target machine, or when a previously configured CP slot is still flagged "configured" in the Configuration Console even though its driver was uninstalled.

2. Symptom Details and Field Conditions

The classic field signature, all confirmed on S7-400 systems in production environments:

• Project runs correctly in the office on a development S7-400 test rack.
• The same .xdb file fails on the target factory PC after SCE import.
• PC Station declares a PROFIBUS CP for FDL connections AND an Industrial Ethernet CP for the S7 connection to the engineering station.
• Only one of the two CP types lights up; the other shows a yellow/red fault in the SCE status bar.
• No Windows Device Manager error; the CP cards are physically enumerated and drivers load.
• Restarting the S7 Communication Service (s7oiehsx) does not clear the fault.

Two of these symptoms together should immediately direct you to the two root causes examined in §4.

3. Affected Software and Hardware Versions

4. Root Cause Analysis

Three root causes account for >95% of the field cases. Each must be eliminated in order.

4.1 Simatic Net Application Version Mismatch (most common)

Every SIMATIC PC Station slot in HW Config carries an Application entry such as:

• Application SW V6.2 SP1
• Application SW V6.3
• Application SW V7.0
• Application SW V8.2

During SCE import, SCE looks up that Application string in the registry under HKLM\SOFTWARE\Siemens\AUTSW (and the WOW6432Node mirror on x64) and in the %ProgramFiles%\Siemens\Automation\SIMATIC_NET\bin Application index. If the PC has drivers installed for, say, V6.2 SP1 only, but the imported station declares "Application SW V6.3", SCE cannot resolve the binding and aborts with the resource error. The error message is identical to a true resource-exhaustion fault, which is why the issue is so often mis-diagnosed.

4.2 SOFTNET Multi-CP Licensing Ceiling

Each SOFTNET product on the PC (SOFTNET-IE S7, SOFTNET-DP, SOFTNET-PB S7, SOFTNET-S7 PCI) authorizes exactly one CP of that bus family. When an HW Config declares two Industrial Ethernet CPs (or two PROFIBUS CPs) under the same PC station, SCE cannot install the second instance because the license does not cover it. The first CP installs cleanly; the second slot remains unbound; the SCE reconciler reports the overall station as unimportable.

4.3 Residual "Configured" State in the Configuration Console

When a CP is uninstalled or its driver is rolled back, the SIMATIC NET Configuration Console may continue to show that index as configured with a stale Application binding. The next SCE import then collides with the ghost binding and fails. Configuration Console is reached via Start → SIMATIC → SIMATIC NET → Configuration Console, or the tray applet Configuration Console. Inspect every CP index under Modules → [Bus] → CP index; a green "configured" LED on hardware that is no longer present is a fault indicator.

5. Diagnostic Workflow

1. Capture the imported configuration. Open the .xdb file in a text editor or in HW Config via Station → Open…. Note every Application index string and every CP slot entry.
2. List the installed Applications. In Configuration Console select SIMATIC NET → Applications and write down the names exactly as displayed. Compare to the .xdb strings character-for-character (including service pack suffixes such as "SP1" or "SP2").
3. List the installed CP drivers. In Configuration Console select SIMATIC NET → Modules. Each IE CP appears under Industrial Ethernet; each PROFIBUS CP appears under PROFIBUS. A module showing yellow triangle with "not configured" is the failure point.
4. Cross-check the bus family CP count against licensing. If more than one CP per bus family appears under Modules, verify that the licenses are HardNet CP (CP 1613 / 1623 / 5613 / 5614) and not SOFTNET. See the order number mapping in §6.2.
5. Inspect the SCE event log. From the Station Configuration Editor main window select Options → Event Display. Resource-lack events are logged with the symbol 0xFFxx8012 or similar internal codes; note the CP index and Application index from the entry.
6. Capture the installed SIMATIC NET version. In Start → Control Panel → Programs and Features, look for entries beginning with SIMATIC NET. The PC Software base version is the master reference; Application index strings must align with it.
7. Decide on a fix path. If the Application version mismatches the PC install, go to §6.1. If the CP count exceeds SOFTNET, go to §6.2. If a ghost binding persists, go to §6.3.

6. Solution Procedures

6.1 Align the HW Config Application Version to the Installed Driver

This is the fix that resolved field reports (Application SW V6.3 declared, V6.2 SP1 installed). Apply it whenever the .xdb Application string and the PC install do not match.

Option A — Re-target the HW Config project (preferred when the project is still under engineering):

1. Open the project in STEP 7 V5.x.
2. Open HW Config on the PC Station.
3. Click the Application slot in slot 2 of the PC station rack.
4. Read the Version property; note any SPx suffix.
5. Right-click → Properties; in the dialog replace the version string with the one installed on the target PC (e.g., change "Application SW V6.3" to "Application SW V6.2 SP1").
6. Save, recompile, re-export the station as .xdb.
7. Re-import in SCE.

Option B — Upgrade the PC installation to match the project:

1. Obtain the matching SIMATIC NET DVD or download package from the Siemens Industry Online Support portal. The release matrix is documented in the SIMATIC NET PC Software release notes.
2. Install the upgrade. Existing station configuration is preserved only if the installer is the same major version; otherwise, capture an SCE backup first via Station → Export.
3. Reboot; verify in Configuration Console that the new Application index appears under Applications.
4. Re-import the original .xdb.

6.2 Lift the SOFTNET CP-Count Ceiling with a HardNet CP

When the project legitimately requires more than one CP per bus family (e.g., a redundant Ethernet pair to two separate S7-400 CPUs, or a PROFIBUS CP plus a CP for an HMI panel), SOFTNET is the wrong product. Upgrade the PC-side CP hardware to a HardNet family module:

After the hardware swap:

1. Install the HardNet driver from the SIMATIC NET DVD matching your PC Software major version.
2. In HW Config, replace each SOFTNET CP slot with the equivalent HardNet catalog entry (CP 1623 instead of CP 1612 SOFTNET-IE; CP 5614 A2 instead of CP 5611 SOFTNET-DP). The slot stays in the same position.
3. Re-export the .xdb.
4. Import in SCE; both CP slots should now come online (green status).

6.3 Clear Ghost Configuration Bindings and Rebuild

When the Configuration Console holds residual entries from a previous install, a clean rebuild is faster than incremental surgery.

1. Open SCE, right-click the PC Station name → Export Station. Save the backup .xdb outside the install path.
2. Stop the SIMATIC NET services: net stop "S7 Communication Service", net stop "SIMATIC NET Configuration Service", net stop "SIMATIC NET OPC Server" (if present).
3. Run the SIMATIC NET uninstaller from Control Panel → Programs and Features. Reboot.
4. Reinstall the SIMATIC NET PC software matching the project's Application version (target version should be the highest version that matches the HW Config Application string of every PC station you intend to load).
5. Reboot. Confirm in Configuration Console that all module indices show "not configured" / no green LED.
6. In SCE choose Station → Import Station… and load the saved .xdb. The import should now complete without resource errors.
7. Test the S7 connection with Start → SIMATIC → STEP 7 → Accessible Nodes, or via the OPC Scout on the OPC server slot.

7. Verification

A successful SCE import is only the start. Walk the full stack to confirm the S7-400 is actually reachable:

1. In SCE, the PC Station status bar shows the green "station is configured" message; all CP icons are green.
2. In Configuration Console, every CP index displays the configured Application binding with no warning triangle.
3. The Windows service S7 Communication Service (binary s7oiehsx.exe) is in RUNNING state. Verify with sc query s7oiehsx.
4. STEP 7 Accessible Nodes lists the S7-400 CPU by its MPI/Profibus/Ethernet address.
5. Online in the S7 program: download blocks, view a VAT, force a single output momentarily to confirm the round-trip.
6. For FDL-bound PROFIBUS traffic, verify with Start → SIMATIC → STEP 7 → NCM S7 → PROFIBUS → Diagnostics that the CP is in OPERATE and the partner station is listed.
7. For the S7 Ethernet connection, run Start → SIMATIC → SIMATIC NET → Commissioning → S7 Connection Diagnostics and confirm Status = Established.

8. Related Error Conditions and Their Codes

9. Best Practices for Future PC Station Projects

• Lock the SIMATIC NET PC Software major version to one release for the lifetime of the machine. Track each PC station's HW Config Application string in the project header comment; enforce it as a reviewable property.
• Keep the .xdb under version control (SVN, Git, TIA-style project vault). A diff between two .xdb files will show every Application and CP change in seconds.
• Prefer one CP per bus family. If you must add a second, swap to HardNet from day one — DO NOT stack two SOFTNET instances.
• Use the SIMATIC NET Configuration Console's Export function as part of the backup before every driver change. Store the export alongside the STEP 7 project.
• Document the CP index assignments. Slot 1 is always IE General; slots 2–4 are Applications; slots 5+ are user CPs. Mark them explicitly in the rack diagram.
• After every SIMATIC NET major upgrade, perform a clean install on at least one test PC station and validate the full .xdb import before rolling out to production.
• For S7-400 systems, set the CP 443-1 (on the PLC side) firmware to V3.x or higher and align with the PC station's IE CP for the cleanest online diagnostics.

10. Platform and Migration Notes

The Station Configuration Editor is the STEP 7 V5.x mechanism. In TIA Portal, the equivalent is the PC System configuration inside the project itself, with runtime management delegated to the SIMATIC NET OPC UA Server or the TIA-integrated S7 communication. A V5.x .xdb cannot be imported directly into TIA Portal. If you are migrating an S7-400 fleet to TIA Portal:

1. Use the Migrate Project wizard in TIA Portal to bring the S7-400 hardware and program across.
2. Re-create the PC Station from scratch in TIA Portal; the SCE workflow does not carry over.
3. Repoint any OPC client applications from the SIMATIC NET OPC server to the TIA OPC UA server.

Until that migration is complete, retain one engineering seat on STEP 7 V5.6 with the matching SIMATIC NET V8.2 to support legacy PC stations; the two product lines coexist on the same Windows 10 / Windows 11 machine provided the SIMATIC NET releases are kept distinct in their install directories.

11. Quick Field Checklist

1. Open Configuration Console → Applications. Note installed Application strings.
2. Open the project .xdb. Note declared Application strings.
3. If they differ, change the project to match the install (or upgrade the install).
4. Count CP slots per bus family in the project. If > 1, confirm HardNet CPs on the PC.
5. Re-export the .xdb.
6. In SCE, delete the existing PC Station entry and re-import.
7. Verify in Accessible Nodes and via a live VAT download.

FAQ