SOLVED

Troubleshooting "Cannot access a failed instance" on PST export

%3CLINGO-SUB%20id%3D%22lingo-sub-15745%22%20slang%3D%22en-US%22%3ETroubleshooting%20%22Cannot%20access%20a%20failed%20instance%22%20on%20PST%20export%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-15745%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20looking%20for%20some%20troubleshooting%20advice%20on%20an%20error%20while%20trying%20to%20perform%20a%20PST%20export%20on%20a%20Exchange%202010%20server.%26nbsp%3B%20The%20export%20process%20starts%20ok%20and%20gets%20to%20about%2070%25%20and%20then%20bombs%20out%20with%20the%20following%20error%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22Error%3A%20%5C%5Cservername%5CExport%5Cusername.pst%20--%26gt%3B%20Cannot%20access%20a%20failed%20instance%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20appears%20that%20the%20process%20has%20lost%20ownership%20of%20the%20PST%20file%20it%20was%20creating.%26nbsp%3B%20I'm%20going%20to%20check%20there%20is%20nothing%20running%20on%20the%20server%20that%20might%20affect%20this%20i.e.%20server%20backups%2C%20AV%20scanning.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20end%20of%20the%20report%20file%20suggest%26nbsp%3Bcorrupt%20items%2C%20however%20this%20appears%20to%20be%20the%20same%20time%20the%20PST%20is%20no%20longer%20accessible%20and%20may%20be%20a%20result%20rather%20than%20cause.%26nbsp%3B%20The%26nbsp%3Bcorruption%20errors%20are%20all%20have%20the%20same%20timestamp%20seconds%20before%20the%20export%20process%20fails.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-15745%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16282%22%20slang%3D%22en-US%22%3ERe%3A%20Troubleshooting%20%22Cannot%20access%20a%20failed%20instance%22%20on%20PST%20export%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16282%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20for%20reference.%26nbsp%3B%20The%20issue%20was%20caused%20by%20AV%20scanner%20grabbing%20the%20PST%20while%20it%20was%20being%20built.%26nbsp%3B%20Excluding%20the%20folder%20where%20the%20PST%20files%20were%20being%20exported%20to%20fixed%20the%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20added%20this%20to%20my%20blog%20%3CA%20href%3D%22http%3A%2F%2Fwww.itgeekrambling.co.uk%2Fexchange-2010-exporting-pst-files-cannot-access-a-failed-instance%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

Hi,

 

I'm looking for some troubleshooting advice on an error while trying to perform a PST export on a Exchange 2010 server.  The export process starts ok and gets to about 70% and then bombs out with the following error:

 

"Error: \\servername\Export\username.pst --> Cannot access a failed instance"

 

It appears that the process has lost ownership of the PST file it was creating.  I'm going to check there is nothing running on the server that might affect this i.e. server backups, AV scanning.

 

The end of the report file suggest corrupt items, however this appears to be the same time the PST is no longer accessible and may be a result rather than cause.  The corruption errors are all have the same timestamp seconds before the export process fails.

 

Thanks 

1 Reply
Highlighted
Best Response confirmed by Rob Clarke (Frequent Contributor)
Solution

Just for reference.  The issue was caused by AV scanner grabbing the PST while it was being built.  Excluding the folder where the PST files were being exported to fixed the error.

 

I've added this to my blog here