服务无法启动错误1920

发布于 2024-10-06 19:43:31 字数 275 浏览 0 评论 0原文

在某些机器上,我们在安装服务时出现以下错误: “服务...无法启动。请验证您是否有足够的权限来启动系统服务。”

服务安装得很好,只是它无法从 Services.msc 作为网络服务启动。 如果从控制台启动它是可执行的,服务启动并运行良好...

作为本地系统启动的另一个服务也会发生同样的情况。

在其他机器上一切都很好。服务作为网络服务启动,没有任何问题。

我们认为是windows权限的问题,就像错误所说的那样,但是如何检查呢?该怎么办?

谢谢, 阿德里亚

On some machine we have the following error at service install:
"Service ... failed to start. Verify that you have sufficient privileges to start system services."

Service is installed fine tho, just that it can't be started as Network Service from Services.msc.
Service starts and runs good if started from console it's executable...

Same thing happens with another service started as Local System.

On other machines everything is fine. Service starts as network service with no problems.

We think is a problem with windows rights, like error says, but how to check? And what to do?

Thanks,
Adrya

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

临风闻羌笛 2024-10-13 19:43:31

刚刚在 2016 年服务器上安装一个非常旧的应用程序时得到了这个。我们有两个障碍 - 确保我们启动服务的帐户在本地组策略中具有“作为服务登录”权限。

另一个 - 我们已经在这个新应用程序的 config.xml 中的默认端口上运行另一个应用程序,因此我们只是更改为不同的端口并保存配置文件,而安装程序仍然显示错误,然后单击重试并成功。

Just got this from installing a really old app on server 2016. We had two hurdles- ensuring that the account we were starting the service with had 'log on as a service' rights in local group policy.

The other- we were already running another app on the default port that this new app had in it's config.xml, so we just changed to a different port and saved the config file while the installer still had an error displayed, then clicked retry and success.

素食主义者 2024-10-13 19:43:31

经过更多调查,我们发现在服务配置文件中添加此内容可以解决问题:

<runtime>
    <generatePublisherEvidence enabled="false"/>
</runtime>

http: //msdn.microsoft.com/en-us/library/bb629393.aspx

我们建议服务使用 元素来提高启动性能。使用此元素还可以帮助避免可能导致超时和服务启动取消的延迟。

After more investigation we discovered that adding this in service configuration file fixed the problem:

<runtime>
    <generatePublisherEvidence enabled="false"/>
</runtime>

http://msdn.microsoft.com/en-us/library/bb629393.aspx

We recommend that services use the <generatePublisherEvidence> element to improve startup performance. Using this element can also help avoid delays that can cause a time-out and the cancellation of the service startup.

疧_╮線 2024-10-13 19:43:31

只是想添加我的解决方案,以防有人像我一样遇到这个问题...

我有一个 .msi 文件,一旦我为其生成了日志:

msiexec -i package.msi /L*V package.log

在日志文件中包含以下内容:

Error 1920. Service 'Controller 01' (Controller01) failed to start. Verify that you have sufficient privileges to start system services.
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 2052 could not be cancelled. Error: 1168
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 5396 could not be cancelled. Error: 1168
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 5404 could not be cancelled. Error: 1168
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 1448 could not be cancelled. Error: 1168
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 1904 could not be cancelled. Error: 1168
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 1088 could not be cancelled. Error: 1168
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 6952 could not be cancelled. Error: 1168
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 6956 could not be cancelled. Error: 1168

查看事件查看器没有帮助,因此在安装程序上单击“取消”之前,我转到了硬盘驱动器上的服务位置,然后尝试以管理员身份运行它。此时,我得到了一条线索,最终解决了这个问题:

MSVCR120.dll was not found

此时,我转到 c:\windows\system32 并查找 DLL...,它就在那里。于是,我直接将其复制到.exe所在的目录中,然后尝试再次运行。这次我收到了不同的错误消息:

应用程序无法正确启动 (0xc000007b)

对于“0xc000007b”的含义,我发现 此处它的含义:“错误 0xc000007b 表示 STATUS_INVALID_IMAGE_FORMAT。这意味着应用程序尝试加载具有错误 CPU 架构的 DLL,因此 32 位应用程序会尝试加载 64 位 Dll 或相反(64 位应用程序会尝试加载)。加载 32 位 DLL)。”

因此,就我而言,安装程序的发布者未能包含 Visual Studio 2013 的 x86 Visual C++ Redistributable Package。安装并重新启动后,我重新运行了安装程序,它成功了。

Just wanted to add my solution in case someone runs across this like I did...

I had a .msi file that once I generated a log for it:

msiexec -i package.msi /L*V package.log

had this in the logfile:

Error 1920. Service 'Controller 01' (Controller01) failed to start. Verify that you have sufficient privileges to start system services.
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 2052 could not be cancelled. Error: 1168
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 5396 could not be cancelled. Error: 1168
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 5404 could not be cancelled. Error: 1168
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 1448 could not be cancelled. Error: 1168
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 1904 could not be cancelled. Error: 1168
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 1088 could not be cancelled. Error: 1168
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 6952 could not be cancelled. Error: 1168
MSI (s) (04:5C) [12:23:11:831]: I/O on thread 6956 could not be cancelled. Error: 1168

Looking in the Event Viewer was no help, so before I hit cancel on the installer, I went to the location of the service on the hard drive and tried to run it as an administrator. At which point, I got a clue that led me to ultimately fix this:

MSVCR120.dll was not found

At which point, I went to c:\windows\system32 and looked for the DLL... and it was there. So, I copied it directly into the directory with the .exe and tried to run it again. This time I got a different error message:

The application was unable to start correctly (0xc000007b)

Searching for the meaning of "0xc000007b", I found here what it signifies: "The error 0xc000007b means STATUS_INVALID_IMAGE_FORMAT. This means an application tries to load DLLs with the wrong CPU architecture. So a 32Bit application tries to load 64Bit Dlls or the opposite (64Bit app tries to load 32Bit DLLs)."

So in my case, the publisher of the installer failed to include the x86 Visual C++ Redistributable Package for Visual Studio 2013. After installing that and rebooting, I reran the installer and it worked.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文