-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Repair option in aspnetcore-runtime-3.1.0-win-x64.exe fails with message account already exists #19536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is about aspnet installer - moved from dotnet/runtime repo. |
Thoughts @joeloff ? |
This is the GA version of 3.1? From the posted log it seems that the SDK bundle can't extract the MSI properly:
The 1316 error is a more cryptic one. Is there an MSI log I can see that showed the 1316 Account Already Exists error? |
@Daniel-Steiner are there any MSI logs you can provide to help diagnose the 1316 error? (@joeloff where could @Daniel-Steiner find those logs?) |
They should be in the %temp% folder. The bundle log will usually report the log names it's going to generate. I think we're looking for %temp%\Microsoft_.NET_Core_SDK_3.1.100_(x64)_20191206084459_014_AspNetCoreSharedFramework_x64.log |
@anurse , added the log you were looking. I just got into same issue. |
@joeloff does that log give you more information to look at? |
A little, it's SECREPAIR that failed:
@dreddy-work If you open RegEdit and search for "Microsoft ASP.NET Core 3.1.2 Shared Framework (x64)" under HKCR\Installer\Products and expand the entry, what do the Media/Net keys under SourceList say. This could be a conflicting with the name used for caching the MSI, but I'm not 100% sure yet |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate. See our Issue Management Policies for more information. |
I do not see that node under: Computer\HKEY_CLASSES_ROOT\Installer\Products\ |
@dreddy-work Does the HKCR\Installer\Products show anything for ASP.NET Core? |
I was searching on string "ASP.NET Core" and it matched under multiple GUIDs. All of them has "SourceList" but not the "InstallProperties". Also, its been few weeks ago when my system was not cooperating. Now i am not sure if it is in same state anymore. |
@joeloff any further thoughts here? It sounds like the install has been corrupted somehow. |
Same problem. dotnet-hosting-3.1.9-win.exe.
|
@dougbu that one was to support upgrades I think. There was another fix where names of the installers were different in VS compared to the standalone bundles. I believe that PR should address this issue. |
Ah, 🆗 Does the other fix mean we can close this issue❔ |
For new installs yes, for older ones, you'd likely still need to work around the issue, e.g. by deleting the cached package. |
@Daniel-Steiner commented on Wed Dec 04 2019
after installation of aspnetcore-runtime 3.1.0 on Windows 10 64-bit by running aspnetcore-runtime-3.1.0-win-x64.exe and than running aspnetcore-runtime-3.1.0-win-x64.exe again and selecting Repair option the repair fails with the error message:
Microsoft ASP.NET Core 3.1.0 - Shared Framework (x64) - Setup
The specified account already exists.
to repair the installation , the package must be first uninstalled before running aspnetcore-runtime-3.1.0-win-x64.exe again.
@JonasSamuelsson commented on Thu Dec 05 2019
I have the same issue
@mcp1979 commented on Mon Dec 16 2019
My problem is that the aspnetcoresharedframework-x64.msi is missing from the Package Cache:
AspNetCoreSharedFramework_x64, action: Repair, path: C:\ProgramData\Package Cache{43AC1AE8-A320-3C4B-BA83-37F5DE40757C}v3.1.0.0\AspNetCoreSharedFramework-x64.msi
no matter how many times i uninstall & reinstall, the problem persists...
@schuettecarsten commented on Sun Dec 29 2019
Same problem here :-(
@diffused commented on Mon Jan 06 2020
Seeing the same issue here too. Can't perform a repair
The text was updated successfully, but these errors were encountered: