OK, this is a blatant copy of an old posting made way back in the year 2011. However, I have been asked 4 or 5 times, all from different sources, if this is possible with Vault in the last 2 weeks. So, it seems that now is a good time to re-use and recycle an old post.
It is possible to configure the Server logs so that administrators get a record of files deleted by users. (2011 or later.)
In the Web.Config file (first make a copy before making changes) located by default here:-
"C:\Program Files\Autodesk\ADMS Professional 2014\Server\Web\Services"
This is a generic error and you will see this message on this blog with multiple solutions.
In this scenario, the reason for the error was discovered after using standard Troubleshooting steps. The Job was a DWF created on a specific file. Regardless of which Job Processor client was used the DWF file persistently failed to generated.
Opening the ipt file in Inventor was successful, but when trying to publish the DWF manually (Export>DWF), a message appeared.
"Excel installation is required for this operation. Failed to launch Excel."
The file was an iPart and Excel was not installed on any of the Job Processor clients.
Now this error is obviously "Unknown" and its generic.Therefore the following explanation of a scenario I worked on may or may not be applicable in your situation.
There are multiple Job Processor Clients
This error occured on all clients at some point, but not necessarily at the same time. Meaning that when it occurred, the failing JP will generate a lot of errored Jobs. Because the other working JP clients are busy doing their jobs correctly, the broken JobProcessor.exe is running but cannot process any job. It therefore looks to the queue, takes a job, cannot not complete it, reports an error, then takes the next job.
Why can the Job Processor not complete any tasks? Well the Job Processor is just an agent. It commands other applications to do its work for it. It knows the tasks that it should be able to complete, such as DWF Create on an ipt, iam etc, because Inventor is installed. So when it sees a job like that appear in the queue it takes it. It then commands Inventor to process it. But in this particular scenario, Inventor had hung.
User interaction is required to fix the issue.
You need to log into the JobPrcessor machine.
Task Manager can show that Inventor is running in the background and consuming a lot of memory.
Manually starting Inventor shows the splash screen appear, but it never actually starts up. Killing both Inventor processes allows Inventor to then start up.
But resubmitting the jobs still result in the "Unknown error during publish" message in the Job Queue. This means recovering from this is a two stage process.
Log into the the Job Processor machine Kill Inventor Exit the Job Processor and restart it. Resubmit the Jobs.
Currently, understanding why Inventor is hanging is the issue, because once the situation is recovered, resubmitting the job allows the job to complete without error.