Troubleshooting
Why Citect Historian 2016 setup never installs SQL Server
Short answer
The completed message from the Historian SQL launcher proves the launcher finished, nothing more. Accept the engine only on two checks: the database-engine service for the instance, and a client connection to it. When the package ships without the SQL installer, copy the separately obtained SQL Server 2012 files into HistorianSQL\Extras\1033\SQL Server\, clean the partial install, and rerun setup; the ActiveX error that follows is a separate COM fault.
On this page
- The completion message is not an acceptance test
- Prove the engine before you reinstall anything
- Check the media for the SQL payload
- Stand up the SQLEXPRESS instance
- The ActiveX error after SQL is in
- Commissioning pass on Windows Server 2012 64-bit with the no-SQL package
- What to do, by what you find
- Questions asked
When Citect Historian 2016 setup reports that the SQL Server 2012 installation completed, the message proves only that the Historian SQL launcher ran to the end of its script. Treat it as zero evidence. The database engine is real when two independent checks pass: a database-engine service for the instance exists in Windows Services or SQL Server Configuration Manager, and a SQL client connects to that instance. On this release both checks usually fail for one reason: the setup variant in use ships without the SQL payload. The fix is to clean the partial install, copy the separately obtained SQL Server 2012 files into HistorianSQL\Extras\1033\SQL Server, and rerun the Historian SQL setup. The "ActiveX component can't create object" error that appears once SQLEXPRESS becomes selectable is a separate, local COM fault.
The completion message is not an acceptance test #
The "SQL Server 2012 Installation completed" text comes from the HistorianSQL launcher, not from SQL Server's own per-feature setup results. Underneath it, three things can be true: the SQL setup failed, it installed only client components such as Management Studio, or it never received a usable payload because the package omits the SQL installer. An entry in installed programs tells you a package registered, not that an engine exists. Management Studio is a client, not the engine. The service inventory plus a real connection are the only results that establish the engine, so those two checks, not the launcher's final line, decide every branch below.
Prove the engine before you reinstall anything #
Work these four checks in order and change nothing until they agree:
- Inventory the installed SQL features from the installed-programs list and the SQL setup results, and separate engine components from clients; Management Studio alone registers entries with no engine behind them.
- Open Windows Services, or SQL Server Configuration Manager, and look for the database-engine service that carries the instance name. With SQLEXPRESS selected later in the Historian configuration, the service entry must name SQLEXPRESS. No entry means no engine, whatever any message claimed.
- Connect to the local instance with a SQL client, and prove the login with the account Historian will use, not only with an administrator account.
- If the SQL setup ran quietly, rerun it with the quiet flag /qs replaced by /INDICATEPROGRESS, and read the Windows event log for the same window; the first failing step becomes visible.
A quiet installer that hides its failure and a launcher that declares success are the same trap: a reported success and a verified effect are different things, the same discipline by which a named query counts as successful only after a completed commit.
Check the media for the SQL payload #
Open the installation media and locate the HistorianSQL folder: its setup.exe is the launcher, and a 1033 folder beneath it carries the SQL package. The 2016 setup is distributed in a variant that omits the SQL installer, and rerunning an incomplete package never supplies files it does not contain.
For the separate-package arrangement, the payload location is HistorianSQL\Extras\1033\SQL Server, and the package identified for that route was the 32-bit SQL Server 2012, taken from Microsoft or an authorized channel. Copy the complete file set there, prepare the machine, then run the Historian SQL setup again. Preparation:
- Uninstall any other SQL Server version first; this product line runs one version at a time, and one is removed before another is installed.
- Delete the SQL extraction and temp folders left by the failed pass.
- Remove SQL applications you do not need, so the installer is not working around them.
Confirm the copied files are complete and readable before launching setup. A 64-bit operating system executes the 32-bit package, but the supported combination is whatever the release requirements state for your build, not what the operating system can run.
Stand up the SQLEXPRESS instance #
Two routes get you an engine: the Historian launcher with a complete payload, preferred because it keeps the intended workflow, or a separate SQL install, which works when the package omits SQL but leaves edition, features, instance name and authentication as your explicit checks.
- Run the supported installer with administrative rights.
- Select the database-engine feature, and record the instance name and authentication mode.
- Read the final setup results per feature; a failed feature is investigated in the SQL setup logs, never in the launcher's summary.
- Confirm the database-engine service is running for that instance.
- Connect with the account Historian will use.
Before committing to an Express edition, compare its documented capacity and feature limits with the archive workload you expect. With the engine proven, the next wall in this stack is database creation on a named instance.
The ActiveX error after SQL is in #
"ActiveX component can't create object" means the Historian configuration tool tried to create a COM object and the activation failed. It is not a missing Windows service, because there is no service called ActiveX, and it is not a SQL connectivity result. SQLEXPRESS appearing as a selectable database means the tool is already past the missing-instance fault; what remains is local to the configuration process. Work it in this order:
- Note the exact time of the error, then read the application event log at that time and record the component identifier it names.
- Repair that component through its own installer, a targeted repair rather than another generic modify pass, which repeats the same registration state and changes nothing.
- Check bitness: a 32-bit configuration process reads the 32-bit COM registration view on 64-bit Windows, so a component present on disk is not necessarily activatable from that process.
- Run the configuration tool elevated, as the account used for installation.
Once configuration completes, sort out the six database rights the historian account needs before the first write. A SCADA connector to the historian that shows disconnected after that is its own case, not a database fault.
Commissioning pass on Windows Server 2012 64-bit with the no-SQL package #
Inputs, each from the deployment being commissioned:
- Host operating system: Windows Server 2012, 64-bit.
- Historian: Citect Historian 2016, the setup variant without the SQL installer.
- SQL package: SQL Server 2012, 32-bit, obtained separately.
- Payload destination: HistorianSQL\Extras\1033\SQL Server.
- Acceptance rule: two independent checks, the database-engine service for the instance exists and runs, and a client connects to that instance.
Rule in words: the engine is accepted only when both checks pass. Each check is one piece of independent evidence; the launcher's completed message is zero evidence and never counts toward the total.
Arithmetic: the requirement is 2 of 2. First attempt, as reported: service entry 0, connection 0, so 0 + 0 = 0 of 2, and the completed message adds 0, leaving the total at 0 of 2. After cleanup, payload copy and rerun: service entry 1, connection 1, so 1 + 1 = 2 of 2.
Result: 2 of 2, engine accepted.
Decision: at 2 of 2, proceed to Historian configuration. At 1 of 2, the failing check names the fault: a service that exists while the connection fails points at instance naming or authentication, not at the Historian install. At 0 of 2, the engine never installed, so go back to the payload checks above. If configuration then throws the ActiveX error, the engine work is finished and the fault is the local COM problem handled one section up.
What to do, by what you find #
- Completed message, no engine service: the payload is missing or failed. Verify the media layout, copy the SQL Server 2012 file set into the documented payload folder, clean, rerun.
- Service present, connection fails: the engine exists. Fix the instance name or the authentication before touching the Historian installation.
- Both checks pass, configuration reports the ActiveX error: local COM. Event log first, then a targeted repair matched to the tool's bitness.
- Host is Windows Server 2016 or SQL Server 2016 is required: the base 2016 release is the wrong tool here. A published upgrade note for this line records hotfix build v4.6.1225.16 as adding Windows Server 2016 and SQL Server 2016 support; take that build from the vendor's support portal and uninstall the earlier version first.
- Archive workload outgrows Express: install the full SQL Server edition your release supports, and rerun the same 2-of-2 acceptance.
Questions asked
Is there an ActiveX service I need to start in Windows Services?
No. Windows has no service called ActiveX. The message means the configuration tool tried to create a COM object and the activation failed. The application event log at the moment of the error names the component at fault; repair that component through its own installer, matching the bitness of the configuration tool, rather than repeating a generic modify pass.
Should I install SQL Server 2012 Express and Management Studio separately from Microsoft?
Yes, when your Historian package ships without the SQL installer that is the legitimate route. Take SQL Server 2012 from Microsoft or an authorized channel, copy the complete file set into HistorianSQL\Extras\1033\SQL Server\, clean the partial install and temp files, then rerun the Historian SQL setup. Management Studio is only a client; acceptance is still the engine service plus a real connection.
Does Citect Historian 2016 support Windows Server 2016 or SQL Server 2016?
Not the base release, which targets the 2012-era stack this article works with. The vendor's upgrade note for this line records hotfix build v4.6.1225.16 as adding support for both. On a Server 2016 host, take that build from the support portal and uninstall the earlier version first; this line runs one version at a time.
The SQL setup ran silently and shows no errors. Where is the failure?
In the per-feature setup results and the Windows event log. A quiet install reports little by design; rerun it with /qs replaced by /INDICATEPROGRESS and each step and the first failure become visible. The Historian launcher's completed message never carries that detail.