How to Delete the Dispatcher Paragon Spooler Controller Cache

What Is the Dispatcher Paragon Spooler Controller Cache?

The Dispatcher Paragon Spooler Controller cache is the persistent storage on the Dispatcher Paragon Spooler Controller server. Dispatcher Paragon Spooler Controller saves all necessary data to the cache so that it can run in offline mode (without connection to Dispatcher Paragon Management Server) and optimize the data flow between Dispatcher Paragon Spooler Controller and Dispatcher Paragon Management Server. The cache contains, for example, the print job metadata, billing codes, users, devices, and so on. Most of the entities stored in the cache are downloaded from Dispatcher Paragon Management Server during the Dispatcher Paragon Spooler Controller's startup. The others (e.g., users) are downloaded when needed.

About Dispatcher Paragon Spooler Controller Cache Deletion

Deleting the Dispatcher Paragon Spooler Controller cache is, in specific cases, the only way to restore proper Dispatcher Paragon Spooler Controller functionality.

When the cache is deleted, the particular Dispatcher Paragon Spooler Controller will lose all information about users, cards, jobs, billing codes, and printers etc.

  • All necessary information about printers, users rights, and billing codes are synchronized again to the Dispatcher Paragon Spooler Controller (from Dispatcher Paragon Management Server) during the first synchronization (after the restart of Dispatcher Paragon Spooler Controller services).

  • Information about print jobs is synchronized as part of the cache recovery mechanism, where Dispatcher Paragon Spooler Controller downloads all its jobs from Dispatcher Paragon Management Server and saves them to the cache.

  • The user's data will be synchronized to Dispatcher Paragon Spooler Controller (from Dispatcher Paragon Management Server) during the first authentication of the user or when the user sends a print job to Dispatcher Paragon that will be accepted by a particular Dispatcher Paragon Spooler Controller.

WARNING

The Dispatcher Paragon Spooler Controller cache is almost equal to the Dispatcher Paragon Management Server database. The request for the deletion of the Dispatcher Paragon Spooler Controller cache will be performed only when requested by Konica Minolta or when it is explicitly defined in the manual.

How to delete the Dispatcher Paragon Spooler Controller Cache

Verify the Dispatcher Paragon Spooler Controller cache recovery settings

Go to Dispatcher Paragon management interface > System > Configuration on and set orsCacheRecovery property to enabled.

In case of Dispatcher Paragon Spooler Controller cache data corruption, cache can be manually deleted and all job-related metadata will be recovered from Dispatcher Paragon Management Server.

If you omit this step, all jobs stored on the Dispatcher Paragon Spooler Controller might be lost after the end of procedure.


Stop Dispatcher Paragon Spooler Controller services

Open the Services window (e.g.Start > Run > services.msc) and stop the following services:

  1. Dispatcher Paragon Spooler Controller service

  2. Dispatcher Paragon Spooler Controller Group Service service

  3. Dispatcher Paragon Terminal Server service

  4. and, optionally, stop:

    1. Dispatcher Paragon Infrastructure Service Proxy service

    2. Dispatcher Paragon End User Interface service

    3. Dispatcher Paragon FlexiSpooler service

    4. Dispatcher Paragon Mobile print service

Delete the Dispatcher Paragon Spooler Controller Cache Directory

Delete the Dispatcher Paragon Spooler Controller cache by deleting the entire folder <install_dir>\SPOC\SpoolCache (e.g., c:\DispatcherParagon\SPOC\SpoolCache)

Start Dispatcher Paragon Spooler Controller services

Open the Services window (e.g., Start > Run > services.msc) and start the following services:

Do not start Dispatcher Paragon Spooler Controller Group Service service. It will be started by Dispatcher Paragon Spooler Controller service when proper configuration is ready.

  1. Dispatcher Paragon Spooler Controller service

  2. Dispatcher Paragon Terminal Server service

  3. and start other Dispatcher Paragon services if they are not running:

    1. Dispatcher Paragon Infrastructure Service Proxy service

    2. Dispatcher Paragon End User Interface service

    3. Dispatcher Paragon FlexiSpooler service

    4. Dispatcher Paragon Mobile print service

The Dispatcher Paragon Spooler Controller cache recovery mechanism on a standalone SPOC with the recommended hardware is processing on average 3000 jobs per minute. That means with 60 000 jobs the recovery will take about 20 minutes. SPOC is not fully functional until the recovery is finished. To see how many jobs is going to be recovered use the following SQL query:

-- query to be launched on SQDB6 database
-- use proper tenant prefix at smartq_jobs table
-- use proper server_guid, SPOC guid can be found on Dispatcher Paragon management interface -> tab Spooler Controller groups
SELECT count(1) FROM tenant_1.smartq_jobs where server_guid = 'j1dvczklt5l5hm69' and cur_status in (1,2,4,8,16,32,64,128,256,512)


Verify the correct Dispatcher Paragon Spooler Controller functionality

Once the Dispatcher Paragon Spooler Controller cache is deleted and Dispatcher Paragon Spooler Controller services are running, verify the correct Dispatcher Paragon Spooler Controller functionality according to the article Dispatcher Paragon Spooler Controller Health Check.