100 | Task Scheduler |
Task Scheduler |
101 | 使用户可以在此计算机上配置和计划自动任务。此服务还托管多个 Windows 系统关键任务。如果此服务被停止或禁用,这些任务将无法在计划的时间运行。如果此服务被禁用,则明确依赖它的所有服务将无法启动。 |
Enables a user to configure and schedule automated tasks on this computer. The service also hosts multiple Windows system-critical tasks. If this service is stopped or disabled, these tasks will not be run at their scheduled times. If this service is disabled, any services that explicitly depend on it will fail to start. |
102 | 任务计划程序将执行“%1”任务。 |
Task Scheduler will execute '%1' task. |
4001 | 错误: 输入意外结束 |
ERROR: unexpected end of input |
4002 | 错误: 未识别的编码 |
ERROR: unrecognized encoding |
4003 | 错误: 无法切换编码 |
ERROR: unable to switch the encoding |
4004 | 错误: 未识别的输入签名 |
ERROR: unrecognized input signature |
4005 | 错误: 缺少空格 |
ERROR: whitespace expected |
4006 | 错误: 缺少分号 |
ERROR: semicolon expected |
4007 | 错误: 缺少 "" |
ERROR: '' expected |
4008 | 错误: 缺少引号 |
ERROR: quote expected |
4009 | 错误: 缺少等号 |
ERROR: equal expected |
4010 | 错误: wfc: 属性值中无 " |
ERROR: wfc: no ' |
4011 | 错误: 需要十六进制数 |
ERROR: hexadecimal digit expected |
4012 | 错误: 需要十进制数 |
ERROR: decimal digit expected |
4013 | 错误: 缺少 "[" |
ERROR: '[' expected |
4014 | 错误: 缺少 "(" |
ERROR: '(' expected |
4015 | 错误: 非法的 xml 字符 |
ERROR: illegal xml character |
4016 | 错误: 非法的名称字符 |
ERROR: illegal name character |
4017 | 错误: 不正确的文档语法 |
ERROR: incorrect document syntax |
4018 | 错误: 不正确的 CDATA 节语法 |
ERROR: incorrect CDATA section syntax |
4019 | 错误: 不正确的备注语法 |
ERROR: incorrect comment syntax |
4020 | 错误: 不正确的条件节语法 |
ERROR: incorrect conditional section syntax |
4021 | 错误: 不正确的 ATTLIST 声明语法 |
ERROR: incorrect ATTLIST declaration syntax |
4022 | 错误: 不正确的 DOCTYPE 声明语法 |
ERROR: incorrect DOCTYPE declaration syntax |
4023 | 错误: 不正确的 ELEMENT 声明语法 |
ERROR: incorrect ELEMENT declaration syntax |
4024 | 错误: 不正确的 ENTITY 声明语法 |
ERROR: incorrect ENTITY declaration syntax |
4025 | 错误: 不正确的 NOTATION 声明语法 |
ERROR: incorrect NOTATION declaration syntax |
4026 | 错误: 缺少 NDATA |
ERROR: NDATA expected |
4027 | 错误: 缺少 PUBLIC |
ERROR: PUBLIC expected |
4028 | 错误: 缺少 SYSTEM |
ERROR: SYSTEM expected |
4029 | 错误: 缺少名称 |
ERROR: name expected |
4030 | 错误: 一个根元素 |
ERROR: one root element |
4031 | 错误: wfc: 元素类型匹配 |
ERROR: wfc: element type match |
4032 | 错误: wfc: 唯一的属性规范 |
ERROR: wfc: unique attribute spec |
4033 | 错误: text/xmldecl 不在输入的开始位置 |
ERROR: text/xmldecl not at the beginning of input |
4034 | 错误: "xml" 带头 |
ERROR: leading 'xml' |
4035 | 错误: 不正确的文本声明语法 |
ERROR: incorrect text declaration syntax |
4036 | 错误: 不正确的 xml 声明语法 |
ERROR: incorrect xml declaration syntax |
4037 | 错误: 不正确的编码名称语法 |
ERROR: incorrect encoding name syntax |
4038 | 错误: 不正确的公共标识符语法 |
ERROR: incorrect public identifier syntax |
4039 | 错误: wfc: pes 在内部子集中 |
ERROR: wfc: pes in internal subset |
4040 | 错误: wfc: pes 在声明之间 |
ERROR: wfc: pes between declarations |
4041 | 错误: wfc: 无递归 |
ERROR: wfc: no recursion |
4042 | 错误: 实体内容格式不标准 |
ERROR: entity content not well formed |
4043 | 错误: wfc: 未声明的实体 |
ERROR: wfc: undeclared entity |
4044 | 错误: wfc: 实体已分析 |
ERROR: wfc: parsed entity |
4045 | 错误: wfc: 无外部实体参考 |
ERROR: wfc: no external entity references |
4046 | 错误: 不正确的处理指令语法 |
ERROR: incorrect processing instruction syntax |
4047 | 错误: 不正确的系统标识符语法 |
ERROR: incorrect system identifier syntax |
4048 | 错误: 缺少 "?" |
ERROR: '?' expected |
4049 | 错误: 元素内容中无 "]]" |
ERROR: no ']]' in element content |
4050 | 错误: 值的部分区块未读取 |
ERROR: not all chunks of value have been read |
4051 | 错误: 非法的限定名字符 |
ERROR: illegal qualified name character |
4052 | 错误: 限定名中有多个冒号 |
ERROR: multiple colons in qualified name |
4053 | 错误: 名称中有冒号 |
ERROR: colon in name |
4054 | 错误: 前缀已声明 |
ERROR: declared prefix |
4055 | 错误: 前缀未声明 |
ERROR: undeclared prefix |
4056 | 错误: 没有带空 URI 的默认命名空间 |
ERROR: non default namespace with empty uri |
4057 | 错误: "xml" 前缀已保留,必须有 http://www.w3.org/XML/1998/namespace URI |
ERROR: 'xml' prefix is reserved and must have the http://www.w3.org/XML/1998/namespace URI |
4058 | 错误: "xmlns" 前缀已保留为供 XML 使用 |
ERROR: 'xmlns' prefix is reserved for use by XML |
4059 | 错误: xml 命名空间 URI (http://www.w3.org/XML/1998/namespace) 仅须指定给前缀 "xml" |
ERROR: xml namespace URI (http://www.w3.org/XML/1998/namespace) must be assigned only to prefix 'xml' |
4060 | 错误: xmlns 命名空间 URI (http://www.w3.org/2000/xmlns/)已保留,不得使用 |
ERROR: xmlns namespace URI (http://www.w3.org/2000/xmlns/) is reserved and must not be used |
0x191 | 由于“%1”中的错误,任务计划程序服务未能启动。其他数据: 错误值: %2。 |
Task Scheduler service failed to start due to an error in \"%1\" . Additional Data: Error Value: %2. |
0x194 | 任务计划程序服务在“%1”中遇到 RPC 初始化错误。其他数据: 错误值: %2。 |
Task Scheduler service has encountered RPC initialization error in \"%1\". Additional Data: Error Value: %2. |
0x195 | 任务计划程序服务无法对 COM 进行初始化。其他数据: 错误值: %1。 |
Task Scheduler service has failed to initialize COM. Additional Data: Error Value: %1. |
0x196 | 任务计划程序服务无法对凭据存储进行初始化。其他数据: 错误值: %1。 |
Task Scheduler service failed to initialize credentials store. Additional Data: Error Value: %1. |
0x197 | 任务计划程序服务无法对 LSA 进行初始化。其他数据: 错误值: %1。 |
Task Scheduler service failed to initialize LSA. Additional Data: Error Value: %1. |
0x198 | 任务计划程序服务无法对空闲状态检测模块进行初始化。空闲任务可能未按要求启动。其他数据: 错误值: %1。 |
Task Scheduler service failed to initialize idle state detection module. Idle tasks may not be started as required. Additional Data: Error Value: %1. |
0x199 | 任务计划程序服务无法对时间更改通知进行初始化。服务可能未选取系统时间更新,并且可能未更新任务计划。其他数据: 错误值: %1。 |
Task Scheduler service failed to initialize time change notification. System time updates may not be picked by the service and task schedules may not be updated. Additional Data: Error Value: %1. |
0x19C | 任务计划程序服务无法启动由计算机启动触发的任务。其他数据: 错误值: %1。 |
Task Scheduler service failed to launch tasks triggered by computer startup. Additional Data: Error Value: %1. |
0x19D | 任务计划程序服务在服务启动时加载任务失败。其他数据: 错误值: %1。 |
Task Scheduler service failed to load tasks at service startup. Additional Data: Error Value: %1. |
0x19E | 任务计划程序服务在 %1 定义中发现配置错误。其他数据: 错误值: %2。 |
Task Scheduler service found a misconfiguration in the %1 definition. Additional Data: Error Value: %2. |
0x2BD | 任务计划程序服务无法启动任务兼容模块。任务可能无法在先前的 Windows 版本上注册。其他数据: 错误值: %1。 |
Task Scheduler service failed to start Task Compatibility module. Tasks may not be able to register on previous Window versions. Additional Data: Error Value: %1. |
0x2BE | 任务计划程序无法初始化用于启动任务兼容模块的 RPC 服务器。任务可能无法在以前版本的 Windows 上注册。其他数据: 错误值: %1。 |
Task Scheduler failed to initialize the RPC server for starting the Task Compatibility module. Tasks may not be able to register on previous Window versions. Additional Data: Error Value: %1. |
0x2BF | 任务计划程序无法为启动任务兼容模块初始化网络计划 API。任务可能无法在先前的 Windows 版本上注册。其他数据: 错误值: %1。 |
Task Scheduler failed to initialize Net Schedule API for starting the Task Compatibility module. Tasks may not be able to register on previous Window versions. Additional Data: Error Value: %1. |
0x2C0 | 任务计划程序无法为启动任务兼容模块初始化 LSA。任务可能无法在先前的 Windows 版本上注册。其他数据: 错误值: %1。 |
Task Scheduler failed to initialize LSA for starting the Task Compatibility module. Tasks may not be able to register on previous Window versions. Additional Data: Error Value: %1. |
0x2C1 | 任务计划程序无法为任务兼容模块启动目录监视。其他数据: 错误值: %1。 |
Task Scheduler failed to start directory monitoring for the Task Compatibility module. Additional Data: Error Value: %1. |
0x2CC | 任务兼容模块无法升级现有计划任务。其他数据: 错误值: %1。 |
Task Compatibility module failed to upgrade existing scheduled tasks. Additional Data: Error Value: %1. |
0x2CE | 任务计划程序无法从 Beta 2 版本升级凭据存储。你可能需要重新注册需要密码的所有任务。其他数据: 错误值: %1。 |
Task scheduler was unable to upgrade the credential store from the Beta 2 version. You may need to re-register any tasks that require passwords. Additional Data: Error Value: %1. |
0x2CF | 为了帮助优化性能,任务计划程序会自动禁用日志记录。若要重新启用日志记录,请使用事件查看器。 |
To help optimize for performance, Task Scheduler has automatically disabled logging. To re-enable logging, please use Event Viewer. |
0x10000031 | 响应时间 |
Response Time |
0x30000000 | 信息 |
Info |
0x30000001 | 开始 |
Start |
0x30000002 | 停止 |
Stop |
0x30000065 | 启动失败 |
Launch Failure |
0x30000066 | 运行失败 |
Run Failure |
0x30000067 | 终止 |
Termination |
0x30000068 | 失败 |
Failure |
0x50000001 | 关键 |
Critical |
0x50000002 | 错误 |
Error |
0x50000003 | 警告 |
Warning |
0x50000005 | 详细 |
Verbose |
0x70000064 | 任务已启动 |
Task Started |
0x70000065 | 任务启动失败 |
Task Start Failed |
0x70000066 | 任务已完成 |
Task completed |
0x70000067 | 操作启动失败 |
Action start failed |
0x70000068 | 登录失败 |
Logon failure |
0x70000069 | 模拟失败 |
Impersonation failure |
0x7000006A | 已注册任务 |
Task registered |
0x7000006B | 任务已由计划程序触发 |
Task triggered on scheduler |
0x7000006C | 任务已由事件触发 |
Task triggered on event |
0x7000006D | 任务已由注册触发 |
Task triggered by registration |
0x7000006E | 任务已由用户触发 |
Task triggered by user |
0x7000006F | 任务已终止 |
Task terminated |
0x70000070 | 启动条件未满足,网络不可用 |
Launch condition not met, network unavailable |
0x70000071 | 不使用某些触发器注册的任务 |
Task registered without some triggers |
0x70000072 | 丢失任务已启动 |
Missed task started |
0x70000073 | 任务更新或删除错误 |
Task update or deletion error |
0x70000074 | 不使用凭据注册的任务 |
Task registered without credentials |
0x70000075 | 任务已由空闲触发 |
Task triggered on Idle |
0x70000076 | 任务已由计算机启动触发 |
Task triggered by computer startup |
0x70000077 | 任务已由登录触发 |
Task triggered on logon |
0x70000078 | 任务已由本地控制台连接触发 |
Task triggered on local console connect |
0x70000079 | 任务已由本地控制台断开连接触发 |
Task triggered on local console disconnect |
0x7000007A | 任务已由远程控制台连接触发 |
Task triggered on remote console connect |
0x7000007B | 任务已由远程控制台断开连接触发 |
Task triggered on remote console disconnect |
0x7000007C | 任务已由锁定工作站触发 |
Task triggered by locking the workstation |
0x7000007D | 任务已由解锁工作站触发 |
Task triggered by unlocking the workstation |
0x7000007E | 由于失败,任务已重新启动 |
Task restarted on failure |
0x70000080 | 启动条件未满足,超出结束时间 |
Launch condition not met, beyond end time |
0x70000081 | 已创建任务进程 |
Created Task Process |
0x70000082 | 启动条件未满足,服务忙 |
Launch condition not met, service busy |
0x70000083 | 启动条件未满足,配额已超出 |
Launch condition not met, quota exceeded |
0x70000084 | 启动条件警告,正接近配额 |
Launch condition warning, quota approaching |
0x70000087 | 未满足启动条件,计算机无空闲 |
Launch condition not met, machine not idle |
0x70000088 | 任务完成挂起 |
Task Completion Pending |
0x7000008C | 任务注册已更新 |
Task registration updated |
0x7000008D | 任务注册已删除 |
Task registration deleted |
0x7000008E | 任务已禁用 |
Task disabled |
0x70000091 | 已通过离开暂停模式触发任务 |
Task triggered by coming out of suspend mode |
0x70000092 | 服务启动时加载任务失败 |
Task loading at service startup failed |
0x70000093 | OS 迁移之后已恢复任务映像 |
Task image recovered after OS migration |
0x70000094 | OS 迁移之后任务映像恢复失败 |
Task image recovering failed after OS migration |
0x70000095 | 任务正在使用的属性组合与计划引擎不兼容 |
Task is using a combination of properties that is incompatible with the scheduling engine |
0x70000096 | 在发生事件时任务注册失败 |
Task registration on event failed |
0x70000097 | 在服务启动时,任务计划程序无法实例化任务。 |
Task Scheduler failed to instantiate task at service startup. |
0x70000098 | 任务已重定向到原有引擎 |
Task was redirected to legacy engine |
0x70000099 | 已拒绝错过的任务启动 |
Missed task start rejected |
0x700000C8 | 操作已启动 |
Action started |
0x700000C9 | 操作已完成 |
Action completed |
0x700000CA | 操作已失败 |
Action failed |
0x700000CB | 操作无法启动 |
Action failed to start |
0x700000CC | 在发生事件时任务无法启动 |
Task failed to start on event |
0x700000CD | 事件模式匹配时任务无法启动 |
Task failed to start on event pattern match |
0x7000012C | 任务引擎已启动 |
Task engine launched |
0x7000012D | 任务引擎已正确关闭 |
Task engine properly shut down |
0x7000012F | 任务引擎已由于错误而关闭 |
Task engine shut down due to error |
0x70000130 | 已将任务发送到引擎 |
Task sent to engine |
0x70000131 | 无法将任务发送到引擎 |
Task failed to be sent to engine |
0x70000132 | 引擎无法接收任务 |
Engine failed to receive the task |
0x70000133 | 服务引擎连接失败 |
Service Engine connection failure |
0x70000134 | 服务引擎已连接 |
Service Engine connected |
0x70000135 | 引擎已被孤立 |
Engine orphaned |
0x70000137 | 任务引擎无法启动 |
Task Engine failed to start |
0x70000138 | 任务引擎作业对象已创建 |
Task Engine job object created |
0x70000139 | 服务引擎通道就绪 |
Service Engine channel ready |
0x7000013A | 任务引擎空闲 |
Task Engine idle |
0x7000013C | 引擎无法将消息发送到服务 |
Engine failed to send message to service |
0x7000013F | 任务引擎已收到启动任务的消息 |
Task Engine received message to start task |
0x70000140 | 任务引擎已收到停止任务的消息 |
Task Engine received message to stop task |
0x70000142 | 启动请求已被忽略,实例已在运行 |
Launch request ignored, instance already running |
0x70000143 | 启动请求已确认,当前实例已停止 |
Launch request acknowledged, current instance stopped |
0x70000144 | 启动请求已排队,实例已在运行 |
Launch request queued, instance already running |
0x70000145 | 启动请求已排队 |
Launch request queued |
0x70000146 | 启动条件未满足,计算机在使用电池 |
Launch condition not met, computer on batteries |
0x70000147 | 由于切换到电池,任务正在停止 |
Task stopping due to switching to batteries |
0x70000148 | 由于计算机无空闲,任务正在停止 |
Task stopping due to computer not idle |
0x70000149 | 由于已达到超时,任务正在停止 |
Task stopping due to timeout reached |
0x7000014A | 由于用户请求,任务正在停止 |
Task stopping due to user request |
0x7000014B | 由于超时,任务无法停止 |
Task failed to stop on timeout |
0x7000014C | 启动条件未满足,用户未登录 |
Launch condition not met, user not logged-on |
0x7000014D | 未满足启动条件,会话为 RemoteApp 会话 |
Launch condition not met, session is RemoteApp Session |
0x7000014E | 不满足启动条件,会话是一个工作进程会话 |
Launch condition not met, session is a Worker Session |
0x70000190 | 服务已启动 |
Service started |
0x70000191 | 服务无法启动 |
Service failed to start |
0x70000192 | 服务正在关闭 |
Service is shutting down |
0x70000193 | 服务关键错误 |
Service critical error |
0x70000194 | 服务 RPC 错误 |
Service RPC error |
0x70000195 | 服务 COM 错误 |
Service COM error |
0x70000196 | 凭据存储初始化错误 |
Cred store initialization error |
0x70000197 | LSA 初始化错误 |
LSA initialization error |
0x70000198 | 空闲检测错误 |
Idle detection error |
0x70000199 | 时间更改通知错误 |
Time change notification error |
0x7000019A | 唤醒计时器错误 |
Wakeup timer error |
0x7000019B | 服务已发出时间更改信号 |
Service signaled time change |
0x7000019E | 任务配置错误 |
Task Misconfiguration |
0x700001F4 | 空闲任务注册 |
Idle Task Register |
0x700001F5 | 空闲任务注销 |
Idle Task Unregister |
0x700001F6 | 空闲任务执行 |
Idle Task Execute |
0x700001F8 | 空闲任务通知 |
Idle Task Notify |
0x700001FA | 空闲任务显式处理 |
Idle Task Explicit Processing |
0x700001FC | 空闲任务显式处理处于活动状态 |
Idle Task Explicit Processing Active |
0x700001FD | 接收到空闲任务电源通知 |
Idle Task Power Notification Received |
0x700001FE | 空闲任务 PerfTrack 资源消耗 |
Idle Task PerfTrack Resource Consumption |
0x700001FF | 空闲任务 PerfTrack 空闲退出 |
Idle Task PerfTrack Idle Exit |
0x70000200 | 空闲检查点 |
Idle Check Point |
0x700002BC | 兼容模块已启动 |
Compatibility module started |
0x700002BD | 兼容模块无法启动 |
Compatibility module failed to start |
0x700002BE | 兼容模块 RPC 失败 |
Compatibility module RPC failed |
0x700002BF | 兼容模块网络计划 API 失败 |
Compatibility module Net Schedule API failed |
0x700002C0 | 兼容模块 LSA 失败 |
Compatibility module LSA failed |
0x700002C1 | 兼容模块目录监视失败 |
Compatibility module directory monitoring failed |
0x700002C2 | 兼容模块任务状态更新失败 |
Compatibility module task status update failed |
0x700002C3 | 兼容模块任务删除失败 |
Compatibility module task deletion failed |
0x700002C4 | 兼容模块安全描述符失败 |
Compatibility module security descriptor failed |
0x700002C5 | 兼容模块任务更新失败 |
Compatibility module task update failed |
0x700002C6 | 兼容模块任务升级失败 |
Compatibility module tasks upgrade failed |
0x700002C7 | 兼容模块任务升级未确定 |
Compatibility module tasks upgrade undetermined |
0x700002C8 | 凭据存储升级失败 |
Credential store upgrade failed |
0x700002CF | TaskScheduler 运行日志已禁用 |
TaskScheduler Operational log was disabled |
0x70000320 | 维护状态已更改 |
Maintenance state has changed |
0x70000321 | 维护启动失败 |
Maintenance launch failed |
0x70000322 | 维护重新配置失败 |
Maintenance re-configuration failed |
0x70000323 | 维护计划程序引擎任务错误 |
Maintenance Scheduler engine task error |
0x70000324 | 已检测到维护循环依赖关系 |
Maintenance task cycle dependency detected |
0x70000325 | 维护任务超出截止时间 |
Maintenance task is behind deadline |
0x70000326 | 维护任务处理错误 |
Maintenance task processing error |
0x70000327 | 维护完成 |
Maintenance complete |
0x70000328 | 已请求维护唤醒 |
Maintenance wakeup requested |
0x700003E6 | 方法失败 |
Method Failure |
0x700003E7 | 调试 |
Debug |
0x90000001 | Microsoft-Windows-TaskScheduler |
Microsoft-Windows-TaskScheduler |
0x90000002 | Operational |
Operational |
0x90000003 | System |
System |
0x90000004 | Debug |
Debug |
0x90000005 | Diagnostic |
Diagnostic |
0x90000006 | Maintenance |
Maintenance |
0xB0000064 | 任务计划程序已为用户“%2”启动“%1”任务的“%3”实例。 |
Task Scheduler started \"%3\" instance of the \"%1\" task for user \"%2\". |
0xB0000065 | 任务计划程序无法为用户“%2”启动“%1”任务。其他数据: 错误值: %3。 |
Task Scheduler failed to start \"%1\" task for user \"%2\". Additional Data: Error Value: %3. |
0xB0000066 | 任务计划程序已为用户“%2”成功完成“%1”任务的“%3”实例。 |
Task Scheduler successfully finished \"%3\" instance of the \"%1\" task for user \"%2\". |
0xB0000067 | 任务计划程序无法为用户“%3”启动“%1”任务的实例“%2”。其他数据: 错误值: %4。 |
Task Scheduler failed to start instance \"%2\" of \"%1\" task for user \"%3\" . Additional Data: Error Value: %4. |
0xB0000068 | 任务计划程序无法登录“%1”。在“%2”中发生故障。用户操作: 确保已正确指定任务的凭据。其他数据: 错误值: %3。 |
Task Scheduler failed to log on \"%1\" . Failure occurred in \"%2\" . User Action: Ensure the credentials for the task are correctly specified. Additional Data: Error Value: %3. |
0xB0000069 | 任务计划程序无法模拟“%1”。其他数据: 错误值: %2。 |
Task Scheduler failed to impersonate \"%1\" . Additional Data: Error Value: %2. |
0xB000006A | 用户“%2”已注册任务计划程序任务“%1” |
User \"%2\" registered Task Scheduler task \"%1\" |
0xB000006B | 由于存在时间触发器条件,任务计划程序已启动任务“%1”的“%2”实例。 |
Task Scheduler launched \"%2\" instance of task \"%1\" due to a time trigger condition. |
0xB000006C | 根据事件触发器,任务计划程序已启动任务“%1”的“%2”实例。 |
Task Scheduler launched \"%2\" instance of task \"%1\" according to an event trigger. |
0xB000006D | 根据注册触发器,任务计划程序已启动任务“%1”的“%2”实例。 |
Task Scheduler launched \"%2\" instance of task \"%1\" according to a registration trigger. |
0xB000006E | 任务计划程序已为用户“%3”启动任务“%1”的“%2”实例。 |
Task Scheduler launched \"%2\" instance of task \"%1\" for user \"%3\" . |
0xB000006F | 任务计划程序已终止“%1”任务的“%2”实例。 |
Task Scheduler terminated \"%2\" instance of the \"%1\" task. |
0xB0000070 | 由于网络不可用,任务计划程序无法启动任务“%1”。用户操作: 确保计算机按任务中指定的那样连接到要求的网络。如果任务不要求网终存在,请从任务配置中删除网络条件。 |
Task Scheduler could not start task \"%1\" because the network was unavailable. User Action: Ensure the computer is connected to the required network as specified in the task. If the task does not require network presence, remove the network condition from the task configuration. |
0xB0000071 | 任务已注册任务“%1”,但并非所有指定的触发器都将启动该任务。用户操作: 确保所有任务触发器像配置的那样有效。其他数据: 错误值: %2。 |
Task registered task \"%1\" , but not all specified triggers will start the task. User Action: Ensure all the task triggers are valid as configured. Additional Data: Error Value: %2. |
0xB0000072 | 任务计划程序无法按计划启动任务“%1”。如果计划被错过,会立即按配置选项的要求启动实例“%2”,以在任务可用时启动任务。 |
Task Scheduler could not launch task \"%1\" as scheduled. Instance \"%2\" is started now as required by the configuration option to start the task when available, if schedule is missed. |
0xB0000073 | 任务计划程序无法在更新或删除任务时回退事务。其他数据: 错误值: %1。 |
Task Scheduler failed to roll back a transaction when updating or deleting a task. Additional Data: Error Value: %1. |
0xB0000074 | 任务计划程序已验证任务“%1”的配置,但无法存储凭据。用户操作: 重新注册任务以确保凭据有效。其他数据: 错误值: %2。 |
Task Scheduler validated the configuration for task \"%1\" , but credentials could not be stored. User Action: Re-register the task ensuring the credentials are valid. Additional Data: Error Value: %2. |
0xB0000075 | 由于存在空闲条件,任务计划程序已启动任务“%1”的“%2”实例。 |
Task Scheduler launched \"%2\" instance of task \"%1\" due to an idle condition. |
0xB0000076 | 由于系统启动,任务计划程序已启动任务“%1”的“%2”实例。 |
Task Scheduler launched \"%2\" instance of task \"%1\" due to system startup. |
0xB0000077 | 由于用户“%2”登录,任务计划程序已启动任务“%1”的“%3”实例。 |
Task Scheduler launched \"%3\" instance of task \"%1\" due to user \"%2\" logon. |
0xB0000078 | 由于用户“%2”正在连接到控制台触发器,任务计划程序已启动任务“%1”的“%3”实例。 |
Task Scheduler launched \"%3\" instance of task \"%1\" due to user \"%2\" connecting to the console trigger. |
0xB0000079 | 由于用户“%2”正在从控制台触发器断开连接,任务计划程序已启动任务“%1”的“%3”实例。 |
Task Scheduler launched \"%3\" instance of task \"%1\" due to user \"%2\" disconnecting from the console trigger. |
0xB000007A | 由于用户“%2”正在远程连接触发器,任务计划程序已启动任务“%1”的“%3”实例。 |
Task Scheduler launched \"%3\" instance of task \"%1\" due to user \"%2\" remotely connecting trigger. |
0xB000007B | 由于用户“%2”正在远程断开触发器连接,任务计划程序已启动任务“%1”的“%3”实例。 |
Task Scheduler launched \"%3\" instance of task \"%1\" due to user \"%2\" remotely disconnecting trigger. |
0xB000007C | 由于用户“%2”正在锁定计算机触发器,任务计划程序已启动任务“%1”的“%3”实例。 |
Task Scheduler launched \"%3\" instance of task \"%1\" due to user \"%2\" locking the computer trigger. |
0xB000007D | 由于用户“%2”正在解锁计算机触发器,任务计划程序已启动任务“%1”的“%3”实例。 |
Task Scheduler launched \"%3\" instance of task \"%1\" due to user \"%2\" unlocking the computer trigger. |
0xB000007E | 任务计划程序无法执行任务“%1”。正在尝试重新启动。其他数据: 错误值: %2。 |
Task Scheduler failed to execute task \"%1\" . Attempting to restart. Additional Data: Error Value: %2. |
0xB000007F | 由于存在关机竞争条件,任务计划程序无法执行任务“%1”。正在尝试重新启动。 |
Task Scheduler failed to execute task \"%1\" due to a shutdown race condition. Attempting to restart. |
0xB0000080 | 由于当前时间超出配置的任务结束时间,任务计划程序未启动任务“%1”。用户操作: 根据需要延长任务的结束时间边界。 |
Task Scheduler did not launch task \"%1\" , because current time exceeds the configured task end time. User Action: Extend the end time boundary for the task if required. |
0xB0000081 | 任务计划程序启动进程 ID 为“%3”的任务“%1”,实例“%2”。 |
Task Scheduler launch task \"%1\" , instance \"%2\" with process ID %3. |
0xB0000082 | 由于服务正忙,任务计划程序无法启动任务“%1”。 |
Task Scheduler failed to start task \"%1\" due to the service being busy. |
0xB0000083 | 由于任务队列中的任务数超出当前配置为 %2 的配额,任务计划程序无法启动任务“%1”。用户操作: 减少正在运行的任务数或增大配置的队列配额。 |
Task Scheduler failed to start task \"%1\" because the number of tasks in the task queue exceeding the quota currently configured to %2. User Action: Reduce the number of running tasks or increase the configured queue quota. |
0xB0000084 | 任务计划程序任务启动队列配额即将达到其预置任务限制(当前配置为 %1)。用户操作: 减少正在运行的任务数或增大配置的队列配额。 |
Task Scheduler task launching queue quota is approaching its preset limit of tasks currently configured to %1. User Action: Reduce the number of running tasks or increase the configured queue quota. |
0xB0000085 | 任务计划程序无法为用户“%3”启动任务引擎“%2”中的任务“%1”。用户操作: 减少正在指定的用户环境中运行的任务数。 |
Task Scheduler failed to start task %1\" in TaskEngine \"%2\" for user \"%3\". User Action: Reduce the number of tasks running in the specified user context. |
0xB0000086 | 用户“%2”的任务引擎“%1”即将达到其预置任务限制。用户操作: 减少正在指定的用户环境中运行的任务数。 |
Task Engine \"%1\" for user \"%2\" is approaching its preset limit of tasks. User Action: Reduce the number of tasks running in the specified user context. |
0xB0000087 | 任务计划程序无法启动任务“%1”,因为该计算机无空闲。 |
Task Scheduler could not start task \"%1\" because the machine was not idle. |
0xB000008C | 用户“%2”已更新任务计划程序任务“%1” |
User \"%2\" updated Task Scheduler task \"%1\" |
0xB000008D | 用户“%2”已删除任务计划程序任务“%1” |
User \"%2\" deleted Task Scheduler task \"%1\" |
0xB000008E | 用户“%2”已禁用任务计划程序任务“%1” |
User \"%2\" disabled Task Scheduler task \"%1\" |
0xB0000091 | 任务计划程序已唤醒计算机以运行任务。 |
Task Scheduler woke up the computer to run a task. |
0xB0000092 | 任务计划程序在服务启动时加载任务“%1”失败。其他数据: 错误值: %2。 |
Task Scheduler failed to load task \"%1\" at service startup. Additional Data: Error Value: %2. |
0xB0000093 | 在 OS 升级期间发生损坏之后,任务计划程序已成功恢复任务“%1”的映像。 |
Task Scheduler recovered sucessfully the image of task \"%1\" after a corruption occured during OS upgrade. |
0xB0000094 | 在 OS 升级期间发生损坏之后,任务计划程序无法恢复任务“%1”的映像。其他数据: 错误值: 0x%2。 |
Task Scheduler failed to recover the image of task \"%1\" after a corruption occured during OS upgrade. Additional Data: Error Value: 0x%2. |
0xB0000095 | 任务“%1”正在使用的属性组合与计划引擎不兼容。 |
Task \"%1\" is using a combination of properties that is incompatible with the scheduling engine. |
0xB0000096 | 任务计划程序无法为任务“%1”的事件触发器订阅。其他数据: 错误值: %2。 |
Task Scheduler failed to subscribe for the event trigger for task \"%1\". Additional Data: Error Value: %2. |
0xB0000097 | 无法实例化任务“%1”。检查点: %2。错误值: %3。 |
Task instantiation failed \"%1\". Check point: %2. Error Value: %3. |
0xB0000098 | 任务“%1”已重定向到原有计划引擎。 |
Task \"%1\" was re-directed to legacy scheduling engine. |
0xB0000099 | 任务计划程序未启动任务“%1”,因为错过了其计划。如果错过了计划,请考虑使用配置选项在任务可用时启动任务。 |
Task Scheduler did not launch task \"%1\" as it missed its schedule. Consider using the configuration option to start the task when available, if schedule is missed. |
0xB000009B | 任务计划程序正在等待完成任务“%1”。 |
Task Scheduler is currently waiting on completion of task \"%1\". |
0xB00000C8 | 任务计划程序已在任务“%1”的实例“%3”中启动操作“%2”。 |
Task Scheduler launched action \"%2\" in instance \"%3\" of task \"%1\". |
0xB00000C9 | 任务计划程序已成功完成任务“%1”,实例“%3”,操作“%2”。 |
Task Scheduler successfully completed task \"%1\" , instance \"%3\" , action \"%2\" . |
0xB00000CA | 任务计划程序无法完成任务“%1”,实例“%2”,操作“%3”。其他数据: 错误值: %4。 |
Task Scheduler failed to complete task \"%1\" , instance \"%2\" , action \"%3\" . Additional Data: Error Value: %4. |
0xB00000CB | 任务计划程序无法启动任务“%1”的实例“%2”中的操作“%3”。其他数据: 错误值: %4。 |
Task Scheduler failed to launch action \"%3\" in instance \"%2\" of task \"%1\". Additional Data: Error Value: %4. |
0xB00000CC | 任务计划程序无法检索任务“%1”的事件触发器值。事件将被忽略。其他数据: 错误值: %2。 |
Task Scheduler failed to retrieve the event triggering values for task \"%1\" . The event will be ignored. Additional Data: Error Value: %2. |
0xB00000CD | 任务计划程序无法匹配任务“%1”的事件模式。事件将被忽略。其他数据: 错误值: %2。 |
Task Scheduler failed to match the pattern of events for task \"%1\" . The events will be ignored. Additional Data: Error Value: %2. |
0xB000012C | 任务计划程序已启动进程 ID 为“%2”的任务引擎“%1”。 |
Task Scheduler started Task Engine \"%1\" with process ID %2. |
0xB000012D | 任务计划程序正在关闭任务引擎“%1” |
Task Scheduler is shutting down Task Engine \"%1\" |
0xB000012F | 任务计划程序由于“%2”中存在错误正在关闭任务引擎“%1”。其他数据: 错误值: %3。 |
Task Scheduler is shutting down Task Engine \"%1\" due to an error in \"%2\" . Additional Data: Error Value: %3. |
0xB0000130 | 任务计划程序已将“%1”任务发送到任务引擎“%2”。任务实例 ID 为“%3”。 |
Task Scheduler sent \"%1\" task to Task Engine \"%2\" . The task instance Id is \"%3\" . |
0xB0000131 | 任务计划程序没有将“%1”任务发送到任务引擎“%2”。其他数据: 错误值: %3。 |
Task Scheduler did not send \"%1\" task to Task Engine \"%2\" . Additional Data: Error Value: %3. |
0xB0000132 | 对于任务计划程序任务引擎“%1”,线程池无法处理该消息。其他数据: 错误值: %2。 |
For Task Scheduler Task Engine \"%1\" , the thread pool failed to process the message. Additional Data: Error Value: %2. |
0xB0000133 | 任务计划程序服务无法连接到任务引擎“%1”进程。其他数据: 错误值: %2。 |
Task Scheduler service failed to connect to the Task Engine \"%1\" process. Additional Data: Error Value: %2. |
0xB0000134 | 任务计划程序已连接到任务引擎“%1”进程。 |
Task Scheduler connected to the Task Engine \"%1\" process. |
0xB0000135 | 在任务引擎“%2”关闭过程中,任务计划程序 %1 任务被孤立。用户操作: 在任务管理器中,找到此任务运行的进程并手动终止它。 |
Task Scheduler %1 tasks orphaned during Task Engine \"%2\" shutdown. User Action: Find the process run by this task in the Task Manager and kill it manually. |
0xB0000136 | 任务计划程序已启动任务引擎“%1”进程。Command=“%2”、ProcessID=%3、ThreadID=%4 |
Task Scheduler started Task Engine \"%1\" process. Command=\"%2\" , ProcessID=%3, ThreadID=%4 |
0xB0000137 | 任务计划程序由于“%3”中发生错误无法启动任务引擎“%1”进程。Command=“%2”。其他数据: 错误值: %4。 |
Task Scheduler failed to start Task Engine \"%1\" process due to an error occurring in \"%3\" . Command=\"%2\" . Additional Data: Error Value: %4. |
0xB0000138 | 任务计划程序已为任务引擎“%1”创建 Win32 作业对象。 |
Task Scheduler created the Win32 job object for Task Engine \"%1\" . |
0xB0000139 | 具有任务引擎“%1”的任务计划程序通道已准备好发送和接收消息。 |
Task Scheduler channel with Task Engine \"%1\" is ready to send and receive messages. |
0xB000013A | 任务计划程序没有任何为任务引擎“%1”运行的任务,且空闲计时器已启动。 |
Task Scheduler has no tasks running for Task Engine \"%1\" , and the idle timer has started. |
0xB000013B | 任务引擎“%1”进程无法连接到任务计划程序服务。其他数据: 错误值: %2。 |
Task Engine \"%1\" process failed to connect to the Task Scheduler service. Additional Data: Error Value: %2. |
0xB000013C | 任务引擎“%1”无法将消息发送至任务计划程序服务。其他数据: 错误值: %2。 |
Task Engine \"%1\" failed to send a message to the Task Scheduler service. Additional Data: Error Value: %2. |
0xB000013D | 任务计划程序已启动任务引擎“%1”进程。 |
Task Scheduler started Task Engine \"%1\" process. |
0xB000013E | 任务计划程序已关闭任务引擎“%1”进程。 |
Task Scheduler shutdown Task Engine \"%1\" process. |
0xB000013F | 任务引擎“%1”已从任务计划程序服务接收到一条请求启动任务“%2”的消息。 |
Task Engine \"%1\" received a message from Task Scheduler service requesting to launch task \"%2\" . |
0xB0000140 | 任务引擎“%1”已从任务计划程序服务接收到一条请求停止任务实例“%2”的消息。 |
Task Engine \"%1\" received a message from Task Scheduler service requesting to stop task instance \"%2\" . |
0xB0000142 | 任务计划程序未启动任务“%1”,因为相同任务的实例“%2”正在运行。 |
Task Scheduler did not launch task \"%1\" because instance \"%2\" of the same task is already running. |
0xB0000143 | 为了启动新实例“%3”,任务计划程序已停止任务“%1”的实例“%2”。 |
Task Scheduler stopped instance \"%2\" of task \"%1\" in order to launch new instance \"%3\" . |
0xB0000144 | 任务计划程序已将任务“%1”的实例“%2”排入队列,并将在实例“%3”完成时立即启动实例“%2”。 |
Task Scheduler queued instance \"%2\" of task \"%1\" and will launch it as soon as instance \"%3\" completes. |
0xB0000145 | 任务计划程序已将任务“%1”的实例“%2”排队。 |
Task Scheduler queued instance \"%2\" of task \"%1\". |
0xB0000146 | 由于计算机正使用电池运行,任务计划程序没有启动任务“%1”。用户操作: 如果需要在使用电池时启动任务,请在任务配置中更改相应的标志。 |
Task Scheduler did not launch task \"%1\" because computer is running on batteries. User Action: If launching the task on batteries is required, change the respective flag in the task configuration. |
0xB0000147 | 任务计划程序停止了任务“%1”的实例“%2”,因为计算机正在切换到电池供电模式。 |
Task Scheduler stopped instance \"%2\" of task \"%1\" because the computer is switching to battery power. |
0xB0000148 | 任务计划程序停止了任务“%1”的实例“%2”,因为计算机不再空闲。 |
Task Scheduler stopped instance \"%2\" of task \"%1\" because computer is no longer idle. |
0xB0000149 | 由于超出为执行任务分配的时间(该时间在任务定义中配置),任务计划程序已终止“%1”任务的“%2”实例。用户操作: 增加已配置的任务超时或调查延迟的外部原因。 |
Task Scheduler terminated \"%2\" instance of the \"%1\" task due to exceeding the time allocated for execution, as configured in the task definition. User Action: Increase the configured task timeout or investigate external reasons for the delay. |
0xB000014A | 任务计划程序已按用户“%3”的请求停止了任务“%1”的实例“%2”。 |
Task Scheduler stopped instance \"%2\" of task \"%1\" as request by user \"%3\" . |
0xB000014B | 由于创建超时机制失败,因此即使是在指定的超时后,任务计划程序也将继续执行任务“%1”的实例“%2”。其他数据: 错误值: %3。 |
Task Scheduler will continue to execute Instance \"%2\" of task \"%1\" even after the designated timeout, due to a failure to create the timeout mechanism. Additional Data: Error Value: %3. |
0xB000014C | 由于当满足启动条件时用户“%2”未登录,任务计划程序没有启动任务“%1”。用户操作: 确保用户已登录或更改任务定义以允许用户被注销时启动。 |
Task Scheduler did not launch task \"%1\" because user \"%2\" was not logged on when the launching conditions were met. User Action: Ensure user is logged on or change the task definition to allow launching when user is logged off. |
0xB000014D | 任务计划程序未启动任务“%1”,因为目标会话为 RemoteApp 会话。用户操作: 如果需要启动 RemoteApp 会话上的任务,请在任务配置中更改相应的标志。 |
Task Scheduler did not launch task \"%1\" because target session is RemoteApp session. User Action: If launching the task on RemoteApp sessions is required, change the respective flag in the task configuration. |
0xB000014E | 由于目标会话是一个工作进程会话,任务计划程序未启动任务“%1”。 |
Task Scheduler did not launch task \"%1\" because target session is a WORKER session. |
0xB0000190 | 任务计划程序服务已启动。 |
Task Scheduler service has started. |
0xB0000192 | 任务计划程序服务正在关闭。 |
Task Scheduler service is shutting down. |
0xB0000193 | 任务计划程序服务在“%1”中遇到错误。其他数据: 错误值: %2。 |
Task Scheduler service has encountered an error in \"%1\" . Additional Data: Error Value: %2. |
0xB000019A | 任务计划程序服务无法设置唤醒计时器。因此,某些计划的任务可能未在系统暂停时运行。其他数据: 错误值: %1。 |
Task Scheduler service failed to set a wakeup timer. As a result, some scheduled tasks may not run while the system is suspended. Additional Data: Error Value: %1. |
0xB000019B | 任务计划程序服务已收到时间系统更改通知。 |
Task Scheduler service received a time system change notification. |
0xB00001F4 | 进程 ID %2 已对空闲任务 ID %1 进行注册。 |
Process ID %2 has registered idle task ID %1. |
0xB00001F5 | 进程 ID %2 已完成空闲任务 ID %1。 |
Process ID %2 has completed idle task ID %1. |
0xB00001F6 | 空闲任务 ID %1 的执行已开始。 |
Execution of idle task ID %1 has started. |
0xB00001F7 | 空闲任务 ID %1 的执行已结束。 |
Execution of idle task ID %1 has ended. |
0xB00001F8 | 已通知空闲任务 ID %1 已请求显式处理。 |
Idle task ID %1 has been notified that explicit processing has been requested. |
0xB00001F9 | 空闲任务 ID %1 已从其显式处理通知返回。 |
Idle task ID %1 has returned from its explicit processing notification. |
0xB00001FA | 已请求显式执行所有空闲任务。 |
Explicit execution of all idle tasks has been requested. |
0xB00001FB | 所有空闲任务的显式执行已完成。 |
Explicit execution of all idle tasks has completed. |
0xB00001FC | 正在显式执行所有空闲任务。 |
Explicit execution of all idle tasks is in progress. |
0xB00001FD | 接收到空闲任务电源通知: %1 (%2) |
Idle Task Power Notification Received: %1 (%2) |
0xB0000200 | 空闲检查点: 状态 %1,原因 %2。 |
Idle check point: State %1, Reason %2. |
0xB00002BC | 任务计划程序服务已启动任务兼容模块。 |
Task Scheduler service started Task Compatibility module. |
0xB00002C2 | 任务兼容模块无法将任务“%1”更新到要求的状态 %2。其他数据: 错误值: %3。 |
Task Compatibility module failed to update task \"%1\" to the required status %2. Additional Data: Error Value: %3. |
0xB00002C3 | 任务兼容模块无法删除任务“%1”。其他数据: 错误值: %2。 |
Task Compatibility module failed to delete task \"%1\" . Additional Data: Error Value: %2. |
0xB00002C4 | 任务兼容模块无法设置任务“%2”的安全描述符“%1”。其他数据: 错误值: %3。 |
Task Compatibility module failed to set security descriptor \"%1\" for task \"%2\" . Additional Data: Error Value: %3. |
0xB00002C5 | 任务兼容模块无法更新任务“%1”。其他数据: 错误值: %2。 |
Task Compatibility module failed to update task \"%1\" . Additional Data: Error Value: %2. |
0xB00002C6 | 任务兼容模块无法升级现有任务。将在下一次“任务计划程序”服务启动时重新尝试升级。其他数据: 错误值: %1。 |
Task Compatibility module failed to upgrade existing tasks. Upgrade will be attempted again next time 'Task Scheduler' service starts. Additional Data: Error Value: %1. |
0xB00002C7 | 任务兼容模块无法升级 NetSchedule 帐户“%1”。其他数据: 错误值: %2。 |
Task Compatibility module failed to upgrade NetSchedule account \"%1\" . Additional Data: Error Value: %2. |
0xB00002C8 | 任务兼容模块无法读取现有存储以升级任务。其他数据: 错误值: %1。 |
Task Compatibility module failed to read existing store to upgrade tasks. Additional Data: Error Value: %1. |
0xB00002C9 | 任务兼容模块无法加载要升级的任务“%1”。其他数据: 错误值: %2。 |
Task Compatibility module failed to load task \"%1\" for upgrade. Additional Data: Error Value: %2. |
0xB00002CA | 任务兼容模块无法注册要升级的任务“%1”。其他数据: 错误值: %2。 |
Task Compatibility module failed to register task \"%1\" for upgrade. Additional Data: Error Value: %2. |
0xB00002CB | 任务兼容模块无法删除 LSA 存储以进行升级。其他数据: 错误值: %1。 |
Task Compatibility module failed to delete LSA store for upgrade. Additional Data: Error Value: %1. |
0xB00002CD | 任务兼容模块无法确定是否需要升级。其他数据: 错误值: %1。 |
Task Compatibility module failed to determine if upgrade is needed. Additional Data: Error Value: %1. |
0xB0000320 | 维护状态已更改为 %1 (上次运行: %2)。 |
Maintenance state changed to %1 (Last Run: %2). |
0xB0000321 | 维护启动操作失败。其他错误信息: %1。 |
Maintenance launch operation failed. Additional error info: %1. |
0xB0000322 | 维护重新配置失败。其他错误信息: %1。 |
Maintenance re-configuration failed. Additional error info: %1. |
0xB0000323 | 维护计划程序引擎任务“%1”无法访问。其他错误信息: %2。 |
Maintenance Scheduler engine task \"%1\" cannot be accessed. Additional error info: %2. |
0xB0000324 | 维护计划程序已检测到下列维护任务的循环依赖关系: %1。 |
Maintenance Scheduler has detected cyclic dependency for the following maintenance tasks: %1. |
0xB0000325 | 维护任务“%1”超出截止时间。 |
Maintenance Task \"%1\" is behind deadline. |
0xB0000326 | 维护任务“%1”处理错误。其他错误信息 %2。 |
Maintenance task \"%1\" processing error. Additional error info %2. |
0xB0000327 | 维护完成(启动类型 %1)。 |
Maintenance complete (launch type %1). |
0xB0000328 | 维护任务“%1”请求在下次常规维护运行时唤醒计算机。 |
Maintenance Task \"%1\" requests computer wakeup during next regular maintenance run. |
0xB00003E6 | DEBUG!(%3:%4)“%1”失败。(%2)。 |
DEBUG! (%3:%4) \"%1\" failed. (%2). |
0xB00003E7 | DEBUG!“%1”。 |
DEBUG! \"%1\". |
0xB00100C9 | 任务计划程序已成功完成任务“%1”、实例“%2”、操作“%3”,返回代码为 %4。 |
Task Scheduler successfully completed task \"%1\" , instance \"%2\" , action \"%3\" with return code %4. |