DX Infrastructure Manager

Expand all | Collapse all

Controller Crash

Jump to Best Answer
  • 1.  Controller Crash

    Posted 11-06-2017 04:52 AM

    Hello!

     

    We have a problem with a robot on a windows server. The robot version is 7.80.

    The nibus service starts without problems, but the controller does not start correctly.

     

    nimbus.log shows:

    Nov 2 16:12:46:463 Nimbus: 'controller' started (pid=2716)

    Nov 2 16:12:48:463 Nimbus: 'controller' stopped (pid=2716) RET = -1073741502

     

    Port 48000 is not open and there are is no controller.log.

    Restarting nibus service does not help. Neither reinstalling the robot.

     

    How can I solve this problem?

     

    Thanks!



  • 2.  Re: Controller Crash

    Posted 11-06-2017 05:57 AM

    Hi 

     

    What is the exact windows OS platform .Ensure ports 48000-48030 open (depending on number of probes expected on this robot)

    Can you try with robot 7.93 and also ensure first_probe_port set to 48000 manuallu in robot.cfg

    http://support.nimsoft.com/Files/Archive/00055/robot_update-7_93.zip 



  • 3.  Re: Controller Crash

    Posted 11-06-2017 06:05 AM

    Hello,

     

    Thanks for your reply!

    Windows version is Server 2008 R2 Standard.

    How can I install this version? The robot looks offline in Admin Console. 



  • 4.  Re: Controller Crash

    Posted 11-06-2017 07:06 AM

    Have you tried uninstall robot , remove nimsoft folder (if it exists ) , reboot server and reinstall

    Ensure Antivirus is not interfering with the installation

    Can try with 7.80 installer again .

    Also ensure ports are open on this server /windows firewall stopped during installation to rule out issues due to this



  • 5.  Re: Controller Crash

    Posted 11-06-2017 07:40 AM

    I tried uninstall robot, remove folder, stop antivirus, reinstall. Both with x32 and x64.

    Searched online and error code 1073741502 means "Initialization of the dynamic link library failed".

    Tried to set installdir in the config file. But it does not work.

     

    The server can't be restarted outside a maintainance window.

    I'll just give up for the moment.

     

    Thanks for your effort!



  • 6.  Re: Controller Crash

    Posted 11-06-2017 09:07 AM

    Did you install the "vc_redist" components on your server?



  • 7.  Re: Controller Crash

    Posted 11-07-2017 04:26 AM

    No, the Microsoft Visual C++ 2008 Redistributable Package was already installed.



  • 8.  Re: Controller Crash

    Posted 11-07-2017 04:44 AM

    Do you have a more detailed message in the Windows Event Log about the start of the robot? Can you share the robot.log and controller.log?



  • 9.  Re: Controller Crash

    Posted 11-07-2017 09:04 AM

    There is an error in the System Log:

     

    Level Date and Time Source Event ID Task Category
    Error 11/7/2017 3:51:55 PM NimbusWatcherService 0 None "The description for Event ID 0 from source NimbusWatcherService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    NimbusWatcherService error: 6
    SetServiceStatus
    "

     

    There is no controller.log, probably because it never started properly.

     

    Here is a shorter version of nibus.log:

     

    Nov 2 16:06:50:963 Nimbus: Ready to begin: starting controller
    Nov 2 16:06:50:978 Nimbus: 'controller' started (pid=2800)
    Nov 2 16:06:50:978 Nimbus: Started
    Nov 2 16:06:52:978 Nimbus: 'controller' stopped (pid=2800) RET = -1073741502
    Nov 2 16:06:58:978 Nimbus: 'controller' started (pid=5204)
    Nov 2 16:07:00:978 Nimbus: 'controller' stopped (pid=5204) RET = -1073741502
    Nov 2 16:07:06:978 Nimbus: 'controller' started (pid=5672)
    Nov 2 16:07:08:978 Nimbus: 'controller' stopped (pid=5672) RET = -1073741502
    Nov 2 16:07:14:978 Nimbus: 'controller' started (pid=5880)
    Nov 2 16:07:16:978 Nimbus: 'controller' stopped (pid=5880) RET = -1073741502
    Nov 2 16:07:22:978 Nimbus: 'controller' started (pid=2636)
    Nov 2 16:07:24:978 Nimbus: 'controller' stopped (pid=2636) RET = -1073741502
    Nov 2 16:07:30:978 Nimbus: 'controller' started (pid=1940)
    Nov 2 16:07:32:978 Nimbus: 'controller' stopped (pid=1940) RET = -1073741502
    Nov 2 16:07:38:978 Nimbus: 'controller' started (pid=5256)
    Nov 2 16:07:40:978 Nimbus: 'controller' stopped (pid=5256) RET = -1073741502
    Nov 2 16:07:46:978 Nimbus: 'controller' started (pid=4980)
    Nov 2 16:07:48:978 Nimbus: 'controller' stopped (pid=4980) RET = -1073741502
    Nov 2 16:07:54:978 Nimbus: 'controller' started (pid=3260)
    Nov 2 16:07:56:978 Nimbus: 'controller' stopped (pid=3260) RET = -1073741502
    Nov 2 16:08:02:978 Nimbus: 'controller' started (pid=4376)
    Nov 2 16:08:04:978 Nimbus: 'controller' stopped (pid=4376) RET = -1073741502
    Nov 2 16:08:10:978 Nimbus: 'controller' started (pid=5728)
    Nov 2 16:08:12:978 Nimbus: 'controller' stopped (pid=5728) RET = -1073741502
    Nov 2 16:08:12:978 Nimbus: Too many retries used starting 'controller', next start in 1200 seconds
    Nov 2 16:11:48:041 Nimbus: Ready to close down: stopping controller
    Nov 2 16:11:48:041 Nimbus: Finished
    Nov 2 16:11:50:447 Nimbus: Ready to begin: starting controller
    Nov 2 16:11:50:447 Nimbus: 'controller' started (pid=5136)
    Nov 2 16:11:50:447 Nimbus: Started
    Nov 2 16:11:52:463 Nimbus: 'controller' stopped (pid=5136) RET = -1073741502
    Nov 2 16:11:58:463 Nimbus: 'controller' started (pid=3756)
    Nov 2 16:12:00:463 Nimbus: 'controller' stopped (pid=3756) RET = -1073741502
    Nov 2 16:12:06:463 Nimbus: 'controller' started (pid=5912)
    Nov 2 16:12:08:463 Nimbus: 'controller' stopped (pid=5912) RET = -1073741502



  • 10.  Re: Controller Crash
    Best Answer

    Posted 11-07-2017 09:21 AM

    What is the user trying to start the service? Did you check if the user used to start the service doesn't have a problem of authentication? Did you try to run the robot "manually” in Command Line? It gives sometimes a lot more information on stdout.



  • 11.  Re: Controller Crash

    Posted 11-07-2017 09:57 AM

    The user trying to start the service is SYSTEM.

     

    Tried to run the robot from command line, but there is no output in stdout.

    BUT, it works and the server is accessible from Admin Console.

    So thanks, this is a good enough workaround.

     

    Thank you!