-
Titel
Core Console is not loading with error "Oops.. Looks like something went completely wrong" after applying a license. -
Beschreibung
Core Console is unresponsive after you apply or change the license from the Core settings.
You receive the next error message: "Oops.. Looks like something went completely wrong"
You see the next error messages in the Core logs:
INFO 2020-02-20T16:03:40 [26] - Events.Licensing.LicenseKeyChangedEvent (RequestUri=https://localhost:8006/apprecovery/api/core/license/changeGroupKey ClientAddress=::1:50213 Service=Replay.Core.Management.Licensing.LicenseManagement Method=ChangeGroupKey) The License Key has been changed
DEBUG 2020-02-20T16:03:41 [131] - Replay.Core.Client.CoreMetadataManagementCoreClient () GET https://localhost:8006/apprecovery/api/core/metadata/cached failed with HTTP status code InternalServerError
DEBUG 2020-02-20T16:03:41 [18] - Replay.Core.Web.Helpers.LogErrorAttribute () Exception encountered at routine: Core/Index System.AggregateException: One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> WCFClientBase.ClientServerErrorException: Call to service method https://localhost:8006/apprecovery/api/core/metadata/cached GET failed: The index 18410715277159449743 is greater than the maximum valid index, which is one less than the capacity 467664895 ---> System.IndexOutOfRangeException: The index 18410715277159449743 is greater than the maximum valid index, which is one less than the capacity 467664895
-
Ursache
Core is failing to gather metadata after the license is applied. This is caused by environmental issues. -
Lösung
Windows Registry Disclaimer:
Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.
Things to check
1. Go to computer management - disk management - storageSee if there are any errors on storage devices, if they appear in the list even.2. Go to msinfo - components- storage - drives and disks. Verify and see if there is any strange data like zero sector sizes that is to try find a root cause
3. Verify if ther is a bad usb device or cdrom
4. Verify that the Core server has received recent Windows updates. This error has been seen on a Rapid Recovery Core server on Windows Server 2012 R2 with no recent Windows updates installed.
Workaround: Switch to a different mode of collecting core metadata1. Open regedit
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\CoreSettings
3. Change the 'EnableWinApiServiceMetadata' from 1 to 0