Cannot upgrade robot

[Daniel Blanco]

Has anyone ever had this issue?
I'm trying to update the robot on a hub and no matter what method I try it fails to restart afterwards. The NimsoftRobot service is completely broken afterwards.
I checked the robot directory after the attempted upgrade and I see some files still have the rename or .old or .new. I tried renaming all the .new and replaced the existing exe's and dll's > didn't work.
I copied the files (*.exe and *.dll) from a working 7.97HF3 robots's to this machine and after wards the nimbus.log just have these entries:

Aug  1 13:05:37:493 Nimbus: Ready to begin: starting controller

Aug  1 13:05:37:493 Nimbus: 'controller' started (pid=880)

Aug  1 13:05:37:493 Nimbus: Started

Aug  1 13:05:39:499 Nimbus: 'controller' stopped (pid=880) RET = -1073741515

Aug  1 13:05:45:523 Nimbus: 'controller' started (pid=2524)

Aug  1 13:05:47:535 Nimbus: 'controller' stopped (pid=2524) RET = -1073741515

Aug  1 13:05:53:561 Nimbus: 'controller' started (pid=2368)

Aug  1 13:05:55:566 Nimbus: 'controller' stopped (pid=2368) RET = -1073741515

Aug  1 13:06:01:595 Nimbus: 'controller' started (pid=4272)

Aug  1 13:06:03:597 Nimbus: 'controller' stopped (pid=4272) RET = -1073741515

Aug  1 13:06:09:622 Nimbus: 'controller' started (pid=4460)

Aug  1 13:06:11:627 Nimbus: 'controller' stopped (pid=4460) RET = -1073741515

Aug  1 13:06:17:649 Nimbus: 'controller' started (pid=5136)

Aug  1 13:06:19:660 Nimbus: 'controller' stopped (pid=5136) RET = -1073741515

Aug  1 13:06:25:681 Nimbus: 'controller' started (pid=4364)

Aug  1 13:06:27:682 Nimbus: 'controller' stopped (pid=4364) RET = -1073741515

Aug  1 13:06:33:692 Nimbus: 'controller' started (pid=6140)

Aug  1 13:06:35:700 Nimbus: 'controller' stopped (pid=6140) RET = -1073741515

Aug  1 13:06:41:714 Nimbus: 'controller' started (pid=4344)

Aug  1 13:06:43:721 Nimbus: 'controller' stopped (pid=4344) RET = -1073741515

Aug  1 13:06:49:752 Nimbus: 'controller' started (pid=996)

Aug  1 13:06:51:758 Nimbus: 'controller' stopped (pid=996) RET = -1073741515

Aug  1 13:06:57:774 Nimbus: 'controller' started (pid=5396)

Aug  1 13:06:59:787 Nimbus: 'controller' stopped (pid=5396) RET = -1073741515

Aug  1 13:06:59:787 Nimbus: Too many retries used starting 'controller', next start in 1200 seconds

The only way to fix is the re-copy the previous robot backup folder into current robot and start services. Sometimes that doesn't work and I have to re-run the base NimBUS Infrastructure.exe installer. I also tried the magic key entry in the controller.cfg but that' didn't help either. 
Looking for any other ideas here.

Thanks...

------------------------------
Daniel Blanco
Enterprise Tools Architect
Alphaserve Technologies
------------------------------

[Gene Howard]

I am not sure if this is what you are running into. But I just had a case where the 7.97hf3 was deployed and the robot would not start on the primary.
Below is what I did to fix it. This is currently with dev.

Below is a recap of what we saw and did

1) you had deployed the 7.97Hf3 robot update to the primary hub.

2) this cause the primary hub robot to restart

3) when it did restart it did not come back up.

4) what we found was that the process to copy and rename the new 7.97 dll's in the robot directory did not work.

5)  We stopped the robot service.

6) we manually renamed the old dll and .exe to _old and then renamed the .797 version back to the original file names.

7) we then started the robot service and it came up as expected.

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[Daniel Blanco]

Thanks Gene. I already tried that before. I hit that issue one time as well in past and got past it doing the above rename manually but in this situation its the nimbus.exe process that is stopped. As per the log you see we are getting:

