• Todas as comunidades
    • Todas as comunidades
    • Fóruns
    • Idéias
    • Blogs
Avançado

O que você está procurando? Pergunte a um especialista!

This forum thread needs a solution.
Kudos0

SYMEFA.DB causes sharing violation on handle.

Hello,

I was double checking our ReFS support for backup and find Norton is interfering.   Basically, We can lock the volume and force the handle off the volume.  But we need to use some FSCTL_ calls that won't work on a dismounted / locked volume.  So typically we open the volume with sharing mode 0, that fails now due to SYMEFA.DB.  We we willing to move to FILE_SHARE_READ since volume will still be protected from changing, but that didn't work either, still sharing violation.  Using both FILE_SHARE_READ|FILE_SHARE_WRITE works, but we can't chance volume changes.  I have a couple other ideas I'm going to try to fudge around it, not sure if it will work.  But be helpful if you guys wouldn't open handles on the volume that aren't needed, or at least read-only mode until you need to write, or maybe delay opening so if we lock / unlock open quickly, we can get the handle before you take it.

Any ideas?

Thanks.

Respostas

Kudos0

Re: SYMEFA.DB causes sharing violation on handle.

Hello DFATNC. Are you using a Symantec Endpoint product or Norton product? Are you in a production environment, small business? There is a Symantec article here about the issue. If you are using SEP head on over to the Symantec support, they can assist you better with that product.

Cheers

"From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows Server 2016 Essentials / Windows 10 Professional x 64 version 1909 / build 18363.657 / N360 Deluxe 22.20.1.69/ Norton Core v.288 on Android 2.22 / Opera GX
Kudos0

Re: SYMEFA.DB causes sharing violation on handle.

it's Norton 360.

Kudos0

Re: SYMEFA.DB causes sharing violation on handle.

Do you have the network drive protection setting set to off or on? I'm thinking the setting being set to OFF MAY have some effect. 

Cheers

"From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows Server 2016 Essentials / Windows 10 Professional x 64 version 1909 / build 18363.657 / N360 Deluxe 22.20.1.69/ Norton Core v.288 on Android 2.22 / Opera GX
Kudos0

Re: SYMEFA.DB causes sharing violation on handle.

The network drive protection is on.

This issue was with a ReFS on USB drive.

Kudos0

Re: SYMEFA.DB causes sharing violation on handle.

I don't believe Norton is compatible with ReFS file system technology, allow me to bump this up to the team and get an answer on that question for you. I believe that is the cause of the sharing violation errors being thrown.

Cheers

"From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows Server 2016 Essentials / Windows 10 Professional x 64 version 1909 / build 18363.657 / N360 Deluxe 22.20.1.69/ Norton Core v.288 on Android 2.22 / Opera GX
Kudos0

Re: SYMEFA.DB causes sharing violation on handle.

May I ask what is the OS on the machine you are using?

"From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows Server 2016 Essentials / Windows 10 Professional x 64 version 1909 / build 18363.657 / N360 Deluxe 22.20.1.69/ Norton Core v.288 on Android 2.22 / Opera GX
Kudos0

Re: SYMEFA.DB causes sharing violation on handle.

@DFATNC Have you tried disabling "Tamper Protection" within your Norton product? 

"From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows Server 2016 Essentials / Windows 10 Professional x 64 version 1909 / build 18363.657 / N360 Deluxe 22.20.1.69/ Norton Core v.288 on Android 2.22 / Opera GX