9.3 version - ApiServer: Error QER.CompositionApi.Password.PasswordApiConfig

Hello colleagues,

After deactivating all the API providers in the ApiServer Administration Portal for the Password Reset, I cannot access the ApiServer anymore.

When I browse the qbm-app-landingpage, I only get a blank page and in the IIS logs the following error:

System.Exception: API could not be loaded. The API server will be running in connectionless mode. System.Exception: API could not be loaded. The API server will be running in connectionless mode.
---> System.Exception: Service QER.CompositionApi.Password.PasswordApiConfig is not registered.
at VI.DB.Services.Resolve[T]()
at QBM.CompositionApi.ApiManager.ApiServerServices.CombinedResolver.Resolve[T]()
at VI.DB.Services.Resolve[T]()
at QBM.CompositionApi.ApiManager.ApiServerServices.Resolve[T]()
at VI.DB.Services.Resolve[T]()
at VI.DB.Services.Resolve[T]()
at QER.CompositionApi.Password.PasswordPortalApiProject..ctor(IResolve resolver)
at QER.CompositionApi.Password.PasswordPortalApiProjectPlugin.Build(IResolve resolver)
at QBM.CompositionApi.ApiManager.PluginMethodSetProvider.<GetMethodSetsAsync>b__3_0(IPlugInMethodSetProvider p, CancellationToken cx)
at VI.Base.TaskExtensions.SelectAsync[TIn,TOut](IEnumerable`1 input, Func`3 selector, CancellationToken cancellationToken)
at QBM.CompositionApi.ApiManager.PluginMethodSetProvider.GetMethodSetsAsync(CancellationToken ct)
at QBM.CompositionApi.ApiManager.DbMethodProvider.GetBranchedMethodSetsAsync(Boolean includeInactive, CancellationToken ct)

I have tried to re-install the ApiServer completely but the error still persist.

Any idea what can I do to get rid of this error?

Kind regards,

David.

  • Hi David,

    Check the *.json configuration files and remove any lines corresponding to deactivated API providers.Then re-upload the changed files using Software Loader.

    There are some API provider classes needed for internal configuration, which must not be simply deactivated without providing a replacement implementation.

    Regards

    Hanno

  • Hello Hanno,

    Thanks for the response ;)

    I have checked the *.json files, and found that this one CCC.CompositionApi.global.json was the one involved.

    I have copied it from another environment and pasted it on the server with the issue and it solved the problem

    Thank you very much ;)

    Kind regards,

    David.