Usually our tasks run just fine, but sometimes there is a client with some issue, like the user triggering the task while the file has been opened in SW and other minor issues.
I noticed that even in those cases the log file is not created in our _LOG folder.
The path in the task is correct, I tried to re select it again, but no log created.
I checked the permissions for the folder and the users could add, move, checkout and delete the fIles…what I am missing? I still have some logs inside those folders, but they seem to be from 3 yrs ago and probably the logging stopped to wotk around that time?
I usually monitor the task dashboard inside the PDM administration, but sometimes I just want to dig an error a bit and a log could be useful.
This log path, sounds like it’s on a network share?
What add-in is the task running? Something custom?
the path is inside the PDM vault, in its root. it used to work at least until a couple of years ago judging by the files inside. Usually I do not have errors, but recently I had a client with some hiccups and I wanted to take a better look at it.
The tasks are all customized, but based on the default ones. I never touched the log part, but it seems the log path is took from the task dialog as expected.
probably time for a task debug… but I need to trigger an error on purpose, hoping it does not make the task to crash.
Just some random thoughts, not to waste your time with goose chase, just sounding board.:
- Could files be there and not seen?
- Correct read permission per folder and state that the new files are in?
- If logged in as admin on the machine that ran the task are the logs there?
- File name/extension issue?
- Is that file extension blocked? Probably not as the file would be local but not added to vault.
- What’s the log naming method? Did something change causing the name to be the same? (no duplicate names thing).
- Antivirus blocking file?