Log File Locations

These will be referred to throughout this article.  

  • Agent Service Deployment Log: {Deployment Guid}.log i.e. 3f52ef9e-63df-4a7a-a3c5-fe55650b5781.log – C:\ProgramData\Capita\Solus3\Deployments\{Deployment Guid}

  • Agent Service Log: system.log - C:\Program Files\Solus3\AgentService\

  • Deployment Service Log: ds_systemlog.txt - C:\ProgramData\Capita\Solus3\Logs

  • Deployment Service Deployment Log: - {Deployment service installation folder} - Default: C:\Program Files\Solus3\DeploymentService\DeploymentLogs

This is a fairly generic error and as such the fix for it will not be the same thing every time. Below are the common reasons for this error to occur:

“Login Failed for SA User” – This means that the SA password is incorrect and needs resetting in the relevant channel.  To fix this go to Environment > Targets > Databases > Edit and enter the correct SA password.

“A non-recoverable I/O error occurred on file for the * Drive” – Check for space on the mentioned drive.  If possible make space for Solus3 to complete a backup of the corresponding database. 

Failure - One or more errors occurred. - Package: xxxxxxxxxxxxxxxxxxxxxxxx - More Info: System.AggregateException: One or more errors occurred. ---> Sims.Solus3.Agent.PackageDeployer.PackageException: Package signature is invalid. ---> System.Security.SecurityException: Package signature is invalid. -  Please attempt one of the following fixes:

  • Restart the Solus3 deployment service from the Solus 3 Server

  • On the affected workstation restart the SOLUS 3 Agent Service
    Re-download the Update in question
    On the affected workstation delete the package from C:\ProgramData\Capita\Deployments\Package
    Deploy the update in question to the affected workstation to resolve the issue. If this does not resolve the issue the solus 3 agent on the workstation will have to be removed and reinstalled.

If you have a tolerance not met error in the deployment, combined with a “Unknown agent attempted to contact” on the environment > Agent entry for the server, please log a call for further assistance. 

It is also worthwhile checking that the Solus3 agent service on the Server is “Started”.  If not go into Services.msc, scroll down to find the Solus3 agent, and check the status Column, if this is blank, right click on the line and select “Start”

Workstation / Agent Specific Problems

If when doing a deployment via SOLUS 3 within the systemlog.txt file for the agent you receive the error of Unable to contact packagedeployer.exe.  To resolve please re-install the SOLUS 3 agent onto the machine

Issues Specific to Solus deployments

When deploying an Upgrade to Solus3 logs, after failing with Tolerance not met, checking the Agent deployment log, you find an error relating to the deployment failing with an exit code of 1603

To resolve take the following steps;

Log a call to request the latest version of Solus 3 and unpack to an accessible location.

Use DBattach to back up the Solus3 Database
From Programs and features, uninstall the 3 components of solus3 in the following order – Solus 3 Deployment UI, Solus3 Deployment Server Service and Solus3 Deployment Server Database (Please do not detach the Solus3 Database)
From the downloaded version of Solus3, please re-install in the following order - Solus3 Deployment Server Database, Deployment Server Service and Solus 3 Deployment UI

Issues Specific to Discover
Tolerance Not Met

Exit code 1618 is a generic windows error code that specifies that another installation is already in progress. Complete that installation before proceeding with this install. If there are no installations running, this could be caused by the system thinking there is one. Restart the server to clear this error.

Exit code 1603 specifies that transfer services are unable to be stopped by the operating system.  Open Services.msc, locate the two Discover transfer services, right click and select “stop” for both from the context menu.  If you are unable to stop either service, restart the server, at a safe time to do so, then attempt to re-deploy the Discover update. 

When deploying Discover via Solus 3 the deployment fails with 'Tolerance not Met' - in the deployment log you read

Failed to deploy database dacpac C:\ProgramData\Capita\Solus3\Deployments\9632d2aa-5080-4758-98f5-1b9905558cc2\Packages\533fceeb-fae0-40b8-be8b-fab3fc1466fc\Unpack\Discover.DataEngine.Database.New.dacpac
Log a call to request the latest release. extract the ISO and run the 'ServerSetup.exe' within the 'Setups' folder.
Using the 'ServerSetup.exe' upgrade both the Discover Database and Discover Windows Services to the desired release.
Using SOLUS3, navigate to: Environment > Agents > Targets. Click on the Discover Database to select it, then click on 'Get Target Version'. Repeat this action for the Windows Discover Services. Both should update to their new version after a few moments.

If none of the steps above help you resolve the issue you are experiencing, please mail support@osmis.co.uk and attach the four log files listed below.

  • Agent Service Deployment Log: {Deployment Guid}.log i.e. 3f52ef9e-63df-4a7a-a3c5-fe55650b5781.log – C:\ProgramData\Capita\Solus3\Deployments\{Deployment Guid}

  • Agent Service Log: system.log - C:\Program Files\Solus3\AgentService\

  • Deployment Service Log: ds_systemlog.txt - C:\ProgramData\Capita\Solus3\Logs

  • Deployment Service Deployment Log: - {Deployment service installation folder} - Default: C:\Program Files\Solus3\DeploymentService\DeploymentLogs