[sims] SOLUS 3.7

zag · July 14, 2014

If anyone finds that Groupcall emerge breaks after installing the Solus update, it has something to do with the new agent setting the security settings on the local C: drive.

Make sure the groupcall exporter and the emerge service have named administrator accounts on them. Then start both the services and it should work again.

Superade · July 14, 2014

Anyone found the 3.7.161.0 exe's to download? Can't find them on Supportnet (as usual)

matt40k · July 14, 2014

Customers new to SOLUS3
The URL and password will be provided on Monday for customers to do this.

Note: he didn't say which Monday

Superade · July 14, 2014

I might dodge 3.7 period. Not had a smooth install/config yet. Especially having trouble with it bringing down packages. All 3 sites have had particular issues with the .net 4.5, Borland and SQL compact packages getting stuck on a download loop and erroring on validation. Importing updates has been troublesome too, kept saying the destination directory was not empty.

Oh yeah also fell foul to the post sql migration issue too.......... Happy days

howartp · July 14, 2014

I've been asked to put Summer Release on tonight.

I've not yet put either version of SOLUS 3.7 or any Summer 14 Release on.

Does the Summer Release depend on SOLUS 3.7? Do I need to upgrade SOLUS or can I just push out Summer?

The reason being, we're installing a new domain on Friday and wiping the lot, but my Data Manager needs to do some prep on SIMS before she comes back in for Exams hence why I gotta install it

Peter

Superade · July 14, 2014

No summer doesn't need 3.7.

howartp · July 14, 2014

No summer doesn't need 3.7.

Woohoo!

Great, I'll leave 3.7 alone then!

Cheers.

Peter

zag · July 14, 2014

Just out of interest wha'ts the difference between agent version

3.7.149.0

and

3.7.147.0

It seems to be that all new clients installed after Solus 3.7 get the "149" version. But does it make a difference?

Edited July 14, 2014 by zag

Boredguy · July 14, 2014

I only have a 3.7.161.0 to download, so tomorrow I'll see what happens as its scheduled for 6am mwhahahaha

Sheridan · July 14, 2014

Just out of interest wha'ts the difference between agent version

3.7.149.0

and

3.7.147.0

It seems to be that all new clients installed after Solus 3.7 get the "149" version. But does it make a difference?

[ATTACH=CONFIG]25623[/ATTACH]

This has confused me as well, I deployed Solus 3.7 which deployed the 3.7.147 Agent. Then I deployed the 3.7.149 update which I thought would update the agents - but they're all still at 3.7.147. I spoke to Capita who said the 3.7.149 update only applied to the Solus server itself. But that doesn't sound right if your agents are now showing as 3.7.149!

MrMat · July 14, 2014

This has confused me as well, I deployed Solus 3.7 which deployed the 3.7.147 Agent. Then I deployed the 3.7.149 update which I thought would update the agents - but they're all still at 3.7.147. I spoke to Capita who said the 3.7.149 update only applied to the Solus server itself. But that doesn't sound right if your agents are now showing as 3.7.149!

For the Agents, 3.7.147 and 149 are essentially the same thing. 149 was the re-release they issued when they spotted a bug. There was a post on the Supportnet homepage which gave further details.

In a nutshell, all your agents that were in your DE when you deployed 3.7 will be on 147 while any new machines that you add, will use 149.

Edit: Oh and no it doesn't make a difference

Sheridan · July 15, 2014

I've just checked and i do now have a handful of 3.7.149 clients - bizzare how they don't update all of them to the same version?

zag · July 15, 2014

I'm trying to roll out the Summer 2 Upgrade with the new Solus and get a message saying

"An error has occured creating the update deployment record".

Any ideas whats going on? Argh...

zag · July 15, 2014

Suprise.... Suprise.... there is a Re-Release of Solus 3.7

http://dl.capitasolus.co.uk/solus3Release/3.7.161.0.zip

Password is on Supportnet. You can upgrade by running each installer with the database one first, deployment server 2nd and UI last.

After upgrading to this release fixed all our problems.

