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
17 Russian=0x419:MSG00419)
27 ; eventlog events 6000-6099
33 SymbolicName=EVENT_LOG_FULL
35 The %1 log file is full.
38 Файл журнала "%1" заполнен.
44 SymbolicName=EVENT_LogFileNotOpened
46 The %1 log file cannot be opened.
49 Файл журнала "%1" не может быть открыт.
55 SymbolicName=EVENT_LogFileCorrupt
57 The %1 log file is corrupted and will be cleared.
60 Файл журана "%1" поврежден и будет очищен.
66 SymbolicName=EVENT_DefaultLogCorrupt
68 The Application log file could not be opened. %1 will be used as the default log file.
71 Файл журнала "Приложения" не может быть открыт. "%1" будет использоваться в качестве файла журана по умолчанию.
77 SymbolicName=EVENT_BadDriverPacket
79 A driver packet received from the I/O subsystem was invalid. The data is the packet.
82 Пакет драйвера, полученный от подсистемы ввода-вывода недопустим. Данные являются пакетом.
88 SymbolicName=EVENT_EventlogStarted
90 The Event log service was started.
93 Служба журана событий была запущена.
99 SymbolicName=EVENT_EventlogStopped
101 The Event log service was stopped.
104 Служба журнала событий была остановлена.
110 SymbolicName=TITLE_EventlogMessageBox
115 Служба журнала событий %0
121 SymbolicName=EVENT_EventlogAbnormalShutdown
123 The previous system shutdown at %1 on %2 was unexpected.
126 Предыдущее завершение работы системы в %1 %2 было неожиданным.
132 SymbolicName=EVENT_EventLogProductInfo
140 SymbolicName=EVENT_ServiceNoEventLog
142 The %1 service was unable to set up an event source.
145 Служба "%1" не смогла установить источник события.
151 SymbolicName=EVENT_ComputerNameChange
153 The NetBIOS name and DNS host name of this machine have been changed from %1 to %2.
156 NetBIOS и DNS имена этого компьютера были изменены с "%1" на "%2".
162 SymbolicName=EVENT_DNSDomainNameChange
164 The DNS domain assigned to this computer has been changed from %1 to %2.
167 DNS-домен присвоенный этому компьютеру был изменен с "%1" на "%2".
172 ; system events 6100 - 6199
178 SymbolicName=EVENT_UP_DRIVER_ON_MP
180 A uniprocessor-specific driver was loaded on a multiprocessor system. The driver could not load.
183 Однопроцессорный драйвер был загружен на многопроцессорной системе. Драйвер не может быть загружен.
188 ; service controller events 7000-7899
194 SymbolicName=EVENT_SERVICE_START_FAILED
196 The %1 service failed to start due to the following error: %n%2
199 Службе "%1" не удалось запуститься из-за следующей ошибки: %n%2
205 SymbolicName=EVENT_SERVICE_START_FAILED_II
207 The %1 service depends on the %2 service which failed to start because of the following error: %n%3
210 Служба "%1" зависит от службы "%2", которой не удалось запуститься из-за следующей ошибки: %n%3
216 SymbolicName=EVENT_SERVICE_START_FAILED_GROUP
218 The %1 service depends on the %2 group and no member of this group started.
221 Служба "%1" зависит от группы "%2" и ни один элемент этой группы не запущен.
227 SymbolicName=EVENT_SERVICE_START_FAILED_NONE
229 The %1 service depends on the following nonexistent service: %2
232 Служба "%1" зависит от следующей несуществующей службы: "%2"
238 SymbolicName=EVENT_CALL_TO_FUNCTION_FAILED
240 The %1 call failed with the following error: %n%2
243 Вызов "%1" завершился ошибкой: %n%2
249 SymbolicName=EVENT_CALL_TO_FUNCTION_FAILED_II
251 The %1 call failed for %2 with the following error: %n%3
257 SymbolicName=EVENT_REVERTED_TO_LASTKNOWNGOOD
259 The system reverted to its last known good configuration. The system is restarting....
265 SymbolicName=EVENT_BAD_ACCOUNT_NAME
267 No backslash is in the account name.
273 SymbolicName=EVENT_CONNECTION_TIMEOUT
275 Timeout (%1 milliseconds) waiting for the %2 service to connect.
281 SymbolicName=EVENT_READFILE_TIMEOUT
283 Timeout (%1 milliseconds) waiting for ReadFile.
289 SymbolicName=EVENT_TRANSACT_TIMEOUT
291 Timeout (%1 milliseconds) waiting for a transaction response from the %2 service.
297 SymbolicName=EVENT_TRANSACT_INVALID
299 Message returned in transaction has incorrect size.
305 SymbolicName=EVENT_FIRST_LOGON_FAILED
307 Logon attempt with current password failed with the following error: %n%1
313 SymbolicName=EVENT_SECOND_LOGON_FAILED
315 Second logon attempt with old password also failed with the following error: %n%1
321 SymbolicName=EVENT_INVALID_DRIVER_DEPENDENCY
323 Boot-start or system-start driver (%1) must not depend on a service.
329 SymbolicName=EVENT_BAD_SERVICE_STATE
331 The %1 service has reported an invalid current state %2.
337 SymbolicName=EVENT_CIRCULAR_DEPENDENCY_DEMAND
339 Detected circular dependencies demand starting %1.
345 SymbolicName=EVENT_CIRCULAR_DEPENDENCY_AUTO
347 Detected circular dependencies auto-starting services.
353 SymbolicName=EVENT_DEPEND_ON_LATER_SERVICE
355 Circular dependency: The %1 service depends on a service in a group which starts later.
361 SymbolicName=EVENT_DEPEND_ON_LATER_GROUP
363 Circular dependency: The %1 service depends on a group which starts later.
369 SymbolicName=EVENT_SEVERE_SERVICE_FAILED
371 About to revert to the last known good configuration because the %1 service failed to start.
377 SymbolicName=EVENT_SERVICE_START_HUNG
379 The %1 service hung on starting.
382 Служба "%1" зависла при запуске.
388 SymbolicName=EVENT_SERVICE_EXIT_FAILED
390 The %1 service terminated with the following error: %n%2
396 SymbolicName=EVENT_SERVICE_EXIT_FAILED_SPECIFIC
398 The %1 service terminated with service-specific error %2.
404 SymbolicName=EVENT_SERVICE_START_AT_BOOT_FAILED
406 At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.
412 SymbolicName=EVENT_BOOT_SYSTEM_DRIVERS_FAILED
414 The following boot-start or system-start driver(s) failed to load: %1
420 SymbolicName=EVENT_RUNNING_LASTKNOWNGOOD
422 ReactOS could not be started as configured. A previous working configuration was used instead.
428 SymbolicName=EVENT_TAKE_OWNERSHIP
430 The %1 Registry key denied access to SYSTEM account programs so the Service Control Manager took ownership of the Registry key.
436 SymbolicName=TITLE_SC_MESSAGE_BOX
438 Service Control Manager %0
444 SymbolicName=EVENT_SERVICE_NOT_INTERACTIVE
446 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.
452 SymbolicName=EVENT_SERVICE_CRASH
454 The %1 service terminated unexpectedly. It has done this %2 time(s). The following corrective action will be taken in %3 milliseconds: %5.
460 SymbolicName=EVENT_SERVICE_RECOVERY_FAILED
462 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
468 SymbolicName=EVENT_SERVICE_SCESRV_FAILED
470 The Service Control Manager did not initialize successfully. The security
471 configuration server (scesrv.dll) failed to initialize with error %1. The
472 system is restarting...
478 SymbolicName=EVENT_SERVICE_CRASH_NO_ACTION
480 The %1 service terminated unexpectedly. It has done this %2 time(s).
483 Служба "%1" неожиданно завершилась. Это произошло %2 раз(а).
487 Severity=Informational
489 SymbolicName=EVENT_SERVICE_CONTROL_SUCCESS
491 The %1 service was successfully sent a %2 control.
494 Служба "%1" успешно отправила "%2".
498 Severity=Informational
500 SymbolicName=EVENT_SERVICE_STATUS_SUCCESS
502 The %1 service entered the %2 state.
505 Служба "%1" перешла в состояние "%2".
511 SymbolicName=EVENT_SERVICE_CONFIG_BACKOUT_FAILED
513 The Service Control Manager encountered an error undoing a configuration change
514 to the %1 service. The service's %2 is currently in an unpredictable state.
516 If you do not correct this configuration, you may not be able to restart the %1
517 service or may encounter other errors. To ensure that the service is configured
518 properly, use the Services snap-in in Microsoft Management Console (MMC).
524 SymbolicName=EVENT_FIRST_LOGON_FAILED_II
526 The %1 service was unable to log on as %2 with the currently configured
527 password due to the following error: %n%3%n%nTo ensure that the service is
528 configured properly, use the Services snap-in in Microsoft Management
535 SymbolicName=EVENT_SERVICE_DIFFERENT_PID_CONNECTED
537 A service process other than the one launched by the Service Control Manager
538 connected when starting the %1 service. The Service Control Manager launched
539 process %2 and process %3 connected instead.%n%n
541 Note that if this service is configured to start under a debugger, this behavior is expected.
545 Severity=Informational
547 SymbolicName=EVENT_SERVICE_START_TYPE_CHANGED
549 The start type of the %1 service was changed from %2 to %3.
552 Тип запуска службы "%1" изменен с "%2" на "%3".
558 SymbolicName=EVENT_SERVICE_LOGON_TYPE_NOT_GRANTED
560 The %1 service was unable to log on as %2 with the currently configured password due to the following error:%n
561 Logon failure: the user has not been granted the requested logon type at this computer.%n%n
563 Domain and account: %2%n%n
564 This service account does not have the necessary user right "Log on as a service."%n%n
566 Assign "Log on as a service" to the service account on this computer. You can
567 use Local Security Settings (Secpol.msc) to do this. If this computer is a
568 node in a cluster, check that this user right is assigned to the Cluster
569 service account on all nodes in the cluster.%n%n
570 If you have already assigned this user right to the service account, and the
571 user right appears to be removed, a Group Policy object associated with this
572 node might be removing the right. Check with your domain administrator to find
573 out if this is happening.
577 Severity=Informational
579 SymbolicName=EVENT_SERVICE_STOP_SUCCESS_WITH_REASON
581 The %1 service was successfully sent a %2 control.%n%n
582 The reason specified was: %3 [%4]%n%n
589 SymbolicName=EVENT_SERVICE_SHUTDOWN_FAILED
591 The %1 service did not shut down properly after receiving a preshutdown control.
596 ; transport events 9000-9499
602 SymbolicName=EVENT_TRANSPORT_REGISTER_FAILED
604 %2 failed to register itself with the NDIS wrapper.
610 SymbolicName=EVENT_TRANSPORT_ADAPTER_NOT_FOUND
612 %2 could not find adapter %3.
615 "%2" не смогла найти адаптер "%3".