Community
Showing results for 
Search instead for 
Do you mean 
Reply

Can't launch Act! in Parallels for Mac.

New Member
Posts: 3
Country: USA

Can't launch Act! in Parallels for Mac.

I am getting this message; When trying to launch Act. using Parallels for Mac. Any suggestions?

Platinum Super Contributor
Posts: 5,275
Country: USA

Re: Can't launch Act! in Parallels for Mac.

Hello Keith,

Welcome to the ACT! Online Community!

 

The image didn't attach properly, what is the message you are receiving? 

Also, what version of ACT! are you running?

 

Greg Martin
Sage
New Member
Posts: 3
Country: USA

Re: Can't launch Act! in Parallels for Mac.

Thanks for your assistance;


The error message I tried to attache says:

-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.Run0

   at

System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserializ

e(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.Deseralize(String fileName)

(Strategy type BuildPlanStrategy, index 3)

 

 

 

New Member
Posts: 3
Country: USA

Re: Can't launch Act! in Parallels for Mac.

Sorry!  I am running Act! version Pro 2011.

Platinum Super Contributor
Posts: 5,275
Country: USA

Re: Can't launch Act! in Parallels for Mac.

This message is generally caused by corrupted ACT! Preference files.  Here is an article with steps to resolve this issue: KB Article 25865

Greg Martin
Sage