Snippet of Client Trace
17/03/2009 17:12:56.552[3244]: CPSTImporter::LocatePSTFileInProfile: 0x0
17/03/2009 17:12:56.552[3244]: Found 1 PSTs in current MAPI profile
17/03/2009 17:12:56.553[3244]: DesktopCommon::ConvertRemoteFileSpec: 0x0
17/03/2009 17:12:56.554[3244]: Translated network path from H:\PST_Networkshare.pst to: \\Machine\Share$\PST_Networkshare.pst
17/03/2009 17:12:56.554[3244]: ~DesktopCommon::ConvertRemoteFileSpec: 0x0
17/03/2009 17:12:56.555[3244]: Found PST in profile: \\Machine\Share$\PST_Networkshare.pst
17/03/2009 17:12:56.555[3244]: CDesktopCommon::EscapeXPathQuery: 0x0
17/03/2009 17:12:56.556[3244]: ~CDesktopCommon::EscapeXPathQuery: 0x0
17/03/2009 17:12:56.556[3244]: None of the PSTs in the current MAPI profile are ready for migration
17/03/2009 17:12:56.557[3244]: ~CPSTImporter::LocatePSTFileInProfile: 0x1
17/03/2009 17:12:56.557[3244]: CPSTImporter::LocatePSTFileOnDisk: 0x0
17/03/2009 17:12:56.557[3244]: No PSTs in server list are ready for client-side migration
17/03/2009 17:12:56.558[3244]: ~CPSTImporter::LocatePSTFileOnDisk: 0x0
17/03/2009 17:12:56.558[3244]: ~CPSTImporter::CopyPSTsToServer: 0x1
17/03/2009 17:12:56.558[3244]: PST Importer sleeping for 60 minutes (there is no work to do)
DTrace of W3WP and DirectoryService
768 12:54:01.032 [2624] (DirectoryService) <6464> EV:M DirectoryService: ChunkPstFile: No access permission error on call to NetShareGetInfo. PST: \\Machine\Share$\PST_Networkshare.pst |
769 12:54:01.032 [2624] (DirectoryService) <6464> EV:M HRXEX fn trace :|Source : .\DirectoryServiceObject.cpp (CDirectoryServiceObject::UpdatePstFile) [lines {15640,15661,15690,15707,15717}] built Jan 2 11:41:02 2008|Description: Unexpected fn exit path.
770 12:54:01.032 [8628] (w3wp) <6304> EV:L CAuthHelper::Reset Cancel registration? true CancelId: 0
772 12:54:01.032 [8628] (w3wp) <6304> EV-M {UPDATEPSTFILES.EN_US} UpdatePstFile failed to get Adminstrative Share name for PST '\\Machine\Share$\PST_Networkshare.pst'
773 12:54:01.032 [8628] (w3wp) <6304> EV-L {UPDATEPSTFILES.EN_US} Successfully updated|
Solution:
1. Ensure that the Vault Service Account has Full Rights to the Administrative Share.
2. If unable to connect to the Administrative Share, from the Enterprise Vault Server, the proper ports may need to be opened, namely 139 and 445.