Skip to main content

Mygeotab API Adapter - DeviceProcessor2 and UserProcessor2 have never been run

MLin-2111
Original Poster

Hello, 

Got a question regarding setting up the "MyGeotabAPI adapter" in my local machine. 

  • model: DM2
  • version: v3.13.0
  • MyGeotabAPIAdapter_SCD_win-x64.zip
  • SQL server
  • SQL platform: SSMS 21
  •  

Following is the:

"Device": { "EnableDeviceCache": true, "DeviceCacheIntervalDailyReferenceStartTimeUTC": "2025-01-01T06:00:00Z", "DeviceCacheUpdateIntervalMinutes": 1, "DeviceCacheRefreshIntervalMinutes": 1440 }, "User": { "EnableUserCache": true, "UserCacheIntervalDailyReferenceStartTimeUTC": "2025-01-01T06:00:00Z", "UserCacheUpdateIntervalMinutes": 1, "UserCacheRefreshIntervalMinutes": 1440 },

error when I start api:

 

2025-11-05 16:11:39.9492|INFO|"******** PAUSING SERVICE: DatabaseMaintenanceService2 because of the following: > The Orchestrator service has not completed initialization. The DatabaseMaintenanceService2 will check again at 11/5/2025 9:11:44 PM (UTC) and will resume operation if the Orchestrator service has completed initialization at that time. "||MyGeotabAPIAdapter.Logging.MessageLogger| 2025-11-05 16:11:40.3148|INFO|Initialization completed.||MyGeotabAPIAdapter.Services.Orchestrator2| 2025-11-05 16:11:41.1251|INFO|******** STARTING SERVICE: MyGeotabAPIAdapter.BinaryDataProcessor2 (v3.13.0.0)||MyGeotabAPIAdapter.Services.BinaryDataProcessor2| 2025-11-05 16:11:41.2785|INFO|"******** PAUSING SERVICE: BinaryDataProcessor2 because of the following: > The prerequisite DeviceProcessor2 has never been run. > The prerequisite DeviceProcessor2 is not currently running or has not yet completed initialization. Please ensure that all prerequisite processors are running. The BinaryDataProcessor2 will check again at 11/5/2025 9:11:51 PM (UTC) and will resume operation if all prerequisite processors are running at that time. "||MyGeotabAPIAdapter.Logging.MessageLogger| 2025-11-05 16:11:41.8026|INFO|******** STARTING SERVICE: MyGeotabAPIAdapter.ChargeEventProcessor2 (v3.13.0.0)||MyGeotabAPIAdapter.Services.ChargeEventProcessor2| 2025-11-05 16:11:41.9561|INFO|"******** PAUSING SERVICE: ChargeEventProcessor2 because of the following: > The prerequisite DeviceProcessor2 has never been run. > The prerequisite DeviceProcessor2 is not currently running or has not yet completed initialization. Please ensure that all prerequisite processors are running. The ChargeEventProcessor2 will check again at 11/5/2025 9:11:51 PM (UTC) and will resume operation if all prerequisite processors are running at that time. "||MyGeotabAPIAdapter.Logging.MessageLogger|   2025-11-05 16:11:42.4718|INFO|******** STARTING SERVICE: MyGeotabAPIAdapter.ControllerProcessor2 (v3.13.0.0)||MyGeotabAPIAdapter.Services.ControllerProcessor2| 2025-11-05 16:11:42.6223|INFO|Controller cache cleared.||MyGeotabAPIAdapter.GenericGeotabObjectCacher`1| 2025-11-05 16:11:42.8622|INFO|Controller cache updated with 815 records added.||MyGeotabAPIAdapter.GenericGeotabObjectCacher`1| 2025-11-05 16:11:42.8622|INFO|Controller cache refresh completed.||MyGeotabAPIAdapter.GenericGeotabObjectCacher`1| 2025-11-05 16:11:43.1555|INFO|******** STARTING SERVICE: MyGeotabAPIAdapter.DeviceProcessor2 (v3.13.0.0)||MyGeotabAPIAdapter.Services.DeviceProcessor2| 2025-11-05 16:11:43.3010|INFO|Device cache cleared.||MyGeotabAPIAdapter.GenericGeotabObjectCacher`1| 2025-11-05 16:11:43.7436|INFO|ControllerProcessor2 pausing for the configured update interval (00:10:00).||MyGeotabAPIAdapter.BackgroundServiceAwaiter`1| 2025-11-05 16:11:44.1486|INFO|******** STARTING SERVICE: MyGeotabAPIAdapter.DeviceStatusInfoProcessor2 (v3.13.0.0)||MyGeotabAPIAdapter.Services.DeviceStatusInfoProcessor2| 2025-11-05 16:11:44.2982|INFO|"******** PAUSING SERVICE: DeviceStatusInfoProcessor2 because of the following: > The prerequisite DeviceProcessor2 and UserProcessor2 have never been run. > The prerequisite DeviceProcessor2 and UserProcessor2 are not currently running.

 

Join the conversation

You need to be logged in to reply to this post and participate in the Geotab Community discussions.

Top Answers

Hi @MLin-2111​,

 

Those aren't error messages. It's part of the orchestration process that coordinates parallel services when the API Adapter starts. It generally takes about a minute for this process to complete and for all of the enabled services to begin processing data.

 

The Service Interdependencies section in the guide provides more detail.

 

Steve

2 Replies

I think @ShuyMijares (Métrica Móvil)​ can help you with this...

Hi @MLin-2111​,

 

Those aren't error messages. It's part of the orchestration process that coordinates parallel services when the API Adapter starts. It generally takes about a minute for this process to complete and for all of the enabled services to begin processing data.

 

The Service Interdependencies section in the guide provides more detail.

 

Steve

Still have questions?