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.
I ran a putlic through a NSH console and it dropped a license on my win1 machine. Login worked successfully after that.