SQL 2008开发人员无法连接到服务器 [英] SQL 2008 developer cannot connect to server
本文介绍了SQL 2008开发人员无法连接到服务器的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
我需要帮助以弄清楚为什么我无法连接到服务器.我运行了修复CD并获得了此摘要文件.还有一个详细的文件，但是很长.
这是摘要文件:
I need help to figure why I cannot connect to server. I ran the repair CD and got this summary file. There is also a detailed file but it is very long.
Here is the summary file:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068119551
Exit facility code: 1211
Exit error code: 1
Exit message: Failed: see details below
Start time: 2012-06-29 20:50:03
End time: 2012-06-29 21:16:18
Requested action: Repair
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120629_204646\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0x0AADD6DA%400xDC80C325
Machine Properties:
Machine name: MIBELOVED-PC
Machine processor count: 2
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Database Engine Services 1033 Developer Edition 10.50.1617.0 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER SQL Server Replication 1033 Developer Edition 10.50.1617.0 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Full-Text Search 1033 Developer Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSAS10_50.MSSQLSERVER Analysis Services 1033 Developer Edition 10.50.1617.0 No
Sql Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER Reporting Services 1033 Developer Edition 10.50.1617.0 No
Sql Server 2008 R2 Management Tools - Basic 1033 Developer Edition 10.50.1617.0 No
Sql Server 2008 R2 Management Tools - Complete 1033 Developer Edition 10.50.1617.0 No
Sql Server 2008 R2 Client Tools Connectivity 1033 Developer Edition 10.50.1617.0 No
Sql Server 2008 R2 Client Tools Backwards Compatibility 1033 Developer Edition 10.50.1617.0 No
Sql Server 2008 R2 Client Tools SDK 1033 Developer Edition 10.50.1617.0 No
Sql Server 2008 R2 Integration Services 1033 Developer Edition 10.50.1617.0 No
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: D:\x64\setup\
Installation edition: DEVELOPER
User Input Settings:
ACTION: Repair
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: .\SQL2008SBSSQLAgent
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASCONFIGDIR: Config
ASDOMAINGROUP: <empty>
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120629_204646\ConfigurationFile.ini
ENU: True
FAILOVERCLUSTERGROUP: <empty>
FAILOVERCLUSTERNETWORKNAME: <empty>
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
PASSPHRASE: *****
QUIET: False
QUIETSIMPLE: False
SQLDOMAINGROUP: <empty>
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: *****
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120629_204646\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xDC80C325
Configuration error description: The name has already been shared
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120629_204646\Detail.txt
Configuration status: Failed: see details below
Configuration error code: 0x30E00066@1211@1
Configuration error description: Service 'SQLSERVERAGENT' stop request failed.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120629_204646\Detail.txt
Feature: SQL Client Connectivity
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Writer
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Browser
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xDC80C325
Configuration error description: The name has already been shared
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120629_204646\Detail.txt
Configuration status: Failed: see details below
Configuration error code: 0x30E00066@1211@1
Configuration error description: Service 'SQLSERVERAGENT' stop request failed.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120629_204646\Detail.txt
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xDC80C325
Configuration error description: The name has already been shared
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120629_204646\Detail.txt
Configuration status: Failed: see details below
Configuration error code: 0x30E00066@1211@1
Configuration error description: Service 'SQLSERVERAGENT' stop request failed.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120629_204646\Detail.txt
Feature: Analysis Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Integration Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Compact Edition Tools
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Compact Edition Runtime
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Connectivity
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Business Intelligence Development Studio
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Books Online
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync Framework
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120629_204646\SystemConfigurationCheck_Report.htm
The following warnings were encountered while configuring settings on your SQL Server. These resources / settings were missing or invalid so default values were used in recreating the missing resources. Please review to make sure they don’t require further customization for your applications:
Service SID support has been enabled on the service.
Service SID support has been enabled on the service.推荐答案
It sounds like your repair isn''t working properly because it is not configured properly. The message "The name has already been shared" seems to be the key indicator of this. Either there is a configuration piece that you are not setting up properly or it wasn''t configured properly during the first installation. This MSDN page seems to have some answers:
http://social.msdn.microsoft.com/Forums/fa-IR/sqlexpress/thread/90c61aef-f8e1-45ab-a37c-b1ce3ec67e03[^]
My suggestion would be to first assess if you really have a problem. Use the PortQuery or PortQueryUI tool to figure out if the correct ports are open on your machine. Here is a link to that tool:
http://www.microsoft.com/en-us/download/details.aspx?id=24009[^]
Next, if you are sure there is a problem, I would recommend completely uninstalling SQL server and then reinstalling it after a reboot. Maybe something got corrupted during the installation. A complete redo should fix the issue. Don''t forget, though, that you will need to adjust your firewall and configure SQL before you will be able to access it remotely.
It sounds like your repair isn''t working properly because it is not configured properly. The message "The name has already been shared" seems to be the key indicator of this. Either there is a configuration piece that you are not setting up properly or it wasn''t configured properly during the first installation. This MSDN page seems to have some answers:
http://social.msdn.microsoft.com/Forums/fa-IR/sqlexpress/thread/90c61aef-f8e1-45ab-a37c-b1ce3ec67e03[^]
My suggestion would be to first assess if you really have a problem. Use the PortQuery or PortQueryUI tool to figure out if the correct ports are open on your machine. Here is a link to that tool:
http://www.microsoft.com/en-us/download/details.aspx?id=24009[^]
Next, if you are sure there is a problem, I would recommend completely uninstalling SQL server and then reinstalling it after a reboot. Maybe something got corrupted during the installation. A complete redo should fix the issue. Don''t forget, though, that you will need to adjust your firewall and configure SQL before you will be able to access it remotely.
这篇关于SQL 2008开发人员无法连接到服务器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
查看全文
