Source code of Windows XP (NT5)
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.

397 lines
9.1 KiB

  1. /*++
  2. Copyright (C) 1996-1999 Microsoft Corporation
  3. Module Name:
  4. logmmsg
  5. Abstract:
  6. Performance Log Manager messages
  7. --*/
  8. //
  9. // This file is automatically generated from logmmsg.mc
  10. //
  11. #ifndef _LOGMMSG_H_
  12. #define _LOGMMSG_H_
  13. //
  14. // Messages
  15. //
  16. //
  17. // Values are 32 bit values layed out as follows:
  18. //
  19. // 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1
  20. // 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
  21. // +---+-+-+-----------------------+-------------------------------+
  22. // |Sev|C|R| Facility | Code |
  23. // +---+-+-+-----------------------+-------------------------------+
  24. //
  25. // where
  26. //
  27. // Sev - is the severity code
  28. //
  29. // 00 - Success
  30. // 01 - Informational
  31. // 10 - Warning
  32. // 11 - Error
  33. //
  34. // C - is the Customer code flag
  35. //
  36. // R - is a reserved bit
  37. //
  38. // Facility - is the facility code
  39. //
  40. // Code - is the facility's status code
  41. //
  42. //
  43. // Define the facility codes
  44. //
  45. //
  46. // Define the severity codes
  47. //
  48. #define STATUS_SEVERITY_WARNING 0x2
  49. #define STATUS_SEVERITY_SUCCESS 0x0
  50. #define STATUS_SEVERITY_INFORMATIONAL 0x1
  51. #define STATUS_SEVERITY_ERROR 0x3
  52. //
  53. // MessageId: LOGMAN_INVALID_COMPUTER
  54. //
  55. // MessageText:
  56. //
  57. // The /COMPUTER_NAME command qualifier has been included but the
  58. // computer name is either incorrect or has not been specified.
  59. //
  60. #define LOGMAN_INVALID_COMPUTER ((DWORD)0xC0001770L)
  61. //
  62. // MessageId: LOGMAN_INVALID_STARTNAME
  63. //
  64. // MessageText:
  65. //
  66. // The /START command qualifier has been included but the
  67. // log or alert name is either incorrect or has not been specified.
  68. //
  69. #define LOGMAN_INVALID_STARTNAME ((DWORD)0xC0001771L)
  70. //
  71. // MessageId: LOGMAN_INVALID_STOPNAME
  72. //
  73. // MessageText:
  74. //
  75. // The /STOP command qualifier has been included but the
  76. // log or alert name is either incorrect or has not been specified.
  77. //
  78. #define LOGMAN_INVALID_STOPNAME ((DWORD)0xC0001772L)
  79. //
  80. // MessageId: LOGMAN_INVALID_SETTINGS
  81. //
  82. // MessageText:
  83. //
  84. // The /SETTINGS command qualifier has been included but the file name is either
  85. // incorrect or has not been specified. The file name must specify the path of
  86. // an existing HTML log or alert configuration file.
  87. //
  88. #define LOGMAN_INVALID_SETTINGS ((DWORD)0xC0001773L)
  89. //
  90. // MessageId: LOGMAN_INVALID_COMMAND
  91. //
  92. // MessageText:
  93. //
  94. // Specify one of the following command qualifiers: /SETTINGS, /START or /STOP.
  95. //
  96. #define LOGMAN_INVALID_COMMAND ((DWORD)0xC0001774L)
  97. //
  98. // MessageId: LOGMAN_SETTINGS_FILE_NOT_OPEN
  99. //
  100. // MessageText:
  101. //
  102. // Unable to open /SETTINGS configuration file '%1'.
  103. //
  104. #define LOGMAN_SETTINGS_FILE_NOT_OPEN ((DWORD)0xC0001775L)
  105. //
  106. // MessageId: LOGMAN_NO_SYSMON_OBJECT
  107. //
  108. // MessageText:
  109. //
  110. // The settings do not contain any complete System Monitor Html objects.
  111. //
  112. #define LOGMAN_NO_SYSMON_OBJECT ((DWORD)0xC0001776L)
  113. //
  114. // MessageId: LOGMAN_DUP_QUERY_NAME
  115. //
  116. // MessageText:
  117. //
  118. // A log or alert with name '%1' already exists, and will not be overwritten.
  119. //
  120. #define LOGMAN_DUP_QUERY_NAME ((DWORD)0x80001777L)
  121. //
  122. // MessageId: LOGMAN_OVERWRITE_DUP_QUERY
  123. //
  124. // MessageText:
  125. //
  126. // A log or alert with name '%1' already exists. Its properties will be overwritten by the new configuration.
  127. //
  128. #define LOGMAN_OVERWRITE_DUP_QUERY ((DWORD)0x80001778L)
  129. //
  130. // MessageId: LOGMAN_PROCESSING_COMPLETE
  131. //
  132. // MessageText:
  133. //
  134. // The following logs and alerts have been configured on computer %1:
  135. //
  136. #define LOGMAN_PROCESSING_COMPLETE ((DWORD)0x40001779L)
  137. //
  138. // MessageId: LOGMAN_NO_COMPUTER_CONNECT
  139. //
  140. // MessageText:
  141. //
  142. // Unable to connect to registry on %1.
  143. //
  144. #define LOGMAN_NO_COMPUTER_CONNECT ((DWORD)0xC000177AL)
  145. //
  146. // MessageId: LOGMAN_SETTINGS_FILE_NOT_LOADED
  147. //
  148. // MessageText:
  149. //
  150. // Unable to load /SETTINGS configuration file '%1' into memory.
  151. //
  152. #define LOGMAN_SETTINGS_FILE_NOT_LOADED ((DWORD)0xC000177BL)
  153. //
  154. // MessageId: LOGMAN_NO_OBJECT_LOGTYPE
  155. //
  156. // MessageText:
  157. //
  158. // Unable to load the LogType property for the current log or alert. This log or alert
  159. // will not be configured.
  160. //
  161. #define LOGMAN_NO_OBJECT_LOGTYPE ((DWORD)0x8000177CL)
  162. //
  163. // MessageId: LOGMAN_NO_OBJECT_NAME
  164. //
  165. // MessageText:
  166. //
  167. // Unable to load the Name property for the current log or alert. This log or alert
  168. // will not be configured.
  169. //
  170. #define LOGMAN_NO_OBJECT_NAME ((DWORD)0x8000177DL)
  171. //
  172. // MessageId: LOGMAN_QUERY_CONFIG_SUCCESS
  173. //
  174. // MessageText:
  175. //
  176. // Configured the %1 log or alert.
  177. //
  178. #define LOGMAN_QUERY_CONFIG_SUCCESS ((DWORD)0x4000177EL)
  179. //
  180. // MessageId: LOGMAN_START_TIMED_OUT
  181. //
  182. // MessageText:
  183. //
  184. // The start action was executed for %1.
  185. // Unable to detect the current status within the timeout period.
  186. // See the application event log on the target computer for any status
  187. // or error events, or use Performance to determine status.
  188. //
  189. #define LOGMAN_START_TIMED_OUT ((DWORD)0xC000177FL)
  190. //
  191. // MessageId: LOGMAN_STOP_TIMED_OUT
  192. //
  193. // MessageText:
  194. //
  195. // The stop action was executed for %1. Unable to detect
  196. // the current status within the timeout period. See the application event log
  197. // on the target computer for any error events, or use Performance
  198. // to determine status.
  199. //
  200. #define LOGMAN_STOP_TIMED_OUT ((DWORD)0xC0001780L)
  201. //
  202. // MessageId: LOGMAN_NO_QUERY_CONNECT
  203. //
  204. // MessageText:
  205. //
  206. // The %1 log or alert does not exist on the target computer.
  207. //
  208. #define LOGMAN_NO_QUERY_CONNECT ((DWORD)0xC0001781L)
  209. //
  210. // MessageId: LOGMAN_INVALID_TOKEN
  211. //
  212. // MessageText:
  213. //
  214. // Parameter value invalid or not found.
  215. //
  216. #define LOGMAN_INVALID_TOKEN ((DWORD)0xC0001782L)
  217. //
  218. // MessageId: LOGMAN_START_FAILED
  219. //
  220. // MessageText:
  221. //
  222. // Unable to start the %1 log or alert on target computer.
  223. //
  224. #define LOGMAN_START_FAILED ((DWORD)0xC0001783L)
  225. //
  226. // MessageId: LOGMAN_STOP_FAILED
  227. //
  228. // MessageText:
  229. //
  230. // Unable to stop the %1 log or alert on target computer.
  231. //
  232. #define LOGMAN_STOP_FAILED ((DWORD)0xC0001784L)
  233. //
  234. // MessageId: LOGMAN_REQUIRED_PROP_MISSING
  235. //
  236. // MessageText:
  237. //
  238. // Required property '%1' is missing for the %2 log or alert.
  239. //
  240. #define LOGMAN_REQUIRED_PROP_MISSING ((DWORD)0x80001785L)
  241. //
  242. // MessageId: LOGMAN_REQUIRED_PROP_INVALID
  243. //
  244. // MessageText:
  245. //
  246. // Required property '%1' is invalid for the %2 log or alert.
  247. //
  248. #define LOGMAN_REQUIRED_PROP_INVALID ((DWORD)0x80001786L)
  249. //
  250. // MessageId: LOGMAN_NONREQ_PROP_MISSING
  251. //
  252. // MessageText:
  253. //
  254. // Property '%1' is missing for the %2 log or alert and will be set to the default value.
  255. //
  256. #define LOGMAN_NONREQ_PROP_MISSING ((DWORD)0x40001787L)
  257. //
  258. // MessageId: LOGMAN_NONREQ_PROP_INVALID
  259. //
  260. // MessageText:
  261. //
  262. // Property '%1' is invalid for the %2 log or alert and will be set to the default value.
  263. //
  264. #define LOGMAN_NONREQ_PROP_INVALID ((DWORD)0x80001788L)
  265. //
  266. // MessageId: LOGMAN_OUT_OF_RANGE
  267. //
  268. // MessageText:
  269. //
  270. // The value %1 for property %2 in the %3 log or alert is invalid and will be set to its default value.
  271. // The valid range is %4 to %5.
  272. //
  273. #define LOGMAN_OUT_OF_RANGE ((DWORD)0x40001789L)
  274. //
  275. // MessageId: LOGMAN_REG_ACCESS_DENIED
  276. //
  277. // MessageText:
  278. //
  279. // Unable to complete the current operation on the target system. You must have read
  280. // and write access to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysmonLog\Log Queries
  281. // registry subkey and its subkeys on that system.
  282. //
  283. #define LOGMAN_REG_ACCESS_DENIED ((DWORD)0x4000178AL)
  284. //
  285. // MessageId: LOGMAN_INSTALL_ACCESS_DENIED
  286. //
  287. // MessageText:
  288. //
  289. // Unable to install the Performance Logs and Alerts configuration on the target system. You must have read
  290. // and write access to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysmonLog
  291. // registry subkey and its subkeys on that system.
  292. //
  293. #define LOGMAN_INSTALL_ACCESS_DENIED ((DWORD)0x4000178BL)
  294. //
  295. // MessageId: LOGMAN_INSTALL_FAILURE
  296. //
  297. // MessageText:
  298. //
  299. // Unable to install the Performance Logs and Alerts configuration on the target system.
  300. //
  301. #define LOGMAN_INSTALL_FAILURE ((DWORD)0x4000178CL)
  302. //
  303. // MessageId: LOGMAN_QUERY_START_SUCCESS
  304. //
  305. // MessageText:
  306. //
  307. // Started the %1 log or alert.
  308. //
  309. #define LOGMAN_QUERY_START_SUCCESS ((DWORD)0x4000178DL)
  310. //
  311. // MessageId: LOGMAN_QUERY_STOP_SUCCESS
  312. //
  313. // MessageText:
  314. //
  315. // Stopped the %1 log or alert.
  316. //
  317. #define LOGMAN_QUERY_STOP_SUCCESS ((DWORD)0x4000178EL)
  318. //
  319. // MessageId: LOGMAN_INVALID_PARAM
  320. //
  321. // MessageText:
  322. //
  323. // Invalid command qualifier "%1".
  324. //
  325. #define LOGMAN_INVALID_PARAM ((DWORD)0xC000178FL)
  326. //
  327. // MessageId: LOGMAN_INVALID_QUERY_NAME
  328. //
  329. // MessageText:
  330. //
  331. // Invalid log or alert name "%1".
  332. // A log or alert name cannot contain any of the following characters:\ / : * ? " < > | .
  333. //
  334. #define LOGMAN_INVALID_QUERY_NAME ((DWORD)0x80001790L)
  335. //
  336. // MessageId: LOGMAN_TOO_MANY_COMMANDS
  337. //
  338. // MessageText:
  339. //
  340. // Specify only one of the following qualifiers: /SETTINGS, /START or /STOP.
  341. //
  342. #define LOGMAN_TOO_MANY_COMMANDS ((DWORD)0xC0001791L)
  343. //
  344. // MessageId: LOGMAN_DISPLAY_HELP
  345. //
  346. // MessageText:
  347. //
  348. // No message. Display the help file.
  349. //
  350. #define LOGMAN_DISPLAY_HELP ((DWORD)0xC0001792L)
  351. #endif //_LOGMMSG_H_
  352. // end of generated file