For weeks I have been dealing with google and researching MS hotfixes to get rid of the above errors in the event log. Everyday it drove me completely insane that I could not find a fix. Then one day I find this .Net 2.0 hotfix for remote servers. I asked the client to obtain the hotfix for me and I tried testing it in a VPC. It would not install the hotfix, because it stated that the component needed did not exist. I was back to square one, so I started poking around Central Administration yesterday. I looked in the "Timer Job Definitions". For some reason every single content deployment job and backup job for one time use that was ever created in Sharepoint still existed in this area. I went through and deleted each job and all my error messages disappeared. For anyone having this same problem look in your timer job definitions and see if Sharepoint is still running one time use jobs. It will help you out a bunch in the long run. There is probably another hotfix for this problem, but I have requested at least 3 to 4 hotfixes in the past two weeks and need a hotfix break for now. I am still holding out that we will get a service pack in the near future to fix any issues anyone has run across in MOSS.
mosslover