Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in June and this forum will be retired.

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?

Thanks, Doug

asked 25 Jun '14, 10:59

dejstone's gravatar image

accept rate: 0%


.lnk files are generally shortcuts. I have never known any running SQL Anywhere engine to ever create a shortcut anywhere.

Why do you suspect that this event log entry has anything to do with SQL Anywhere?

A google search indicates "Blocked by access protection rule" comes from McAfee.

(25 Jun '14, 11:18) Breck Carter

Breck, I guess I suspected sqla because the sqla engine stopped and the event log mentioned blocked access due to a protection rule. I will ask the customer to turn off McAfee for a trial period to see if sqla stays up and running. Thanks!

(25 Jun '14, 11:35) dejstone
Comment Text Removed

off topic: can't configure McAfee to check a directory or file/ file type like Symantec's end point protection and others?

I prefer not to totally turn off any malware protection whenever possible

(26 Jun '14, 19:53) gg99
Replies hidden

IMO McAfee **is** malware but that's just me talking :)

(27 Jun '14, 08:53) Breck Carter

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?

permanent link

answered 25 Jun '14, 11:33

Mark%20Culp's gravatar image

Mark Culp
accept rate: 41%

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.

permanent link

answered 27 Jun '14, 11:11

Reg%20Domaratzki's gravatar image

Reg Domaratzki
accept rate: 36%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 25 Jun '14, 10:59

question was seen: 6,619 times

last updated: 27 Jun '14, 11:11