PST Administrator user accounts experience bad logon attempts when importing PSTs into Enterprise Vault

book

Article ID: 100033317

calendar_today

Updated On:

Description

Error Message

Dtrace of MigratorServer

(MigratorServer)    <9464>    EV:L    {CMigrator::GetAccountPassword} (Exit) Status: [Success]
(MigratorServer)    <9464>    EV:H    {CMigrator::ImpersonateClientContext}|Logon with current account failed before impersonation - User1
 (MigratorServer)    <9464>    EV~E    Event ID: 28974 The user name or password is incorrect.  (0x8007052e) file access error occurred | |Reason:    PST |PST file:  C:\Temp\User1_Export_0001.pst |Account:    |Supplementary Info: PST migration cannot continue because the task cannot use the account. Check that it is possible to log in to the account. |For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3683&error=V-437-28974
(MigratorServer)    <9464>    EV:H    {CMigrator::ImpersonateClientContext} (Exit) Status: [Unspecified error  (0x80004005)]

Security Event Log

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          11/23/2016 3:28:29 AM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      EVSERVER1.EV.Local
Description:
An account failed to log on.

Subject:
    Security ID:        EV\vsa
    Account Name:        vsa
    Account Domain:        EV
    Logon ID:        0xC5E53E

Logon Type:            2

Account For Which Logon Failed:
    Security ID:        NULL SID
    Account Name:        User1
    Account Domain:        EV

Failure Information:
    Failure Reason:        Unknown user name or bad password.
    Status:            0xC000006D
    Sub Status:        0xC000006A

Process Information:
    Caller Process ID:    0x2df0
    Caller Process Name:    C:\Program Files (x86)\Enterprise Vault\MigratorServer.exe

Enterprise Vault Event Log

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault
Date:          11/23/2016 4:44:28 AM
Event ID:      28974
Task Category: Migrator Server
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EVSERVER1.EV.Local
Description:
The user name or password is incorrect.  (0x8007052e) file access error occurred
 
Reason:    PST
PST file:  C:\Temp\Personal Folders(3).pst
Account:    
Supplementary Info: PST migration cannot continue because the task cannot use the account. Check that it is possible to log in to the account.

Workaround

To workaround the problem, create a dummy task and change the logon account of this task from the default Vault Service Account to the account of the PST Administrator.  A new SharePoint archiving task is a good option for a dummy account as it requires almost no configuration.  The steps to create this account are as follows:

1)  On the EV server, create a new SharePoint Archiving Task.  There is no need to start it and it can be set to disabled once created.  
2)  In the properties of the SharePoint Archiving Task, click the Logon tab and select "Use this account". Enter the details for one of the PST Migration Administrators and click OK.
3)  If there is more than one PST Administrator account then individual SharePoint Tasks can be created for each user.  To avoid confusion, the task can be renamed via the General tab so that it is clear that each task is not a SharePoint task but rather a workaround for each individual PST Administrator.

Once a dummy task has been created and configured for each PST Administrator account, bad logons will no longer occur for these users.  However, event ID 28974 may be logged with error "
Access is denied.  (0x80070005) file access error occurred" in the Enterprise Vault event log.  Despite this error, data from the PST will be migrated successfully into Enterprise Vault. 

Cause

The PST Migration Wizard attempts to read credential information for the logged on account from the EnterpriseVaultDirectory database.  As a record for the logged on user does not exist in the database, it is not able to read this information.  Despite no record being found, the wizard still attempts to logon as the user using incomplete credential information.  This results in a bad logon attempt.

Resolution

This issue has been addressed in the following release:

Enterprise Vault 12.1.3

Enterprise Vault 12.2

Issue/Introduction

User accounts that are part of an Enterprise Vault role that permits the migration of PST's into Enterprise Vault experience bad logon attempts when migrating PST's with the "Automatically assign archives to PST's" and "Give priority to information in marked PST's" options selected in the PST Migration Wizard. Depending on the Active Directory lockout policy, affected accounts may be locked as a result of these bad logon attempts.

Additional Information

ETrack: 3905592 JIRA: CFT-75