none
TC2.4.1 WRP stop codes RRS feed

  • Question

  • Could you advise what does WRP Stop Codes mean? Here is the paragraph from the TestFramework doc TC2.4.1:

    ===================

    Examine the logs from AppVerifier. Examine all LayerName=”LuaPriv”, and Severity=”Error”. Any Errors or Warnings should be examined. Specifically regarding Windows Resource Protection, examine logs for these Stop Codes: 331B, 331C, 3323, 3322, 3324.

     

    Thursday, November 1, 2007 9:29 AM

Answers

  •  

    Please note that any Error could potentially be a Failure, but does not automatically Fail the application from becoming Certified. All Errors need to be investigated and documented.

     

    331B: The application opened an object (such as a file or registry key) and requested access permissions that were granted solely to trusted users. This indicates that untrusted users will have difficulty running the application correctly.

     

    331C: The application opened an object (such as a file or registry key) and requested access permissions that were granted solely to trusted users. This indicates that untrusted users will have difficulty running the application correctly. This message will always be followed by other messages.

     

    3322: The application requested MAXIMUM_ALLOWED access to an object (such as a file or registry key). Because of this, the open function will always succeed, even if no permission is actually granted to the user. This is unacceptable programming practice. In addition, the Verifier cannot authoritatively determine what rights the application actually needs in order to operate. The Verifier has attempted to analyze the application as if all access privileges granted were actually required, which may cause false-positives.

     

    3323: The application requested MAXIMUM_ALLOWED access to an object (such as a file or registry key). Because of this, the open function will always succeed, even if no permission is actually granted to the user. This is unacceptable programming practice. In addition, the Verifier cannot authoritatively determine what rights the application actually needs in order to operate. The Verifier has attempted to determine what rights might have been granted to the application by the object, but failed to do so.

     

    3324: The application requested permissions that are unknown to the Verifier. Lacking context, the Predictor cannot currently diagnose problems relating to these access bits.

     

    These Error Codes can be examined more closely within the Application Verifier Help file, and by right clicking the appropriate Verifier check.

     

    Hope this helps,

     

    Thursday, November 1, 2007 11:24 PM

All replies

  •  

    Please note that any Error could potentially be a Failure, but does not automatically Fail the application from becoming Certified. All Errors need to be investigated and documented.

     

    331B: The application opened an object (such as a file or registry key) and requested access permissions that were granted solely to trusted users. This indicates that untrusted users will have difficulty running the application correctly.

     

    331C: The application opened an object (such as a file or registry key) and requested access permissions that were granted solely to trusted users. This indicates that untrusted users will have difficulty running the application correctly. This message will always be followed by other messages.

     

    3322: The application requested MAXIMUM_ALLOWED access to an object (such as a file or registry key). Because of this, the open function will always succeed, even if no permission is actually granted to the user. This is unacceptable programming practice. In addition, the Verifier cannot authoritatively determine what rights the application actually needs in order to operate. The Verifier has attempted to analyze the application as if all access privileges granted were actually required, which may cause false-positives.

     

    3323: The application requested MAXIMUM_ALLOWED access to an object (such as a file or registry key). Because of this, the open function will always succeed, even if no permission is actually granted to the user. This is unacceptable programming practice. In addition, the Verifier cannot authoritatively determine what rights the application actually needs in order to operate. The Verifier has attempted to determine what rights might have been granted to the application by the object, but failed to do so.

     

    3324: The application requested permissions that are unknown to the Verifier. Lacking context, the Predictor cannot currently diagnose problems relating to these access bits.

     

    These Error Codes can be examined more closely within the Application Verifier Help file, and by right clicking the appropriate Verifier check.

     

    Hope this helps,

     

    Thursday, November 1, 2007 11:24 PM
  • Thank you very much.
    Tuesday, November 6, 2007 11:10 AM