When I start Reporting4Act!, I receive the message "Error #1426 (0x8013150): Failed to initialize StonefieldQuery.ACT2005COM."

StonefieldQuery.ACT2005COM is a component of the Reporting4Act! installation. This error message indicates that this component has not been registered properly with Windows, or that some problem is preventing this component from properly starting up and interacting with Act! itself. There are several known situations which can produce this error. These causes are listed below, along with instructions for resolving them.

Rather than attempting to resolve this problem manually, a simple option is to re-run the Reporting4Act! installer. Often this resolves the problem directly.

Also, the component in question is a fairly minor one, and it's possible to simply switch it off. To do this, edit the file data.ini in the Data folder inside your main Reporting4Act! program folder, and add a ConnectSDK=No line to the [Options] section:

ConnectSDK=No

There are several known causes of this error message.

1. Reporting4Act! is not configured properly for use with Act! 2013 or later.

Reporting4Act! requires a configuration file to be in place in order to interact properly with Act! version 2013 or later. If this file is not in place, then Reporting4Act! will be unable to function properly. Normally, this file is created as part of the Reporting4Act! installation, on systems with such versions of Act! installed. Follow the instructions in the Act 2013 (15.*) or Later Configuration topic to resolve this problem.

2. A Reporting4Act! component was not registered correctly during the installation of Reporting4Act!.

The installation program for Reporting4Act! does all the necessary registration of files for Reporting4Act! to run properly. If one of these registrations has failed for some reason, then this error can appear.

The Reporting4Act! installation includes a set of small utility programs to do this registration for you. The particular program to use depends on your version of Act!, and your version of Windows:

• RegisterQueryDLLs1.bat - For use with Act! 2005 and 2006, under a 32-bit version of Windows.
• RegisterQueryDLLs2.bat - For use with Act! 2007 (9.*), under a 32-bit version of Windows.
• RegisterQueryDLLs3.bat - For use with Act! 2008 (10.*) - 2012 (14.*), under a 32-bit version of Windows.
• RegisterQueryDLLs4.bat - For use with Act! 15.* (2013) and later, under a 32-bit version of Windows.
• RegisterQueryDLLs64bit1.bat - For use with Act! 2005 and 2006, under a 64-bit version of Windows.
• RegisterQueryDLLs64bit2.bat - For use with Act! 2007 (9.*), under a 64-bit version of Windows.
• RegisterQueryDLLs64bit3.bat - For use with Act! 2008 (10.*) - 2012 (14.*), under a 64-bit version of Windows.
• RegisterQueryDLLs64bit4.bat - For use with Act! 15.* (2013) and later, under a 64-bit version of Windows.

These files are stored in the Utilities subdirectory of your Reporting4Act! program directory. In most cases, you can simply double-click the appropriate file to run it. The exceptions are if you have a non-standard location for the Windows Program Files folder, or a non-standard location for the .NET Framework. In these cases, you must alter the file to point to the correct location for these items on your system.

These batch files each use 2 files: regasm.exe, and one of SFQueryAct2005COM.dll, SFQueryAct2007COM.dll, or SFQueryAct2008COM.dll. The Reporting4Act! installer places the dll file into the Common Files folder in the Program Files folder. Usually, this is located at "C:\Program Files\Common Files\Microsoft Shared\VFP" (for 32-bit versions of Windows) and "C:\Program Files (x86)\Common Files\Microsoft Shared\VFP" (for 64-bit versions of Windows). If your machine uses a different folder, you will need to modify the command lines in the batch file to reference the correct location on your machine. Similarly, regasm.exe is a part of the Microsoft .NET installation, which is usually located at "C:\Windows\Microsoft.NET\Framework". If your system has this folder in a different location, you will need to modify the command lines as well.

Once you've made these changes (if necessary), double-click the file to run it. On some systems, you may need to right-click on the file and choose "Run as Administrator" to execute it properly. You should see a screen appear with some text ending with "Types Registered Successfully". This should resolve the error message in Reporting4Act!.

3. The necessary Microsoft .NET version is not enabled on the machine.

This component requires .NET to be available. On recent versions of Windows, this can be done through the Turn Windows features on or off link in the Windows Programs and Features app.

4. There is a problem with the security settings for this component on your machine.

Particularly in the cases of Act! 2005 and Act! 2006, a Reporting4Act! file can have incorrect security settings. These incorrect settings will prevent Windows from running this file when Reporting4Act! requests it, resulting in this error. You can restore the correct security settings with the following steps.

• Open the Windows Control Panel from your Windows Start menu
• In Control Panel, double-click Administrative Tools, and then double-click Microsoft .NET Framework 1.1 Wizards.
• In the .NET Wizards window, click Trust an Assembly. The Trust an Assembly dialog box appears.
• Click to select the Make changes to this computer option, and then click Next.
• Click Browse. The Choose Assembly dialog box appears.
• In the Choose Assembly dialog box, locate the file C:\Program Files\Common Files\Microsoft Shared\VFP\SFQueryAct2005COM.dll, and then click Open.
• In the Trust an Assembly dialog box, click Next.
• In the Trust an Assembly dialog box, move the slider to Full Trust, and then click Next.
• Click Finish.

5. There is a problem with the Act! installation on the machine.

Act! versions 2005-2009 use "policy" files to help with the development of add-ons, such as Reporting4Act!. The purpose of these policy files is to allow these add-ons to successfully reference the particular version of Act! on a machine. In some cases, these Act! policy files can be corrupted, and this error is the result.

In this situation, the problem can be resolved by adding a configuration file to the Reporting4Act! program directory. This file contains the Act! version information for the Act! program installed on your machine, allowing the system to bypass the policy files completely. To add this configuration file to your copy of Reporting4Act!, follow these steps.

First, find the version number of the Act! files on your machine. To do this, open Windows Explorer, and navigate to C:\Windows\assembly. You will see a listing of all assemblies on your machine, similar to this screenshot:

Find the ACT assemblies in the list, and note the version number. In this example, the version number is 11.1.178.0, as shown by the highlighted item in the list.

Second, copy the file sfquery-HandleActVersion.exe.config from the Utilities subfolder of the Reporting4Act! program folder into the main Reporting4Act! program folder. Rename this file to simply sfquery.exe.config.

Finally, use Notepad to edit the sfquery.exe.config file in the Reporting4Act! program folder. Modify each newVersion entry to match the version number you found in the assembly folder in step 1. The following screenshot shows the first two entries in the config file properly edited to the 11.1.178.0 version number.

With the sfquery.exe.config file in place and properly edited, the error message should no longer come up.