Forums

Forums / Developing Portals / IPortalConnectorAdminAppInitializer No matching bindings are available

IPortalConnectorAdminAppInitializer No matching bindings are available

3 posts, 0 answered
  1. Max Bayer
    Max Bayer avatar
    4 posts
    Registered:
    28 Sep 2023
    27 Nov 2023
    Link to this post
    Hello there,

    currently I am getting an error when trying to run sitefinity/portal connector, the error appears when initlializing the system.
    Error activating IPortalConnectorAdminAppInitializer
    
    No matching bindings are available, and the type is not self-bindable.
    
    Activation path:
    
      1) Request for IPortalConnectorAdminAppInitializer
    
    
    
    Suggestions:
    
      1) Ensure that you have defined a binding for IPortalConnectorAdminAppInitializer.
    
      2) If the binding was defined in a module, ensure that the module has been loaded into the kernel.
    
      3) Ensure you have not accidentally created more than one kernel.
    
      4) If you are using constructor arguments, ensure that the parameter name matches the constructors parameter name.
    
      5) If you are using automatic module loading, ensure the search path and filters are correct.
    
    
                                    
    at Ninject.KernelBase.Resolve(IRequest request) at Ninject.ResolutionExtensions.GetResolutionIterator(IResolutionRoot root, Type service, Func`2 constraint, IEnumerable`1 parameters, Boolean isOptional, Boolean isUnique) at Ninject.ResolutionExtensions.Get[T](IResolutionRoot root, IParameter[] parameters) at pavliks.PortalConnector.AdminApp.Startup.InitilizeAdminApp(Object sender, ExecutedEventArgs e) at pavliks.PortalConnector.AdminApp.Startup.Bootstrapper_Initialized(Object sender, ExecutedEventArgs e) at System.EventHandler`1.Invoke(Object sender, TEventArgs e) at Telerik.Sitefinity.Abstractions.Bootstrapper.OnInitialized(Object sender, ExecutedEventArgs args) at Telerik.Sitefinity.Abstractions.Bootstrapper.Bootstrap() at Telerik.Sitefinity.Web.SitefinityHttpModule.<>c.<BootstrapAsync>b__4_0(Object ctx)

    I got the current state of the system via git from my server. Sitefinity/tpc runs fine on the server and no error is thrown.

    What did I try:

        1. Created a new folder with the content from the git branch on the server, run it, worked.
        2. Doing the sames as 1, but on my laptop. Didnt work.
        3. Got the same version of vs on my laptop as on the server, compared the addons, nugets etc. didnt work.
        4. copied the working folder, the initlial commit which worked on the server manually to the laptop, didnt work.
        5. reinstalled all nugets, didnt work.
        6. Updated all nugets to the newest version, didnt work. (reset it afterwards using git)
        7. Cleared and rebuild the solution many times, didnt work.
     
    Does someone have an idea, what the issue might be?


    On my Laptop I am running VS 2019/2022 and on the server VS 2019
    The Laptop is using Win 11 (DE) and the Server Windows Server 2022 Datacenter(EN)


  2. Max Bayer
    Max Bayer avatar
    4 posts
    Registered:
    28 Sep 2023
    27 Nov 2023 in reply to Max Bayer
    Link to this post
    As sidenote, when the code didnt compile at all in vs, I used the last successful build, which worked.
  3. Rawdon Edghill
    Rawdon Edghill avatar
    76 posts
    Registered:
    16 Dec 2020
    27 Nov 2023
    Link to this post
    Hi Max,

    Thank you for your question. 

    I am assuming you are trying to perform an upgrade. 

    During an upgrade, you may come across an error in your SF logs and/or directly on the webpage that says something like: 
    “Error activating IPortalConnectorAdminAppInitializer [or ITpc…] No matching bindings are available, and the type is not self-bindable. …

    Suggestion:
    1) Ensure that you have defined a binding for IPortalConnector…”

    Resolution:
    It is likely that the ControllerContainerAsembliesLocation.json in the bin doesn't contain any or some pavliks references.

    These references are cached in the portal and so before an upgrade, it is best to disable the caching of the assemblies as there may be new references in later TPC versions.  

    Other scenarios where this issue can arise from:
        -When configuring an external authentication provider that you have never used before which uses an interface like ITpcExternalAuthUserHandle

    By the time this error gets generated, the portal site is no longer functional, so it is recommended that you do the following step before you do an upgrade.  

    1.  To disable the cache on the controller container assemblies, go to
    Administration > Settings > Advanced > Feather > uncheck the checkbox “use cached controller container assemblies” 

    2.  Close the app and readd the correct ControllerContainerAsembliesLocation.json file with the proper references to the bin.

    3.  Start the application once more and the error should go away.

    4.  Once the application has started, recheck the box to re-enable caching on the controller container assemblies


    I hope this helps answer your question or lead you in the right direction. 

    Regards,

    Rawdon
    Last modified on 27 Nov 2023 16:11 by Rawdon Edghill
3 posts, 0 answered