I was setting up sqla12 with a new customer and noticed that the sqla12 engine suddenly quit. I looked at the event log and found this event: Blocked by access protection rule. Access to object c:\users...\AppData\Roaming...\resq.lnk.
Does sqla12 create any *.lnk files when processing? Does it create any other files in the Users...\AppData\Roaming... directory?
asked 25 Jun '14, 10:59
SQLAnywhere will create some files in a subdirectory (SQL Anywhere [ver]) of the %APPDATA directory which, on Windows (depending on version), will default to be in the user's AppData\Roaming\ directory.
I am not aware of any .LNK files being created by SQL Anywhere (in the "SQL Anywhere [ver]" directory). Other products using SQLA may create these files?
answered 25 Jun '14, 11:33
Unlikely, but I don't suppose SQL Remote is involved? The FILE and FTP SQL Remote message system will create files with these extensions (right after writting a file with the .lnl extension), but I can't imaging how that would cause the database engine to shut down, or why they'd be written to the AppData\Roaming directory, unless that was the current directory of the dbremote executable and you haven't specified a root directory. As I continue to type, I feel like the odds of this being the case are smaller and smaller and I'm wasting my time here.
If this is the case, I can imagine virus/malware software on a machine getting upset about SQL Remote creating files with a .lnk extension, which is exactly why we have the 'invalid_extensions' SQL Remote option for the FILE and FTP messaging system.
answered 27 Jun '14, 11:11