"Compile Error in Hidden Module: Distmon"

I deleted these two files and it worked:<br /><br />C:Documents and Settings\<user>\Application Data\Microsoft\Excel\XLSTART\PDFMaker.xla<br /><br />C:Documents and Settings\<user>\Application Data\Microsoft\Office\Recent\PDFMaker.xla.LNK<br /><br />--jsh

I also had a similar problem, but found that my pdfmaker.dot and pdfmaker.xla files were not in the program files tree. Instead they resided in the documents and settings tree, with one instance in every user account on the computer.

Removing them all and performing the repair option as above cured the error.

YAY! I followed Robert Caspe's instructions (with the following exceptions) and it worked. THANKS, my brain won't explode now!

1. Didn't remove "acrobat 6 upgrade" (don't even know if it's there)
2. Deleted PDFMaker.dot and PDFMaker.xla files from both OFFICE11 and XLStart folders
3. Didn't reinstall 8.0, just opened it and went to Help/Repair Adobe Reader Installation. It took about 45 seconds.

Well, on next boot the same error message appeared. I tried deleting the empty XLStart folder (instead of renaming), but it didn't help.
Sorry for any false hope. I did send an email to Adobe Tech Support, but I'm not very hopeful.

I followed Nod-e's suggestion. My XLStart folder was empty (didn't contain any pdfmaker files). I just renamed it to _XLStart and problem disappeared.

I am having the same problem today. Not having any luck though trying the suggestions here. I first did a search for the two files PDFMaker.dot and PDFMaker.xla They do not exist, have hidden files to show.

I've tried both Adobe 8.0 and Office XP repair. That didn't make any difference. Uninstalled then reinstalled 8.0. No difference.

The odd thing is it's only doing this with one profile on the computer. Tried all of these with the different profiles, still didn't help.

Any thoughts?

I also upgraded to Adobe Acrobat 8 over Microsoft Office 2007. I just removed the file:Program Files/Microsoft Office/Office12\XLSTART and that completely resolved the problem - no need for any other action.
I remember this happening a few years ago upgrading to Acrobat 5? would think Adobe would have their act together by now and done some decent testing before release so their tech support people were prepared for the inevitable...

I called Adobe first for support... Actually I opened a web case first with the Customer Service section and they replied and said to contact Tesh Support. I opened a web case with Tech Support and they replied and said to contact Customer Service so that's when I called.

Long story short the tech dept did not have the answer and after an hour of troublshooting he said it was an issue with MS. I didn't buy that answer.

The above worked and it seems to be an Adobe issue not MS - maybe the Adobe tech team should have someone checking the forums so they can update their knowledge tree.

dph

I had the same problem and could not find the PDFMaker.xla until I checked the search box under advanced to look for hidden files and folders as B. Casey noted above. I found two of the files under documents and settings. After I deleted them the problem with XL went away. I then did detect and repair and it is still ok.

I got the same error (..Compile error.. DISTMON) when launching XL. I'm running Office 2007 and recently upgraded Acrobat 6.0 to 8.0, which I believe caused the error.

I then did two things:

First, under the control panel, Add/Remove Programs, I removed "acrobat 6.0 upgrade" which did not seem to be removed automatically by the 8.0 installer.

Then, I found the "pdfmaker.xla" file in C:/program files/microsoft office/office11/xlstart and deleted it (also deleted one in ../recent but I don't know if it matters. (I may have an error in my recollection here, it might have been in the folder OFFICE12 instead of OFFICE11 but neither any longer has an .XLA file in it (they are completely empty).)

Then, I reinstalled the 8.0 DVD and selected "INSTALL" and "REPAIR". I then waited patiently about 15 minutes for the install and...

Voila.. it worked and removed the error. Thanks.