resin1 · January 11, 2015

Hoping someone might have some ideas on this before I or LA support waste time on it.

Having had a belly full of Solus 3 over the last years, I have tended to keep hands off for a while now - not touching S3 itself and getting it to do the required SIMS updates as needed for Census etc, which admittedly have increasingly become less of a headache.

However, I realised that our site is lagging behind on S3 and decided to kick it to update itself to 3.8 the other night through auto-deploy. In the morning I discover that had failed. Upon investigation I see that the failure actually occurred where it was trying to do the first update from the 3.6.94.0 version we were at, to 3.7.161.0 which we missed, before it should have gone on to do 3.8.

Even though I was loathe to waste time I don't have on this thing yet again, I intervened and did a manual update deploy of 3.7.161 itself, after first re-booting the server to a clean state just to be sure. Still failed with a "tolerance not met for target Solus 3 database" message in the GUI.

I did it again and sat watching it go through each stage and it is that last point i.e. it does the server instance name patch, the .Net 4.5, the 3.7.147 agent stages 1-3 ok, but stage 4 to update the database to 3.7.161.0 fails. The agent on the server just momentarily says there are 1 or more errors but gives no info. The process then completes roll back and completes with failure, so I'm stuck at 3.6.94.

The log at the point of failure confirms the check that causes the tolerance not met message, but as far I i interpret, that simply checks some flag to say "is the db reporting the right version errr no!", and so triggers that message.

The log lines are below.

As far as I am concerned, I'm trying to update versions that have long since been the replacements for earlier versions that may have had problems when they first came out, so its reasonable to assume it would all go fine. We have not changed anything I'm aware of as far as the server setup i.e. its the same 64bit Windows Server 2012 with SQL Server 2012.

I looked in the ProgramData/Capita/Solus3/logs/ds_systemlog also but that didn't seem to provide any useful info on what has caused the failure on the database deploy.

