Fixing TIA Administrator Server Not Running Error in TIA Portal

1. Problem Overview

Engineering workstations running Siemens TIA Portal V16 Update 4 and V17 can fail to launch the TIA Administrator web front-end. The browser opens directly to the TIA Administrator URL but displays the message:

The TIA-Administrator server is currently not running, please wait for some time and reload the page. If the problem persists, please check the service in the service control panel.

The TIA Administrator client is a browser-based management tool that wraps two related utilities:

• TIA Administrator (V1.0 / V2.x / V3.0) - the web UI used to manage installed TIA Portal instances, language packs, licenses, and update channels.
• TIA Updater - the background updater that pulls patches, HSPs (Hardware Support Packages), and language data from the Siemens update server or a configured offline source.

When the underlying Windows service fails to start, neither tool responds. The error is independent of which browser is used and is not a network, proxy, or browser-cache fault.

2. Symptoms and Error Messages

Typical observable symptoms across V16 and V17 workstations:

Browser screenshots typically capture the TIA Administrator splash/login page rendered as plain HTML with the inline error text, no Siemens logo, and no interactive controls. This is the diagnostic fingerprint of a back-end service that never bound to the configured TCP port.

3. Root Cause Analysis

Four root-cause families account for almost every reported case:

1. TIA-Administrator Windows service is not running. The service is registered at install time but defaults to Manual start. After a reboot, a Windows feature change, or a Service Control Manager reset, it remains in the Stopped state until manually started.
2. WMIC (Windows Management Instrumentation Command-line) is disabled or removed. Starting with TIA Administrator V3.0, the TIA-Administrator service uses WMIC to enumerate installed TIA Portal instances and to query OS-side product data. Microsoft has deprecated WMIC; the component is disabled by default on Windows 10 21H2 and removed/disabled on Windows 11 24H2 and Windows Server 2022 cumulative updates released after April 2024. Siemen's official KB entry 109976735 documents this exact failure mode.
3. Underlying .NET / ASP.NET hosting components missing. TIA Administrator V2/V3 hosts its web UI in a self-contained Kestrel-style process but still depends on .NET Framework 4.8 and the Windows Process Activation Service. A stripped Server Core image or a manually trimmed Windows 10 SKU may lack these.
4. Corrupted or partially installed TIA Portal instance. TIA V16 and V17 share registry entries under HKLM\SOFTWARE\Siemens\Automation\. A failed V17 install after a working V16 leaves the Administrator service in a confused state.

4. Pre-Diagnostic Checklist

Run the following before changing anything. Capture the output so you can confirm the fix later:

1. Confirm Windows version and build. Open winver from the Run dialog. Record the exact build number (e.g., 10.0.19045.4526 or 10.0.22631.4391). Windows 10 21H2 and Windows 11 24H2+ are the high-risk builds for the WMIC failure.
2. Confirm TIA Portal inventory. Launch TIA Administrator from the Start Menu and, if it ever worked, use the top-right info icon. Otherwise open Control Panel → Programs and Features and note each Siemens SIMATIC TIA Portal entry, its version, and update level (e.g., V16 Update 4, V17, V17 Update 3).
3. Capture the Administrator service state. Press Win, type services.msc, press Enter. Accept the UAC prompt. Locate the TIA-Administrator service. Record: Display Name, Service Name, Status, Startup Type, and the identity of the Log On As account.
4. Capture application event log. Open eventvwr.msc and navigate to Windows Logs → Application. Filter the source to .NET Runtime and Service Control Manager. Note any error entries from the last 24 hours referencing Siemens, TIA, wmic, or System.TypeLoadException.
5. Confirm WMIC availability. Open an elevated Command Prompt and run where wmic and wmic os get caption. A missing executable or a "not recognized as an internal or external command" error confirms the root cause.

5. Solution 1: Start the TIA Administrator Windows Service

This is the answer referenced verbatim in the on-screen error message and resolves cases where the service is simply stopped.

Step-by-step

