tables involved in tracking configurations ?

[SheetalAgrawalSoni]

My deployment wizard has different entry for tracking server but when it comes to delivery its always connectING TO WRONG SERVER and we think thats the reason for not resolving this problem. As deployment wizard does not show the one that reported in logs, I am interested to find from where this is comming ? Do we know any table or xml file that will have tracking server configurations that delivery is getting and i can modify the same ? 

I followed the steps and deleted hard cache on my computer and restart neolane and apache services. 

any recommondations please respond to this post. 

Value in NmsTracking_SecureServerUrl is correct "https://gmde-mid-stage14-t.adobe-campaign.com" but in reality its picking up wrong URL " 'https://gmde-mid-stage14.campaign.adobe.com'" .. From Where else it can pick up this url ? Cache ?

Logs 

07/28/2020 1:01:30 PM DLV-490038 An error occurred while validating the delivery.
07/28/2020 1:01:30 PM DLV-490043 Delivery action canceled. Unable to export tracking data to the tracking server.
07/28/2020 1:01:30 PM RED-520026 Could not upload redirection information on the tracking server(s).
07/28/2020 1:01:20 PM RED-520025 Communication failed with tracking server 'https://gmde-mid-stage14.campaign.adobe.com'. Please check that the server is started and check if the connection parameters defined in the deployment wizard (or directly in the options), are correct.
07/28/2020 1:01:20 PM RED-520021 Invalid login or password.
07/28/2020 1:01:20 PM Uploading tracking information on server 'gmde-mid-stage14.campaign.adobe.com'...

07/28/2020 1:01:10 PM RED-520025 Communication failed with tracking server 'https://gmde-mid-stage14.campaign.adobe.com'. Please check that the server is started and check if the connection parameters defined in the deployment wizard (or directly in the options), are correct.
07/28/2020 1:01:10 PM RED-520021 Invalid login or password.
07/28/2020 1:01:09 PM Uploading tracking information on server 'gmde-mid-stage14.campaign.adobe.com'...
07/28/2020 1:01:04 PM DLV-490119 Analysis completed in 8s with warnings (3 message(s) waiting).
07/28/2020 1:01:04 PM Applying rule 'Wave scheduling check'.
07/28/2020 1:01:04 PM Applying rule 'Deco-mail check'.

[SheetalAgrawalSoni]

I faced same issue long back and here are steps I took for tracking not working :- Here are steps or best practices to resolve the issue :-

1- Truncate table XtkWorkflowLog

2- INSERT INTO XtkWorkflowLog(iWorkflowId) values (0)

3. Go to platform > options and Set the LastConsolidated to latest date time and Pointer remove the numbers from Options settings.

4. In technical Workflow section - Restart Tracking workflow

it should work !

Have fun ! 

Sheetal 

+1 678 599 8911 

[#3 · Accepted solution]

 faced same issue long back and here are steps I took for tracking not working :- Here are steps or best practices to resolve the issue :-

1- Truncate table XtkWorkflowLog

2- INSERT INTO XtkWorkflowLog(iWorkflowId) values (0)

3. Go to platform > options and Set the LastConsolidated to latest date time and Pointer remove the numbers from Options settings.

4. In technical Workflow section - Restart Tracking workflow

it should work !

Have fun ! 

Sheetal 

+1 678 599 8911 

[Prasanna_Soni]

Hi please check the option "NmsTracking_SecureServerUrl" . That will give the tracking server URL.

[Prasanna_Soni]

Value in NmsTracking_SecureServerUrl is correct "https://gmde-mid-stage14-t.adobe-campaign.com" but in reality its picking up wrong URL " 'https://gmde-mid-stage14.campaign.adobe.com'" .. From Where else it can pick up this url ? Cache ?

[amritakedia_epsilon]

 Can you please check the username and password if that is correct for the external account .. Check the external account (internal name) mentioned in the value of the option NmsTracking_ExtAccount . In the mid sourcing tab of the external account you can test the connection by clicking "Test Connection" button.

[Prasanna_Soni]

Test connections works as expected and NmsTracking_ExtAccount value is "defaultEmailMid" .. Now where should i check what is defaultEmailMid

[amritakedia_epsilon]

You will need to search the External Account with the Internal name "defaultEmailMid"

[Prasanna_Soni]

thats my "Email routing using mid-sourcing" and It test perfectly fine. When I click on test connection I get message that testing is succesful. Additionally when i click on enable tracking for instance, I get that also succesful message. So all good there.