Troubleshooting SIMATIC Information Server 2014 SP3 Installation and Setup Failures
Installation and setup aborts with SIMATIC Information Server 2014 SP3 on Windows Server 2016 typically occur due to missing Internet Information Services (IIS) role prerequisites, Microsoft SQL Server Reporting Services (SSRS) configuration conflicts, or corrupt temporary installation caches. To resolve these failures, verify that the required Windows Server IIS features (including ASP.NET 4.6 and Windows Authentication) are installed, ensure the SQL Server Reporting Services instance is initialized with valid encryption keys, completely uninstall partial setup attempts, reboot, and execute the installation using an elevated local Administrator account.
Table of Contents
- Executive Summary
- Architecture and Fundamental Mechanics
- Step-by-Step Implementation Procedure
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Executive Summary
SIMATIC Information Server (IS) is the web-based reporting system for PCS 7 and WinCC, delivering automated reporting from Process Historian and WinCC archives into Microsoft Excel, Word, and PDF. Installing Information Server 2014 SP3 on Windows Server 2016 requires exact alignment with underlying Microsoft server components—specifically IIS web application pools, SSRS reporting instances, and SQL database permissions. Setup crashes during the initialization phase are common when prerequisite server roles are omitted. This article provides a comprehensive installation recovery guide.
Architecture and Fundamental Mechanics
Information Server Architecture and Setup Dependency Mechanics:
- Architecture of SIMATIC Information Server:
- Built upon Microsoft SQL Server Reporting Services (SSRS) and Internet Information Services (IIS).
- Web application frontend provides dashboarding and report scheduling.
- Backend interfaces connect to Process Historian (PH) or WinCC OS Servers via specialized OLE-DB / OPC HDA drivers.
- Common Setup Failure Points:
1. IIS Role Requirements: Information Server requires specific IIS role services (ASP.NET 4.5/4.6, .NET Extensibility, ISAPI Filters, Windows Authentication, Static Content).
2. SSRS Initialization: The SQL Server Reporting Services instance must be running, configured, and bound to HTTP port 80/8080 with initialized backup encryption keys.
3. User Account Privileges: The account executing the installer must be a member of the localAdministratorsgroup and havesysadminrights in the Microsoft SQL Server instance.
Step-by-Step Implementation Procedure
Step-by-Step Procedure to Resolve Information Server Setup Failures:
- Verify and Install Windows Server 2016 IIS Roles:
- Open Windows Server Manager -> Add Roles and Features.
- Select Web Server (IIS) -> ensure the following Role Services are installed:- Common HTTP Features: Default Document, Directory Browsing, HTTP Errors, Static Content.
- Security: Request Filtering, Windows Authentication.
- Application Development: .NET Extensibility 4.6, ASP.NET 4.6, ISAPI Extensions, ISAPI Filters.
- Management Tools: IIS Management Console, IIS Management Scripts and Tools.
- Verify SQL Server Reporting Services (SSRS) Configuration:
- Open Report Server Configuration Manager.
- Connect to the local SQL Server instance (e.g.,HISTORIANorWINCC).
- Under 'Web Service URL', verify the Report Server virtual directory is active (e.g.,http://localhost/ReportServer).
- Under 'Database', ensure theReportServerandReportServerTempDBdatabases are created and connected.
- Under 'Encryption Keys', ensure backup keys are exported and valid. - Clean Up Failed Installation Remnants:
- Open Windows Control Panel -> Programs and Features -> uninstall any failed SIMATIC Information Server packages.
- Delete temporary setup folders underC:\Users\<User>\AppData\Local\Temp.
- Restart the server. - Execute Clean Installation as Administrator:
- Right-clickSetup.exefrom the Information Server 2014 SP3 media -> Run as Administrator.
- Follow the wizard; select the initialized SSRS instance.
- Complete the setup and reboot when prompted.
Verification
To verify Information Server installation:
1. Open a web browser on the server; navigate to http://localhost/InformationServer.
2. Verify the Information Server login dashboard displays without HTTP 500 or 404 errors.
3. Log in using Windows administrative credentials; verify the administration console allows configuring data source connections to Process Historian or WinCC.
Limitations and Operational Precautions
Operational precautions:
- Ensure that Windows Firewall allows inbound connections on the configured web ports (typically TCP port 80, 443, or 8080).
- Information Server requires specific client and server licensing in ALM (SIMATIC Information Server Basic Package and Client Access Licenses).
- Do not install conflicting third-party web servers (e.g., Apache) on the same machine running Information Server.
Engineer FAQ
What causes Information Server setup to fail during installation?
Missing IIS role services (such as ASP.NET 4.6 or Windows Authentication), uninitialized SQL Server Reporting Services (SSRS), or lack of local administrator rights.
Does Information Server require Microsoft SQL Server Reporting Services?
Yes. Information Server is built directly upon Microsoft SQL Server Reporting Services (SSRS).
Can Information Server run on Windows Server 2016?
Yes, SIMATIC Information Server 2014 SP3 and newer versions are certified for Windows Server 2016.
What URL opens Information Server locally?
http://localhost/InformationServer (or the server computer name).
What database does Information Server query for report data?
It queries the SIMATIC Process Historian database or local WinCC OS Server databases.
Technical References
- SIMATIC Information Server 2014 SP3 Operating Manual
- SIMATIC Process Control System PCS 7 Process Historian Manual
- PCS 7 V9.0 SP3 Licenses and Configuration Limits
Related Articles
- Architecting and Commissioning Central Process Historian Servers in PCS 7
- Troubleshooting DataMonitor Archive Discrepancies and Report Anomalies in PCS 7
- Querying WinCC Historical Archives via WinCC OLE-DB Provider and OpenPCS 7
Related Tags
- Information Server
- SSRS
- IIS Roles
- Reporting System
- Process Historian