SIMS Summer 2025 loads of failed installed

[Sheridan]

Anyone deployed Summer 2025 yet? We did it tonight and about 20% of the clients showed as successful, the rest failed as one or more errors occurred

 

After panicking a lot, I checked a handful of the failed ones and they had worked, running 7.224 - despite the failure messages in Solus3. Some had failed but this is always the case with Solus3 as we regularly have to fix clients

 

Re-running has the same effect and all are running the same version of Windows 11 and are on 1 of 2 types of hardware so no consistency as far as I can see

 

The error in the client log that failed (but worked!) is

PackageRunner: Install failed. Exception: Sims.Solus3.Agent.PackageDeployer.TaskException: Execution of task 2b05c745-cf87-46db-9615-a9bf15631d3e failed. ---> System.InvalidOperationException: Process must exit before requested information can be determined.

 

So my reading of this is that the install hasn't so much failed but hasn't terminated in a timely manner to show the process as complete?

Edited July 3, 2025 by Sheridan

[PotNoodleTech]

No but if it possibly hasnt terminated cleanly then you gotta wonder if theres anything it hasnt done/installed?

[Sheridan]

It looks like its worked and then it fails to connect on port 8739 to report in. Weird as this is (and has been for a while) deployed via GPO

 

What's even odder is when I test connecting to port 8739 from the sims server to a failing one (using TNC) it fails, but if anyone is logged in on that PC then it works!

 

I can't think of anything that would only allow an incoming connection on port 8739 if a user is logged in, that doesn't make much sense to me

 

Also strange is the Client Check from Soolus 3 works even when some isn't logged in - got my head warped this one!

Edited July 4, 2025 by Sheridan

[SIMS_Customer_Support]

Hi @Sheridan

 

Please can you log a ticket via your support provider and provide the UI and service log files. If required, the service desk can help with the locations of the logs. 

 

I hope this helps. 

 

Many thanks

Sally 

[Koldov]

On 04/07/2025 at 11:53, Sheridan said:

I can't think of anything that would only allow an incoming connection on port 8739 if a user is logged in, that doesn't make much sense to me

 

Firewall rules deployed by USER GPO and not COMPUTER?

[Sheridan]

Actually I think the firewall rules are all good, the port 8739 thing is a false flag

 

From my testing the port 8739 is only open when the Solus 3 GUI is active, which is only when someone is logged in - so my updates have worked but failed to tell the UI to inform the logged in user - which seems normal as the gui is separate from the service running that actually pulls down the updates

 

So I'm back to the original error which seems to be the problem: "Process must exit before requested information can be determined."

 

This only happened with the Summer 2025 updates, all worked fine with Spring 2025 and nothing has changed apart from the usual monthly server patches. Its been logged but no response as yet

 

 

 

 

 

[Sheridan]

We're getting the same error on a single deploy as well. I think our Solus is dead 😵

[ITGuyNW]

We have our Summer update tonight... do you think its just your site or is it widespread?

[Sheridan]

28 minutes ago, ITGuyNW said:

We have our Summer update tonight... do you think its just your site or is it widespread?

I'm not sure, no one else has reported it on here as far as I can see. However our Solus 3 setup worked fine during the last update so it could just be us!

[BOOT]

Does the file: "C:\Program Files\Solus3\AgentService\Solus3.Keys.PackageServer.Public.xml" exist on the affected PCs?

[Sheridan]

48 minutes ago, BOOT3988 said:

Does the file: "C:\Program Files\Solus3\AgentService\Solus3.Keys.PackageServer.Public.xml" exist on the affected PCs?

Yes, exists on all of the the failing computers that I've checked

 

ESS seem to have dismissed this ticket claiming 8739 is not open and not paid attention to the original error 'Process must exit before requested information can be determined'

 

Its something I've tested a lot recently; 8739 is only open when a user is logged in - which makes sense as the gui loads with a login. The services are running in the background so allow the update to take place whether anyone is logged in or not - so in my case the update has started (and seems to have completed or just about) and then errors out, then also logs an error saying the gui isn't active.

 

I've checked the working computers and they mostly have the 8739 port error as well - because the update was done during the evening when users were logged out! A small percentage have no errors at all and they were computers that had a user logged in (my machine for example)

 

Good luck with anyone's summer 2025 updates, cos it looks like I'm stuck with my issue!

 

 

 

