[cifs-protocol] [REG:113102210883291] - [MS-SMB2] 3.3.5.22.1 NT_STATUS_REQUEST_NOT_ACCEPTED?

[Edgar Olougouna]

The last Create is transitioning the oplock state to BREAK_TO_TWO_TO_NONE while the previous oplock BREAK_TO_TWO is still unacknowledged.
This explains why the ack to Level2 returned the error.
>From server implementation perspective, you can either explicitly ack straight to None (FSCTL_OPLOCK_BREAK_ACK_NO_2) or ack and end up with either Level2 or None, depending on the state of the oplock when your ack shows up (FSCTL_OPLOCK_BREAK_ACKNOWLEDGE).

Let's me know whether this helps.

FSCTL_OPLOCK_BREAK_ACK_NO_2
http://msdn.microsoft.com/en-us/library/windows/desktop/aa364580(v=vs.85).aspx

FSCTL_OPLOCK_BREAK_ACKNOWLEDGE
http://msdn.microsoft.com/en-us/library/windows/desktop/aa364579(v=vs.85).aspx

Thanks,
Edgar

-----Original Message-----
From: Volker Lendecke [mailto:Volker.Lendecke at SerNet.DE] 
Sent: Thursday, November 7, 2013 8:08 AM
To: Edgar Olougouna
Cc: 'cifs-protocol at samba.org'; MSSolve Case Email
Subject: Re: [REG:113102210883291] - [cifs-protocol] [MS-SMB2] 3.3.5.22.1 NT_STATUS_REQUEST_NOT_ACCEPTED?

On Wed, Nov 06, 2013 at 04:45:33PM +0000, Edgar Olougouna wrote:
> Volker,
> It appears that the previous ETW were not decodable. The files might 
> have been corrupted when emailing or before.
> Can you please recollect the ETW and network trace and upload to the 
> workspace I have created for this case. If it's possible, please run 
> the t.cmd in a new folder.
> From an elevated command prompt:
> t.cmd srvon
> Start network capture
> Reproduce the issue
> t.cmd srvoff
> Stop network capture
> 
> Upload the t.cab and network trace to the workspace.
> I will be sending you the workspace information in a separate email.

Done. t.cab and trace.cap should be uploaded.

Thanks,

Volker

--
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kontakt at sernet.de