Resolving TIA Portal Step 7 Basic License Not Found Error

1. Problem Summary

The "License 'Step 7 Basic' was not found" error appears in Siemens TIA Portal when a user attempts to open an organization block (such as OB1) on an S7-1200 CPU project. The engineering station accepts device insertion in the project tree, but every attempt to open an editable block triggers the license dialog and refuses to load the editor. The same project may have been authored successfully on a different PC or under a prior TIA Portal version, which is what makes the symptom confusing.

This error is fundamentally different from a missing package, missing HSP (Hardware Support Package), or missing firmware support. It is a software entitlement error reported by the Automation License Manager (ALM) subsystem, which TIA Portal queries before opening any block editor. Because the check happens before the editor initializes, the user sees a license dialog instead of a hardware fault or a project file error.

The error is also version-aware. TIA Portal does not silently inherit a license from a previous major version, and it does not auto-upgrade a V14 license to a V15 entitlement just because the user installed the V15 binaries. A deliberate license upgrade step through ALM (or a fresh license transfer from the supplied USB) is required.

2. Affected Products, Versions, and Packages

The error has been observed against the following product matrix. Use it to determine whether the engineering station is in a supported state before pursuing license remediation.

Key insight: The license required to edit OB1 on an S7-1200 is "STEP 7 Basic". This is a separate SKU from "STEP 7 Professional" and is bundled by default in every Professional installer. If the engineering station reports a Professional license but the S7-1200 entitlement is missing or un-upgraded, the dialog will specifically cite "Step 7 Basic" — not "Professional".

3. Root Cause Analysis

The root cause is a license version mismatch between the TIA Portal binaries and the installed entitlement. There are four failure modes that produce this exact symptom:

1. V14 license present, V15/V15.1 binaries installed. The V14 key cannot satisfy the V15 entitlement check. TIA Portal will not auto-apply the V15 upgrade key, even if the upgrade license file is on the same USB stick or in the same delivery folder.
2. License present on a floating server but not cached locally. Floating licenses are served from a license server. If the engineering station is offline from the server at editor-open time, or the local lease cache is empty, ALM cannot find the entitlement locally and reports "not found".
3. USB transfer done, license not yet activated. Transferring a license .zip file from a USB stick to the local hard drive is not the same as installing the license. ALM must import and activate the file, or move it into the License Key Store, before TIA Portal can detect it.
4. Multiple ALM instances disagreeing on license state. Running ALM as a non-administrator while TIA Portal runs as administrator (or vice versa) can produce a store that one process can see but the other cannot. This is most common after UAC elevation.

4. TIA Portal License Architecture

Understanding how TIA Portal queries ALM is critical to diagnosing this error in any environment.

TIA Portal queries ALM through a named-pipe / IPC channel at editor-open time. If ALM returns a "not found" result for "Step 7 Basic", TIA Portal aborts the editor initialization and surfaces the dialog. There is no retry, no fallback to a lower version, and no prompt to install the license from a file.

5. Pre-Diagnosis Checklist

Run through this checklist before initiating the resolution. It isolates whether the problem is local entitlement, network entitlement, or installation state.

1. Open Automation License Manager from the Start menu. Confirm the application loads and displays the local license key store.
2. In ALM, expand the folder representing the local PC. Verify that a license with the exact name Step 7 Basic or Step 7 Professional (with embedded Basic entitlement) is listed.
3. Check the Validity column for each listed license. The status must read "Valid", not "Invalid" or "Expired".
4. Confirm the version tag of the license matches the version tag of TIA Portal. A license labeled V14 cannot satisfy a V15 entitlement check.
5. For floating licenses: confirm the configured license server is reachable (ping or Telnet on the ALM port, default 1947).
6. Confirm the user has logged in with the same Windows identity that originally received the floating license lease, or that the concurrent-user pool is not exhausted.
7. Check the TIA Portal version: Help → About. If it shows V15.1 but the license tag says V14, that is the defect.

6. Resolution Procedure

The standard recovery path follows this exact sequence. Do not skip the verification step between phases.

6.1 Phase A — Verify the License File Is on the Engineering Station

1. Insert the USB license media shipped with the TIA Portal DVD package.
2. Browse to the License folder. Look for a .zip file named S7Basic_V15_xxxxxxxx.zip or S7Pro_V15_xxxxxxxx.zip.
3. Copy the .zip to the local drive. Do not unzip — ALM imports the archive directly.

6.2 Phase B — Import the License Through ALM

1. Launch ALM as Administrator: right-click → Run as administrator.
2. Right-click the folder representing the local PC.
3. Select Open License Key Store.
4. Use the License Key → Install menu and point to the copied .zip file.
5. Confirm the new entry appears with status "Valid" and the correct version tag (V15 or V15.1).

