Active license, but single Core gives error: The grace period has expired Check license settings

Hi,

We have an error on one of our Rapid Recovery Core servers: 'The grace period has expired Check license settings'
Before this error, it has ran without license issues for years now on this Windows 2019 standard server.

A manual attempt to contact the license server (through settings) shows:

----
Unable to contact licensing server

Communication with the license portal failed. This could have several causes, including the following:

    The license portal may be experiencing heavy load
    Your ISP may be having an issue
    A firewall rule has been added or changed

Note: There is a 15 day grace period during which your license will continue to work. Please contact Quest Software Inc Support if this failure continues.
----


When I click on the link (rapidrecovery.licenseportal.com/) it forwards me to 'id.quest.com/.../auth ...'

No changes are made on this server, except Windows updates.

2 other Rapid Recovery cores with the same license do not have any issues.

Already tried:
- rebooted the Rapid Recovery services and the server
- upgraded Rapid recovery to the latest version (6.10.0.316)
- deleted registry key (HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\LicenseInfo ), restarted service and re-added the license
- the ID's are different between the 3 cores
- removed the affected core from the Quest license portal.

Unfortunately this didn't help, does anyone else have an idea what this could be?

  • This might be related, a manual update check gives this error on the affected core server (Other core server do not give the error):

    I have no idea which file this is.

    Details:

    Exception chain:

    The data at the root level is invalid. Line 1, position 1.
    Error in deserializing body of reply message for operation 'GetManifest'. The data at the root level is invalid. Line 1, position 1.


    Stack trace:

    Server side:

    System.ServiceModel.CommunicationException: Error in deserializing body of reply message for operation 'GetManifest'. The data at the root level is invalid. Line 1, position 1. ---> System.Xml.XmlException: The data at the root level is invalid. Line 1, position 1.
       at System.Xml.XmlExceptionHelper.ThrowXmlException(XmlDictionaryReader reader, String res, String arg1, String arg2, String arg3)
       at System.Xml.XmlExceptionHelper.ThrowInvalidRootData(XmlDictionaryReader reader)
       at System.Xml.XmlUTF8TextReader.Read()
       at System.Xml.XmlBaseReader.IsStartElement()
       at System.Xml.XmlBaseReader.IsStartElement(XmlDictionaryString localName, XmlDictionaryString namespaceUri)
       at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, String action, MessageDescription messageDescription, Object[] parameters, Boolean isRequest)
       at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeBodyContents(Message message, Object[] parameters, Boolean isRequest)
       at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeReply(Message message, Object[] parameters)


    --- End of inner exception stack trace ---


    Server stack trace: 
       at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeReply(Message message, Object[] parameters)
       at System.ServiceModel.Dispatcher.DemultiplexingClientMessageFormatter.DeserializeReply(Message message, Object[] parameters)
       at System.ServiceModel.Dispatcher.ProxyOperationRuntime.AfterReply(ProxyRpc& rpc)
       at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)


    Exception rethrown at [0]: 
       at Cloud.Common.Communication.Wcf.ErrorHandling.CloudWcfErrorInspector.AfterReceiveReply(Message& reply, Object correlationState)
       at System.ServiceModel.Dispatcher.ImmutableClientRuntime.AfterReceiveReply(ProxyRpc& rpc)
       at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)


    Exception rethrown at [1]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Cloud.Common.Contracts.AutoUpdate.IAutoUpdatePublicCloudService.GetManifest(String coreId, String coreVersion, String productType, String locale)
       at Replay.Core.Implementation.AutomaticUpdate.ManifestResolver.GetManifest(Version currentVersion)
       at Replay.Core.Implementation.AutomaticUpdate.AutoUpdateService.DownloadManifest()
       at Replay.Core.Implementation.AutomaticUpdate.AutoUpdateService.CheckUpdatesInternal(Boolean nightlyJob)
       at Replay.Core.Implementation.AutomaticUpdate.AutoUpdateService.CheckUpdates()


    UI side:

       at WCFClientBase.HttpResponseMessageExtensions.Check(HttpResponseMessage message, Uri uri, String method, ILogger logger)
       at WCFClientBase.ClientBase.GetResponse(Uri uri, String method, String knownEtag)
       at WCFClientBase.ClientBase.ExecuteServiceCall[T](Uri uri, String method, String knownETag)
       at Replay.Core.Client.AutoUpdateManagementCoreClient.CheckUpdates()
       at Replay.Core.Web.Controllers.UpdateController.CheckForUpdates()
       at lambda_method(Closure , ControllerBase , Object[] )
       at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters)
       at System.Web.Mvc.ControllerActionInvoker.<>c__DisplayClass24_0.b__0()
       at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation)
       at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation)
       at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation)
       at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation)
       at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation)
       at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation)
       at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation)
       at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName)

  • (Temporary) disabled the firewall and removed the AV, didnt help.
    We do not use a proxy server.

  • Thank you Victor.Portillo,
    I did not found this page in my search, but it contained the fix for my issue!
    My problem was this, an expired certificate: https://support.quest.com/kb/4043104/core-fails-to-contact-license-portal-with-the-http-request-is-not-authorized-on-the-anonymous-client-authentication-scheme