3.1.4.21.1 MapPath (Opnum 3)

The MapPath method is called by the server in an RPC_REQUEST packet. In response, the client implementation receives the details of the specific mapping decision and optionally, can change the results by using its return.

 HRESULT MapPath(
   [in] BSTR bstrConfigPath,
   [in] BSTR bstrMappedPhysicalPath,
   [out, retval] BSTR* pbstrNewPhysicalPath
 );

bstrConfigPath: The hierarchy path being mapped.

bstrMappedPhysicalPath: The server side physical path that the administration system has determined maps to the specified hierarchy path.

pbstrNewPhysicalPath:  Set to the new or updated physical path to use for the mapping. If the mapping stays the same, the client implementer returns the identical physical path that was passed in as bstrMappedPhysicalPath.

Return Values: The client MUST return zero if it successfully processes the message that is received from the client. If processing fails, the server MUST return a nonzero HRESULT code as defined in [MS-ERREF]. The following table describes the error conditions that MUST be handled and the corresponding error codes. A server MAY return additional implementation-specific error codes.

Return value/code	Description
0X00000000 NO_ERROR	The operation completed successfully.
0X00000008 ERROR_NOT_ENOUGH_MEMORY	Not enough memory is available to process this command.
0X80070057 ERROR_INVALID_PARAMETER	One or more parameters are incorrect or null.