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 runnlserver monitor -missingas well as /r/test you need to test connectivity between mid and frontals, revalidate tracking through deployment wizard. useful commandshttps://experienceleague.adobe.com/docs/campaign-classic/using/monitoring-campaign-classic/production-p...

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.

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-campaign-on-prem/deployment-guidelines/network-configuration.html?lang=en

To expand on craig's answer, it's also not recommended to delete an operator, and even disabling it can cause a lot of errors on the workflows created by it and they may need to be restarted (perhaps by an ootb operator such as the admin) to prevent future errors. Start by changing the password and disable access to rich client, then run a workflow to query your campaign/workflow schemas to find objects created by the disabled operator and proceed to restart them with a permanent admin account.

In the failing deliveryMapping, you may have the value of 'none' in the additional fields tab, this should actually be mapped correctly. if you are not sure, go through each custom mapping and check which one has the 'none' value and remove that. and test again, perhaps it was left by mistake.