Error 1316. The specified account already exists when running RSA Authentication Agent 7.x for Windows update_x64.exe
Originally Published: 2015-11-04
Article Number
Applies To
RSA Product/Service Type: Authentication Agent for Windows
RSA Version/Condition: 7.x
Issue
Error 1316. the specified account already exists
Error 1316. A network error occurred while attempting to read from the file <File Path>
Cause
When the update is run, the update.exe file always copies the msi file under an install directory (e.g. C:\Users\admineb\AppData\Local\Downloaded Installations{57C6D711-91E7-4657-9C3F-6DA19FDE2D4E}\) with the name RSA Authentication Agent x64.msi which is the default name.
Then the installer looks for the msi file in the same directory. With the initial version msi name changed from the default name, the installer fails giving the error shown above.
Resolution
- Use the ConfigWizard.exe included in the agent zip file to create a new msi having the old renamed msi name, e.g.: RSA_renamed_Auth.msi
- Then push the package down to the PC, and run the following command:
"RSA_renamed_Auth.msi" /quiet /norestart REINSTALL=ALL REINSTALLMODE=vomus /lv C:\log.txt
- This new package will update the agent with no issues moving forward.
Workaround
- Open a command prompt and run the commands below to generate an log file.
cd <Update Directory> Update_x64.exe /V"/L*v c:\log_update.txt"
- This will take you through the steps of the update until you face the same error. Close the installation wizard after it fails.
- Open the log file named C:\log_update.txt in the example above. Search for the string original package. Yyou should find a line similar to the one shown below:
MSI (c) (A4:78) [12:55:24:321]: Original package ==> C:\Users\Administrator\AppData\Local\
Downloaded Installations\{57C6D711-91E7-4657-9C3F-6DA19FDE2D4E}\RSA Authentication Agent x64.
- This points to the Install directory. In the example, the install directory is C:\Users\Administrator\AppData\Local\Downloaded Installations\{57C6D711-91E7-4657-9C3F-6DA19FDE2D4E}\.
- In the log file, search for the word PackageName. You should find one or more lines similar to the one shown below:
MSI (s) (D8:58) [12:55:48:925]: Executing op: ProductInfo(ProductKey={1CBBF615-E223-45A3-BE98-4B67EC6846DA},
ProductName=RSA Authentication Agent,PackageName=RSA_renamed_Auth.msi,Language=1033,Version=117571585,
Assignment=1,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,,PackageCode={57C6D711-91E7-4657-9C3F-6DA19FDE2D4E},
,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
- This points to the package name. In the above example the Package name is RSA_renamed_Auth.msi.
- Open the install directory.
- You will find a file called RSA Authentication Agent x64.msi.
- Rename it to the package name you found.
- Run the update_x64.exe file. The update should succeed this time.
Notes
Attachments
If the attachment does not open when clicked, please refresh the page and try again. You must be logged into view the file(s).
Related Articles
TERMINATION_DATE from Oracle HRMS Authentication System is not getting stored in RSA Identity Governance and Lifecycle 7.0 20Number of Views How to change the default Oracle Statistics History Retention period for RSA Identity Governance & Lifecycle 84Number of Views Error: Cannot connect to database. 'Access denied. The database cannot be accessed at this time. RSA ACE/Server database a… 20Number of Views AMPrime com.rsa.ucm.AuthManager.AmisCommandTargetException : Key not found 33Number of Views How to set up a CRL Distribution Point in a certificate during certificate manual approval 8Number of Views
Trending Articles
How to recover the Application and AFX after an unexpected database failure in RSA Identity Governance & Lifecycle Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager Upgrade Process
Don't see what you're looking for?