Error 1316: The specified account already exists.

[deepakd016]

I am getting this error while upgrading the previous version of my application

In other words when previous version is already installed in the target machine and when newer version is tried to install up on that then this error is popping up which in turn rollbacks to previous version

plz suggest how to get rid of this error.

[dan_hoeger]

Any help would be appreciated.

[DataAnalyzer]

We have a customer report of this same problem but can't reproduce it. In our case, the customer said they tried to uninstall the original version first. It failed for some reason but the product disappeared from the Control Panel list of programs. They then installed the update which triggered this error but installed successfully. However, it doesn't appear on the Control Panel list of programs, so we're not sure how it can be uninstalled. Would like to have a clean uninstall to reset the user's machine. We haven't had reports of this from other customers. Any insight or solution would be appreciated. Thanks.

[thaopham]

I got the same error message, but in my case when I looked into the install log, it failed at RegisterProduct action and I figured out that I've been renamed our product name to a new trademark (from (R) to (TM)) and caused this error during upgrade.

You can do the same by looking into your install log and see where it throws this error.

Thanks,
Thao

[phanik]

hi all,

I too faced the same issue and solved by rerun the same version installer. important thing is you have to rerun the exact version of the installer i mean packaging code( GUID may or may not be same)) should be the same.

in my case we have designed our installer to go to maintenance mode if i try to install my product on a host where same version(same package code but GUID may or may not be same) product is already installed. I Install the product once again by choosing modify option. once installation is completed I will have choice to uninstall the product from add/remove programs or by using GUID.

if your are not designed your installer to go to maintenance mode, then simply install the same version product (same package code but GUID may or may not be same). on a host where your seeing the issue and then uninstall.


1. when you are ended up in this situation mostly you dont see installed files some times add/remove programs entries too, so find out what version you have installed by looking at stale entries from registry under
HKEY_LOCAL_MACHINE\SOFTWARE\your product name

if your product is 32 bit and installed on 64 bit machine check here HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\your product name

you can get more detials HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall



hope your issue will be resolved.

Phanik

[LynetteE]

I am having a similar problem but I can't seem to get past it. I am using InstallShield 2015 to update an installer that was originally created with InstallShield 2010. I am creating a minor upgrade for the product. After I let IS 2015 update the project, I changed the Product Version and the Package Code GUID. The Upgrade Code and the Product Code GUIDs are the same. When I run the new installer to upgrade the product, it fails with Error 1316.The specified account already exists.

The log entries just before this error are as follows:

[FONT=Courier New]MSI (s) (6C:A4) [17:19:45:114]: Re-registering product - performing upgrade of existing installation.
MSI (s) (6C:A4) [17:19:45:114]: Resolving source.
MSI (s) (6C:A4) [17:19:45:114]: Resolving source to launched-from source.
MSI (s) (6C:A4) [17:19:45:114]: Setting launched-from source as last-used.
MSI (s) (6C:A4) [17:19:45:114]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'C:\Users\elwly02\AppData\Local\Temp\{89601578-96BD-4D7B-B9B1-2DE3B4A73B23}\'.
MSI (s) (6C:A4) [17:19:45:114]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'C:\Users\elwly02\AppData\Local\Temp\{89601578-96BD-4D7B-B9B1-2DE3B4A73B23}\'.
MSI (s) (6C:A4) [17:19:45:114]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{D026D7B8-FE82-44B3-9617-F88C98BCFB2D}'.
MSI (s) (6C:A4) [17:19:45:114]: SOURCEDIR ==> C:\Users\elwly02\AppData\Local\Temp\{89601578-96BD-4D7B-B9B1-2DE3B4A73B23}\
MSI (s) (6C:A4) [17:19:45:114]: SOURCEDIR product ==> {D026D7B8-FE82-44B3-9617-F88C98BCFB2D}
MSI (s) (6C:A4) [17:19:45:114]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (6C:A4) [17:19:45:114]: Determining source type
MSI (s) (6C:A4) [17:19:45:114]: Note: 1: 2203 2: C:\Users\elwly02\AppData\Local\Temp\{89601578-96BD-4D7B-B9B1-2DE3B4A73B23}\CA Datacom Server Version 14.0 x86.msi 3: -2147287038
MSI (s) (6C:A4) [17:19:45:114]: Note: 1: 1316 2: C:\Users\elwly02\AppData\Local\Temp\{89601578-96BD-4D7B-B9B1-2DE3B4A73B23}\CA Datacom Server Version 14.0 x86.msi
MSI (s) (6C:A4) [17:19:45:114]: SECREPAIR: Error determining package source type
MSI (s) (6C:A4) [17:19:45:114]: SECUREREPAIR: SecureRepair Failed. Error code: 524EF0044B8
Error 1316.The specified account already exists.

MSI (s) (6C:A4) [17:19:52:777]: Product: CA Datacom Server Release 14.0 x86 -- Error 1316.The specified account already exists.


Action ended 17:19:52: RegisterProduct. Return value 3.[/FONT]

Can someone help me resolve this?

Thanks,
Lynette

[LynetteE]

I finally determined that I had changed the name of the .msi file. The original installer was called 'xxxxx Version 14.0 xxx'.msi. The minor upgrade called it 'xxxxx Release 14.0 xxx'.msi. After I changed it back to the original name, it worked just fine. Thanks to all who've posted here.

[Thesorus]

sorry did not see that you fixed this.

[DataAnalyzer]

I didn't figure out this problem until today. Since I don't use the MSI naming approach and use the InstallScript MSI Project instead, the previous response didn't seem to apply to me.

It turns out it's the name of the release that triggers the problem. Because under Releases, I changed the Project Name to reflect the new build, the 1316 error is triggered. Apparently, the GUIDS for the Product Code and Upgrade Code aren't the only items the matter. The name of the product can't be changed either. Wish I knew this when I posted this a few years ago. Ugh!