**Fixed in 6.3** DataPortal & OLI issue

AyaNova 1.x - 6.x AyaNova 3.x to 6.x
1

There is a known issue selecting any AyaNova menu option in Outlook ifyour computer’s connection to your AyaNova database is via a data portal connection. Development is aware of the issue and is looking into a solution. We will post soon.

Error that occurs:

AyaNova initialization failed. Error:

Unable to find assembly ‘CSLA, Version=6.2.0.0, Culture=neutral, PublicKeyToken=df66a8d8e49833d3’.

StackTrace:
at System.Runtime.Serialization.Formatters.Binary.BinaryAssemblyInfo.GetAssembly()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(BinaryAssemblyInfo assemblyInfo, String name)
at System.Runtime.Serialization.Formatters.Binary.ObjectMap…ctor(String objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable)
at System.Runtime.Serialization.Formatters.Binary.ObjectMap.Create(String name, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable)
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryObjectWithMapTyped record)
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryHeaderEnum binaryHeaderEnum)
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 CSLA.DataPortal.Decompress(Byte[] bytes)
at CSLA.DataPortal.Fetch(Object Criteria)
at CSLA.Security.BusinessIdentity.LoadIdentity(String UserName, String Password, AyaNovaConnectionSettings ACS)
at CSLA.Security.BusinessPrincipal…ctor(String Username, String Password, AyaNovaConnectionSettings ACS)
at CSLA.Security.BusinessPrincipal.Login(String Username, String Password, AyaNovaConnectionSettings AyaNovaConnectionSetting)
at GZTW.AyaNova.BLL.AyaBizUtils.Login(String Username, String Password)
at GZTW.AyaNova.BLL.AyaBizUtils.1()
at GZTW.AyaNova.BLL.AyaBizUtils.Initialize()
at AyaNovaOL.Util.Login()

OK

2

[Forum Note: Issue resolved in version 6.3.0.0]

Issue resolved with replacement AyaNovaOL.dll file for use with AyaNova 6.2 - perform the following if you are using a data portal connection with the OLI plugin:

  1. Make sure Outlook is exited on your computer (give it a minute or two to fully unload)

  2. Download AyaNovaOL_April12_2010.zip (download no longer provided - update to latest version 6)

  3. Extract using Winzip and replace the existing AyaNovaOL.dll file dated March 4 2010 located in your AyaNova program folder C:\Program Files\Ground Zero Tech-Works Inc\AyaNova with the zipped file AyaNovaOL.dll dated April 12 2010

  4. Load Outlook

  5. Now when you select any option in the AyaNova menu in Outlook will no longer get the error.

Issue is actually caused by a bug in the .NET framework that Microsoft does not dare to fix because it’s so deep in there it would break lot’s of other stuff to fix it. The bug causes a failure in .net to recognize that an assembly is already loaded or to locate an assembly when in a different appdomain. Development has added code for OLI now that kicks in if a dataportal connection to work around this .NET issue.