logging into Unity OnBase 14: You do not have a SQL CE installed but are using disconneted client?

[Shahid_Bookwala]

We are getting this message when logging into Unity OnBase 14: You do not have a SQL CE installed but are using disconneted client?
Anyone seen this message and have a resolution?

[Jonathan_Finney · Accepted solution]

Hello Shahid,

Thank you for posting to Community.

There are a couple of reasons for this error to be displayed within the Unity Client in OnBase 14.

The first thing that I would recommend checking is if SQL CE is installed ont he workstation itself. If it is not, you can download the file from the following location and install it on the workstation.

                                   http://www.microsoft.com/en-us/download/details.aspx?id=5783

The second thing that you can check is the version of ,NET framework that is installed on the workstation launching the Unity Client. OnBase 14 supports .NET 3.5, 3.5.1, and 3.5.2. If you workstation has .NET version 3.6 or higher installed in it, this might be causing the issue.

Another cause of the issue could be related to an issue with the machine.config file containing an extra closing tag of '<DbProviderFactories/>'. The machine.config file is located in two different locations on a Windows 64-bit workstation:

• C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config   --x86
• C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config  -- x64

SCR #127911 was created to allow the SQL CE operations to be disabled if there is no Unity Briefcase license is found during the login process. At this time, the SCR has not been completed.

If you need further assistance with troubleshooting this issue or additional information on the SCR mentioned above, please reach out to your First Line of Support.

Thanks.

Jonathan Finney
Team Leader
Hyland Software Technical Support Department

[Craig_Mohlenhof]

I have a customer that is having this same issue in 15.0.2.128 with the Unity Client. When IBM i Access for Windows is installed, it places the extra tag that has to be removed. The customer is now running the Thick Client until further testing is complete. They will be taking a sampling of computers to determine the state of the machine.config file. If the computers can just have the machine.config file replaced that can be pushed out, however other applications also write to this file so it seems that would problematic. It would not be acceptable if all computers wold need to be manually edited.
Craig Mohlenhoff