Folder monitoring stops working SOLVED

[soenke]

I am using PDF-XChange Pro and utilizing the folder monitoring feature.

I have set up three folder monitoring tasks. I can start all three and have enabled the auto-start option. However, after a relatively short time, one or even two of these monitoring tasks automatically deactivate themselves.

What could be the reason for this behavior? Is there a log file that might provide some insight?

First the folders are on network drives. I changed that to local folders and still it happens from time to time.

image.png

[Dimitar - PDF-XChange]

Hello Soenke,

Welcome to our Forum!

It seems you may have missed the e-mail that we also sent you earlier, as we haven’t received any feedback regarding the things we asked you to check in that mail.

Could you please confirm whether you’ve set the folder monitor to start with the system, as described in the following guide?

https://help.pdf-xchange.com/pdfxt10/fo ... ors_t.html

Looking forward to your reply.

Best regards.

[soenke]

Hello,

you are right, I do not receive Emails to my Service requests. I asked several Times about the Status but never received Feedback.

That is why I asked the same question via forum.

I Set up the folder Monitoring as described in that link except the autostart.

In newer Version there is the autostart function selectable via the GUI and not with the shortcut.

Please let me Highlight that the Monitoring task is running for some time and stops than.

I still want to ask if there is any logfile that Shows the reason why it stops?

Sönke

[Daniel - PDF-XChange]

Hello, soenke

Thank you for the clarification. Since it seems to be starting as expected, and the core of the issue is a sudden stop after running for a while, I will admit I am a bit perplexed. Even if a file location is lost due to some network huiccup, or a full disconnection, I believe the monitor should normally remain running, waiting for that path to "reappear" so it can continue processing.

I have just passed this along to the Dev team for further review, since I do not know of any log files which would record when/why the monitor itself stopped running, only the changes that have been made to file, by the monitor.

We will return as soon as we have heard from the Dev team on this topic. Hopefully they have some steps for us to locate the cause of the issue and find a solution.

Kind regards,

[soenke]

Hi,

any news from the dev Team?

Yesterday again two folder watch stopped without any interaction of me.

Sönke

[Sean - PDF-XChange]

Hi soenke,

No news to report I'm afraid.

Kind regards,

[Daniel - PDF-XChange]

Hello,

I have a small update - this issue is related to a ticket that is seeing active work to be resolved:
RT#7636: Folder monitor stops and does not resume.

While I cannot offer a timeline for its resolution, we have so far determined that this will occur when some exception causes a given monitor to crash independently from the rest of the application. They are working to prevent such exceptions, but this may be a case of gradual fixing - you may notice over the next few updates that this happens to progressively less of your monitors, until they are all working normally.
I am sorry that I cannot offer more at this time.

Kind regards,

[soenke]

Hello Daniel,

so I will hope that this will be solved soon

Is there any chance to monitor if the folder watcher is still active or not?

Is that a process or a service that I can check if it is still running?

I am open to check this will a external tool in the background, as I believe there is no CLI command for, right?

Sönke

[Daniel - PDF-XChange]

Hello, soenke

Aside from running PDF-Tools and opening the folder monitor, a background process should exist in the task manager for each monitor, though they are not clearly labelled as one or the other:

image.png

Beyond this, I am afraid there are not yet any updated for ticket RT#7636 which I can offer..

Kind regards,

[soenke]

Hello,

I see that in the latest version there is a fix for this reconnect topic.

And the good news is, that I do not observe the problem in the last weeks after using this software.

BUT:

Now I have an new problem with this.

Please take a look at the beginning of my thread. There you can see that I have three folders that I watch, perform different tools and save to different folders.

I see now that when one of this watched folders is triggered, not only the tool that is connected to this folder watcher is performed, but also an second one.

I also see now a task in the taskmanager called "ProcessToolWorker".

Could you please check this?

If you need more information, please let me know.


Sönke

[Daniel - PDF-XChange]

Hello, soenke

Thank you for the report, I am unable to reproduce the issue personally, but I have raised it with the Dev team for review and action. It is the holidays right now so I cannot promise a swift reply, but as soon as I hear back from them, I will be sure to let you know.

Kind regards,

[soenke]

Hello,

the whole thing is getting more and more crazy:

Even when I completly turn off all folder watcher and disable the autorun. I than checked the task manager and none of the folder wtacher pcoesses is visible.

I than put a file to one of the folder that normally are observed.

The tool starts immiditaly to process the file (by the way with the wrong toolsset).

I turned on the debug output /textfile) and see that it is performed by the pdf tools.

What is going on here?


Could you please tell me where the information of the folder watcher dialog are saved? I would like to delete this file to check if there is anything in it should not.

I really would like to help to speed up solving this problem. I purchased the pdfxtools for especially this functionality.

BTW: Do you need me logfiles?


Thanks,

Sönke

[Sean - PDF-XChange]

Hi soenke,

Thanks for the update - we will get back to you on this once the development team have reviewed it.

Kind regards,

[Daniel - PDF-XChange]

Hello,

Yes, if you could please send us an export of your PDF-Tools application settings that would be very helpful.

Second, could you please follow the steps here to capture processmonitor logs of Tools while the issue is occuring: https://www.pdf-xchange.com/knowledgeba ... or-Procmon

Since it seems you have two related issues here, it may be best to record two separate times - place the two separate logs into zip files with the relevant name"

1. tool2runs-after-tool1
2. toolrunswhendisabled

Once you have done that, please open "regedit.exe" and export the registry key here:
Computer\HKEY_CURRENT_USER\Software\Tracker Software\PDFXTools

Include all of the above and upload them to this URL, then let me know once the upload is complete:
https://files.pdf-xchange.com/s/n2e8c2fBr4q6YHg

Finally, you can try deleting this registry key to blow away all of your folder monitors - note that a system restart may be required to take full effect:
Computer\HKEY_CURRENT_USER\Software\Tracker Software\PDFXTools\8.0\FolderMonitors
After that you will of course need to re-create the monitors, but perhaps there is an error in the registry data here which causes the issue.

Kind regards,

[soenke]

Hello and thanks for investigating my problem.

I did all the requested steps and the files are on the server.

(I do not see the uploaded files, the upload just finished, is that correct)?

Additionaly I did the following:

Create exact the same folder structure and pdf tools on a second computer. I do not see the same same problem.

I completly deinstall on the system with the problem the pdf pro, I did manually delete all folders I can found on the system

- program files
- %appdata%
- program data

and delete the complete registry key on "current user" and also on "local machine"

Than I restart the computer and install the pdf pro new.

I have to activate the license again.

There is still the same problem existing.

Especially the part, that the tool runs and is triggered for a new file when all folder monitors are disabled and are not existing in the task manager, is very surprising for me and shows that there is anything in the background running.

Thanks,

Sönke

[soenke]

OK!

I have to say sorry.

After hours of searching, I found that there is from a different tool a folder watcher process that starts a CLI of the second tool.

That also explains why the process is also started even when all folder monitors of PDFXTool are disabled.

So, you can close the ticket.

Thansk,

Sönke

[Daniel - PDF-XChange]

Hello, soenke

Thank you for the update! I will get rid of these files then, and close the ticket.

Kind regards,