InsDBConnection Error

Database Initialisation Failed – InsDBConnection Error

Introduction

This document describes issues that may arise with the installation of InSite software. The standard solution to this problem can be found on page 3. This has been found to be more common, particularly on Corporate Active Directory based networks, where security settings can impede a successful installation. In such circumstances, the following information is provided for the guidance of your IT team.

To improve data sharing and data security the InSite Database used by InSite now runs in a separate process from the User Interface. This process is run as a Windows NT Service. The user interface components link to the Database service using Microsoft DCOM technology.

If InSite is installed in a client server configuration then there will be a requirement to install a service on both the Client machines and on the Server machine.

Default Installation - Workstation

By default the setup.exe program will attempt to create a LOCAL account on the install machine – called ‘InsDBSvcUsr87’ and will generate a complex password for this account. The InSite Database Service – named ‘InsDB8x’, where ‘x’ is the minor version number, will be installed to use this account.

In order to successfully start the service the ‘InsDBSvcUsr87’ account must be a member of the LOCAL ‘Administrators’ group on the machine AND have the ‘Logon as Service’ privilege.

Since setup.exe must be run by a member of the Administrators Group on the machine, the installation usually succeeds.

Default Installation – Server

Installation on a machine running Windows Server 2007 or later follows the same process as on a workstation, with the exception that if the Server is a Member Server of an Active Directory Domain then the Account created will be named ‘InsDBSvcUsr8Z’ and will be a DOMAIN account.

Diagnosing Problems

Having successfully installed the software the User should start InSite whilst still logged in as Administrator. If there are no errors then the installation has been successful and no further action should be required.

However, on occasion an error message will be encountered on first start of the software. This usually means that the InSite Database Service has failed to start. The pop-up will state an RPC code, of which, two existing versions are most common: RPC code 8007041d and RPC code 8007042d (as shown below).

Occasionally, we have seen an error with the RPC code 800706ba which has a similar solution but on a server/citrix installation.

The Corporate Active Directory Environment

When setting up an Active Directory Domain in a corporate environment it is usual for the IT department to restrict the actions allowed on Member Machines using Group Policy. If the InSite Database Service fails to start then it is usually because the Group Policy has been set in such a way as to prevent the Service logging in.

To check these rights, click the Windows Start button and search secpol.msc. If the application is available on the machine, this will start the Local Security Policy window. Expand Local Policies | User Rights Assignment and look for the Entry ‘Log on as a service’. If this entry does not contain the ‘Administrators’ group, within the Security Setting column, then the service will be unable to start.

Problem Resolution – Standard

This will guide you through the most common solution to this problem and can often be completed without needing to contact the IT team.

Open the Services application on your computer. Click on the Windows/Start key in the bottom left hand corner of your screen. In the search box, type Services and open the link Services link within the Programs section. Alternatively, you can reach the same window by navigating to Control Panel | Administrative Tools.

The Services window should now appear. It should look similar to the image below. Scroll down on the list of Services until you see “InSite87 DB Server”

Double click on it to open the properties window (you can also right click and select Properties). Click on the Log On tab and click the button beside Local System account. This should now allow you to open InSite as normal.