Message Tracking errors 8004100e and 80041010
ssjaronx4
Member Posts: 37 ■■□□□□□□□□
Hi guys,
All of our work computers give the same error when trying to run message tracking - WMI 8004100e. I found a batch file which was supposed to cure it and ran it and now I get 80041010. Any idea why we get these errors? The software is deployed by GP.
All of our work computers give the same error when trying to run message tracking - WMI 8004100e. I found a batch file which was supposed to cure it and ran it and now I get 80041010. Any idea why we get these errors? The software is deployed by GP.
Comments
-
HeroPsycho
Inactive Imported Users Posts: 1,940
It would be helpful to know which version of Exchange you're running, and what the batch file you ran was.
Also, does running Message Tracking work when you do it on the Exchange server?Good luck to all! -
blargoe
Member Posts: 4,174 ■■■■■■■■■□
Try wmiadap /fIT guy since 12/00
Recent: 11/2019 - RHCSA (RHEL 7); 2/2019 - Updated VCP to 6.5 (just a few days before VMware discontinued the re-cert policy...)
Working on: RHCE/Ansible
Future: Probably continued Red Hat Immersion, Possibly VCAP Design, or maybe a completely different path. Depends on job demands...