The customer's WebDav auto import from a SharePoint library has been faultless, but suddenly there are log alerts, as well as errors pointing to a "disabled directory".
Example Log Entry:
[7/28/2020 9:01:06 AM - Error - v22.214.171.124]
Auto Import failed to monitor one or more directories because it could not create a required state tracking file. The path to the file is: share.exampleURL/AutoImport.xml. The file exists
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Path.InternalGetTempFileName(Boolean checkHost)
Documents from the monitored SharePoint location are no longer being imported. The consistent wording for these error messages looks like this...
If you look at the files in that monitored location, you do not see an AutoImport.xml file present, even though the error states that "the file exists"
This issue can be confused as a SharePoint issue, in reality it is due to a temp file location. It is initially written to the C:\Windows\Temp folder of the Capture Server, before being written to the WebDav directory. When that Temp folder fills up, there may be other like-named files present. The solution is to clear out the C:\Windows\Temp folder as well as the %temp% location.
Please sign in to leave a comment.