This article only applies to Squared Up Version 2.0. If you're looking for help with Squared Up Version 3.0, please visit our new knowledge base

In a multi-server deployment, one Squared Up web server must act as a primary server, with all other servers designated as secondary servers. The secondary servers report usage to the primary server, ensuring that usage across all servers stays within licensed limits.


For information about user licencing see Who can log on to Squared Up? and Managing Named Users (Licensing)


For how to activate a licence and problems activating a licence see How to activate your licence


For information about the different Squared Up licences available see An overview of Squared Up Licensing


If the secondary server cannot communicate with the primary server for licensing then a warning will be shown:



Troubleshooting Multiserver Licencing

1. Check the list of errors at the end of this article to see if there is a specific solution.

2. If you have edited the users.xml file, then check that the xml is formatted correctly, with the correct xml header, and all the required beginning and end tags.  For formatting information see Managing Named Users (Licensing)

3. Check that the primary server is specified as the licence server on the secondary server, see Licensing Multi-server Deployments

4. Check the HTTP Activation feature is enabled, see How to add the Windows Feature 'HTTP Activation'

5. Ensure that the C:\inetpub\wwwroot\SquaredUpv2\web.config file on the Primary server contains the following section:

6. Check the bindings (In IIS Manager, click on 'Default Web Site', and then click 'bindings' on the right-hand side). If there are multiple bindings (e.g. HTTP & HTTPS) you may need to add the following to the <serviceHostingEnvironment> section of the web.config files on both the Primary and Secondary server.

<serviceHostingEnvironment multipleSiteBindingsEnabled="true"/>

7. If you have HTTPS bindings you may need to add the following to your web.config file within the <system.serviceModel> section. This translates the HTTPS binding back into a HTTP binding for licensing.

<bindings>
    <basicHttpBinding>
        <binding name="LicenseServerHttpsBinding">
            <security mode="TransportCredentialOnly">
                <transport clientCredentialType="InheritedFromHost" />
            </security>
        </binding>
    </basicHttpBinding>
</bindings>

8. Check that a firewall is not blocking communication between the two servers.

9. Browse to http://<squaredupserver>/squaredup/licensing.svc

If the license service is running you should see a service page similar to the one shown below:

If you don't see this service page, check steps 1-8 above.


10. Browse to http://<squaredupserver>/squaredup/licensing.svc/release in Internet Explorer (it will look like a blank page in Chrome) and you should see a HTTP 400 Bad Request page:


If you do not get the HTTP 400 Bad Request page and get a HTTP 404 instead, check step 7 above.

Error messages

Unable to verify your product license. The license server is not configured.

See Unable to verify your product license. The license server is not configured.


Unable to verify your product license. The license server returned the following error: {3F68EDCE-179E-4997-90C2-A6FCE582D6E5} (System.Object[])System.Object[]

See Unable to verify your product license. The license server returned the following error: {3F68EDCE-179E-4997-90C2-A6FCE582D6E5} (System.Object[])System.Object[]


Unable to verify your product license. The license server returned the following error: There is an error in XML document (1,2)

See Unable to verify your product license. The license server returned the following error: There is an error in XML document (1,2)


Unable to verify your product license. The license server returned the following error: Access to the path 'C:\inetpub\wwwroot\SquaredUpv2\AppState\users.xml' is Denied

See Unable to verify your product license. The license server returned the following error: Access to the path 'C:\inetpub\wwwroot\SquaredUpv2\AppState\users.xml' is Denied


Unable to verify your product license. The license server returned the following error: The remote server returned an unexpected response: (405) Method Not Allowed)

See How to add the Windows Feature 'HTTP Activation'


Unable to verify your product license. The license server returned the following error: The HTTP request was forbidden with client authentication scheme 'Negotiate'.

If you have HTTPS bindings you may need to add some bindings information to your web.config file to translate the HTTPS binding back into a HTTP binding for licensing, see step 7 above.