Troubleshooting

This content applies to legacy components (such as K2 Studio and K2 for Visual Studio), legacy assemblies, legacy services or legacy functionality. If you have upgraded from K2 blackpearl 4.7 to K2 Five, these items may still be available in your environment. These legacy items may not be available in new installations of K2 Five. These legacy items may also not be available, supported, or behave as described, in future updates or versions of K2. Please see the legacy component support policy for more information about support for these components.
  1. Multiple Bindings

    Microsoft  .NET Framework 3.5 does not support multiple bindings in IIS without configuring a single address and setting up a prefix filter as per the following MSDN KB (Refer to section ‘Multiple IIS Binding Support in .NET Framework 3.5’): http://msdn.microsoft.com/en-us/library/aa751841.aspx

    Some of the following errors may occur when bindings are incorrectly configured.

    • Could not find a base address that matches scheme http for the endpoint with binding WebHttpBinding. Registered base address schemes are [].
    • No protocol binding matches the given address 'http://api.denallix.com:85/K2Services/REST.svc/Worklist/Items'. Protocol bindings are configured at the Site level in IIS or WAS configuration.
    • The resource cannot be found.
    • This collection already contains an address with scheme http. There can be at most one address per scheme in this collection. Parameter name: item

    The K2 installation will not configure <baseAddressPrefixFilters> entries.  To configure K2 Services to support a web site with multiple bindings add a prefix entry for the bindings you wish to support in the <serviceHostingEnvironment><baseAddressPrefixFilters> section of the K2 Services web.config found at [Installation Directory]\WebServices\K2Services\web.config.

Example of supporting the http://api.denallix.com:81 and https://api.denallix.com:443 bindings on an IIS site with multiple bindings.  

<serviceHostingEnvironment>
    <baseAddressPrefixFilters>
        <add prefix="http://api.denallix.com:81" />
        <add prefix="https://api.denallix.com:443" />
    </baseAddressPrefixFilters>
</serviceHostingEnvironment>