Problem

After entering credentials, CONNECTION Client displays an animation as it attempts to sign in, but it never completes.

Solution

A duplicate entry in a Microsoft .NET Framework configuration file on the computer may be causing the problem. To check for this, perform the following steps:

1. Open the Windows Start menu, and search for Bentley Log Collector.
2. Click the Collect button, and save the resulting zip archive.
3. Open the BeLicSvc.log file in the zip archive.
4. Search for the following string:
   System.Configuration.ConfigurationErrorsException
5. If found, the message will highlight the duplicate entry in a machine.config file. Remove the duplicate from the file to resolve the issue.

Below is an example found in the BeLicSvc.log file:

Exception Information Details:
======================================
Exception Type: System.Configuration.ConfigurationErrorsException
Message: An error occurred creating the configuration section handler for system.data: Column 'InvariantName' is constrained to be unique. Value 'Pervasive.Data.SqlClient' is already present. (C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config line 152)

The first highlighted selection shows the error that was searched. The second highlighted selection shows the value that has a duplicate entry. The third highlighted selection shows the configuration file and specific location where further investigation is required.

Below is an example from a machine.config file manifesting this issue:

<system.data>

<DbProviderFactories>

<add description="Pervasive Provider, Current Release 4.2" invariant="Pervasive.Data.SqlClient" name="Pervasive PSQL Provider" type="Pervasive.Data.SqlClient.PsqlFactory, Pervasive.Data.SqlClient, Version=4.2.0.0, Culture=neutral, PublicKeyToken=c84cd5c63851e072"></add>
<add description="Pervasive Provider, Release 4.0" invariant="Pervasive.Data.SqlClient.4.0" name="Pervasive PSQL Provider v4.0" type="Pervasive.Data.SqlClient.PsqlFactory, Pervasive.Data.SqlClient, Version=4.0.0.0, Culture=neutral, PublicKeyToken=c84cd5c63851e072"></add>
<add description="Pervasive Provider, Release 4.2" invariant="Pervasive.Data.SqlClient.4.2" name="Pervasive PSQL Provider v4.2" type="Pervasive.Data.SqlClient.PsqlFactory, Pervasive.Data.SqlClient, Version=4.2.0.0, Culture=neutral, PublicKeyToken=c84cd5c63851e072"></add>
<add description="Pervasive Provider, Current Release 3.5" invariant="Pervasive.Data.SqlClient" name="Pervasive PSQL Provider" type="Pervasive.Data.SqlClient.PsqlFactory, Pervasive.Data.SqlClient, Version=3.5.0.0, Culture=neutral, PublicKeyToken=c84cd5c63851e072"/>
<add description="Pervasive Provider, Release 3.2" invariant="Pervasive.Data.SqlClient.3.2" name="Pervasive PSQL Provider v3.2" type="Pervasive.Data.SqlClient.PsqlFactory, Pervasive.Data.SqlClient, Version=3.2.0.0, Culture=neutral, PublicKeyToken=c84cd5c63851e072"/>
<add description="Pervasive Provider, Release 3.5" invariant="Pervasive.Data.SqlClient.3.5" name="Pervasive PSQL Provider v3.5" type="Pervasive.Data.SqlClient.PsqlFactory, Pervasive.Data.SqlClient, Version=3.5.0.0, Culture=neutral, PublicKeyToken=c84cd5c63851e072"/>

The two selections highlighted in yellow show the two duplicate entries. Note that they have the same invariant name. While deleting either <add> entry would resolve the issue for CONNECTION Client, this example shows that the second <add> entry already had another entry further down with the same type and version. These have been highlighted in green. Therefore the <add> entry with a description of "Pervasive Provider, Current Release 3.5" was selected for removal.