Common ndImport Errors

Follow

Created:
Updated:

When using ndImport, you may encounter a number of errors. The more commonly encountered errors are listed below.

Error Explanation & Solution
-1 File indentifier check failed. parsing .msg file. Corrupt MSG header, need to import as a txt file. Retry.
-1 Import failed: -2147467259 Application-defined or object-defined error. failure during document creation. Either the file doesn’t exist, the document has been moved or you don’t have access. Retry.
-1 Import failed: 5 The given key was not present in the dictionary. failure during document creation. Retry.
-1 Import failed: The given key was not present in the dictionary. Retry.
-1 Invalid Directory ID in the Root element. parsing .msg file. Retry.
-1 Object reference not set to an instance of an object. File doesn't exits or you don't have access, possibly retry.
-1 The parent folder already contains a subfolder with this name. Retry. 
-1 Unexpected error in ndImport.aspx: Incomplete upload. Retry.
-1 Unexpected error in ndImport.aspx: Unable to write data to the transport connection. Retry.
-1 Unexpected error in ndImport.aspx: There was an error writing to the pipe: The pipe is being closed. (232, 0xe8)  
-2147024773: The filename, directory name, or volume label syntax is incorrect. Retry.
-2147024893: The system cannot find the path specified. Either the file doesn’t exist, the document has been moved or you don’t have access. Retry.
-2147024894: The system cannot find the file specified. Either the file doesn’t exist, the document has been moved or you don’t have access. Retry.

 

Back to Top

Was this article helpful?
0 out of 0 found this helpful

Comments

Have more questions? Submit a request
Powered by Zendesk