I see that there is an EXE out there for installing robot 7.10 on Windows. Is there still an MSI file for installing robot 7.1 as well? Or has the MSI gone away?
It went away.. saw it in some release notes or somewhere else. I believe the .exe installer was more favorable to ade.
Actually this is in ade 1.22 release notes:
Change = bad
So the robot_exe package contains these files:
But the Downloads page on the support site still has an option to download this file:
I assume the latter is the legacy installer and that the package contains new-fangled wunder-installers. Am I close?
Does the new EXE installer take an nms-robot-vars.cfg file like the MSI did? I found information about installing the robot in the online docs, but I cannot tell if those instructions are for the new EXE or the old one (assuming the two are different).
Thanks for any insight!
Thanks! That's very helpful to get me started. Time to give it a test!
the reason support gave me for the demise of the MSI package was dependent on .NET 2.0 framework. Rather than fix this (which is quite easy to do) they took "a design decision" to drop the MSI and 'we re-wrote it into into the .EXE format' (their words). It's a pity they didn't make a design decision to make the .EXE installer smart enough to have the 32 & 64bit versions in the same file and deploy the correct one accordingly.
If you haven't upgraded to 7.1 be aware that, according to the logfile, that robot_msi.zip (along with others) are removed from the archive directory. IF you want to keep it, then back it up beforehand.
I'll miss the MSI because I could enable the progress bar display (for obvious reasons) - alas the EXE is sadly missing this
UPDATE: Had a quick nose at the new installer and it's actually InnoSetup (see http://jrsoftware.org/) - so much for "we re-wrote"...
I used to complain about the .net requirement for the MSI, it seemed insane to me in the first place.. had no idea this new installer was supposed to fix that. Makes sense, since support for new Windows iterations was added in the exe and they come with .net 4 which is different CLR..
That being said, I wish they'd give real attention to the installer and especially the push mechanism and just make it WORK.
AFAIK, that was the only problem with the MSI version. Why engineering chose the route of going with a different installer package, building their scripts and testing (!), not to mention all the time expended is crazy. Considering the solution to the .NET problem is to change a couple of key settings (i've created quite a few MSI packages in my time) in the project.
MSI fix = 5-10 minutes (per project).
New installer = ??
Obviously, someone thought it was the right way to go
Yeah, we have been getting some complaints about the need for .NET 2.0, which is what prompted me to test the robot 7.10 installer. I noticed that the removal of the dependency on .NET 2.0 was listed in the release note for the robot_exe package. Otherwise I was intending to hold off on robot 7.x for a while because of the reports of issues with it that were mentioned in another thread.
Robot 7.10 installed fine and picked up settings from the nms-robot-vars.cfg file. But now that it is registered with the hub and listed in Infrastructure Manager, I am having a hard time managing it. When I double-click the controller, I get an error that it could not reach the robot. But then the GUI opens with the right settings for the robot. If I make a change in the GUI, I cannot save the config because the robot claims it is locked.
Any idea if robot 7.10 does not work nicely with older versions of the hub (5.82 in our case) even if they are not on the same server? Other known gotchas that I need to know about? Thanks!
Just installed robot 7.10 on 2 more servers in our lab, and they have the same issue. I guess it is not just an issue with that first server. Bummer.
I'm probably missing something obvious/simple here...
I had to roll back to hub 5.82 because it gets lots of permission denied errors in IM 4.08 on our set-up.
I know it sounds silly, but after the robot install have you tried a restart of the robot from the IM?
This fixed the "unable to set_hub" is was getting so maybe worth a try.
Thanks for the suggestion. I might have restarted previously, but I tried it again just now to be sure. No improvement.
Will be testing with config file locking disabled shortly.
Disabling config file locking helps. I can save changes and even the pre-GUI communication error does not occur.
When I turn config file locking back on and restart, things seem to be okay. But then after a cold restart, they are broken again.
And now it looks like I am having the same issue with a robot that was upgraded from 5.70 to 7.10. I have not tested quite as much with that one.
Retrieving data ...