08-01-2013 02:58 AM
Hello,
a customer of ours gets this exception. After examining the log files, I see that the exception is cause by these two innocent lines of code in my program:
The stack trace looks like this:
08-01-2013 07:41 AM
Hello Andrey,
This exception is thrown when the SQL server master database cannot be found, reinstalling SQL may resolve the issue.
08-01-2013 07:49 AM
Hi Matthew,
Thank you for your answer. I will pass this to the customer and will let you know if it helps.
08-03-2013 01:29 PM
If this client is running ACT! 2013 and your other clients have been running ACT! 2012 or earlier you must recompile stand alone programs that work with the new version of ACT! with .NET 4.0 or create a config file directive that tells the program to work with the later libraries.
Stan
08-05-2013 01:36 AM - edited 08-06-2013 05:45 AM
The customer has reported that it helped. I just wonder why the database got deleted, and why he could access the DB from ACT! without problems.
08-05-2013 01:40 AM
To wellmet:
You can actually run your programs compiled for ACT 2012 with ACT 2013 without having to rebuild them, if you use the startup section in the config file:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0"/>
</startup>
</configuration>
08-05-2013 12:04 PM
Thanks for the concise config file entry. After rereading the original post it does appear that Matt's solution is probably the best. There is a "master" database in SQL and if it is gone for some reason that is probably what is causing the problem. I don't remember ever seeing that happen but I think I have read about it from occasionally.
Stan