Is there somewhere else I should be looking to provide a clue? Or is there some files/archive that it would be worth clearing to give it a chance to do things cleanly - that's just grasping at straws, but I'm concerned we are looking at a clean S3 install to get this moving forward, which is just the pits and should be wholly unnecessary :-(

I searched through the forum including this post, but my eyes didn't catch any golden nugget of known issue which I may be hitting here.

Thanks.

===================

Log lines at failure:

2015-01-10 15:22:37.5917|***

2015-01-10 15:22:37.5917|*** Deploying Solus 3 - 3.7.161.0 to Solus 3 Database (64Bit) targets at SOLUS3 System (99999999-9999999)

2015-01-10 15:22:37.5917|***

2015-01-10 15:22:37.6073|ds|Info|1 agent target(s) found for Solus 3 Database at site SOLUS3 System.|SetAgentTargetsForThisDeployment()

2015-01-10 15:22:37.6229|oda-sims-01|Info|Target version 3.6.94.0, expected target version 3.7.161.0, update will be deployed|ProcessAgentTargets()

2015-01-10 15:22:37.6697|oda-sims-01|Info|Agent is available for target id 4.|AgentIsAvailable()

2015-01-10 15:22:37.6697|oda-sims-01|Debug|Throttling - Download slot now available|AgentIsAvailable()

2015-01-10 15:22:37.6697|oda-sims-01|Debug|Target id 4 instructed to deploy.|Execute()

2015-01-10 15:22:37.6853|ds|Debug|CreateAgentPackageSiteRecord updating _agentTargeted for agent target id 4|SendExecuteCommandToAgent()

2015-01-10 15:22:38.2001|oda-sims-01|Info|Started downloading package 'Solus 3 - 3.7.161.0 (Solus 3 Database solus3_deployment_server)'|UpdateProgress()

2015-01-10 15:22:38.2001|oda-sims-01|Info|Successfully finished downloading update 'Solus 3 - 3.7.161.0 (Solus 3 Database solus3_deployment_server)'. (File had already been downloaded.)|UpdateProgress()

2015-01-10 15:22:38.2001|oda-sims-01|Debug|Throttling - Downloaded update, download slot has been cleared|b__0()

2015-01-10 15:23:15.2539|oda-sims-01|Info|Tgt 4, Pkg 6a7c81e6-693e-4717-ba75-d29d6134d23c, One or more errors occurred.|UpdateProgress()

2015-01-10 15:23:17.7657|ds|Info|Agent 4, target id oda-sims-01 reported target version number 3.6.94.0, expected target version is 3.7.161.0.|WaitForAgentResponse()

2015-01-10 15:23:17.7657|oda-sims-01|Info|Agent has responded|Execute()

2015-01-10 15:23:27.6722|ds|Info|Waiting for target Solus 3 Database to complete deployment for 1 sites 99999999-9999-9999-9999-999999999999|BackgroundWorkerDoWork()

2015-01-10 15:23:27.7970|ds|Info|Deployment to site SOLUS3 System (99999999-9999-9999-9999-999999999999) has been completed.|RunInternal()

2015-01-10 15:23:27.7970|ds|Info|Deployment plan has failed to install at site SOLUS3 System 99999999-9999999|RunInternal()

2015-01-10 15:23:37.6880|***

2015-01-10 15:23:37.6880|*** Checking tolerance for Solus 3 Database (64Bit) targets

2015-01-10 15:23:37.6880|***

2015-01-10 15:23:37.6880|ds|Info|Site count: 1, no failed site deployments: 1, required tolerance: 100, calculated tolerance: 0, tolerance passed: False|CheckTolerance()

2015-01-10 15:23:37.6880|ds|Info|Tolerance not met for target Solus 3 Database, deployment stopping.|CheckTolerance()

3s-gtech · January 11, 2015

Sounds just like my issue from yesterday! See if this helps.

SOLUS 3.6 to SOLUS 3.7 and 3.8 issues – resolved | welsh-edu-it

Ghostgame · January 12, 2015

@resin1 - to resolve this, I have had to reinstall SOLUS3.

Removed the UI, service and databse via Programs and features.

I did not remove the database from the SQL instance, as when you run the latest installers, the SOLUS3 database is upgraded.

You will need to re-register SOLUS3 again before you can deploy updates but all your settings from 3.6.94 should be there.

Update the agents by running the SOLUS3 update.

resin1 · January 12, 2015

Thanks for the quick reply 3s-gtech. Based on your blog, I was going to try the change to NT AUTHORITY/SYSTEM perms in Management Studio, but since I'm no expert with that, I'm not sure I'm looking in the right place, or seeing what I should be seeing. I opened the SIMS db=>Security=>Users and looked at Properties for NT AUTHORITY/SYSTEM and the Membership page of that. But these are the tick boxes. I guess I'm in the wrong place?

#### ignore that. Have found how to add it after further searching on SupportNet. Lo and behold, I'm in business. 3.7 updated. 3.8 going through as I type. Interestingly, I found KB119666 on SupportNet which includes the line: "We have included the SQL patch 'SOLUS3 SQL2012 NT Authority Patch.rar' inside the ZIP file for Solus3 installations experiencing issues with SQL2012".

Probably my naivety, if that happens to be their fix for this issue, could they not have pushed that out on S3 so that users would at least be aware and see it, and know they might need it? If there is a known problem which has caused some sites to have to re-install S3 from scratch because no solution was forthcoming, to get round it, and other sites like ours that are only now hitting it when they would like to move on to 3.8 but necessarily it needs to move to 3.7 first, perhaps there has been time to help users out???? Grrrr!!!

Edited January 12, 2015 by resin1

[sims] SOLUS 3.7

Recommended Posts

zag

Superade

matt40k

Superade

howartp

Superade

howartp

zag

Boredguy

Sheridan

MrMat

Sheridan

zag

zag

resin1

3s-gtech

Ghostgame

resin1

Create an account or sign in to comment

Create an account

Sign in

Recent Threads

Confirm acknowledgement of parental consent requirement for the Additional Google services

Lenovo Tablet Firmware

Outloook 365 - Classic

Home

Forums

What's New