Error message received after installing AyaNova:
AyaNova was unable to start
Depending on how early in startup the problem occurred,
a detailed log of the problem with suggestions may have
been saved to the file AyaLog.txt
located at: file:\C:\Program Files\Ground Zero Tech-Works Inc\AyaNova
Error details:
Unhandled exception:
This AyaNova database appears to have been modified outside of the AyaNova program or is damaged in some way.
This may very rarely be caused by corruption but is more likely a result of someone tampering with
the database and making changes outside the AyaNova program.
(In some cases you may get this error when attempting to use AyaNova 5.x or newer with Microsoft SQL server 2000
which is not supported, only version 2005 or newer.)
Your data is probably ok, but the database is not in a supportable state and will need to be returned to it’s proper state.
Please provide the following information to AyaNova technical support for assistance:
Schema Count: 0
Schema:
System.Security.SecurityException
Stack Trace:
à GZTW.AyaNova.BLL.AyaBizUtils.1()
à GZTW.AyaNova.BLL.AyaBizUtils.Initialize()
à AyaNova.clsMain.MyApp.OnCreateMainForm()
--------------------
Solution:
The above issue was resolved by the following:
- Go to http://support.microsoft.com
- Under Downloads & Updates click on Microsoft Update
- Check to see if any updates needed.
- Apply all recommended updates including .NET Framework 3.5 SP1 and any other fixes or patches to .NET
- Reboot when completed whether it says to or not
- Run AyaNova again
NOTE: Do not just click on OK and ignore a message that AyaNova gives you - in this case, when you installed AyaNova, it does tell you if you need to install .NET Framework 3.5 SP1
Do note too further research has found that when Windows 7 was first released, it came with .net 3.5 sp1 however Microsoft didnt’ set the sp value correctly to 1 and had it set to zero so a lot of apps setups were bailing (including many of Microsofts own software) because they were looking for sp1 and not finding it. Since then apparently Microsoft has fixed that through a very early service pack. But it’s possible that some people with an early windows 7 may persistently get the error that .net framework 3.5 sp1 is not installed in which case they simply need to set the registry setting to 1 here: HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\SP to 1 if it’s set to zero. Or alternatively uncheck .net framework 3.5 sp1 in the list of windows features to uninstall it then pick it again to re-install it.