Client driven manual PST submission fails with error 'The network path was not found. (Exception HRESULT: 0x80070035)'
Article ID: 100046827
Updated On:
Description
Error Message
Client Trace shows the following :
[12372][M]: PSTMIG: {CPstClientMigrator::AddPstFiles:#628} XML is
...
...
13/08/2019 11:46:33.405[12372][L]: CInternetSendDataBase::ReadResponseBody
13/08/2019 11:46:33.406[12372][M]: Body is
Dtrace on 'Directory Service' on the EV server shows the following :
EV:L {CDirectoryServiceObject::BreakDownShareIntoComponentParts:#19328} Source Path [\\Client_Machine\C$\Users\User1\Desktop\test-stk_n.pst] Broken Into [Client_Machine] [C$] [\Users\User1\Desktop\test-stk_n.pst]
EV:L {CDirectoryServiceObject::PstTranslatePath:#19361} Path doesn't need translating
EV:L {CDirectoryServiceObject::AddPstComputerInternal:#36855} Entry
EV:L {CDirectoryServiceObject::GetComputerInfo:#37080} Entry
EV:H {CDirectoryServiceObject::GetComputerInfo:#37105} NetWkstaGetInfo failed with error code-53 for machine 'EV-EXCH'
EV:H {CDirectoryServiceObject::GetComputerInfo:#37119} Encountered COM error: [0x80070035]
Error code 0x80070035 translates to "The network path was not found"
Cause
Once the client machine sends the PST file information to the EV server, the server uses 'NetWkstaGetInfo' which is a Windows API call, to get more details about the client machine (domain, OS version, etc.).
This call fails with error 0x80070035, which points to an issue with the name resolution.
Accessing path "\\Client_Machine\C$\Users\User1\Desktop\test-stk.pst" from the EV server should result in a credential prompt, which means the path is valid and resolvable.
Resolution
Creation of a HostFile entry for the client machine on the EV server and ensuring the path of the PST is accessible (should get a credential prompt) can be a temporary solution.
A permanent solution would be to ensure that the DNS records are correct so that the PST path on the client machine is resolvable.
Issue/Introduction
