Reply to thread

Message

<blockquote data-quote="danb" data-source="post: 1017740" data-attributes="member: 62850">Thank you guys for letting me know!&nbsp; Is there an older version of VS or DefenderUI Pro that does not have this issue?&nbsp; If so, I can compare the old code to the new code and it will be a super quick and easy fix.&nbsp; I think [USER=52096]@Gandalf_The_Grey[/USER] ran VS for a long time without any issues, so it must be a recent change in the code that caused this issue.&nbsp; So if possible, if you can install the last version of VS or DefenderUI you know was working and let me know which version it is, we will have a fix very quickly.&nbsp; BTW, I will probably need to send you a modified version of the old version you were using because it probably expired today.&nbsp; Just email me at support at voodooshield.com and I will send you a version you can test.The only other thing that might be causing this is when I downgraded our SQL server 3 or so weeks ago.&nbsp; The SQL Server we were using was extreme overkill, so I downgraded it to a more appropriate level.&nbsp; I do not think this would cause this issue, but I can certainly upgrade it to the previous level to test.&nbsp; Thanks again!</blockquote>

[QUOTE="danb, post: 1017740, member: 62850"] Thank you guys for letting me know! Is there an older version of VS or DefenderUI Pro that does not have this issue? If so, I can compare the old code to the new code and it will be a super quick and easy fix. I think [USER=52096]@Gandalf_The_Grey[/USER] ran VS for a long time without any issues, so it must be a recent change in the code that caused this issue. So if possible, if you can install the last version of VS or DefenderUI you know was working and let me know which version it is, we will have a fix very quickly. BTW, I will probably need to send you a modified version of the old version you were using because it probably expired today. Just email me at support at voodooshield.com and I will send you a version you can test. The only other thing that might be causing this is when I downgraded our SQL server 3 or so weeks ago. The SQL Server we were using was extreme overkill, so I downgraded it to a more appropriate level. I do not think this would cause this issue, but I can certainly upgrade it to the previous level to test. Thanks again! [/QUOTE]

Verification