Error 80 - ERROR_FILE_EXISTS

Follow

Revision: 1.1

Date: Jan 9, 2017

Affected Products

Enterprise Random Password Manager - v5.5.0 and earlier, v5.5.1

Problem

When attempting to perform a system refresh or related refreshes against a Linux/UNIX target, you may encounter errors similar to this:

** Internal warning (FileHelperBase.cpp:2594): Condition false: iUniqueValue (0x00000000) > 0 (0) - Last Error: 80 - ERROR_FILE_EXISTS
** Internal warning (LinuxOperations.cpp:350): HRESULT failed (0x80070050: ERROR_FILE_EXISTS)
** Internal warning (LinuxOperations.cpp:322): HRESULT failed (0x80070050: ERROR_FILE_EXISTS)
Could not read account data from remote system; error 80 - ERROR_FILE_EXISTS

Cause

The problem occurs when ERPM is, for any reason, incapable of deleting the temp files in the temp directory that it creates during the refresh of a Linux/UNIX system during the refresh operations.

In versions 5.5.0 and earlier, ERPM made no attempt to clean up these files. In 5.5.1 ERPM and later does attempt to clean up these temp files, however, for many reasons, file cleanup may fail including issues with user profile (service account or interactive account), process issues during operations (crash, user stop/restart during operation) etc.

The temp files use a 4 character file name and eventually can run out of possible names.

Resolution

Should you receive this error during an SSH based refresh, identify if you were performing the refresh interactively or if it was being done as a scheduled operation.

If interactive, go to your %tmp% directory and delete the files out of your temp directory. ERPM will continue functioning without further interaction.

If scheduled, go to the temp directory of the service account running the ERPM deferred Processing Service or appropriate zone processor (and host) and clear the service account's temp directory. The scheduling service will resume functioning without further interaction.

If you are on a version older than 5.5.1, it is recommended to upgrade for the best possible long term outcome.

 

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

Comments

  • Avatar
    Kevin Shannon

    · Create 2 files (1 batch file / 1 "filename.vbs"). Beware - You can change file location and file name below
    · Create a batch file on locate system with contents
    @echo off
    cscript.exe c:\bin\Scheduled\VBScript\daily-delete-old-temp-files.vbs //B //Nologo
    · Create a VBS file (above name is "daily-delete-old-temp-files.vbs") but whatever name you want - Contents -
    Rem The referenced folder will not be deleted, only sub-folders and files
    sBaseFolder = "c:\Windows\Temp"
    Set oShell = CreateObject("WScript.Shell")
    oShell.Run "%comspec% /c cd /d """ & sBaseFolder & """ && rd . /s /q", 0, True
    sBaseFolder = "c:\Temp"
    Set oShell = CreateObject("WScript.Shell")
    oShell.Run "%comspec% /c cd /d """ & sBaseFolder & """ && rd . /s /q", 0, True
    sBaseFolder = "%temp%"
    Set oShell = CreateObject("WScript.Shell")
    oShell.Run "%comspec% /c cd /d """ & sBaseFolder & """ && rd . /s /q", 0, True


    · Create a scheduled Task to run batch file

    You may have to adjust to delete files on multiple profiles

    Cheers,

    Brian Botelho | Sr. Security Consultant - Lieberman – Privileged Access Management, Identity & Access Management (IAM)
    M. 925-858-8071
    brian.botelho@optiv.com
    www.optiv.com

Powered by Zendesk