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'.