Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

291 lines
8.4 KiB

  1. ; /*
  2. ; Microsoft
  3. ; Copyright (c) 1992-2001 Microsoft Corporation
  4. ;
  5. ; This file contains the message definitions for the Secure Server Roles project.
  6. ; The content of the file is modified from the msgtable sample.
  7. ;-------------------------------------------------------------------------
  8. ; HEADER SECTION
  9. ;
  10. ; The header section defines names and language identifiers for use
  11. ; by the message definitions later in this file. The MessageIdTypedef,
  12. ; SeverityNames, FacilityNames, and LanguageNames keywords are
  13. ; optional and not required.
  14. ;
  15. ;
  16. MessageIdTypedef=HRESULT
  17. ;
  18. ; The MessageIdTypedef keyword gives a typedef name that is used in a
  19. ; type cast for each message code in the generated include file. Each
  20. ; message code appears in the include file with the format: #define
  21. ; name ((type) 0xnnnnnnnn) The default value for type is empty, and no
  22. ; type cast is generated. It is the programmer's responsibility to
  23. ; specify a typedef statement in the application source code to define
  24. ; the type. The type used in the typedef must be large enough to
  25. ; accomodate the entire 32-bit message code.
  26. ;
  27. ;
  28. SeverityNames=(Success=0x0:STATUS_SEVERITY_SUCCESS
  29. Informational=0x1:STATUS_SEVERITY_INFORMATIONAL
  30. Warning=0x2:STATUS_SEVERITY_WARNING
  31. Error=0x3:STATUS_SEVERITY_ERROR
  32. )
  33. ;
  34. ; The SeverityNames keyword defines the set of names that are allowed
  35. ; as the value of the Severity keyword in the message definition. The
  36. ; set is delimited by left and right parentheses. Associated with each
  37. ; severity name is a number that, when shifted left by 30, gives the
  38. ; bit pattern to logical-OR with the Facility value and MessageId
  39. ; value to form the full 32-bit message code. The default value of
  40. ; this keyword is:
  41. ;
  42. ; SeverityNames=(
  43. ; Success=0x0
  44. ; Informational=0x1
  45. ; Warning=0x2
  46. ; Error=0x3
  47. ; )
  48. ;
  49. ; Severity values occupy the high two bits of a 32-bit message code.
  50. ; Any severity value that does not fit in two bits is an error. The
  51. ; severity codes can be given symbolic names by following each value
  52. ; with :name
  53. ;
  54. ;
  55. FacilityNames=(System=0x0:FACILITY_SYSTEM
  56. Runtime=0x2:FACILITY_RUNTIME
  57. Stubs=0x3:FACILITY_STUBS
  58. Io=0x4:FACILITY_IO_ERROR_CODE
  59. )
  60. ;
  61. ; The FacilityNames keyword defines the set of names that are allowed
  62. ; as the value of the Facility keyword in the message definition. The
  63. ; set is delimited by left and right parentheses. Associated with each
  64. ; facility name is a number that, when shift it left by 16 bits, gives
  65. ; the bit pattern to logical-OR with the Severity value and MessageId
  66. ; value to form the full 32-bit message code. The default value of
  67. ; this keyword is:
  68. ;
  69. ; FacilityNames=(
  70. ; System=0x0FF
  71. ; Application=0xFFF
  72. ; )
  73. ;
  74. ; Facility codes occupy the low order 12 bits of the high order
  75. ; 16-bits of a 32-bit message code. Any facility code that does not
  76. ; fit in 12 bits is an error. This allows for 4,096 facility codes.
  77. ; The first 256 codes are reserved for use by the system software. The
  78. ; facility codes can be given symbolic names by following each value
  79. ; with :name
  80. ;
  81. ;
  82. ; The LanguageNames keyword defines the set of names that are allowed
  83. ; as the value of the Language keyword in the message definition. The
  84. ; set is delimited by left and right parentheses. Associated with each
  85. ; language name is a number and a file name that are used to name the
  86. ; generated resource file that contains the messages for that
  87. ; language. The number corresponds to the language identifier to use
  88. ; in the resource table. The number is separated from the file name
  89. ; with a colon.
  90. ;
  91. LanguageNames=(English=0x409:MSG00409)
  92. ;
  93. ; Any new names in the source file which don't override the built-in
  94. ; names are added to the list of valid languages. This allows an
  95. ; application to support private languages with descriptive names.
  96. ;
  97. ;
  98. ;-------------------------------------------------------------------------
  99. ; MESSAGE DEFINITION SECTION
  100. ;
  101. ; Following the header section is the body of the Message Compiler
  102. ; source file. The body consists of zero or more message definitions.
  103. ; Each message definition begins with one or more of the following
  104. ; statements:
  105. ;
  106. ; MessageId = [number|+number]
  107. ; Severity = severity_name
  108. ; Facility = facility_name
  109. ; SymbolicName = name
  110. ;
  111. ; The MessageId statement marks the beginning of the message
  112. ; definition. A MessageID statement is required for each message,
  113. ; although the value is optional. If no value is specified, the value
  114. ; used is the previous value for the facility plus one. If the value
  115. ; is specified as +number then the value used is the previous value
  116. ; for the facility, plus the number after the plus sign. Otherwise, if
  117. ; a numeric value is given, that value is used. Any MessageId value
  118. ; that does not fit in 16 bits is an error.
  119. ;
  120. ; The Severity and Facility statements are optional. These statements
  121. ; specify additional bits to OR into the final 32-bit message code. If
  122. ; not specified they default to the value last specified for a message
  123. ; definition. The initial values prior to processing the first message
  124. ; definition are:
  125. ;
  126. ; Severity=Success
  127. ; Facility=Application
  128. ;
  129. ; The value associated with Severity and Facility must match one of
  130. ; the names given in the FacilityNames and SeverityNames statements in
  131. ; the header section. The SymbolicName statement allows you to
  132. ; associate a C/C++ symbolic constant with the final 32-bit message
  133. ; code.
  134. ; */
  135. MessageId=0x01
  136. Severity=Warning
  137. Facility=Runtime
  138. SymbolicName=W_SSR_PROPERTY_NOT_FOUND
  139. Language=English
  140. The property does not exist.
  141. .
  142. MessageId=0x02
  143. Severity=Error
  144. Facility=Runtime
  145. SymbolicName=E_SSR_MEMBER_NOT_FOUND
  146. Language=English
  147. The SSR member does not exist.
  148. .
  149. MessageId=0x0D
  150. Severity=Error
  151. Facility=Runtime
  152. SymbolicName=E_SSR_INVALID_ACTION_TYPE
  153. Language=English
  154. The action type is invalid.
  155. .
  156. MessageId=0x0E
  157. Severity=Error
  158. Facility=Runtime
  159. SymbolicName=E_SSR_INVALID_ACTION_VERB
  160. Language=English
  161. The action verb is invalid.
  162. .
  163. MessageId=0x0F
  164. Severity=Error
  165. Facility=Runtime
  166. SymbolicName=E_SSR_INVALID_XML_FILE
  167. Language=English
  168. The XML is invalid according to the schema.
  169. .
  170. MessageId=0x10
  171. Severity=Error
  172. Facility=Runtime
  173. SymbolicName=E_SSR_MISSING_INT_ATTRIBUTE
  174. Language=English
  175. The member's XML registration is missing integer attribute(s).
  176. .
  177. MessageId=0x11
  178. Severity=Error
  179. Facility=Runtime
  180. SymbolicName=E_SSR_MISSING_STRING_ATTRIBUTE
  181. Language=English
  182. The member's XML registration is missing string attribute(s).
  183. .
  184. MessageId=0x12
  185. Severity=Error
  186. Facility=Runtime
  187. SymbolicName=E_SSR_MAJOR_VERSION_MISMATCH
  188. Language=English
  189. The member's major version mis-matches SSR engine dll's major version.
  190. .
  191. MessageId=0x13
  192. Severity=Error
  193. Facility=Runtime
  194. SymbolicName=E_SSR_MEMBER_INVALID_REGISTRATION
  195. Language=English
  196. The member's registration XML is invalid.
  197. .
  198. MessageId=0x16
  199. Severity=Error
  200. Facility=Runtime
  201. SymbolicName=E_SSR_MEMBER_XSD_INVALID
  202. Language=English
  203. SsrMember.xsd file is not a valid schema.
  204. .
  205. MessageId=0x17
  206. Severity=Error
  207. Facility=Runtime
  208. SymbolicName=E_SSR_LOG_FILE_MUTEX_WAIT
  209. Language=English
  210. Waiting for the log file's mutex encounters errors.
  211. .
  212. MessageId=0x18
  213. Severity=Error
  214. Facility=Runtime
  215. SymbolicName=E_SSR_EXPAND_ENVIRONMENT_STRING
  216. Language=English
  217. Failed to expand the environment string.
  218. .
  219. MessageId=0x20
  220. Severity=Error
  221. Facility=Runtime
  222. SymbolicName=E_SSR_ACTION_DATA_NOT_AVAILABLE
  223. Language=English
  224. The action data object is not available.
  225. .
  226. MessageId=0x21
  227. Severity=Error
  228. Facility=Runtime
  229. SymbolicName=E_SSR_ENGINE_NOT_AVAILABLE
  230. Language=English
  231. SSR Engine is not available.
  232. .
  233. MessageId=0x22
  234. Severity=Error
  235. Facility=Runtime
  236. SymbolicName=E_SSR_ENGINE_NOT_SUPPORT_INTERFACE
  237. Language=English
  238. SSR Engine does not support the ISsrEngine interface.
  239. .
  240. MessageId=0x23
  241. Severity=Error
  242. Facility=Runtime
  243. SymbolicName=E_SSR_VARIANT_NOT_CONTAIN_OBJECT
  244. Language=English
  245. The variant does not contain COM objects.
  246. .
  247. MessageId=0x24
  248. Severity=Error
  249. Facility=Runtime
  250. SymbolicName=E_SSR_ARRAY_INDEX_OUT_OF_RANGE
  251. Language=English
  252. The requesting index is out of the range.
  253. .
  254. MessageId=0x25
  255. Severity=Error
  256. Facility=Runtime
  257. SymbolicName=E_SSR_NO_VALID_ELEMENT
  258. Language=English
  259. The variant does not contain valid element.
  260. .
  261. MessageId=0x26
  262. Severity=Warning
  263. Facility=Runtime
  264. SymbolicName=W_SSR_MISSING_FILE
  265. Language=English
  266. Some file(s) are missing.
  267. .