<div class="content"><p>The CommitChanges method is received by the server in an
RPC_REQUEST packet. In response, the server commits any in-memory changes that
it accumulates to a persisted store. This behavior essentially writes out the
changes that are made by the client.</p><dl>
<dd>
<div><pre> HRESULT CommitChanges();
</pre></div>
</dd></dl><p>This method has no parameters.</p><p><b>Return Values: </b>The server MUST return zero if
it successfully processes the message that is received from the client. If
processing fails, the server MUST return a nonzero <a href="../ms-dtyp/a9046ed2-bfb2-4d56-a719-2824afce59ac" data-linktype="relative-path">HRESULT</a>
code as defined in <a href="../ms-erref/1bc92ddf-b79e-413c-bbaa-99a5281a6c90" data-linktype="relative-path">[MS-ERREF]</a>.
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.</p><dl>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Return value/code</p>
   </th>
   <th>
   <p>Description</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>
  <p>0X00000000</p>
  <p>NO_ERROR</p>
  </td>
  <td>
  <p>The operation completed successfully.</p>
  </td>
 </tr><tr>
  <td>
  <p>0X00000008</p>
  <p>ERROR_NOT_ENOUGH_MEMORY</p>
  </td>
  <td>
  <p>Not enough memory is available to process this
  command.</p>
  </td>
 </tr><tr>
  <td>
  <p>0X80070013</p>
  <p>ERROR_INVALID_DATA</p>
  </td>
  <td>
  <p>Configuration data or schema on the server are
  malformed or corrupted.</p>
  </td>
 </tr><tr>
  <td>
  <p>0X00000002</p>
  <p>ERROR_PATH_NOT_FOUND</p>
  </td>
  <td>
  <p>The system cannot find the path specified.</p>
  </td>
 </tr><tr>
  <td>
  <p>0X80070002</p>
  <p>ERROR_FILE_NOT_FOUND</p>
  </td>
  <td>
  <p>The system cannot find the file specified.</p>
  </td>
 </tr><tr>
  <td>
  <p>0X80070005</p>
  <p>ERROR_ACCESS_DENIED</p>
  </td>
  <td>
  <p>Access is denied.</p>
  </td>
 </tr></tbody></table>
</dd></dl><p> </p></div>