请求失败或者服务没有及时响应?

发布于 2024-08-09 05:38:40 字数 333 浏览 5 评论 0原文

当我使用 Windows 身份验证连接到 SQL Server 2008 Management Studio 时,出现以下错误。

"The request failed or the service did not respond in a timely fashion.
Consult the event log or other applicable error logs for details."

有人告诉我为什么我会收到此错误,而我的 SQL Server 正在 a/c 内置的网络服务下运行???

我用谷歌搜索但没有得到解决方案..

谢谢

I have the following error while I connect to SQL Server 2008 Management Studio with Windows authentication.

"The request failed or the service did not respond in a timely fashion.
Consult the event log or other applicable error logs for details."

Is anybody tell me why i am getting this error, whereas my SQL Server is running under network service built in a/c????

I googled it but not getting solution..

Thanks

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

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

发布评论

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

评论(21

纵性 2024-08-16 05:38:40

有同样的问题,我解决了。

  1. 打开 SQL Server 配置管理器
  2. 单击 SQL Server 服务(左侧)
  3. 双击我想要启动的 SQL Server 实例
  4. 日志中选择内置帐户单选按钮在 选项卡上,从下拉菜单中选择本地系统
  5. 单击底部的应用,然后右键单击实例并选择启动

Had the same problem, I fixed it.

  1. Open SQL Server Configuration manager
  2. Click on the SQL Server Services (on the left)
  3. Double-click on the SQL Server Instance that I wanted to start
  4. Select the Built-in account radio button in the Log On tab and choose Local system from the dropdown menu
  5. Click apply at the bottom, then right click the instance and select Start
如何视而不见 2024-08-16 05:38:40

上述问题发生在我的本地系统中。检查 sql server 配置管理器。
第 1 步:
SQL Server 网络配置
步骤 2:

  • 本地服务器名称的
  • 协议 协议名称 VIA 是否禁用..
  • 如果未禁用,禁用并检查

..在我进行更改后,sql server 浏览器开始工作

Above mentioned issue happened in my local system. Check in sql server configuration manager.
Step 1:
SQL server Network configuration
step 2:

  • Protocols for local server name
  • Protocol name VIA Disabled or not..
  • if not disabled , disable and check

.. after I made changes the sql server browser started working

情释 2024-08-16 05:38:40

这确实有效 - 我验证了很多网站并终于得到了答案。

当 master.mdf 或 mastlog.ldf 损坏时,可能会发生这种情况。为了解决该问题,请转到以下路径。

C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL ,在那里你会找到一个文件夹“Template Data”,复制 master.mdf 和 mastlog.ldf 并将其替换为

C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA 文件夹。

就是这样。现在启动 MS SQL 服务就完成了。

This really works - i had verified lot of sites and finally got the answer.

This may occurs when the master.mdf or the mastlog.ldf gets corrupt . In order to solve the issue goto the following path.

C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL , there you will find a folder ” Template Data ” , copy the master.mdf and mastlog.ldf and replace it in

C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA folder .

That's it. Now start the MS SQL service and you are done.

┼── 2024-08-16 05:38:40

如果您在本地环境中运行 SQL Server,而不是通过 TCP/IP 连接运行。转到“SQL Server 配置管理器”下的“协议”、“属性”,然后禁用 TCP/IP。完成此操作后,重新启动服务时错误消息将消失。

If you are running SQL Server in a local environment and not over a TCP/IP connection. Go to Protocols under SQL Server Configuration Manager, Properties, and disable TCP/IP. Once this is done then the error message will go away when restarting the service.

北城半夏 2024-08-16 05:38:40

当我遇到同样的问题时,这非常乏味。当我遇到这个问题时,我卸载了 SQL Server 2008,但再次安装 SQL Server 2008 后,我遇到了同样的问题。我非常紧张,而且我没有从任何网站得到任何帮助。

来克服这个问题。您只需进入 SQL Server 配置管理器,然后单击左侧面板上的协议即可。如果您运行网络服务,只需禁用“VIA”协议。
之后尝试启动 SQL 服务,它将成功运行。

It was very tedious when I get same problem. When I got this problem, I uninstall my SQL Server 2008 but after installing the SQL Server 2008 again,I got the same problem. I was so tensed plus, I had not gotten any help from any site.

To over come this problem. Simply You Need to go on SQL Server Configuration Manager and then click On Protocols on left panel. If you running Network service just disable 'VIA' Protocol.
And after that try to start your SQL service it will run successfully.

甜味超标? 2024-08-16 05:38:40

如果您最近更改了与服务帐户关联的密码:

  1. 启动SQL Server 配置管理器
  2. 在左侧窗格中选择SQL Server 服务
  3. 右键单击右侧窗格中您尝试启动的服务,然后单击属性
  4. 输入新密码并确认密码。

If you recently changed the password associated with the service account:

  1. Start SQL Server Configuration Manager.
  2. Select SQL Server Services in the left pane.
  3. Right click the service you are trying to start in the right pane and click Properties.
  4. Enter the new Password and Confirm password.
等风也等你 2024-08-16 05:38:40

在追踪这个问题几个小时后,我们在 SQL Server 代理日志中发现了一条日志,内容如下:

This installation of SQL Server Agent is disabled. The edition of SQL server that installed this service does not support SQL server agent.

我们正在使用 SQL Server Express。经过一番谷歌搜索后,似乎 SQL Server Express 不支持 SQL Server Agent。

我没有找到 Microsoft 的直接通信表明 SQL Express 不支持 SQL Server Agent,但是这种情绪似乎在许多论坛上得到回应。

After chasing this issue for some hours, we found an log in the SQL Server Agent logs stating the following:

This installation of SQL Server Agent is disabled. The edition of SQL server that installed this service does not support SQL server agent.

We were using SQL Server Express. After some Googling it appears SQL Server Express does not support SQL Server Agent.

I didn't find a direct piece of Microsoft communications stating that SQL Express doesn't support SQL Server Agent, however this sentiment seems to be echoed across many forums.

简单爱 2024-08-16 05:38:40

就我而言,问题是我正在运行另外两个 SQL Server 实例(或至少其中一个)导致冲突。

解决方案只是停止其他 SQL Server 实例及其附带的 SQL Server 代理。

停止 sql服务器服务

当我这样做时,我还建议确保在服务器的协议设置中启用命名管道

SQL Server 命名管道协议 1

命名的 SQL Server 协议管道2

In my case, the issue was that I was running two other SQL Server instances which were (or at least one of them was) causing a conflict.

The solution was simply to stop the other SQL Server instance and its accompanying SQL Server Agent.

stop sql server service

While I'm at it, I'll also recommend making sure Named Pipes is enabled in your server's protocol settings

SQL Server Protocols Named Pipes 1

SQL Server Protocols Named Pipes 2

一花一树开 2024-08-16 05:38:40

我从事件日志中发现 My SQL Server 评估已过​​期。
我需要升级或需要使用社区版。

I found from event logs that My SQL server evaluation has expired.
I needed to upgrade or needed to use community edition.

爱,才寂寞 2024-08-16 05:38:40

我有类似的问题。下一个解决方案是在*情况下无法本地启动服务器*,您将看到相同的错误消息。(图 1)

在此处输入图像描述
图片 1

在此输入图像描述
Imagen 2

要解决该问题并使服务器正常工作,您必须执行后续步骤。

  1. 转到 SQL Server Services
  2. 右键单击​​打开属性
  3. 转到登录选项卡(默认情况下,您将看到类似图 3 的内容)
  4. 选择单选按钮内置帐户(图4)
  5. 单击确定
  6. 返回SQL Server Services并再次启动服务器(图5)
    之后您必须能够看到运行它。

图片 3
图片 3

在此处输入图像描述
图片 4

在此处输入图像描述
图片 5

我希望它对您或其他有类似问题的人有用。关注我获取更多提示。

I had a similar issue. The next solution is in *case to can't launch the server Locally * and you will see the same error msg.(Image 1)

enter image description here
Imagen 1

enter image description here
Imagen 2

To solve that and have the server working you must have the next steps.

  1. Go to SQL Server Services
  2. Right click to open properties
  3. Go to LogOn tab (By default you will see something like Image 3)
  4. Select the radio button Built-in account (Image 4)
  5. Click on Ok
  6. Go back to SQL Server Services and launch again the server (Image 5)
    After that you must be able to see run it.

Image 3
Image 3

enter image description here
Image 4

enter image description here
Image 5

I hope that works for you or others with similar issues. Follow me for more tips.

┈┾☆殇 2024-08-16 05:38:40

只需在sql server配置管理器中禁用VIA协议即可

Just disable the VIA protocol in sql server configuration manager

痴者 2024-08-16 05:38:40

对我来说,一个简单的 Windows 更新就解决了这个问题,我希望我之前尝试过。

For me a simple windows update fixed it, I wish I tried it before.

囚你心 2024-08-16 05:38:40

我安装了 SQL 2017,并且在免费试用/评估期结束时发生此问题,问题的解决方案如下:

1 - 转到 Windows 开始按钮,找到 Microsoft SQL Server 20XX 文件夹

2- 然后,SQL Server 20XX安装中心

3- 在左侧,选择“维护”选项

4- 然后单击“版本升级”

5- 然后在组合框中选择“开发人员”选项,然后单击“下一步”按钮

6- 单击“版本升级”选项我接受许可条款”,然后下一步

7- 最后,单击“下一步”,然后单击“升级”,等待大约 15 分钟。

8-之后,在“Services.msc”中重新启动 SQL Server 服务并再次打开 SQL,它应该可以工作。
如需了解更多信息,请观看此视频:https://www.youtube.com/watch?v= EVG35ahjec

I have SQL 2017 installed and this issue happens when the free trial / evaluation period ends, the solution to the problem is the following:

1 - Go to the windows start button, find the Microsoft SQL Server 20XX folder

2- Then, SQL Server 20XX Installation Center

3- On the left, select the option "Maintenance"

4- Then click on “Edition upgrade”

5- Then in the combox select "developer" option, and then click on “next” button

6- Click on the option "I accept the license terms" and then next

7- Finally, click on "Next" and click on "Upgrade", and wait approximately 15 minutes.

8- After this, restart the SQL Server service in "Services.msc" and open SQL again, it should work.
For more information: watch this video: https://www.youtube.com/watch?v=EVG35ahhjec

优雅的叶子 2024-08-16 05:38:40

我认为这个解决方案更合适,因为它不会阻止你使用TCP/IP访问。

在 Windows 防火墙中打开端口以进行 TCP 访问

在“开始”菜单上,单击“运行”,键入 WF.msc,然后单击“确定”。

在高级安全 Windows 防火墙的左窗格中,
右键单击“入站规则”,然后单击操作窗格中的“新建规则”。

在“规则类型”对话框中,选择“端口”,然后单击“下一步”。

在“协议和端口”对话框中,选择“TCP”。选择具体
本地端口,然后键入该实例的端口号
数据库引擎,例如默认实例的 1433。单击“下一步”。

在“操作”对话框中,选择“允许连接”,然后单击
下一步。

在“配置文件”对话框中,选择描述
当您要连接到计算机时的连接环境
数据库引擎,然后单击“下一步”。

在“名称”对话框中,键入此规则的名称和说明,然后
然后单击“完成”。

(来源:https://msdn.microsoft.com/en-us/library/ ms175043.aspx)

I think this solution is more appropriate, because it does not prevent you from using TCP/IP access.

To open a port in the Windows firewall for TCP access

On the Start menu, click Run, type WF.msc, and then click OK.

In the Windows Firewall with Advanced Security, in the left pane,
right-click Inbound Rules, and then click New Rule in the action pane.

In the Rule Type dialog box, select Port, and then click Next.

In the Protocol and Ports dialog box, select TCP. Select Specific
local ports, and then type the port number of the instance of the
Database Engine, such as 1433 for the default instance. Click Next.

In the Action dialog box, select Allow the connection, and then click
Next.

In the Profile dialog box, select any profiles that describe the
computer connection environment when you want to connect to the
Database Engine, and then click Next.

In the Name dialog box, type a name and description for this rule, and
then click Finish.

(Source: https://msdn.microsoft.com/en-us/library/ms175043.aspx)

£烟消云散 2024-08-16 05:38:40

如果您仍在滚动浏览答案,那么您可能还错过了一步。

使用管理员访问权限打开 SQL Server 配置管理器。

首先应用更改(到本地系统),然后尝试运行。

输入图片此处描述

If you are still scrolling through the answers, here is one more step you might have missed.

Open SQL server configuration manager with admin access.

Apply the changes first(to local System) and then try to run.

enter image description here

守望孤独 2024-08-16 05:38:40

如果您在企业或企业环境中使用“管理工具”下的“计算机管理”或“SQL Server 配置管理器”来配置 SQL Server 连接,
确保您以管理员身份打开计算机管理或 SQL Server 配置管理器,或者您已

管理权限

上面的所有答案对我来说都不起作用,但是当我以管理模式运行它时,我现在可以启动我的 SQL Server 代理或 SQL Server 服务。

If you are configuring your SQL Server connection using Computer Management under Administrative Tools or SQL Server Configuration Manager in Enterprise or Corporate environment,
make sure you open your Computer Management or SQL Server Configuration Manager as an Administrator or you have

Administrative Privileges

All answers above didn't work for me, but when I run it as Administrative mode, I can now start my SQL Server Agent or SQL Server service.

假面具 2024-08-16 05:38:40

对我来说,当我卸载 Microsoft Visual C++ 2015-2020 Redistributable 并安装 Microsoft Visual C++ 2017 版本时,也发生了类似的问题

。重新安装 Microsoft Visual C++ 2015-2020 Redistrubutable 版本时修复了此问题。然后服务自动启动。

For me happened similar issue when I did uninstall Microsoft Visual C++ 2015-2020 Redistributable and installed the Microsoft Visual C++ 2017 version

Fixed this issue when re-installed Microsoft Visual C++ 2015-2020 Redistrubutable versions. then services started automatically.

划一舟意中人 2024-08-16 05:38:40

尝试从不同的帐户更改登录名:

  1. 管理员身份打开 SQL Server 配置管理器。
  2. 右键单击“SQL 服务器”和“SQL Server 集成服务”。
  3. 转到属性并选择登录。
  4. 选择内置帐户。
  5. 选择本地服务。
  6. 申请并确定。
  7. 再次开始服务。

Try changing login from different account:

  1. Open SQL Server Configuration Manager as Admin.
  2. Right click SQL sever and SQL Server Integration Services.
  3. Go to Properties and choose Log on.
  4. Choose Built in account.
  5. Select local service.
  6. Apply and Ok.
  7. Start service again.
嗼ふ静 2024-08-16 05:38:40

这是因为您的两个 SQL Server 使用相同的 TCP 端口号,即 1433,并且一次只能有一台服务器在此端口上运行。您必须从以下设置中更改或删除端口号

  1. 在 SQL Server 配置管理器中,单击“SQL Server 网络配置”。
  2. 点击所需的 SQL 协议...
  3. 双击“TCP/IP”,然后选择“IP 地址”选项卡。
  4. 向下滚动以结束双击 TCP 端口文本框。
  5. 将端口号从 1433 更改为其他端口号或将其删除。

保存这些设置后,立即启动所需的服务器。

祝你好运
关注这些步骤

This is beacuse your both SQL Servers are using same TCP Port Number i.e. 1433 and only one server could run at this port at a time. You have to change or Remove Port number from below settings;

  1. In SQL Server Configuration Manager Click on SQL Server Network Configration.
  2. Click on required Protocols for SQL...
  3. Double click on TCP/IP then select IP Address tab.
  4. Scroldown to end double click in TCP Port Textbox.
  5. Change Port number from 1433 to other one or remove it.

After save these settings now Start your required server.

Good Luck
Follow These Steps

塔塔猫 2024-08-16 05:38:40

另请检查您是否有 Express 版本或开发人员版本
因为 Express 版本不允许

Also check you have Express edition or developer edition
cause Express edition don't allow

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