Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 16593 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

The on-access driver failed to determine the new name for file %2

pfox

Hi all,

We are receiving the following errors on our Windows 2003 R2 file servers (yes we will be upgrading them soon :-). We are using DFSR for file share replication.

Has anyone seen this before? The dfsrprivate folder is excluded from the on-access scanning as I thought this may be the cause.

Application Log Error

Event Type:       Error

Event Source:    Sophos Anti-Virus

Event Category: On-access

Event ID:          17

Date:                19/06/2013

Time:                4:58:31 PM

User:                NT AUTHORITY\LOCAL SERVICE

Computer:         VEGAS

Description:

The on-access driver failed to determine the new name for file %2 following a rename.

System Log Error  

Event Type:       Error

Event Source:    SAVOnAccessControl

Event Category: None

Event ID:          17

Date:                19/06/2013

Time:                5:47:07 PM

User:                N/A

Computer:         VEGAS

Description:

The on-access driver failed to determine the new name for file %2 following a rename.

Data:

0000: 00 00 04 00 01 00 6e 00   ......n.

0008: 00 00 00 00 11 00 3d e0   ......=à

0010: 5e 00 3a 01 83 01 00 c0   ^.:.ƒ..À

0018: 00 00 00 00 00 00 00 00   ........

0020: 00 00 00 00 00 00 00 00   ........

0028: 01 00 00 c0               ...À   

Cheers,

Paul.

:40945


This thread was automatically locked due to age.
Parents
  • 0

    On the affected DFS Storage Server, as a test can you:

    1. Check if Data Control is currently enabled?
    2. Disable Data Control and see if the error still occurs.
      Note:       . This is not a permanent solution if Data Control is required on a DFS server, however Data Control is generally not required on servers in typical usage scenarios.

    If this resolves the problem error you could keep Data Control off for the DFS server(s) by having a new group with a different policy.  Or we can troubleshoot further - we would probably need a memory dump from the computer (open a case with Support for guidance of the type required and steps).

    :41215
Reply
  • 0

    On the affected DFS Storage Server, as a test can you:

    1. Check if Data Control is currently enabled?
    2. Disable Data Control and see if the error still occurs.
      Note:       . This is not a permanent solution if Data Control is required on a DFS server, however Data Control is generally not required on servers in typical usage scenarios.

    If this resolves the problem error you could keep Data Control off for the DFS server(s) by having a new group with a different policy.  Or we can troubleshoot further - we would probably need a memory dump from the computer (open a case with Support for guidance of the type required and steps).

    :41215
Children
No Data