workflow scanning on 75XX and 57XX Microsoft | Windows Server 2012

[MikeAXD8QA-AA]

This is a rights issue with the share. Check your NTFS right under the security tab. Make sure the user has full control of that share.

[MikeAXD8QA-AA]

There is a know issue with scanning on the SPAR Software Release version 061.121.222.32600 on 75xx. Is there a reason whjy service installed this spar? You might need get service to downgrade the firmware to the public release version.

[Fabio]

can you remove the share and recreate it? see it that resolves the ntts issues?

[JordanAXAUQE-AA]

mohammed_k,

Yes, I have configured both SMB and FTP scanning on such systems. It's very odd that is wont let you modify the file which is causing your issue. Have you tried setting up an FTP server (FileZilla) to see if you can scan successfully with it? With it - you will get better logging information to see if you can pinpoint the error down without putting a network trace on it. When I get into the office on Monday I will search for some tips to see if anything shows up - I will let you know.

Thank you,
Jordan

If someone helped you make sure you give Kudos for their efforts! Don't forget to Select Accept as Solution if the reply resolved your issue as it will be able to help others!

[mohammed_k]

i check the SHARE and NTFS permissions and iam  sure USER is using in the file repository setup and that user has FULL control on both SHARE and NTFS and has admin rights also . 

Dear jorth did you Configure  workflow scanning befour on Windows Server 2012 ?

[JordanAXAUQE-AA]

mohammed_k,

This sounds to me like a permission issue. Double check the SHARE and NTFS permissions and make sure to add the USER you are using in the file repository setup - and that user has FULL control on both SHARE and NTFS. Try that and then get back to us.

Thank you,
Jordan

If someone helped you make sure you give Kudos for their efforts! Don't forget to Select Accept as Solution if the reply resolved your issue as it will be able to help others!

[mohammed_k]

In my case the system can create the file lock on the system, but from there all fails.  The event log shows that successful login and access by the approved account, but other than the lock folder and file creation nothing.  The system is preventing the lock from being manipulated to create the PDF and then delete the lock.  The problem is definitely around security on the new system as it applies to remote file manipulation from a non-Microsoft system.

[mohammed_k]

i did't think its rights issue Because i try also by local admin user and domain admin user  . 

[Fabio]

that seems to be an ntfs issue maybe? maybe you are using a user with no delete/remove rights?

[mohammed_k]

i  try all of this and its not pass

also i see in the  confirmation report 

{Remote directory lock failed .}. 
in both smb port 
445 and 139