[sims] Moved Solus3 to new server

[tech-man]

Hello

 

I have had to move SOLUS3 to a new server which I have done following KB115891 and all has gone well. I am trying to remove the old server from the "SOLUS3 Agents" screen however when I click the remove computer I receive the following error:

 

 

Does anyone know how I can clear this up?

 

Thanks!

[Rawns]

Yep, you cant remove the old server as it's had the UI against it.

 

Does your new server have the same name as the old one, or is it different?

 

If it has the same name:

 

Load SQL Server management Studio, expand the SOLUS3 database > Tables, right click and select edit top 200 rows for the SOLUS3.Agent table. Find the old server in the list and in the agent_status cell for the old server, change the value from 2 (Offline) to 16 (Install Failed) and save. Back in the SOLUS3 UI, under the SOLUS3 Agents screen, the old server's status should now be listed as 'Install Failed' allowing you to highlight it and click on Reinstall Agent. SOLUS3 will now reinstall the agent onto the new server and you won't lose any links that have been set up in the your environment.

 

If the server name is different:

 

When you changed the Deployment Service Host Computer in the UI, it should have prompted you to install a new SOLUS3 agent. Load SQL Management Studio, expand the SOLUS3 database > Tables, right click and edit top 200 rows for the SOLUS3.Agent table. Find the old server in the list and make a note of the GUID for the server name and copy this. Go to c:\program files\Solus3\AgentService and edit the following file: Sims.Solus3.Agent.AgentService.exe.config

 

Find where is says

Edited May 8, 2013 by Rawns

[matt40k]

What did I tell you @tech-man!! If you can't remove the UI, that's why I said you don't install it on your machine - cause this would happen more often. Have you logged a call cause Nick should be able to remote in and do it directly in the db.

[tech-man]

Matt, had to move SIMS to another server because of the .net issue I then had to move SOLUS with it... Spoke to Nick but he's snowed said I'd post on here as well...

[tech-man]

Thanks RAWNS will look at that...

[matt40k]

Ah yer, forgot about that little gem, sorry mate. Yer spoke with Nick on the way out, lots of teething issues at the mo. I assume you are renaming the server to match the former? What did you end up doing, install S3 then restoring the DB? Assuming so, doing like @Rawns said about setting then agent to failed then redeploying will sort it out.

[tech-man]

Hi @Rawns

 

The new SOLUS3 server has an agent installed on it already and appears in agents and is apparently responsible for the user interface as well as database etc. Still cant remove the old SOLUS3 server after failing it. Do you have any other ideas?

 

Thanks

[Rawns]

Hi @Rawns

 

The new SOLUS3 server has an agent installed on it already and appears in agents and is apparently responsible for the user interface as well as database etc. Still cant remove the old SOLUS3 server after failing it. Do you have any other ideas?

 

Thanks

 

Again, is the server name the same or different to the old one?

 

You can't remove the server agent from the UI despite the server having the same name or a different name. You have to reuse the server entry and not add a brand new agent entry. You have to either re-deploy the agent to the server after marking it as failed in the database (if the new server name is the same as the old one),

 

or

 

If the server has a new name, once you load the UI and update the settings to reflect the new name, it will prompt you to install a new SOLUS3 agent on the server. You will then have two servers listed, the old (offline, with the SOLUS3 UI protection against it) and the new (online). The old one has all the SIMS/FMS database, sql, workstation settings etc set up and the new server entry will have nothing. You then have to get the GUID of the old offline server from the DB and put it into the new SOLUS3 agent config file and restart the agent. This will cause the old server entry to now come back online and the new server to go offline. You can then remove the offline new entry which has no settings against it so you can remove it without errors.

[tech-man]

Sorry it's a new server with a different name/ip.

[tech-man]

Thanks @Rawns, think this is stuck - trouble is now I have two SOLUS3 servers in the DB with "UI installed"

[Rawns]

Sounds like you jumped the gun and re-associated the new server agent with everything including SOLUS3 rather than modifying the config file to make it the "old" agent instead.

 

Guess you'll need to log a call with Capita to get them to strip it out of the database.

[tech-man]

Thanks... my good LA support have logged a call for me.