Installer Messages

The four Cygna Forest Recovery packages (CygnaDR.Manager.msi, CygnaDR.DcAgent.msi, CygnaDR.StorageAgent.msi, and CygnaDR.HostAgent.msi) install silently with msiexec /i <package> /qn and have no installer screens. When a package refuses to install, msiexec ends with an error, and the message is written to the installer log if you asked for one with /l. This topic lists each message, its cause, and the fix.

Note: An installer log records the properties given on the command line, except ENROLLMENTTOKEN, which Windows Installer masks. Keep commands that carry the token out of scripts and command history.

Messages that stop an installation

Message	Package	Cause and fix
`The Cygna Disaster Recovery Manager requires 64-bit Windows.` The DC agent, storage agent, and Isolated Recovery Host agent packages give the same message with their own names.	All	The machine runs 32-bit Windows. Install on 64-bit Windows Server 2019 or later, or for the DC agent, 64-bit Windows Server 2016 or later.
`The Cygna Disaster Recovery Manager requires Windows Server 2019 or later — build 17763 or higher. This machine reports build` n`.` The storage agent and Isolated Recovery Host agent packages give the same message with their own names. The DC agent package gives it with Windows Server 2016 and build 14393.	All	The operating system is older than the package supports. The message gives the build the machine reports. Install on a supported operating system: Windows Server 2019 or later for the Manager, storage agent, and Isolated Recovery Host agent, or Windows Server 2016 or later for the DC agent; see System Requirements.
`ENROLLMENTTOKEN is required, and must match the token given to the agent installers.`	Manager	The first installation of the Manager was run without `ENROLLMENTTOKEN`. Choose a token, give it on the command line, and store it offline: every agent needs the same token. An upgrade does not need it, because the installer keeps the stored token.
`MANAGERADDRESS is required.`	DC agent, storage agent, Isolated Recovery Host agent	The first installation was run without `MANAGERADDRESS`. Give the Manager's agent address, `https://<manager IP>:5211`. The Agents screen shows complete install lines with the right address.
`MANAGERCAFINGERPRINT is required: the manager CA fingerprint shown on the manager's console. Example: msiexec /i …`	DC agent, storage agent, Isolated Recovery Host agent	The first installation was run without `MANAGERCAFINGERPRINT`. Copy the fingerprint from the Agents screen. It is public, not secret.
`STORAGEROOT is required: the absolute path to this machine's storage volume, for example E:\CygnaDR. It cannot be set from the manager.`	Storage agent	The first installation was run without `STORAGEROOT`. Give an absolute path on the storage machine's backup volume.
`A newer version of the Cygna Disaster Recovery Manager is already installed. Uninstall it before installing this version.` The DC agent, storage agent, and Isolated Recovery Host agent packages give the same message with their own names.	All	The package is older than the installed version, and downgrades are not allowed. Install the current package instead. Uninstall first only if you really intend to go back to the older version.

Properties are required on a first installation only. An upgrade reads them back from the registry, so msiexec /i <package> /qn on its own is a complete upgrade, and a property you do give replaces the stored value. This includes the Manager's RESTPORT, GRPCPORT, LISTENADDRESS, and REDIRECTPORT. See Upgrading and Uninstalling.

Installer failures during a self-update

When an agent updates itself from the Manager, it runs the package with msiexec /i … /qn /norestart /l*v from a one-time scheduled task as SYSTEM, and writes the log to the update subfolder of its data folder, for example %ProgramData%\Cygna Labs\Disaster Recovery Suite Storage Agent\update. If the installer fails, Windows Installer rolls the change back, the old build keeps running, and the agent reports the failure. The update's transcript shows the msiexec status, the installer's failure message, and the log lines before the first failure. The outcome is Install failed. For the messages an update gives before the installer runs, see Agent Enrollment and Connectivity.

The DC agent after a DC state restore

A DC state restore puts the registry back to how it was when the backup was taken. That includes a DC state recovery and each restore of a domain controller in a domain or forest recovery plan. Windows Installer's record of installed programs is in the registry, but its saved installer packages in C:\Windows\Installer are not, and the restore leaves them as they are. If the DC agent was updated after the backup, the restore brings back the record of the older agent, whose saved package the update deleted. Every install or update of the agent then fails with Error 1714, "The older version of Cygna Disaster Recovery DC Agent cannot be removed", and System Error 1612.

The agent mends this itself, so nothing is needed from you in the normal case:

Before the restore, the agent copies its own installer package to its data folder, which a restore does not touch.
On the first normal start after the restore, before it checks the restored domain controller, the agent looks at Windows Installer's record of itself. If the record names a version whose package is gone, the agent removes that one product's entries and reinstalls the package it copied, which is the version that was running before the restore. The agent's files, service, identity, and settings are kept. Its service restarts once, in about a minute. The run's timeline says what the agent did.

Afterwards the domain controller runs the same agent version as before the restore, and automatic and manual updates work as usual. A full system recovery restores whole volumes, including C:\Windows\Installer, and is not affected.

If the agent could not mend it, the restore still completes, and the run's Steps card notes that the agent on this domain controller needs reinstalling by hand, with the script's full path and the package to install. That happens when no package could be copied before the restore, or the reinstall failed; its log is agent-reinstall.log in the run's folder under the agent's restore data.

To reinstall the DC agent by hand:

On the domain controller, open an elevated PowerShell prompt in the agent's installation folder, for example C:\Program Files\Cygna Labs\Disaster Recovery Suite DC Agent.
List Windows Installer's stale records of the agent:
```
powershell -ExecutionPolicy Bypass -File .\Remove-StaleDcAgentRegistration.ps1
```
The script lists only agent versions whose installer package is missing. It never touches the agent's files, service, or settings, or any other product. If it finds nothing to remove, go on to step 4.

Remove the records it listed:

powershell -ExecutionPolicy Bypass -File .\Remove-StaleDcAgentRegistration.ps1 -Remove

Remove the agent's service, so that the installer can create it again:
```
sc.exe stop CygnaDRDcAgent
sc.exe delete CygnaDRDcAgent
```
Install the agent: the package the note names, or the current CygnaDR.DcAgent.msi:
```
msiexec /i CygnaDR.DcAgent.msi /qn
```
No Manager address or enrollment token is needed. The installer reads the existing settings, and the agent keeps its identity, so it reconnects as the same agent.

Problems after installation

Some problems appear only when the service starts. They are written to the service's log and, for warnings and errors, to the Application log.

Symptom	Cause and fix
The Manager service does not start, and logs that no listen endpoints are configured and it refuses to start on the framework default port	The Manager's port configuration is missing from its registry key and from `appsettings.json`. Reinstall the Manager with `msiexec /i CygnaDR.Manager.msi /qn`, giving `RESTPORT` and `GRPCPORT` if you use ports other than the defaults. Do not add your own listener settings (a `Kestrel` section) to `appsettings.json`: it would override the installed ports and leave the firewall rules on the old ones.
The Manager logs a warning that its redirect port is in use, and starts without it	Another program, such as IIS, holds the port given by `REDIRECTPORT` (80 by default). The console still works at `https://<manager>:5210/`. Free the port, or reinstall with `REDIRECTPORT=0` to turn the redirect off.
The storage agent service stops at startup	The storage root is not reachable, for example because its volume is not yet present. Once it is present, start the service by hand.
An agent logs that it cannot connect to a manager	Its Manager address or CA fingerprint cannot work. See Agent Enrollment and Connectivity.