Community
Showing results for 
Search instead for 
Do you mean 
Reply

Resolution of the dependency failed.

New Member
Posts: 3
Country: USA

Resolution of the dependency failed.

Can someone walk me through a fix WITHOUT having to rebuild ACT. I've tried the "Run Administrator" and "Tahoma" font fixes without success. The error message that comes up when I try to launch ACT is:

 

 

Microsoft.Practices.Unity.ResolutionFailedException: Resolution of the dependency failed, type = "Act.UI.ActApplication", name = "". Exception message is: The current build operation (build key Build Key[Act.UI.ActApplication, null]) failed: System.Runtime.Serialization.SerializationException: Binary stream '0' does not contain a valid BinaryHeader. Possible causes are invalid stream or object version change between serialization and deserialization.

   at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()

   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)

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

   at Act.UI.Core.CustomCommandHelper.Deserialize(String fileName) (Strategy type BuildPlanStrategy, index 3) ---> Microsoft.Practices.ObjectBuilder2.BuildFailedException: The current build operation (build key Build Key[Act.UI.ActApplication, null]) failed: System.Runtime.Serialization.SerializationException: Binary stream '0' does not contain a valid BinaryHeader. Possible causes are invalid stream or object version change between serialization and deserialization.

   at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()

   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)

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

   at Act.UI.Core.CustomCommandHelper.Deserialize(String fileName) (Strategy type BuildPlanStrategy, index 3) ---> System.Exception: System.Runtime.Serialization.SerializationException: Binary stream '0' does not contain a valid BinaryHeader. Possible causes are invalid stream or object version change between serialization and deserialization.

   at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()

   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)

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

   at Act.UI.Core.CustomCommandHelper.Deserialize(String fileName)

   at Act.UI.Core.CustomCommandHelper.Deserialize(String fileName)

   at Act.UI.Core.CustomCommandHelper.get_CustomMacroHandlers()

   at Act.UI.Core.Explorer.RestoreImagesToCollection()

   at Act.UI.Core.Explorer.LoadDisconnectedMenuToolBar()

   at Act.UI.ActApplication.InitializeExplorer()

   at Act.UI.ActApplication.InitializeApplication()

   at Act.UI.ActApplication..ctor(IUnityContainer container, IEventAggregator eventAggregator)

   at BuildUp_Act.UI.ActApplication(IBuilderContext )

   at Microsoft.Practices.ObjectBuilder2.DynamicMethodBuildPlan.BuildUp(IBuilderContext context)

   at Microsoft.Practices.ObjectBuilder2.BuildPlanStrategy.PreBuildUp(IBuilderContext context)

   at Microsoft.Practices.ObjectBuilder2.StrategyChain.ExecuteBuildUp(IBuilderContext context)

   --- End of inner exception stack trace ---

   at Microsoft.Practices.ObjectBuilder2.StrategyChain.ExecuteBuildUp(IBuilderContext context)

   at Microsoft.Practices.ObjectBuilder2.Builder.BuildUp(IReadWriteLocator locator, ILifetimeContainer lifetime, IPolicyList policies, IStrategyChain strategies, Object buildKey, Object existing)

   at Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type t, Object existing, String name)

   --- End of inner exception stack trace ---

   at Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type t, Object existing, String name)

   at Microsoft.Practices.Unity.UnityContainer.Resolve(Type t, String name)

   at Microsoft.Practices.Unity.UnityContainerBase.Resolve[T]()

   at Act.Application.ActBootstrapper.ConfigureContainer()

   at Microsoft.Practices.Composite.UnityExtensions.UnityBootstrapper.Run(Boolean runWithDefaultConfiguration)

   at Act.Application.Act.Main(String[] args)

Platinum Elite Contributor
Posts: 6,537
Country: USA

Re: Resolution of the dependency failed.

[ Edited ]

Hello Norm,
KB article 25865 contain the known solutions we have at this time. If the solutions you listed as having tried did not resolve, then (per the article), you will need to try deleting the DependentDlls.xml file or manually rebuilding the ACT! preferences file (by renaming the ACT! Data folder indicated in the article). These are the steps:
1. Close Sage ACT! and all running MS Office applications (Word, Outlook, Excel)
2. Open your Windows Task Manager (Ctrl+Alt+Del)
3. Under the Processes tab in the Task Manager, locate the following processes (if running), select them, and click End Process:

     ActSage.exe
     Act.Outlook.Service.exe
     Act.Scheduler.exe
     Sage.ACT.Integration.exe

4. Close the Task Manager
5 Click on your Windows Start button. For Windows 2000 and Windows XP, click Run on the Start Menu and type in the following command: %appdata%. For Windows Vista and Windows 7, type this command in the Search box in the lower left of the start menu.
6. This will open the Application Data folder. In this folder open the ACT folder.
7. In this folder you should see one or more folders with the following names:
* ACT! by Sage 2010 and earlier: Act for Windows (version#), where "version#" is the current (or previous) version of ACT! installed on this machine.
* Sage ACT! 2011, 2012: ACT Data.
8. Right-click on these folders, select Rename, and add the word "OLD" to the end of the filename. Ex: "Act for Windows 12OLD"
9. Close Windows Explorer.
10. Reboot your computer to ensure that the services you stopped in Step 3 properly restart.
11. When your computer boots back up, open Sage ACT! to test.

Greig Hollister

Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.

New Member
Posts: 2
Country: Canada

Re: Resolution of the dependency failed.

Running Window 7 & ACT! 2011

 

This method does not resolve the problem

New Member
Posts: 6
Country: Argentina

Re: Resolution of the dependency failed.

WORKED ! GENIUS, W7+ACT 2011. TXS A LOT.

Administrator
Posts: 4,024
Country: United_Kingdom

Re: Resolution of the dependency failed.

The Knowledgebase article for this error can be found below:
http://kb.act.com/app/answers/detail/a_id/25865