Configure CMR (as a Service) is failing

[kiranilla]

After successfully installation of InspectIT, i tried running the CMR as service from command-mode as an administrator in windows as shown below.. I was not able to start it up. (tried manual and automatic)

I navigated to services (services.msc) there i have tried it, but i have encountered with error, as shown below

Further i have checked in system event logs as shown below:

In the "Details Tab" which contains the following data:

System 

  - Provider 

   [ Name]  Service Control Manager 
   [ Guid]  {555908d1-a6d7-4695-8e1e-26931d2012f4} 
   [ EventSourceName]  Service Control Manager 
 
  - EventID 7024 

   [ Qualifiers]  49152 
 
   Version 0 
 
   Level 2 
 
   Task 0 
 
   Opcode 0 
 
   Keywords 0x8080000000000000 
 
  - TimeCreated 

   [ SystemTime]  2017-11-02T09:56:33.789663300Z 
 
   EventRecordID 57702 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  796 
   [ ThreadID]  19408 
 
   Channel System 
 
   Computer B7-L-5465JVL.
 
   Security 
 

- EventData 

  param1 inspectIT CMR (64 Bit) 
  param2 %%1 
   69006E00730070006500630074004900540043004D0052000000 

I tried the following ways to run it as a service:

1. Uninstall and reinstall the inspectIT, (for unistalling i used the "uninstall" folder present in the inspectit C:\inspectIT\inspectITSft\Uninstaller)
2. deleted all the shortcuts which were present in the programfiles after unistalling and restarted the machine again reinstalled it..
3. finally as i couldn't run it as a service i tried running the "startup.bat" present in the CMR folder of inspectIT.
   It was running and picking the agent but not able to pull the profile which was created for inspection. please find the screen below:
   
   
   
   
   Could you please check this issue or provide an alternative as this totally blocking the workflow.
   Thanks in advance..

Regards,
Kiran.

[ivansenic]

Hi @kiranilla.

We'll check the service starting problem, this might be a bug. Can you tell us what version of Windows do you have.

Regarding the profiles I see that you have created the seek profile and seek environment. Are you sure that your agent is mapped to use the seek environment (see https://inspectit-performance.atlassian.net/wiki/spaces/DOC18/pages/93009241/Agent+mappings+configuration)? If this is mapped correctly, then it can be that your classes are not loaded, as we do instrument them only once they are loaded (maybe try sending some requests to your app a bit). Or you have a typo in your classes FQN?

[kiranilla]

Hi @ivansenic ,
Thanks for your reply...
I am using windows 10 Enterprise.
Later i have deleted the "seekEnvironment" and "seekProfile" and recreated them and mapped the "SeekInspectAgent" with "SeekEnvironment" with a agent name "seekInspectAgent*" and its found to be loading the classes.
But as said earlier the installation is giving some problem, the CMR is not coming up as a service (as we are using windows 10). so i am using startup.bat to bring the CMR service up.. (C:\inspectIT\inspectITSft\CMR\startup.bat) Could you please check this once.
Thank you..
Regards,
Kiran.

[ivansenic]

I have created an internal ticket for this: https://inspectit-performance.atlassian.net/browse/INSPECTIT-2554. You can follow the state on the JIRA.

It's totally fine to use startup.bat for starting the CMR, I think this is a meaningful alternative to starting a service.