Community
Showing results for 
Search instead for 
Do you mean 
Reply

Error Message Act will not start up - HeaderHandler boolean fCheck...

New Member
Posts: 1
Country: USA

Error Message Act will not start up - HeaderHandler boolean fCheck...

[ Edited ]

I see others have had the same problem. I was having no problem and now I have lost complete access to act. What's the solution please. I'm not using Norton and I don't believe I have had any updates since yesterday when it was working. Help

 

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 Act.Composite.UnityExtensions.SimpleUnityBootstrapper.Run(Boolean useDefaultConfiguration)
at Act.Application.Act.Main(String[] args)

 

 

[Edit: Subject to match issue]

Platinum Super Contributor
Posts: 5,275
Country: USA

Re: Error Message Act will not start up - HeaderHandler boolean fCheck...

Hello Mevanc,

Welcome to the Sage ACT! Online Community!

 

This may be caused by damaged Sage ACT! preference files.  You may be able to resolve this issue using the instructions in the following article: KB Article 25865

 

If that does not resolve it, use the option "Alternate Option: Manually Rebuilding Preferences" in this article: KB Article 14770

Greg Martin
Sage