6.3 Phase C — Apply the V15 Upgrade If Only a V14 Key Exists

1. Insert or mount the TIA Portal V15 upgrade media.
2. In ALM, right-click the existing V14 license entry (for example, "Step 7 Pro 14.0 floating unlimited").
3. Select License Key → Upgrade.
4. Browse to the upgrade .zip file corresponding to V15 or V15.1.
5. Complete the upgrade wizard. The original V14 entry will be replaced with a V15 entry.

6.4 Phase D — Re-launch TIA Portal as Administrator

1. Close all TIA Portal instances.
2. Right-click the TIA Portal shortcut and select Run as administrator.
3. Open the project, navigate to the S7-1200 PLC, and double-click OB1.
4. Confirm the editor opens without a license dialog.

7. Automation License Manager — Detailed Operation Reference

The following ALM operations are the standard toolkit for resolving license-state errors. Document the state before and after each operation.

For floating licenses, configure the license server under View → Settings → Connection. The default TCP port is 1947. If a firewall sits between the engineering station and the license server, this port must be open bidirectionally.

8. License Upgrade Workflow — V14 to V15 Family

Siemens ships the V15 upgrade as a separate .zip file on the installation media. The upgrade is not bundled with the V15 base installer, and it is not pulled automatically by the TIA Updater. The upgrade must be applied manually through ALM.

9. Verification Procedure

After applying the resolution, verify with these checks before resuming project work.

1. In ALM, confirm at least one license entry whose name contains "Step 7" and version tag matches the installed TIA Portal major version (V15 or V15.1).
2. Close and re-open TIA Portal as Administrator.
3. Open the affected project.
4. Double-click Main [OB1] under Program blocks. The block editor must open without prompting for a license.
5. Add a ladder network and confirm that FBD / LAD / STL edit operations complete without a "License missing" dialog appearing at compile or download.
6. Attempt a download to the S7-1200 CPU. The download will require the license once, even if online editing succeeds without it.
7. Check the TIA Portal status bar — there should be no red license indicator in the lower-right.

If step 4 fails with the same error after the license is installed, repeat Phase D and confirm TIA Portal was launched elevated. Mixed-elevation ALM access is the most common cause of false-negative verification.

10. Edge Cases and Related Errors

Several adjacent errors are commonly confused with the "Step 7 Basic not found" defect. Use this matrix to disambiguate.

11. Floating License Server Configuration

If the engineering station is configured against a floating license server, the resolution has additional layers. A floating license error that looks identical to a local "not found" can occur if the lease is unavailable.

1. Confirm the engineering station can reach the license server by hostname (DNS resolution and TCP 1947 connectivity).
2. In ALM, navigate to View → Settings → Connection. Verify the server hostname or IP is correct.
3. Right-click the server entry and select Connect. ALM will refresh the visible licenses.
4. Confirm the user has available slots. Floating licenses can be configured as "named user" (locked to a Windows identity) or "concurrent user" (a shared pool). If the pool is exhausted, the error appears identical to "not found".
5. Use License Key → Borrow to take a lease offline if the workstation will be disconnected from the server during commissioning.

12. Prevention and Best Practices

To prevent recurrence on multi-user engineering sites:

• Maintain a written record of every engineering station's TIA Portal major version and the matching license version. Treat version upgrades as a coordinated change.
• Apply license upgrades at the same maintenance window as TIA Portal upgrades. Do not let the binaries advance beyond the entitlement.
• Standardize on a single ALM elevation model across the engineering team. Mixing elevated and non-elevated launches leads to ghost license states.
• For floating licenses, deploy redundant license servers with active failover, or use the Siemens license server high-availability pattern.
• Archive the original license .zip files in a project-share location that survives PC replacement or OS re-imaging.
• Configure TIA Administrator to default all new project templates to the lowest version of TIA Portal installed on the site, to prevent users from opening a V15 project on a V14-only PC.
• Schedule a quarterly audit of the License Key Store across all engineering stations. Compare the installed keys against the purchased entitlements in the Siemens license tracking portal.

13. When to Escalate

If the resolution above does not clear the error, escalate to Siemens Technical Support with the following bundle:

• Screenshot of the ALM local license key store.
• TIA Portal version (Help → About, full output).
• Output of C:\ProgramData\Siemens\Automation\LogFiles\almservice.log filtered to the last hour.
• Windows event viewer application log filtered for ALM and TIA Portal sources.
• The exact error text including timestamp and project name.

Siemens Technical Support for TIA Portal licensing is reachable through the Siemens Industry Online Support portal, where license-related service requests can be filed under the "License" topic. Do not disclose license keys in service requests — Siemens support will never ask for the key itself.

14. FAQ