Expand my Community achievements bar.

SOLVED

AC 6.1.1 Classic b8770 Tracking logs issue

Avatar

Community Advisor

I am currently facing a tracking issue in one of my instances after upgrading from 6.0.2 to 6.1.1

Tracking files are being generated as expected (redir urls,tags,log)

Instance 1 ( tracking uploads to frontal servers) working fine

Instance 2  (registers to frontal tracking servers), tracking workflow working fine, redirection on links working, [NmsTrackingLogRtEvent not being updated]

What could be the reason?

florentlb

Adobe Campaign

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Solved as misconfiguration in frontal server config instance datasource hosts.

View solution in original post

6 Replies

Avatar

Employee

If data is present in the redirection file, you can check if tracking workflow is running or not .   

Also check the value of option NmsTracking_Pointer.

Avatar

Community Advisor

The workflow is working fine,

10/05/2018 10:22:05 nlmodule Workflow finished

10/05/2018 10:22:05 nlmodule [575/575] record(s) processed (step 'writer')

10/05/2018 10:22:05 nlmodule : Insertion of 575 record(s) 'writer' step)

10/05/2018 10:22:05 nlmodule : updating 0 record(s) ('writer' step)

10/05/2018 10:22:05 nlmodule : 0 record(s) unchanged ('writer' step)

10/05/2018 10:22:04 nlmodule 575 record(s) result from the union '' (step 'union')

10/05/2018 10:22:04 nlmodule Executing union '' (step 'union')

10/05/2018 10:22:04 nlmodule 0 record(s) selected for the query '' (step 'trackinglog')

10/05/2018 10:22:03 nlmodule Executing query '' (step 'trackinglog')

10/05/2018 10:22:03 nlmodule 575 record(s) selected for the query '' (step 'broadlog')

10/05/2018 10:22:03 nlmodule Executing query '' (step 'broadlog')

10/05/2018 10:22:03 nlmodule Workflow finished

10/05/2018 10:22:03 nlmodule [67/67] record(s) processed (step 'writer')

10/05/2018 10:22:03 nlmodule : Insertion of 67 record(s) 'writer' step)

10/05/2018 10:22:03 nlmodule : updating 0 record(s) ('writer' step)

10/05/2018 10:22:03 nlmodule : 0 record(s) unchanged ('writer' step)

10/05/2018 10:22:02 nlmodule 67 record(s) result from the union '' (step 'union')

10/05/2018 10:22:02 nlmodule Executing union '' (step 'union')

10/05/2018 10:22:02 nlmodule 0 record(s) selected for the query '' (step 'trackinglog')

10/05/2018 10:22:02 nlmodule 67 record(s) selected for the query '' (step 'broadlog')

10/05/2018 10:22:02 nlmodule Executing query '' (step 'trackinglog')

10/05/2018 10:22:02 nlmodule Executing query '' (step 'broadlog')

nmspointer option is updated as expected

<?xml version='1.0'?>

<tracking>

  <server lastLog="2018-05-10 09:25:05.188Z" lastMsgId="100107765" url="http://myhostxxx:8080"/>

  <server lastLog="2018-05-10 09:25:05.444Z" lastMsgId="72282666" url="http://myhostxxx:8080"/>

</tracking>

Avatar

Employee

Hello David,

I believe the table you are looking at , i.e- NmsTrackingLogRtEvent  Should be blank if it's a control instance. This table is populated only on a RT server (Message centre) and in the Control side the table nms:trackingLogEventHisto should be populated.

This is updated by a Mc_sync workflow and not the usual tracking workflow. In the newer version of 6.1.1 there is a new version of the sync workflow that works. Can you check if this is also running fine and then check the data in nms:trackingLogEventHisto

Regards,

Adhiyan

Avatar

Level 10

Hi David,

Were you able to find something relevant for your query here?

Gaurang

Avatar

Correct answer by
Community Advisor

Solved as misconfiguration in frontal server config instance datasource hosts.