2 ; netevent.mc MESSAGE resources for netevent.dll
7 SeverityNames=(Success=0x0:STATUS_SEVERITY_SUCCESS
8 Informational=0x1:STATUS_SEVERITY_INFORMATIONAL
9 Warning=0x2:STATUS_SEVERITY_WARNING
10 Error=0x3:STATUS_SEVERITY_ERROR
13 FacilityNames=(System=0x0:FACILITY_SYSTEM
16 LanguageNames=(English=0x409:MSG00409)
26 ; eventlog events 6000-6099
32 SymbolicName=EVENT_LOG_FULL
34 The %1 log file is full.
40 SymbolicName=EVENT_LogFileNotOpened
42 The %1 log file cannot be opened.
48 SymbolicName=EVENT_LogFileCorrupt
50 The %1 log file is corrupted and will be cleared.
56 SymbolicName=EVENT_DefaultLogCorrupt
58 The Application log file could not be opened. %1 will be used as the default log file.
64 SymbolicName=EVENT_BadDriverPacket
66 A driver packet received from the I/O subsystem was invalid. The data is the packet.
72 SymbolicName=EVENT_EventlogStarted
74 The Event log service was started.
80 SymbolicName=EVENT_EventlogStopped
82 The Event log service was stopped.
88 SymbolicName=TITLE_EventlogMessageBox
96 SymbolicName=EVENT_EventlogAbnormalShutdown
98 The previous system shutdown at %1 on %2 was unexpected.
104 SymbolicName=EVENT_EventLogProductInfo
112 SymbolicName=EVENT_ServiceNoEventLog
114 The %1 service was unable to set up an event source.
120 SymbolicName=EVENT_ComputerNameChange
122 The NetBIOS name and DNS host name of this machine have been changed from %1 to %2.
128 SymbolicName=EVENT_DNSDomainNameChange
130 The DNS domain assigned to this computer has been changed from %1 to %2.
135 ; system events 6100 - 6199
141 SymbolicName=EVENT_UP_DRIVER_ON_MP
143 A uniprocessor-specific driver was loaded on a multiprocessor system. The driver could not load.
148 ; service controller events 7000-7899
154 SymbolicName=EVENT_SERVICE_START_FAILED
156 The %1 service failed to start due to the following error: %n%2
162 SymbolicName=EVENT_SERVICE_START_FAILED_II
164 The %1 service depends on the %2 service which failed to start because of the following error: %n%3
170 SymbolicName=EVENT_SERVICE_START_FAILED_GROUP
172 The %1 service depends on the %2 group and no member of this group started.
178 SymbolicName=EVENT_SERVICE_START_FAILED_NONE
180 The %1 service depends on the following nonexistent service: %2
186 SymbolicName=EVENT_CALL_TO_FUNCTION_FAILED
188 The %1 call failed with the following error: %n%2
194 SymbolicName=EVENT_CALL_TO_FUNCTION_FAILED_II
196 The %1 call failed for %2 with the following error: %n%3
202 SymbolicName=EVENT_REVERTED_TO_LASTKNOWNGOOD
204 The system reverted to its last known good configuration. The system is restarting....
210 SymbolicName=EVENT_BAD_ACCOUNT_NAME
212 No backslash is in the account name.
218 SymbolicName=EVENT_CONNECTION_TIMEOUT
220 Timeout (%1 milliseconds) waiting for the %2 service to connect.
226 SymbolicName=EVENT_READFILE_TIMEOUT
228 Timeout (%1 milliseconds) waiting for ReadFile.
234 SymbolicName=EVENT_TRANSACT_TIMEOUT
236 Timeout (%1 milliseconds) waiting for a transaction response from the %2 service.
242 SymbolicName=EVENT_TRANSACT_INVALID
244 Message returned in transaction has incorrect size.
250 SymbolicName=EVENT_FIRST_LOGON_FAILED
252 Logon attempt with current password failed with the following error: %n%1
258 SymbolicName=EVENT_SECOND_LOGON_FAILED
260 Second logon attempt with old password also failed with the following error: %n%1
266 SymbolicName=EVENT_INVALID_DRIVER_DEPENDENCY
268 Boot-start or system-start driver (%1) must not depend on a service.
274 SymbolicName=EVENT_BAD_SERVICE_STATE
276 The %1 service has reported an invalid current state %2.
282 SymbolicName=EVENT_CIRCULAR_DEPENDENCY_DEMAND
284 Detected circular dependencies demand starting %1.
290 SymbolicName=EVENT_CIRCULAR_DEPENDENCY_AUTO
292 Detected circular dependencies auto-starting services.
298 SymbolicName=EVENT_DEPEND_ON_LATER_SERVICE
300 Circular dependency: The %1 service depends on a service in a group which starts later.
306 SymbolicName=EVENT_DEPEND_ON_LATER_GROUP
308 Circular dependency: The %1 service depends on a group which starts later.
314 SymbolicName=EVENT_SEVERE_SERVICE_FAILED
316 About to revert to the last known good configuration because the %1 service failed to start.
322 SymbolicName=EVENT_SERVICE_START_HUNG
324 The %1 service hung on starting.
330 SymbolicName=EVENT_SERVICE_EXIT_FAILED
332 The %1 service terminated with the following error: %n%2
338 SymbolicName=EVENT_SERVICE_EXIT_FAILED_SPECIFIC
340 The %1 service terminated with service-specific error %2.
346 SymbolicName=EVENT_SERVICE_START_AT_BOOT_FAILED
348 At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.
354 SymbolicName=EVENT_BOOT_SYSTEM_DRIVERS_FAILED
356 The following boot-start or system-start driver(s) failed to load: %1
362 SymbolicName=EVENT_RUNNING_LASTKNOWNGOOD
364 ReactOS could not be started as configured. A previous working configuration was used instead.
370 SymbolicName=EVENT_TAKE_OWNERSHIP
372 The %1 Registry key denied access to SYSTEM account programs so the Service Control Manager took ownership of the Registry key.
378 SymbolicName=TITLE_SC_MESSAGE_BOX
380 Service Control Manager %0
386 SymbolicName=EVENT_SERVICE_NOT_INTERACTIVE
388 The %1 service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.
394 SymbolicName=EVENT_SERVICE_CRASH
396 The %1 service terminated unexpectedly. It has done this %2 time(s). The following corrective action will be taken in %3 milliseconds: %5.
402 SymbolicName=EVENT_SERVICE_RECOVERY_FAILED
404 The Service Control Manager tried to take a corrective action (%2) after the unexpected termination of the %3 service, but this action failed with the following error: %n%4
410 SymbolicName=EVENT_SERVICE_SCESRV_FAILED
412 The Service Control Manager did not initialize successfully. The security
413 configuration server (scesrv.dll) failed to initialize with error %1. The
414 system is restarting...
420 SymbolicName=EVENT_SERVICE_CRASH_NO_ACTION
422 The %1 service terminated unexpectedly. It has done this %2 time(s).
426 Severity=Informational
428 SymbolicName=EVENT_SERVICE_CONTROL_SUCCESS
430 The %1 service was successfully sent a %2 control.
434 Severity=Informational
436 SymbolicName=EVENT_SERVICE_STATUS_SUCCESS
438 The %1 service entered the %2 state.
444 SymbolicName=EVENT_SERVICE_CONFIG_BACKOUT_FAILED
446 The Service Control Manager encountered an error undoing a configuration change
447 to the %1 service. The service's %2 is currently in an unpredictable state.
449 If you do not correct this configuration, you may not be able to restart the %1
450 service or may encounter other errors. To ensure that the service is configured
451 properly, use the Services snap-in in Microsoft Management Console (MMC).
457 SymbolicName=EVENT_FIRST_LOGON_FAILED_II
459 The %1 service was unable to log on as %2 with the currently configured
460 password due to the following error: %n%3%n%nTo ensure that the service is
461 configured properly, use the Services snap-in in Microsoft Management
468 SymbolicName=EVENT_SERVICE_DIFFERENT_PID_CONNECTED
470 A service process other than the one launched by the Service Control Manager
471 connected when starting the %1 service. The Service Control Manager launched
472 process %2 and process %3 connected instead.%n%n
474 Note that if this service is configured to start under a debugger, this behavior is expected.
478 Severity=Informational
480 SymbolicName=EVENT_SERVICE_START_TYPE_CHANGED
482 The start type of the %1 service was changed from %2 to %3.
488 SymbolicName=EVENT_SERVICE_LOGON_TYPE_NOT_GRANTED
490 The %1 service was unable to log on as %2 with the currently configured password due to the following error:%n
491 Logon failure: the user has not been granted the requested logon type at this computer.%n%n
493 Domain and account: %2%n%n
494 This service account does not have the necessary user right "Log on as a service."%n%n
496 Assign "Log on as a service" to the service account on this computer. You can
497 use Local Security Settings (Secpol.msc) to do this. If this computer is a
498 node in a cluster, check that this user right is assigned to the Cluster
499 service account on all nodes in the cluster.%n%n
500 If you have already assigned this user right to the service account, and the
501 user right appears to be removed, a Group Policy object associated with this
502 node might be removing the right. Check with your domain administrator to find
503 out if this is happening.
507 Severity=Informational
509 SymbolicName=EVENT_SERVICE_STOP_SUCCESS_WITH_REASON
511 The %1 service was successfully sent a %2 control.%n%n
512 The reason specified was: %3 [%4]%n%n
519 SymbolicName=EVENT_SERVICE_SHUTDOWN_FAILED
521 The %1 service did not shut down properly after receiving a preshutdown control.
526 ; transport events 9000-9499
532 SymbolicName=EVENT_TRANSPORT_REGISTER_FAILED
534 %2 failed to register itself with the NDIS wrapper.
540 SymbolicName=EVENT_TRANSPORT_ADAPTER_NOT_FOUND
542 %2 could not find adapter %3.