[MS-ASCMD]: ActiveSync Command Reference Protocol Specification
[MS-ASCMD]: ActiveSync Command Reference Protocol Specification
[MS-ASCMD]: ActiveSync Command Reference Protocol Specification
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Command</strong><br />
request/response<br />
Parent elements<br />
Child<br />
elements<br />
Data type<br />
Number<br />
allowed<br />
FolderCreate command<br />
response (section<br />
2.2.2.2.2)<br />
FolderCreate<br />
(section 2.2.3.63)<br />
None<br />
unsignedByte ([<strong>MS</strong>-<br />
ASDTYPE] section<br />
2.7)<br />
1…1<br />
(required)<br />
The following table lists the status codes for the FolderCreate command (section 2.2.2.2). For<br />
information about the scope of the status value and for status values common to all <strong>ActiveSync</strong><br />
commands, see section 2.2.4.<br />
Value Meaning Cause Scope Resolution<br />
1 Success. Server successfully completed<br />
command.<br />
Global<br />
None.<br />
2 A folder that has<br />
this name already<br />
exists.<br />
The parent folder already<br />
contains a folder that has this<br />
name.<br />
Item<br />
Prompt user to supply a<br />
unique name.<br />
3 The specified folder<br />
is a special system<br />
folder.<br />
The specified folder is a special<br />
system folder, like the Inbox<br />
folder, Outbox folder, Contacts<br />
folder, Recipient information, or<br />
Drafts folder, and cannot be<br />
created by the client.<br />
Item<br />
Create a folder with a<br />
different type.<br />
5 The specified parent<br />
folder was not<br />
found.<br />
The parent folder does not exist<br />
on the server, possibly because<br />
it has been deleted or renamed.<br />
Item<br />
Issue a FolderSync<br />
command (section<br />
2.2.2.4) for the new<br />
hierarchy and prompt the<br />
user for a new parent<br />
folder.<br />
6 An error occurred<br />
on the server.<br />
Server misconfiguration,<br />
temporary system issue, or bad<br />
item. This is frequently a<br />
transient condition.<br />
Global<br />
Retry the FolderSync<br />
command. If continued<br />
attempts to<br />
synchronization fail,<br />
consider returning to<br />
synchronization key zero<br />
(0).<br />
8 The request timed<br />
out.<br />
The server took too long to<br />
respond to the request.<br />
Global<br />
Retry the FolderSync<br />
command.<br />
9 Synchronization key<br />
mismatch or invalid<br />
synchronization<br />
key.<br />
The client sent a malformed or<br />
mismatched synchronization<br />
key, or the synchronization state<br />
is corrupted on the server.<br />
Global<br />
Delete folders added since<br />
last synchronization and<br />
return to synchronization<br />
key to zero (0).<br />
10 Malformed request. The client sent a FolderCreate<br />
command request (section<br />
2.2.2.2.1) that contains a<br />
semantic error.<br />
Global<br />
Double-check the request<br />
for accuracy.<br />
11 An unknown error<br />
occurred.<br />
Unknown. Global. None.<br />
12 Code unknown. Unusual back-end issue. Global None.<br />
220 / 369<br />
[<strong>MS</strong>-<strong>ASCMD</strong>] — v20110315<br />
<strong>ActiveSync</strong> <strong>Command</strong> <strong>Reference</strong> <strong>Protocol</strong> <strong>Specification</strong><br />
Copyright © 2011 Microsoft Corporation.<br />
Release: Tuesday, March 15, 2011