none
Handling SMB2_0_INFO_FILE (SMB2 Procotol ) RRS feed

  • Question

  • In what circumstances should a SMB2_0_INFO_FILE request give the status code STATUS_INVALID_PARAMETER.
    We see on a number occasions that this is the response given, yet section 3.3.5.20.1 make no reference to this status code.
    Monday, April 14, 2008 1:40 PM

Answers

  •  

    Hello Neil,

     

    Thank you for your feedback. This is a valid concern.

     

    We will update our documentation to include this error code.  You will be able to see it in an upcoming documentation release.

     

    Regards,

     

    Jim Reynolds – MSFT

     

    Wednesday, April 16, 2008 7:01 PM
  • Hi Neil, As noted in the previous response, the document has been updated.    We apologize for not including a further clarification.  The recent update to the document includes a revision history entry for 3/14/2008, version 8.0.   Section 3.3.5.20 now includes error codes including STATUS_INVALID_PARAMETER.

     

    Furthermore, an additional clarification is needed explaining what circumstances may result in this error.  An implemented method will return one of these status codes, as determined by the message processing.  

     

    Will Gregg - MSFT

    Wednesday, May 7, 2008 11:01 PM

All replies

  • Hello Neil,

     

    Thank you for contacting Microsoft regarding Windows protocol documentation.   

     

    I’ll be working with you and our Microsoft technical teams to resolve this issue.

     

    I’ll let you know if we need any network trace files.

     

    Regards,

     

    Jim Reynolds – MSFT

     

     

    Tuesday, April 15, 2008 4:08 AM
  •  

    Hello Neil,

     

    Thank you for your feedback. This is a valid concern.

     

    We will update our documentation to include this error code.  You will be able to see it in an upcoming documentation release.

     

    Regards,

     

    Jim Reynolds – MSFT

     

    Wednesday, April 16, 2008 7:01 PM
  • Hi Neil, As noted in the previous response, the document has been updated.    We apologize for not including a further clarification.  The recent update to the document includes a revision history entry for 3/14/2008, version 8.0.   Section 3.3.5.20 now includes error codes including STATUS_INVALID_PARAMETER.

     

    Furthermore, an additional clarification is needed explaining what circumstances may result in this error.  An implemented method will return one of these status codes, as determined by the message processing.  

     

    Will Gregg - MSFT

    Wednesday, May 7, 2008 11:01 PM