1. Open the Services console with administrative rights: press Win, type services.msc, right-click the result and choose Run as administrator.
2. Locate the service named TIA-Administrator (Display Name) / Siemens TIA Administrator Server (or similar Service Name). Sort by Description to find it quickly - the description contains "Totally Integrated Automation".
3. Right-click the entry and choose Properties. On the General tab, set Startup type to Automatic (Delayed Start). This is preferred over plain Automatic to avoid boot-time contention with SQL Server, SIMATIC Logon, and other TIA-related services.
4. Switch to the Log On tab. The default LocalSystem account is acceptable for single-user engineering workstations. For domain-managed PCs where TIA Portal project data lives on a network share, switch to This account and specify a domain service account with read/write rights to the project paths.
5. Click Apply, then Start. The service status should transition to Running within 2-5 seconds.
6. Re-launch TIA Administrator from the Start Menu. The error message should be replaced by the TIA Administrator landing page.

Command-line equivalent

For automation, scripting, or remote remediation:

# Query current state
sc query "Siemens.Automation.TiaAdministrator"

# Set startup type to delayed-auto
sc config "Siemens.Automation.TiaAdministrator" start= delayed-auto

# Start the service
sc start "Siemens.Automation.TiaAdministrator"

# Confirm running PID
sc queryex "Siemens.Automation.TiaAdministrator"

Replace the service name string with the exact value shown in services.msc if it differs on your build.

6. Solution 2: Enable WMIC in Windows

Siemens KB 109976735 confirms that TIA Administrator V3.0 cannot start when WMIC is disabled. This applies to any V17+ installation whose Administrator component updated to V3.0. The fix re-enables the Windows feature that Microsoft turned off by default.

Why WMIC matters

WMIC is the legacy command-line and scripting interface for Windows Management Instrumentation. TIA Administrator V3.0 calls wmic product get name,version, wmic os get caption,version, and wmic process where name="Siemens.Automation.Portal.exe" during startup to enumerate installed TIA Portal products. If WMIC is absent, the startup probe returns null and the service treats it as a fatal configuration error.

Step-by-step re-enable (Windows 10 / 11 GUI)

1. Open Settings → Apps → Optional features (Windows 10) or Settings → System → Optional features (Windows 11).
2. Click Add an optional feature (Windows 10) or View features next to "Add an optional feature" (Windows 11).
3. Search for WMIC. On Windows 11 24H2 it appears as WMI Command-line Tool (WMIC).
4. Tick the entry, click Install.
5. Reboot when prompted.
6. Verify by opening an elevated Command Prompt and running wmic os get caption,version,buildnumber. A version table should print.

Step-by-step re-enable (PowerShell)

# Check WMIC capability state
Get-WindowsCapability -Online -Name "WMIC~~~~" | Format-List Name, State

# If State = NotPresent, install it
Get-WindowsCapability -Online -Name "WMIC~~~~~" | Add-WindowsCapability -Online

# Alternative: re-enable the legacy feature path
dism /online /enable-feature /featurename:"WMIC" /all

# Verify
wmic cpu get name

Step-by-step re-enable (Windows Server, Server Core)

1. Mount the Windows install media or specify a /source path to sxs.
2. Run dism /online /enable-feature /featurename:WMIC /all /source:D:\sources\sxs /limitaccess.
3. Reboot.

7. Solution 3: Repair TIA Portal Installation

If the service is configured correctly and WMIC is present, but the Administrator still fails, repair the installation. This re-registers the service, refreshes its ACLs, and rebuilds the Siemens.Tia.Administrator.Service.exe shadow-copy folder.

1. Close TIA Portal, TIA Administrator, and TIA Updater.
2. Open Control Panel → Programs and Features.
3. Right-click Siemens SIMATIC TIA Portal (the version showing the issue - V16 or V17) and select Repair.
4. Accept the UAC prompt. The installer re-runs the original MSI/Setup sequence in repair mode. This typically takes 5-15 minutes.
5. Reboot the workstation when prompted.
6. Re-test TIA Administrator.

If repair fails or the entry is missing, run the original TIA Portal setup .exe as administrator and choose Modify → Repair from the installer menu.

