"Unable to connect to the SQL database." When Using LocalDB
My company is using SmartAssembly as part of its automated build processes. We recently upgraded to 184.108.40.2060 which forced us to start using an SQL Database, when we used to be able to do an mdb file. We don't even use the Error Reporting tool, we only use SmartAssembly for obfuscation, but no matter what without a proper SQL Database the whole process breaks.
To counteract this, as we don't want our build process dependent on an SQL Server being online, we tried using the LocalDB method as documented on your forums. The issues is, if our server is running and comes to the SmartAssembly process, everything crashes with the following error:
</code><code>Failed: SmartAssembly.InformationException: Unable to connect to the SQL database.<br> at ?..(String )<br> at ?..(TypeAndMethodObfuscator , IEnumerable`1 , Boolean )<br> at SmartAssembly.Processors.PruningObfuscation.Obfuscator.AdvancedTypeAndMethodObfuscator.(TypeDefinition , TypeDefinitionBuilder )<br> at SmartAssembly.Processors.PruningObfuscation.Obfuscator.()<br> at ?..(Obfuscator )<br> at ?..(ProcessingAssemblyHelper , )<br> at ?..(ProcessingAssemblyHelper )<br> at SmartAssembly.ProcessingProjectHelper.()If I open up SmartAssembly on that machine, it immedatly yells at me that the database cannot be connect to. However, if I go into the settings, change the name of the database, then change it back to what it should be, it all connects. In addition, after that, if I keep SmartAssembly open in the background on that server then the automated process works fine. This is not a sustainable solution however, as if we need to reboot and forget to do this "revalidation" process then everything stops working.
My first question is, is there any way we can shut off the SQL Database requirement, considering we don't utilize the feature? If not, can we get that option in a future version? If not, why? My second question is, what can I do in the meantime to fix this issue?
0 · Share on Twitter