Error: "Resolution of the dependency failed" or "Exception has been thrown by the target of an invocation." When Launching Act!

Symptom:
I am attempting to launch Act! when I receive one of the following Errors: "Resolution of the dependency failed." Or "Exception has been thrown by the target of an invocation."

Product Details:
Product Family: Act!
Product: Act! Pro, Act! Premium
Version: 2010 and later

---

Cause:
This error can occur for multiple reasons:

• Program shortcut failed to update after upgrading to Act! v16 or later
• Windows User Account Control settings are stopping Act! from opening
• Act! program preferences are damaged
• A third-party add-on is causing a conflict
• Windows font, Tahoma, is missing or damaged
• Act! installation is damaged
• Missing Microsoft .NET Framework 3.0 registry key
• Damaged Microsoft .NET Framework installation

Solution:

Refer to each section below for steps towards resolving this error.

Program shortcut failed to update after upgrading to Act! v16 or later

1. Find the Act! shortcut on your desktop, right-click it, and choose Delete
2. When prompted with the confirmation, click Yes
3. Click Start > Computer
4. Browse to the following location based on your operating system:
   
   32-bit: C:\Program Files\ACT\ACT for Windows
   64-bit: C:\Program Files (x86)\ACT\ACT for Windows
   
   
5. In the ACT for Windows folder, look for Act!.exe
6. Right-click Act!.exe and choose Send to > Desktop (create shortcut)
7. Go back to the desktop and attempt to launch Act! again to test
   
   

Windows User Account Control settings are stopping Act! from opening

Run As Administrator:

1. Right-click the Act! icon on your desktop and choose Properties
2. Click the Compatibility tab
3. Under Privilege Level, check the box next to Run this program as an administrator
4. Click Apply, then click OK
5. Attempt to open Act! again to test
   

Note: If running the program as an administrator does not work, it may be necessary to disable UAC. For information on disabling UAC, refer to the following Knowledgebase article:



Damaged Preference File (2010 - 2012 only)

This issue may be caused by a damaged preferences file. Follow the steps below to delete this file.

Sage ACT! 2012
If you are using Sage ACT! 2012, this issue can been resolved by applying the latest cumulative hot fix for Sage ACT! 2012 SP1. Please see the following Knowledgebase article for more information and download instructions for this hot fix:



Act! versions 2010 and 2011

1. Close Act!
2. Click your Windows Start button, either click Run or go to the Search box on your Start Menu, and type %appdata%.
3. Open the ACT! folder, then either ACT! Data or ACT! for Windows (version#), depending on your version of Act!.
4. Open the Preferences folder.
5. Locate the file CustomMacros.ser and delete it.
6. Locate the file CustomCommands.ser and delete it.
7. Reopen Act!

Delete the DependentDlls.xml File (2010 and later)
If the above suggestions do not resolve the issue, then deleting the following file and allowing it to be rebuilt have resolved this issue in some cases. Please use the following steps:

1. Close Act!
2. Click on Windows Start button.
3. Windows XP®: Select RUN.
4. Windows Vista/Windows 7: Use Search field.
5. Type in the command %appdata% and press the Enter key on your keyboard.
6. Browse to the following location:
   
7. Windows XP: ACT\ACT for Windows {version #}
8. Windows Vista/Windows 7: ACT\ACT for Windows {version #}
Locations for Act! versions 2011 and later:
• Windows XP: C:\Documents and Settings\{User_Name}\Application Data\ACT\ACT Data
• Windows Vista/Windows 7: C:\Users\{User_Name}\AppData\Roaming\ACT\ACT Data
9. Right-click the DependentDlls.xml file, and then click Delete from the shortcut menu.
10. Click Yes to confirm the deletion and then exit Windows Explorer (or My Computer).
11. Open Act! and test

If the above steps did not resolve your issue, please refer to the following knowledgebase answer for more help prior to proceeding to the next section:



Add-on Conflict
To determine if there is a conflict with add-ons:

1. Close Act!
2. Browse to the Act! installation location
   
   Default locations:
   • 32-bit Operating System: C:/Program Files/ACT/Act for Windows
   • 64-bit Operating System: C:/Program Files (x86)/ACT/Act for Windows
3. Rename folder Plugins (ex: add '-old' to end of name)
4. Attempt to open Act!

If you are able to successfully open the database, close Act!, rename the Plugins folder to original name. Open the Plugins folder and rename individual plugin files and test opening Act! to determine which plugin is at fault.


Damaged or Missing Tahoma Font:
This error has been reported to occur if the Tahoma font is either corrupt on your computer or missing from the Windows® Font folder (C:\Windows\Fonts).



You can attempt to resolve this issue by replacing the missing Tahoma fonts.

Please use the following steps:

1. Go the bottom of this article and click on the tahoma.ttf file under File Attachments, and choose Save. Save to Desktop. Repeat this step also for the tahomabd.ttf file.
2. Launch Windows® Explorer and navigate to the C:\Windows\Fonts directory.
3. Copy or drag and drop both Tahoma font files from the Windows Desktop into the Fonts directory. There will be a quick dialog box that appears as each font is installed.
4. Attempt to launch Act!.

Act! installation is damaged
This can occur if Act! did not install properly or if the installation has become damaged. To resolve:

1. Uninstall Act!. For instructions:
   
   How do I uninstall Act!?
   Answer ID How do I uninstall Act!?
   
   
2. Reinstall Act!. For instructions:
   
   How do I install Act!?
   Answer ID How do I install Act!?
   
   
3. Attempt to open Act! to test

Missing Microsoft .Net 3.0 Registry Key

1. Close Act!
2. Click on Windows Start button.
3. Windows XP®: Select RUN.
4. Windows Vista/Windows 7: Use Search field.
5. Type in regedit and click OK.
6. Locate the following registry key:
   
   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\Windows Presentation Foundation
   
   

If the key is not present, follow these steps to add it:

1. Backup the windows registry per the instructions in the following Knowledgebase article:
   
   How to Back Up the Windows Registry
   Answer ID: How to Back Up the Windows Registry
2. Download the file 25865.reg from the bottom of this document.
3. Double-click on 25865.reg
4. Click Yes when prompted to the registry editor confirmation.
5. Launch Act!.

Damaged Microsoft .NET Framework installation

This error can occur if your Microsoft .NET Framework installation has become damaged. You may need to repair or uninstall and reinstall .NET in order to resolve this. For more information on repairing or uninstalling and reinstalling Microsoft .NET Framework, refer to Microsoft or your IT department for assistance.