When we click on Enable the tracking instance in instance Configuration wizard it gives us error as shown in Screen shot. Please note this use to work as expected and all of suden this problem started
ERROR :- HTTP Connection Timed out.
RED-520025 Communication failed with tracking server 'http://10.30.142.228. Please the that server is started and check if the connecation parameter defined in deployment wizard are correct.
Solved! Go to Solution.
It turn out to be Processes was stuck up at Mid source level. Not sure exact reason but as soon as Adobe restarted the Mid source it started working.
The screenshot is not availble, please upload, also can you login into the mkt host and telnet to your tracking server on ports 8080 and 80, please see the architecture diagram below to see which ports need to be open, also check the network configuration guide https://experienceleague.adobe.com/docs/campaign-classic/using/installing-campaign-classic/install-c...
80 and 8080 against RT server does not work, 443 works
open up port 80,
on your internal tracking configuration also see if you can set https rathern than http then, but you should enable 443 and 80 ideally between mkt and frontal servers.
But if you notice error , the ip address does not look like Mid source ip address. It appears its some kind of Private ip address so not sure enable is going to help anyway
Views
Replies
Total Likes
Can you provide an architecture diagram, it seems its the mid source needing to connect to tracking, also is this full-on prem deployment? hybrid?
[MKT] --- [MID]--- [FRONTALS]
Check services are running on frontal servers and also run
nlserver monitor -missing
as well as /r/test you need to test connectivity between mid and frontals, revalidate tracking through deployment wizard.
useful commands
Views
Replies
Total Likes
It turn out to be Processes was stuck up at Mid source level. Not sure exact reason but as soon as Adobe restarted the Mid source it started working.
Views
Likes
Replies
Views
Likes
Replies