[SIMS_Customer_Support]

36 minutes ago, Sheridan said:

Yes, exists on all of the the failing computers that I've checked

 

ESS seem to have dismissed this ticket claiming 8739 is not open and not paid attention to the original error 'Process must exit before requested information can be determined'

 

Its something I've tested a lot recently; 8739 is only open when a user is logged in - which makes sense as the gui loads with a login. The services are running in the background so allow the update to take place whether anyone is logged in or not - so in my case the update has started (and seems to have completed or just about) and then errors out, then also logs an error saying the gui isn't active.

 

I've checked the working computers and they mostly have the 8739 port error as well - because the update was done during the evening when users were logged out! A small percentage have no errors at all and they were computers that had a user logged in (my machine for example)

 

Good luck with anyone's summer 2025 updates, cos it looks like I'm stuck with my issue!

 

 

 

@Sheridan Please let me know the details of the raised case you referenced yesterday and I will be happy to ask one of our analysts to reach out and help you resolve this. 

 

Many thanks

Sally 

[Sheridan]

8 minutes ago, SIMS_Customer_Support said:

@Sheridan Please let me know the details of the raised case you referenced yesterday and I will be happy to ask one of our analysts to reach out and help you resolve this. 

 

Many thanks

Sally 

Ticket was raised, and closed as explained above. I'll have to get another ticket raised with an edited log file so the port 8739 error isn't the focus

[Sheridan]

We now can't install individual copies using Solus as we see the signature error:

 

'Sims.Solus3.Agent.PackageDeployer.PackageException: Failed to validate signature'

 

So mass deployments aren't working, neither are individual ones. Is there a good way to completely reinstall Solus?

[Homer]

3 hours ago, Sheridan said:

We now can't install individual copies using Solus as we see the signature error:

 

'Sims.Solus3.Agent.PackageDeployer.PackageException: Failed to validate signature'

 

So mass deployments aren't working, neither are individual ones. Is there a good way to completely reinstall Solus?

See below, had to rip Solus off loads of machines post domain migration last Summer so automated it. Get your Solus installer from the Deployment Console, and package it in with this powershell script to do an automated remove/reinstall of Solus. Make sure to delete the machine from the Solus console first though or it'll faff around and not bother to actually install or update SIMS. 

 

In the AgentInstaller.js it exports make sure to uncomment the product selection line so that it actually does do something useful. 

 

## new ini settings
$connectdata = @"
  [SIMSConnection]
  ServerName=SERVER.FQDN\sims2016
  Connectiontype=TrustedAuto
  DatabaseName=sims
  commandtimeout=70000
"@

  $fmsconnectdata = @"
  [FMSConnection]
  Server=SERVER.FQDN\SIMS2016
  Database=FMS=
  SQL_Driver_Version=5
"@

$connectinipath = "C:\Program Files (x86)\SIMS\SIMS .net\connect.ini"
$fmsinipath = "C:\Program Files (x86)\SIMS\FMSSQL\FMSConnect.ini"

##### nuke section below ######################################################
# Array of product GUIDs (add any others here if needed later)
$msiGuids = @(
    '{D8D4C490-37C1-4DB8-A038-FC5BD7EA7944}',   # original version
    '{2FFAD32A-DD51-4CBD-8D05-8291532C76E5}'    # new version
)

# Service associated with the product(s)
$serviceName = 'Solus3Agent'

# Stop the service if it’s running
$service = Get-Service -Name $serviceName -ErrorAction SilentlyContinue
if ($service -and $service.Status -ne 'Stopped') {
    Write-Verbose "Stopping $serviceName..."
    Stop-Service -Name $serviceName -Force -ErrorAction SilentlyContinue
}

