WebUX screen settings can remain visible in the engineering project even when the PC has no WebUX server components. Project authoring, runtime installation, and license authorization are separate layers. The missing configurator therefore points first to installation media and installed features, not to the screen configuration or transferred license.
Installation and licensing mechanism
The term engineering capability here means the editor can store WebUX-related screen properties. It does not mean that the workstation contains the server software needed to publish those screens. The engineering installation exposes the project settings, while the server installation provides the runtime-side WebUX files and configurator.
| Observed condition | Meaning | Next check |
|---|---|---|
| WebUX screen options exist in engineering | The project editor recognizes WebUX configuration data | Identify the installation source |
WebUX Configurator is absent |
The WebUX server feature is not installed or its installation did not complete | Check the runtime media and installed feature set |
| WinCC Professional and WebUX licenses are transferred | Authorization is present | Confirm that the corresponding software binaries are installed |
| Engineering and runtime run on one PC | The roles are colocated | Verify each role independently; colocation does not add missing features |
A license enables installed software; it does not copy program files or create configuration utilities. Repeated license transfers will not restore a configurator that was never installed.
Check 1: Engineering-only symptom boundary
Open the project and inspect the existing WebUX screen setting. The expected reading is that screens can still be marked or enabled for WebUX while no runtime-side configurator is available on the PC.
If the screen option is present, treat the engineering installation as functional for this diagnosis and continue to the media check. Do not rebuild the project, remove the WebUX screen selections, or recreate screens. Those actions change project data but cannot add a missing server component.
If the screen option is also absent, the fault extends beyond the reported condition. Confirm that the project is opened with WinCC Professional V15 engineering software before following the server-installation branch.
Check 2: Installation source
Identify the exact media used for the current installation. Read the media label or mounted-image identity rather than relying on the applications presently listed on the PC.
Expected reading: the Web options, including WebUX Server, come from the WinCC Professional Runtime DVD. They are not included in the Engineering and Simulation installation source.
If setup was launched from Engineering and Simulation media, the missing WebUX selection and missing configurator are expected. Proceed to the resolving procedure with the Professional Runtime DVD. Running a runtime package or runtime simulation from the same workstation does not prove that WebUX Server was installed from the required media.
If the Professional Runtime DVD was used, continue to Check 3. The remaining distinction is between correct media with an omitted feature and correct media with an incomplete installation.
Check 3: Installed role and license state
Review the installed WinCC components or rerun the Professional Runtime setup in maintenance mode. Look specifically for the Web options or WebUX Server feature. Do not use the presence of base Runtime as a substitute reading.
If WebUX Server is absent from the installed feature set, add it from the Professional Runtime DVD. If the feature is reported as installed but the configurator is still absent, use the same media to repair or reinstall that feature, then check the installation log for a failed or skipped component. The log result decides whether setup completed normally; guessing from shortcuts does not.
After the binaries are present, verify the authorization separately. The expected reading for the reported configuration is a WinCC Professional license and a WebUX license transferred to the PC. If either authorization is unavailable to runtime, correct that license condition after installing the feature. Installing WebUX Server cannot substitute for its license, just as transferring the license cannot substitute for its installation.
Resolving installation procedure
- Close WinCC engineering and runtime applications so setup can service their shared components.
- Mount or insert the
WinCC Professional Runtime DVDthat corresponds to the installedV15system. - Start its setup and open the component-selection or maintenance path.
- Select the Web options entry containing
WebUX Server. If setup reports the feature as already installed, choose the available repair path for that component. - Complete setup and review its final status. Treat any failed or skipped WebUX component as unresolved and inspect the setup log before proceeding.
- Restart the PC if setup requests it.
- Locate and run the
WebUX Configurator, then apply the installation-specific server configuration required by the project. - Confirm that the transferred WinCC Professional and WebUX licenses remain visible to the installed runtime.
Use the same product generation across the existing engineering/runtime installation and the feature source. Do not substitute Engineering and Simulation media merely because it displays WebUX project properties.
Verification readings
-
Check 1: Installed component. Expect
WebUX Serverto appear among the installed or maintainable Professional Runtime features. If absent, return to the Runtime DVD component selection. -
Check 2: Configuration utility. Expect
WebUX Configuratorto be present and launch successfully. If it is missing while setup lists the feature, repair the feature and inspect the setup log. - Check 3: Authorization. Expect both the WinCC Professional and WebUX licenses to be available on the runtime PC. If the configurator opens but runtime rejects WebUX operation, resolve licensing rather than reinstalling engineering.
- Check 4: Project publication. Expect the screens selected for WebUX in engineering to remain selected after the server installation. A server installation should not require recreating those screen settings.
- Check 5: End-to-end access. Start the configured runtime and connect through the configured WebUX client path. Expect an enabled screen to open through WebUX; a missing-server result sends the diagnosis back to Checks 1 and 2.
FAQ
What happens if WinCC V15 shows WebUX screen options but no configurator?
The engineering editor can store WebUX screen settings without the server binaries. Install WebUX Server from the WinCC Professional Runtime DVD.
What happens if the WebUX license is transferred before WebUX Server is installed?
The license is present, but it does not deploy the server files or configurator. Add the WebUX Server feature first, then verify that runtime can access the transferred license.
What happens if engineering and runtime are installed on the same PC?
Each role still retains its own installed components. A combined workstation needs the WebUX server feature from the Professional Runtime media even though engineering already exposes the screen option.
What happens if WebUX Configurator is still missing after using the Runtime DVD?
Confirm that setup lists WebUX Server, repair that feature, and read the setup log for a failed or skipped component. Final verification is successful when the configurator launches and an enabled screen opens through the configured WebUX client path.