We've been seeing this error more freqently and in fact I can recreate it on demand on my desktop computer by simply restarting the machine and logging in.
Dialog box is titled ScriptLogic Notice
ScriptLogic has encountered a critical error while "executing SLStart".
There is simply an "OK" button.
This is on top of a black desktop that has our startup graphic behind the scenes (you would see the startup graphic more prominantly back in the Windows 7 and XP days - but normally Windows 10 covers this up until the desktop is available).
Looks like the login script started but it does not complete. There are no mapped drives. Even a partially executed logon script is not copied to our DA server sltrace$ share for review. If I manually run the script after dismissing this message, the login script completes successfully and I have my mapped drives.
\\domain.com\netlogon\slogic.bat
We are on DA 10.2.0.256
Windows 10 1909 OS Build 18363.693
We've had a few calls for this issue. My machine does it, and at least 3 other machines that we know of do it consistently. There may be others that do it randomly.
Any help would be greatly appreciated!
If looking at %temp%\Desktop Authority\sltrace.htm, you see it ends on a line talking about cant create a file when one exists. With this sparse of logging information the issue I have is it does not tell you what file its trying to create. I have no basis to troubleshoot.
15:08:50.552 Spawn engine 15:08:50.557 CreateProcess 15:08:50.562 Check KIX Cache 15:08:50.585 Error Creating wkix32 Process 15:08:50.591 Cannot create a file when that file already exists.
Hi Sauerk
This behavior could be related to antivirus activities, when did it start?
Could you please follow article below and add the Desktop Authority exceptions to your antivirus software?
https://support.quest.com/kace-desktop-authority/kb/sl4593/anti-virus-exceptions
Yes we just switched to Crowdstrike Falcon Complete. Its compltely managed from their SoC. I pasted that article in a support ticket to them to see if they can do exceptions. Its next gen av and endpoint detection, mitigation.
Ok what was causing this was Dell Secureworks Red Cloak. Uninstalling that allows Desktop Authority scripts to run at login, not just manually pasting the slogic.bat netlogon path from the RUN dialod box.
Ok what was causing this was Dell Secureworks Red Cloak. Uninstalling that allows Desktop Authority scripts to run at login, not just manually pasting the slogic.bat netlogon path from the RUN dialod box.
Hello Sauerk.
Thank you for the update!!!
As this was related to antivirus I'll mark this article as the answer, if you don't mind:
https://support.quest.com/kace-desktop-authority/kb/sl4593/anti-virus-exceptions