1 Reply Latest reply on Sep 29, 2008 2:28 PM by Bill Robinson

    RSCD Agent has encountered a problem and must be closed

      During my Onboarding labs, I fired up my VM to begin the days work. Once my win1 machine was up and running (my app server host), I was greeted with the "RSCD Agent has encountered a problem and must be closed" dialog, inviting me to send the status report to Microsoft.

       

      I checked the services and found everything to be running as it should be.

       

      When I tried to log in to my Operations Manager, I got a "Could not authenticate" error. I looked up the cause of this error and found it was telling me that my application server was not running. This didn't agree with what my services page was telling me.

       

      To troubleshoot, I uninstalled the RSCD agent. It installed and started up with no problems. However, I was still having the "Could not authenticate" error when trying to log in to OM.

       

      I uninstalled and reinstalled the Operations Manager (full). During the configuration, I had problems pointing to my fileserver. When I clicked "Next" on the fileserver configuration portion, it told me that my fileserver was not licensed and would not respond to requests. I told it to press on anyway, but noted the error to look into later.

       

      After the installation, I was not surprised to find that I still received the "Could not authenticate" error which was telling me that my app server is not running. Again, this was contrary to what my services page was telling me.

       

      At this point, I realized this was not a problem that was going to be solved by reinstalling any aspect of the BladeLogic package. I started digging around in log files and struck gold.

       

      In the following location:

       

      C:\Program Files\BladeLogic\OM\br\ConfigAppServer1.log (where ConfigAppServer1 is the name of my App Server)

       

      I opened that log file and the very last line is the clue that I needed. Reviewing my log file from previous sessions, I realized that this last line is NOT what should be there for a successful launch, which indicated that this was the source of my problem.

       

      Either a file server is not specified or it is not running a licensed agent. Please make sure that a valid file server is specified.

       

      I ran a putlic through a NSH console and it dropped a license on my win1 machine. Login worked successfully after that.

        • 1. Re: RSCD Agent has encountered a problem and must be closed
          Bill Robinson

          During my Onboarding labs, I fired up my VM to begin

          the days work. Once my win1 machine was up and

          running (my app server host), I was greeted with the

          "RSCD Agent has encountered a problem and must be

          closed" dialog, inviting me to send the status report

          to Microsoft.

           

          This could have been from the VM... just restart the agent service.

           

          I checked the services and found everything to be

          running as it should be.

           

          When I tried to log in to my Operations Manager, I

          got a "Could not authenticate" error. I looked up

          the cause of this error and found it was telling me

          that my application server was not running. This

          didn't agree with what my services page was telling

          me.

          Look in the %PROGRAMFILES%\OM\br\appserver.log to see if it's actually running or not (like if there are error messages in here indicating a failure of the appserver) also look to see if something is listening on the appserver ports and see if the binary is actually running is a ps/taskman list.

           

           

           

           

          To troubleshoot, I uninstalled the RSCD agent. It

          installed and started up with no problems. However,

          I was still having the "Could not authenticate" error

          when trying to log in to OM.

          The RSCD agent has nothing to do w/ authentication of the client GUI. you should have left it installed.... :)

           

           

           

           

          I uninstalled and reinstalled the Operations Manager

          (full). During the configuration, I had problems

          pointing to my fileserver. When I clicked "Next" on

          the fileserver configuration portion, it told me that

          my fileserver was not licensed and would not respond

          to requests. I told it to press on anyway, but noted

          the error to look into later.

          This is probably the last thing you should do, look through logs and what not and determine why the appserver is not starting. Also, as you found out, uninstalling the agent means that a reinstall of the agent results in a unlicensed host....

           

           

          After the installation, I was not surprised to find

          that I still received the "Could not authenticate"

          error which was telling me that my app server is not

          running. Again, this was contrary to what my

          services page was telling me.

          yeah - ignore that ;)

           

          At this point, I realized this was not a problem that

          was going to be solved by reinstalling any aspect of

          the BladeLogic package. I started digging around in

          log files and struck gold.

          see above...

           

          In the following location:

           

          *C:\Program

          Files\BladeLogic\OM\br\ConfigAppServer1.log*

          (where ConfigAppServer1 is the name of my App

          Server)

           

          I opened that log file and the very last line is the

          clue that I needed. Reviewing my log file from

          previous sessions, I realized that this last line is

          NOT what should be there for a successful launch,

          which indicated that this was the source of my

          problem.

           

          * Either a file

          server is not specified or it is not running a

          licensed agent. Please make sure that a valid file

          server is specified.*

          was this there before you uninstalled? that would indicate that your agent wasn't running when the appserver tried to start, probably due to the crash you noted at the begining.

           

           

          I ran a putlic through a NSH console and it

          dropped a license on my win1 machine. Login worked

          successfully after that.

           

          What VM do you have? (eg where did you get it) - do you have an 'AppServerProfiles.xml' file present in the br directory? That would indicate having a "multi-instance" appserver - just changes some of the log files. One known issue w/ vmware, and even real servers is that if the app and db are on the same box, you need to make sure the app service is dependant on the db service, so the db is up when the appserver starts...