Sage Fix Sage Act Error Resolution of the Dependency Failed

Fix Sage Act Error Resolution of the Dependency Failed

Sage Act! is designed to run on Windows and data must be stored in the database of SQL Servers. It is integrated with Word, Microsoft Outlook, Excel, and other popular software. It is the most innovative and best-selling customer and a contact manager that lets businesses hold notes, account history, contacts, and other activities in a specific centralized location. The software lets business leaders send emails, advertise their goods and services, and drive on-the-go sales results. Sometimes like other software, it also gives errors when users try to open Sage Act! In order to fix the Sage Act error resolution of the dependency failed, go through this blog to get your error resolved at ease.

Symptoms of the Sage Act! Error

When users attempt to start Act! Then the error message pops up on the screen:

β€œException has been thrown by the target” or β€œResolution of the dependency failed”.

Causes of the Sage Act! Error

However, there can be multiple reasons behind this error. Some of the possible reasons are listed below:

  • Failed to update program shortcut after updating to Act! V16 or higher.
  • Act! can damage the program preferences.
  • Settings on Windows User Account Control stop Act! Starting from the start.
  • An add-on by a third party creates disputes.
  • Take action! Installation is harmful.
  • Windows font, Tahoma, is either absent or damaged.
  • Damaged Configuration of Microsoft. NET Framework.
  • Without the registry key for Microsoft. NET Framework 3.0.

Steps for Fix Sage Act Error Resolution of the Dispensary Failed

To fix the Sage Act error resolution of the dispensary failed, you have to carefully observe the reasons that lead to this error and accordingly perform the appropriate methods to fix this issue. Let’s see one by one method to fix it.

Method 1: Run as an Administrator

πŸ’  Firstly, make a right-click on the Act! icon that you can see on desktop
πŸ’  Next, select Properties and then click on the Compatibility tab
πŸ’  Check the box under the privilege level which is next to Run this program as an Admin
πŸ’  Hit the Apply button and then β€œOk” button
πŸ’  Finally, try to open the Act! And then again to test.

Method 2: Damaged Act! Program Preferences

You have to rebuild the Act! Preference files manually. To do so, follow the steps:

πŸ’  Initially, close the ACT!
πŸ’  Next, press the Windows Start button and then hit Run
πŸ’  Type β€œactdiag” in the appear dialog box
πŸ’  Now, go to the Databases and then select Database list
πŸ’  Go to the Tools menu in the Database View

Select the Delete Preferences

πŸ’  Hit the β€œYes” button within the dialog box to continue

Use ACT! Diagnostics

πŸ’  Close the ACT! Diagnostics
πŸ’  And then start ACT!
πŸ’  Hit the β€œNo” button in the dialog box
πŸ’  Now, you can see the ACT! that are getting started Wizard appears
πŸ’  Click on the Cancel option and hit the β€œOpen Database” button
πŸ’  Go to Tools and select Preferences to verify whether your email, fax preferences, and word processor are configured correctly or not
πŸ’  In case, there is a problem, remove Preferences that could cause the conflict
πŸ’  Delete all Preferencesnnn.xml files containing the word BAK, too
πŸ’  At last, open Act! And then test.

Method 3: Windows User Account Control Settings Stopped Act from Opening

πŸ’  The very first, login as an Admin
πŸ’  Next, make a right-click on the Act! And choose Properties
πŸ’  Now, go to the Compatibility tab
πŸ’  Check the box which is not next to Run this program as an Admin under Privileged level
πŸ’  Hit the Apply and then click on the β€œOk” button
πŸ’  Finally, try to open the Act! Then try again and test.

Method 4: Missing Microsoft .NET Framework 3.0 Registry Key

πŸ’  The very first, close Act!
πŸ’  Next, press the Windows Start button
πŸ’  Then type β€œregedit” and hit the β€œOk” button
πŸ’  Now, locate the registry key as mentioned:
πŸ’  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework
πŸ’  Setup\NDP\v3.0\Setup\Windows Presentation Foundation
πŸ’  If you don’t find the below-mentioned registry key then you’ve to add it
πŸ’  To add it follow the steps:
πŸ’  Create a backup for windows registry before you start editing
πŸ’  Then download the 25865.reg file
πŸ’  Make a double-click on the same and hit the Yes button if asked you to confirm
πŸ’  And finally start Act!

Method 5: A Third-party Add-on Caused a Conflict

πŸ’  Initially, close Act!
πŸ’  Next, browse the installation location of Act!
πŸ’  32-bit Operating System: C:/Program Files/ACT/Act for Windows
πŸ’  64-bit Operating System: C:/Program Files (x86)/ACT/Act for Windows
πŸ’  Now, rename the folder as Plug-in
πŸ’  After that, once again attempt to open Act!
πŸ’  If you can trigger an Act! Try to close it again. Now revert to the original name of the Plug-in tab. Rename individual plug-in files in the plug-in folder, and attempt to open Act! It will help figure out which plug-in triggers the conflict. To resolve the error, reinstall/uninstall the plug-in.

Method 6: Tahoma (Windows Font) is Damaged or Missing

πŸ’  Firstly, download the ttfΒ  and tahoma.ttf file
πŸ’  Save them on your desktop
πŸ’  Now, launch the Windows Explorer and navigate to the C:\Windows\Fonts directory
πŸ’  After that, copy both font files of Tahoma and paste them in the Fonts directory
πŸ’  Finally, launch Act! And try to test.

In Conclusion

Hopefully, this blog covered the major information and resolution methods to fix Sage Act! Error resolution of the dependency failed. To know more about Sage Act! & best resolution of Sage errors or any other functional glitches; feel free to connect with Sage 50 support toll-free number . You can also easily reach the team of experts by dropping an email at support@apropayroll.com or can do a Sage 50 live chat to get better assistance with less delay. The team will dedicatedly be committed to serving your doubts all round the clock.

Related Post