[sims] Error updating fileset Agent has no value for SimsUsername

[edumezz]

Hi all,

 

Please forgive my ignorance as I'm new to the educational scene. I'm just trying to catch our SIMS server up with updates and all was fine until I got to a fileset update and was met with the following error:

 

2018-05-10 22:07:00.3806|ds|Info|Deployment plan does not contain withdrawn packages, deployment can be continued.|CanExecutePlan()

2018-05-10 22:07:00.5356|ds|Info|Checking target parameters have been defined|CanExecutePlan()

2018-05-10 22:07:00.5426|ds|Info|Some targets have missing parameters|CanExecutePlan()

2018-05-10 22:07:00.5446|ds|Error|Agent UKSIMS01 64cccc1d-36ff-4d9d-9f5d-be7fcccc5b39 has no value for parameter SimsUsername|CanExecutePlan()

2018-05-10 22:07:00.5446|ds|Error|Agent UKSIMS01 64cccc1d-36ff-4d9d-9f5d-be7fcccc5b39 has no value for parameter SimsPassword|CanExecutePlan()

 

This would have been the first update I tried that would update the document server. I've trawled through every setting I can find and I have no clue where I can fill out this missing username/password.

 

Any ideas?

 

Again apologies for the ignorance.

Edited May 12, 2018 by edumezz

[ajp233]

In the SOLUS Deployment Server UI you need to go to Environment > Targets > Services > SIMS DMS and then edit it to specify a SIMS username and password

[edumezz]

Thanks for the help everyone. It was just missing from the services section in Solus.

 

In order to help the next unfortunate soul that stumbles across this problem here are the fix instructions in full:

 

Note: You don’t have to create a dedicated update user but it is recommended to stop the “old staff member hasn’t been here for years lets delete their account… many moons later… sims doesn’t update any more… IT must have broke it” problem.

 

Start from step 4 if you like to cause death and destruction for the IT people who come after you.

 

1. Log into SIMS as someone who can create new users

2. Under System Manager → Manage Users, create a new user and make sure they have the following permissions:

◦ Returns Manager, System Manager

3. Log back into SIMS as the new user to check it works and go through the first time password change routine.

4. Load up the Solus 3 Deployment Server UI

5. Navigate to: Environment → Targets → Services

6. Select the SIMS DMS service and click Edit near the bottom

7. Fill out the Server Name and use Select to fill out the database information, it will be something like:

◦ Server Name: my_sims_server_hostname\sims2012

◦ Database: sims

8. Fill out the user name and password you created in steps 2 and 3.

9. Hit Save

 

From here you’ll be able to deploy your fileset updates without upsetting the server gods.

 

Cheers all

Edited May 14, 2018 by edumezz
Formatting horrors

[supportman]

Thanks for the help everyone. It was just missing from the services section in Solus.

 

In order to help the next unfortunate soul that stumbles across this problem here are the fix instructions in full:

 

Note: You don’t have to create a dedicated update user but it is recommended to stop the “old staff member hasn’t been here for years lets delete their account… many moons later… sims doesn’t update any more… IT must have broke it” problem.

 

Start from step 4 if you like to cause death and destruction for the IT people who come after you.

 

1. Log into SIMS as someone who can create new users

2. Under System Manager → Manage Users, create a new user and make sure they have the following permissions:

◦ Returns Manager, System Manager

3. Log back into SIMS as the new user to check it works and go through the first time password change routine.

4. Load up the Solus 3 Deployment Server UI

5. Navigate to: Environment → Targets → Services

6. Select the SIMS DMS service and click Edit near the bottom

7. Fill out the Server Name and use Select to fill out the database information, it will be something like:

◦ Server Name: my_sims_server_hostname\sims2012

◦ Database: sims

8. Fill out the user name and password you created in steps 2 and 3.

9. Hit Save

 

From here you’ll be able to deploy your fileset updates without upsetting the server gods.

 

Cheers all

 

Big thanks for this, I just ran into it myself for fileset 1304! No idea why it suddenly stopped working.

 

And why they put the config details buried in those hidden menus is beyond me. But it works! so thanks.