Community
Showing results for 
Search instead for 
Do you mean 
Reply

RESOLUTION OF THE DEPENDENCY FAILED, TYPE ERROR

New Member
Posts: 1
Country: USA

RESOLUTION OF THE DEPENDENCY FAILED, TYPE ERROR

I am getting an error when I start the ACT! program:

 

Resolution of the dependency failed, type = "ACT.UI.ACTAPPLICATION", name = "". Exception message is:  The Current build operation (build key BUILD KEY [ACT.UI.ACT APPLICATION, null]) failed:

System.Runtime.Serialization.SerializationException: Binary stream '0' does not contain a valid Binary Header.  Possible cause are invalid stream or object version change between serialization and deserialization.

at

System.Runtime,serialization.formatters.binary._BinaryParser.Run()

at

System.Runtime.serializations.formatters.binary.objectreader.deserialize(HeaderHandler handler,_BinaryPar serParser, Boolean fCHeck, Boolena is CrossAppDomain, IMethodCallMessage

methodCallMessage)

at

System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage

methodCallMessage)

at ACT.UI.Core.CustomCommandHelper.Deserialization(String fileName)

(Strategy type BuildPlanStrategy, index3)

 

 

I received an e-mail from another respresentative and followed all suggestions, but it didn't fix it:

 

 
Sage North AmericaSage Support

21CHAT HOURS
  • Sage 50 US Edition -   Mon-Fri, 8:30 AM to           8:30 PM Eastern
  • Sage 100 Fund Accounting -   Mon-Fri, 10:00 AM to           4:00 PM Central
  • Sage ACT! -   Mon-Fri, 8:30 AM to           8:30 PM Eastern
  • Sage BusinessVision -   Mon-Fri, 9:00 AM to           4:00 PM Eastern
  • Sage BusinessWorks Accounting -   Mon-Fri, 6:00 AM to           4:00 PM Pacific
  • Sage DacEasy -   Mon-Fri, 8:30 AM to           5:30 PM Eastern
  • Sage Fixed Assets -   Mon-Fri, 9:00 AM to           5:00 PM Eastern
  • Sage Fundraising 50 -   Mon-Fri, 10:00 AM to           4:00 PM Central
  • Sage HRMS -   Mon-Fri, 9:00 AM to           5:00 PM Eastern
  • Sage Timeslips -   Mon-Fri, 8:30 AM to           7:00 PM Eastern
21ADVANCED FEATURES
(Login required)
Search
Advanced Search
Search terms
Screen Reader users press enter to Limit by product. Limit by productThis button does not work with screen readers. Please use the previous link instead. Select a product
 
 
 
Sort byDefaultSummaryNew or UpdatedDescriptionDate UpdatedDirectionAscendingDescending
Helpful search tips
Find the answer to your question
Error: "Resolution of the dependency failed" or "Exception has been thrown by the target of an invocation." When Launching ACT!
                Answer ID 25865          |                   Published 01/13/2010 04:15 PM          |           Updated 07/13/2012 03:40 PM   
You are attempting to launch ACT! when you receive one of the following error messages: "Resolution of the dependency failed." -or- "Exception has been thrown by the target of an invocation."
There is more than one possible cause for this issue. Please try the solutions listed below, one at a time and in the order listed.
Run As Administrator: If you are using either Windows Vista® or Windows® 7, you may be able to work around this issue by launching ACT! with the Run as Administrator option. This is done by right-clicking on the ACT! icon and selecting Run as Administrator from the dialog box.
Damaged Preference FileThis issue may be caused by a damaged preferences file. Follow the steps below to delete this file.
  1. Close Sage 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 Sage ACT!.
  4. Open the Preferences folder.
  5. Locate the file CustomMacros.ser and delete it.
  6. Reopen Sage ACT!
If the above steps did not resolve your issue, please refer to the following knowledgebase answer for more help:
How To Rebuild the Sage ACT! Preferences File Answer ID: 14770

 

Delete the DependentDlls.xml File 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 Sage ACT!
  2. Click on Windows Start button.
    • Windows XP®: Select RUN.
    • Windows Vista/Windows 7: Use Search field.
  3. Type in the command %appdata% and press the Enter key on your keyboard.
  4. Browse to the following location:
    • Windows XP: ACT\ACT for Windows {version #}
    • Windows Vista/Windows 7: ACT\ACT for Windows {version #}
    Locations for Sage ACT! 2011 & Sage ACT! 2012 Installations:
    • 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
  5. Right-click the DependentDlls.xml file, and then click Delete from the shortcut menu.
  6. Click Yes to confirm the deletion and then exit Windows Explorer (or My Computer).
  7. Open ACT! and test
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).
Image
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 Sage ACT!.
Missing Microsoft .Net 3.0 Registry Key
  1. Close Sage ACT!
  2. Click on Windows Start button.
    • Windows XP®: Select RUN.
    • Windows Vista/Windows 7: Use Search field.
  3. Type in regedit and click OK.
  4. 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: 11568
  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 Sage ACT!.