Multiple Windows event log errors : DCOM failed to start as it cant find Foxit Reader

[Memfis]

Hi,

I used a portable version of foxit reader on a usb stick to open a pdf on a colleague's computer.
Since then his event log is is filling with hundreds of these errors :

WinEvtLog: System: ERROR(10000): DCOM: {username}: {Hostname}: {Hostname}: Unable to start a DCOM Server: {14E8BBD8-1D1C-4D56-A4DA-D20B75EB814E}. The error: "%3" Happened while starting this command: J:\Foxit.exe -Embedding

Obviously this is because J:\Foxit.exe no longer exists.

I've tried installing the full version (downloaded from your site in the last couple of days).
Uninstalling it.
Cleaning the registry of anything to do with foxit that I could find.
Searched registry for 14E8BBD8.
Using dcomcnfg.exe to search for anything related.
Searched PC for foxit & 14E8BBD8 (nothing found).
Reinstalling foxit.

However I am still getting hundreds of these errors.

My thanks to the writers of foxit Reader, I have found it very useful over the last year or so and would like to continue using it.

[christina]

Hello Memfis, have you tired sticking to another machine to open pdfs? Or ever tried another portable pdf reader on your colleague's computer?

Please have a look at the following link that I searched in Microsoft website, I hope that helps.
http://search.microsoft.com/Results.aspx?qsc0=0&q=Event+ID+10000++Unable+to+start+a+DCOM+Server&mkt=en-US&FORM=QBME1&l=1

[Memfis]

Hello Memfis, have you tired sticking to another machine to open pdfs? Or ever tried another portable pdf reader on your colleague's computer?

I'm sorry I'm not sure that this will help. I don't have a problem opening pdf's on their computer using foxit after reinstalling it. The problem is that the original version of foxit I used to open the pdf has added a dcom process that can no longer be started as the original foxit executable no longer exists (as it was on a usb stick). The problem is that the dcom server will no longer start and is filling the errorlogs with hundreds of the above error.

Please have a look at the following link that I searched in Microsoft website, I hope that helps.
http://search.microsoft.com/Results.aspx?qsc0=0&q=Event+ID+10000++Unable+to+start+a+DCOM+Server&mkt=en-US&FORM=QBME1&l=1

I had a look at the links on this page without success. The only thing Microsoft recommend is to reinstall the program : ms842069 (http://msdn.microsoft.com/en-us/library/ms842069.aspx)

I really need a foxit reader developer to explain how to remove this process so that the dcom server can start and so that the logs aren't filling up (which is setting off our security logging software too).

Do developers read this forum or would I have better success emailing support?

[christina]

Sorry for my late. I saw your email and have replied to you, please check it. thanks.

[Memfis]

Thank you Christina, I recieved your email and I look forward to a reply.

[Memfis]

Hi Christina,

I'm afraid your latest suggestion didn't work.
I've also replied to your email.

Regards
Memfis

[Memfis]

Hi Christina,

I haven't heard anything lately. Is there anything I can do?

[christina]

Hello Memfis，sorry for this delay. In my last email, I suggested you to delete the following two items but no hlep.
HKEY_CLASSES_ROOT\FoxitReader.Document
HKEY_CLASSES_ROOT\CLSID\{14E8BBD8-1D1C-4D56-A4DA-D20B75EB814E}

Just now, I discussed with our developer, he told me try to delete the following item too:
HKEY_CLASSES_ROOT\.pdf

If you still have errors active after deleting the above registry items, I believe Foxit Reader not the cause of this problem. You need to look into your dcom server or your system.

I just read again your message, and noticed you said "you has added Foxit Reader to a dcom process" . How do you add Foxit to a dcom process?

Basically, reinstall and uninstall foxit reader will remove foxit info keep in registry after you remove usb stick. In my end, it does this.

[Memfis]

Hi Christina, Thanks for getting back to me.


Just now, I discussed with our developer, he told me try to delete the following item too:
HKEY_CLASSES_ROOT\.pdf

I've just tried installing the latest version of foxit reader from your website and then uninstalling it. I then searched the windows registry for any items related to foxit reader or pdf's using the following search terms and removed a few which the uninstaller had missed :
"fox" (excluding foxpro the outlook db system)
"foxit"
"pdf"
"{14E8"
"14E8"
"J:\" hoping to locate where it's starting it from without success.

If you still have errors active after deleting the above registry items, I believe Foxit Reader not the cause of this problem. You need to look into your dcom server or your system.

Foxit Reader did insert this process into the dcom service. To be honest I don't see why it setup a dcom process when it was run as a standalone exe. If installed using the setup then I would understand, however as a stand alone executable this is not required.

Yes I also believe the problem lies in something left in the dcom server and not the windows registry, however the dcom process browser (configurator or what ever it calls itself) does not have a search/find function it is impossible to find without know where the foxit reader developers have placed such a command.

I just read again your message, and noticed you said "you has added Foxit Reader to a dcom process" . How do you add Foxit to a dcom process?

Please understand that I did NOT add this dcom process. The only people who can tell you how to add such a process and where foxit reader has places it's process is the foxit reader developers.

Basically, reinstall and uninstall foxit reader will remove foxit info keep in registry after you remove usb stick. In my end, it does this.
I have tried a number of times to install the latest downloadable setup files from your website then uninstall them without success. It seams that the uninstall program only removes processes/entries added by the installer and does not remove any erroneous entries left over by other installations.

You can duplicate this bug by downloading the zip package onto a usb stick and just running (not installing) the program on a clean copy of XP.
If you monitor eventlogs with security software such as ossec it will email you everytime this error occurs.

[Memfis]

Please could you ask your developers where they insert the command 'Foxit.exe -Embedding'.

[christina]

Hello Memfis,

1. We have tested for many times, but no luck to reproduce this issue in our end.

2. "Please could you ask your developers where they insert the command 'Foxit.exe -Embedding'. "
-- Our developers told me they don't insert a command like 'Foxit.exe -Embedding'. "

3. " Foxit Reader did insert this process into the dcom service. To be honest I don't see why it setup a dcom process when it was run as a standalone exe. If installed using the setup then I would understand, however as a stand alone executable this is not required."
-- Foxit Reader doesn't insert process to the dcom service, but it registers itself as a dcom component when it's run at the first time, so it can be recongnized and called by IE to open pdfs within it. Here is its location in registry: HKEY_CLASSES_ROOT\AppID\{14E8BBD8-1D1C-4D56-A4DA-D20B75EB814E}. Please delete this item to see if it helps.