Aug  1 13:05:37:493 Nimbus: Started

Aug  1 13:05:39:499 Nimbus: 'controller' stopped (pid=880) RET = -1073741515

Aug  1 13:05:45:523 Nimbus: 'controller' started (pid=2524)

Aug  1 13:05:47:535 Nimbus: 'controller' stopped (pid=2524) RET = -1073741515

Which I don't know what this means...

------------------------------
Daniel Blanco
Enterprise Tools Architect
Alphaserve Technologies
------------------------------

[Stephen Danseglio]

stopped -1073741515 usually indicates file system corruption so it may mean the nimbus.dll was corrupted.

Any Windows events in App or System for the controller.exe that may shed some light?

Steve

------------------------------
[Designation]
[City]
------------------------------

[Franklin Ravi D'souza]

Hi 

Can try
Please check if some other vs2017 runtime present on the system .If present try removing those and use the one provided by UIM and deploy separatley
Or else deploy  vs2017_vcredist_x86 1.0 or vs2017_vcredist_x64 1.0 separately and reboot the system so it uses the UIM VS2017 runtime exe and then try the robot update to 7.97

[Yu Ishitani]

A bat file is shipped with recent robot_update package and it is supposed to run part of deployment, however I have seen some cases the bat failed.
You can run the bat manually or do the same operation written in the bat manually.

[Yu Ishitani]

The bat is "robot_shared_libs_rename.bat" in robot folder. See "robot_shared_libs_rename.log" for batch log.

[Daniel Blanco]

Thanks guys. I think this is the filesystem issue not UIM specific. I already did all the renames, copy in place restart etc.. When the box rebooted there was a file system issue message and box would not boot. Did a 2nd reboot and when it started has a windows error issue. 
Going to request a new Vm for this box and rebuild the hub. 
I even just tired updating the cdm probe and afterwards it would not start. So the box is toast... Thanks for the suggestions...

------------------------------
Daniel Blanco
Enterprise Tools Architect
Alphaserve Technologies
------------------------------

[Daniel Blanco]

Ok there is something really wrong with this robot update to 7.97. Case #: 20049371

I just hit  a 3rd box where after upgrading to robot 7.97 the robot service will not start up. The OS was at a fresh Windows 2008 R2 Standard no updates. I then ran Windows updates and brought the machine up to Windows 2008 R2 Standard Service Pack 1. 

Re-tried the robot update and it still broke the Nimsoft service. The robot would not start up. 
So before the upgrade I had this in the robot directory:

Then upgrading the 7.80 robot to 7.97HF3:

Then afterwards service was broken.

Have this in the robot directory:

The only way to fix it is to re-run the 7.80 hub installer. Tried running the 7.9x version and that won't start up on a clean install on this OS. I also noticed that on these boxes that the update breaks, on every re-install I get this pop up during the re-install:

No one else hit this issue? This is the 3rd box in 3 different client environment that I hit this problem. 

I do have the 2017 redistributables on this box. 

​

------------------------------
Daniel Blanco
Enterprise Tools Architect
Alphaserve Technologies
------------------------------

[Yu Ishitani]

Take a look robot_shared_libs_rename.log in robot folder, any errors ?

[Daniel Blanco]

Hi Yu, that doesn't work either. Manually renaming the exe's doesn't fix it. 
In the case [20049371Robot Upgrade Broke Hub AGAIN! Same issue completely broke] I also tried installing a vs2017 probe like cdm 6.42 and that doesn't run afterwards either. I had to downgrade the cdm probe to pre-vs2017 version.
Its looking like some 2008 OS versions are not supported possibly. But shouldn't the robot_update check for this before it actually updates so the service doesn't break completely?

------------------------------
Daniel Blanco
Enterprise Tools Architect
Alphaserve Technologies
------------------------------

[Daniel Blanco]

This just gave me a safer way to test if the update would work. I'd update the cdm probe to 6.42 and if it doesn't start up afterwards I know that hub update would break after updating to robot v7.97. This should take out the guess work. If doesn't work then downgrade to 6.30 cdm.

------------------------------
Daniel Blanco
Enterprise Tools Architect
Alphaserve Technologies
------------------------------