Article ID: 123432, created on Nov 6, 2014, last review on Nov 6, 2014

  • Applies to:
  • Business Automation 5.5

Question

You are trying to synchronize a resource from service template to subscription or synchronize all subscriptions on plan.

There are many subscriptions and after some time error appears: Service Unavailable. Synchronization process however runs in backend.

How to check whether it eventually completed with success or failed?

Answer

For resource synchronization in service template:

  1. Open /usr/local/bm/log/PEMGATE.log on PBA-E server.
  2. Search up from the bottom for start of method InstallSTResourceToSubscrs. The line will look like(where XXX is id of the staff member that initiated synchronization):

    [14-07-18 16:50:45.164 Worker1.3   RQ1216619 NTE] Entering method PEMGATE_Container::Worker1.3.InstallSTResourceToSubscrs(user = XXX, transaction = 1121228, SID = 164774, lang = en, HP)
    
  3. Remember thread ID(in example above RQ1216619) and search down again for the end of InstallSTResourceToSubscrs. The line should contain the same thread ID, e.g. line will look like:

    [14-07-18 16:59:37.162 Worker1.3   RQ1216619 NTE] ---[0] ErrorMessage* PEMGATE::InstallSTResourceToSubscrs(Int, Int, Int, Int, Int, Int, Int, Int, Int, Int, Int, Int, Int)
    

It means that synchronization was completed successfully. If instead you see the following line:

    [14-07-18 16:59:37.162 Worker1.3   RQ1216619 NTE] ...[0] *** INTERRUPTED BY EXCEPTION *** ErrorMessage* PEMGATE::InstallSTResourceToSubscrs(Int, Int, Int, Int, Int, Int, Int, Int, Int, Int, Int, Int, Int)

it means that synchronization was completed with error. Please scroll up to check the error.

If you did not find end of the method InstallSTResourceToSubscrs then it is still being executed. Please check it after 10 minutes.

For service plan synchronization with subscriptions:

Please use method above, but check /usr/local/bm/log/BM.log and method SynchronizeSubscr.

Search Words

synchronization

service unavailable

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 801221f8cd76fba7300d1e6817c8e08b 92711db0799e8aefe8e51f12dace0496

Email subscription for changes to this article
Save as PDF