8. Solution 4: Configure TIA Administrator for Language Management

The original use case behind the symptom - switching TIA V17 to French - is a common TIA Administrator workflow. The language packs are not stored inside the base install; they are pulled by the TIA Updater after being authorised through TIA Administrator.

1. Once the service starts (Solutions 1-3), launch TIA Administrator from the Start Menu. The landing page shows the installed TIA Portal products.
2. Select TIA Portal V17 in the product list.
3. Open the Languages tab.
4. Tick the target language (e.g., Français).
5. Click Install selected languages. TIA Updater opens in a separate window and downloads the language pack from the Siemens update server.
6. When the download completes, restart TIA Portal V17 once. The language switch takes effect on next launch.

Offline language install

For air-gapped or proxy-restricted networks, TIA Updater supports an offline download mode:

1. On a connected PC, run the TIA Updater and choose Export update package.
2. Copy the resulting .zip container to the offline engineering workstation.
3. In TIA Administrator, choose Import update package and select the file.

9. TIA Portal Update Path Considerations

The discussion thread references TIA V16 Update 4, TIA V17 (no specific Update), and TIA Administrator V1.0. Mismatched versions are a frequent cause of the symptom.

Apply updates in this order:

1. Update TIA Administrator itself to the newest release available on the Siemens support portal.
2. Update TIA Portal V16 to the latest Update.
3. Update TIA Portal V17 to the latest Update.
4. Reboot between updates when prompted. The TIA Updater prompts for reboots but does not always enforce them.

10. Verification and Acceptance Test

After applying any of the solutions above, run the following checks. Each must pass before the workstation is returned to production.

1. Service health. sc query "Siemens.Automation.TiaAdministrator" returns STATE : 4 RUNNING.
2. Web UI reachability. Open the TIA Administrator landing page in Edge, Chrome, or Firefox. The page must list each installed TIA Portal product within 5 seconds of navigation.
3. WMIC round-trip. Run wmic product where "vendor like 'Siemens%'" get name,version. The output should enumerate every installed Siemens automation product. If the output is empty or returns an error, WMIC is still misconfigured.
4. TIA Updater connectivity. Launch TIA Updater directly. It should connect to the local Administrator server without showing the "No server connection" banner.
5. Language round-trip. In TIA Administrator, add a test language pack (or remove and re-add an existing one). The download must start within 30 seconds.
6. Event log clean. In eventvwr.msc, clear the Application log, perform the round-trip steps above, then re-check. No new .NET Runtime error 1026 or Service Control Manager 7034 entries should appear.
7. Survive reboot. Reboot the workstation. After logon, the TIA-Administrator service must auto-start and the web UI must be reachable without any user interaction.

11. TIA Administrator Service Architecture Reference

For engineers troubleshooting a wider deployment, the following reference data is useful when correlating logs and designing monitoring scripts.

Common event-log patterns and meanings

PowerShell readiness script

Use this snippet on multiple engineering workstations as part of a deployment readiness audit:

$svc = Get-Service -Name "Siemens.Automation.TiaAdministrator" -ErrorAction SilentlyContinue
if (-not $svc) {
    Write-Warning "TIA Administrator service is not registered."
    return
}

Write-Host "Service status : $($svc.Status)"
Write-Host "Startup type   : $($svc.StartType)"

# WMIC presence
$wmic = Get-Command wmic -ErrorAction SilentlyContinue
Write-Host "WMIC available : $([bool]$wmic)"

# .NET Framework version
$net = Get-ChildItem "HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" -ErrorAction SilentlyContinue
Write-Host ".NET 4.x release: $($net.GetValue('Release'))"

# Connectivity probe
try {
    Invoke-WebRequest -Uri "http://localhost:58472/" -UseBasicParsing -TimeoutSec 5 | Out-Null
    Write-Host "Web UI         : reachable"
} catch {
    Write-Warning "Web UI not reachable on default port."
}

Adjust the localhost port to match your local TIA Administrator binding, visible in appsettings.json.

12. Frequently Asked Questions