# Uninstall each GUID that actually exists on the machine
foreach ($guid in $msiGuids) {
    Write-Verbose "Checking for product $guid ..."
    $product = Get-CimInstance -ClassName Win32_Product `
                               -Filter "IdentifyingNumber='$guid'" `
                               -ErrorAction SilentlyContinue
    if ($product) {
        Write-Verbose "Uninstalling $guid ..."
        Start-Process msiexec.exe -ArgumentList "/x $guid /quiet /norestart" `
                                  -Wait -NoNewWindow
        Write-Verbose "Finished uninstall for $guid."
    } else {
        Write-Verbose "Product $guid not found – skipping."
    }
}
###############################################################################


# Check if the uninstallation was successful
if ($uninstallProcess.ExitCode -eq 0) {
    Write-Output "Uninstallation successful."
    # Place further commands here
} else {
    Write-Output "Uninstallation failed with exit code $($uninstallProcess.ExitCode)."
}

$msiInstalled = Get-WmiObject -Query "SELECT * FROM Win32_Product WHERE IdentifyingNumber = '$msiGuid'"

Write-Host "Solus has been taken out back and shot"

Write-Host "destroy the old crypto file "

Invoke-Command -ScriptBlock {Remove-Item C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\1db350c* -Force}

#  clear up solus crap 

Invoke-Command -ScriptBlock {
    write-host "cleaning up solus crap"
    Remove-item C:\ProgramData\Capita\* -Recurse -Force
    Remove-Item 'C:\ProgramData\Solus 3\*' -Recurse -Force
}

& cscript /nologo AgentInstaller.js "agent_installer.log" "net.tcp://localhost:52966" "net.tcp://REPLACE-WITH-YOUR-FQDN:52965" "Solus3.Keys.DeploymentService.Public.xml" "SOLUS3AgentInstaller_x86.msi" "SOLUS3AgentInstaller_x64.msi"



Write-Host "Updating ini files"
Set-Content -Path $connectinipath -Value $connectdata
Set-Content -Path $fmsinipath -Value $fmsconnectdata -ErrorAction Continue

 

[Sheridan]

Thanks, looks like my summer now has an extra job to rip this mess out and start again!

[Sheridan]

Anyone else run the Summer 2025? Curious to know if mine is an isolated disaster 🙂

[NegativeKillDeath]

Did ours last night, all OK. 

[gshaw]

Just found this thread via Google search as I'm trying to push a fresh install of SIMS to a newly deployed InTune machine. SOLUS picks up the installation, it starts to deploy then bombs out with "one or more errors occurred"

 

I was wondering why it's playing up when our other InTuned site has been fine with the same deployment. The only difference is the Summer 2025 update rather than Spring, which has been fine.

[Sheridan]

Ours was working fine until the summer update but our only fix is to remove solus and reinstall it. Haven’t started yet as it’s over 100 computers that showed the error 

[gshaw]

Which version of Solus agent were you deploying?

 

Our InTune package was 3.12.72.1 though I see it tries to update to 3.12.86.1 on an affected client before both the Agent and SIMS client installs hit the "one or more errors occurred" message

[Sheridan]

Our Solus clients were 3.12.86.1 already (I believe so anyway - I didn't check to be fair!)

 

Even deleting a solus client completely (manually) and then redeploying I see the same error - so I'm a bit stuck as ess still think its the firewall even when I've tested this a lot and found the firewall ports all correctly open

[gshaw]

Yeah I saw the "can't connect to localhost Packager" errors which I see is related to that port 8739 you posted earlier (if you open up the .config files you'll see where it gets defined)

 

The first run of the Solus agent adds that port to a firewall rule, which makes it even stranger.

 

I've got a fresh installer for the latest Agent so will try to reinstall and see what happens next...

Edited July 28, 2025 by gshaw

[Sheridan]

14 minutes ago, gshaw said:

Yeah I saw the "can't connect to localhost Packager" errors which I see is related to that port 8739 you posted earlier (if you open up the .config files you'll see where it gets defined)

 

The first run of the Solus agent adds that port to a firewall rule, which makes it even stranger.

 

I've got a fresh installer for the latest Agent so will try to reinstall and see what happens next...

We've had the ports defined by a gpo for a long time. I tried a fresh download as well but no luck

[David44]

We don't use SOLUS (Why waste time on a known buggy deployment tool that at best only deploys one application?) but we have seen an issue where SIMSApplicationSetup.exe fails to exit.

 

We have been testing Microsoft Configuration Manager, this deploys SIMS and reports something similar to what @Sheridan is seeing, the .exe never exits. We have set the Application install to timeout after 15 minutes (the lowest possible in MCM) and after that time it reports that the install failed. When the application is deployed again, it detects that it is already installed and marks it as a successful deployment.

 

We are actually installing the previous version rather than the Summer release at the moment but this is not a new issue...