sql数据库安装失败

SQL Server数据库连接失败错误及解决方法在使用SQL Server 的过程中，用户遇到的最多的问题莫过于连接失败了。

一般而言，有以下两种连接SQL Server 的方式，一是利用SQL Server 自带的客户端工具，如企业管理器、查询分析器、事务探查器等;二是利用用户自己开发的客户端程序，如ASP 脚本、VB程序等，客户端程序中又是利用ODBC 或者OLE DB 等连接SQL Server。

下面，我们将就这两种连接方式，具体谈谈如何来解决连接失败的问题。

一、客户端工具连接失败在使用SQL Server 自带的客户端工具(以企业管理器为例)连接SQL Server时，最常见的错误有如下一些：1、SQL Server 不存在或访问被拒绝ConnectionOpen (Connect())2、用户'sa'登录失败。

原因：未与信任SQL Server 连接相关联。

3、超时已过期。

下面我们依次介绍如何来解决这三个最常见的连接错误。

第一个错误"SQL Server 不存在或访问被拒绝"通常是最复杂的，错误发生的原因比较多，需要检查的方面也比较多。

一般说来，有以下几种可能性：1、SQL Server名称或IP地址拼写有误;2、服务器端网络配置有误;3、客户端网络配置有误。

要解决这个问题，我们一般要遵循以下的步骤来一步步找出导致错误的原因。

首先，检查网络物理连接：ping <服务器IP地址>或者ping <服务器名称>如果ping <服务器IP地址> 失败，说明物理连接有问题，这时候要检查硬件设备，如网卡、HUB、路由器等。

还有一种可能是由于客户端和服务器之间安装有防火墙软件造成的，比如ISA Server。

防火墙软件可能会屏蔽对ping、telnet 等的响应，因此在检查连接问题的时候，我们要先把防火墙软件暂时关闭，或者打开所有被封闭的端口。

SQL2000数据库安装提示挂起的处理方法
安装SQL 2000的过程中，有时候可能会遇到下图提示挂起的问题，那么遇到这样的问题需要怎么解决呢？
下面给大家提供两种处理方法：
一、通过执行处理挂起的工具处理
处理SQL2000安装挂起提示的工具下载地址：点击下载
下载后解压文件，直接双击解压后的.reg后缀名的文件执行完毕后，再安装SQL2000数据库即可。

二、手动删除注册表相关项值
具体操作步奏如下：
1.电脑开始→运行中输入regedit，回车；
2.到注册表：
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager 位置；
3.在右边窗口找到注册表PendingFileRenameOperations项，右键选择删除，然后确认。

以上步奏操作完以后，再重新安装SQL 2000数据库即可.
特殊情况：有时候上述两种方法都试过了，安装SQL 2000数据库时还会有挂起提示的问题，出现这个现象的时候，重启下电脑，然后按第二种处理方法，手动删除注册表项值，然后再安装SQL 2000
数据库就可以正常安装了。

SQl server 2008 附加数据库失败如何解决
通过附加功能添加现成的数据库是非常方便的，然而有时会出现附加数据库失败。

那么，我们该如何解决此问题？
方法一、
1.
找到要添加数据库的.mdf文件，点击右键，选择属性。

2.
在属性页面点击安全，选择Authenticated Users，单击编辑
3. 3
Authenticated Users权限中选择完全控制，点击确定，点击属性界面的确定。

4.
同理，右键点击数据库的.ldf文件，打开属性。

按以上步骤再次设置即可。

5.
完成以上步骤，再进行附加数据库，这时就可以。

END
方法二、
1.打开数据库实例的安装目录，打开ＤＡＴＡ文件夹。

（如我的实例目录地
址为：D:\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA 也可能当时安装时装在C盘了)
2.将要附加的数据库．ｍｄｆ文件和．ｌｄｆ文件，剪切或复制到ＤＡＴＡ
文件夹里。

3.完成以上步骤，再次附加数据库。

这时就可以了。

SQL Server 2008 安装过程及部分错误解决本文分为三部分：一、SQL Server 2008完全卸载过程二、SQL Server 2008安装过程三、我在安装过程中所遇到的问题及解决办法（1）创建窗口句柄之前，不能在控件上调用Invoke或BeginInvoke的错误解决办法（2）找不到方法“boolean microsoft.sqlserver.configuration.msiextensionmetadata.get_isslipstreamorpatch()"（3）“试图执行未授予权限”（4）出现以下错误:对路径“C:\Windows\system32\perf-ReportServer$MSSQLSERVER3-rsctr.dll”的访问被拒绝。

（5）“重启电脑失败”一、SQL Server 2008完全卸载1、程序与功能中，右键SQL Server 2008删除2、进入删除SQL Server 2008，一路下一步下去3、在程序和功能中，还有SQL Server 2008相关如果前面卸载比较顺利，相关的组件不多，继续删除SQL Server 2008 Native Client等红框中的组件4、如果前面没有卸载干净，下载Windows Installer Clean UP选择SQL Server 2008相关移除再使用SRVINSTW移除SQL Server 2008相关服务。

我后来卸载的时候，在程序和功能卸的就很干净，用不着这两个小工具了。

5、清理注册表：开始-运行-regedit.exe在注册表里找到对应的文件夹，删除（1）HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ Microsoft SQL Server（2）HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server Native Client 10.0（3）HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer（4）HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server下面是我在网上搜到还需要删除的文件夹，但是我一般就删除上面的文件夹就好。

SQL数据库安装过程问题解决SQL Server 2000有四个正式版本：企业版/标准版/个人版/开发版问题1 安装数据库的时候提示下面的对话框，确定以后在安装定义的窗口“服务器和客户端工具”是灰的，只能选择仅安装客户端工具。

解决方法a).SQL server不同版本的安装与操作系统是否支持直接有关。

b).SQL server 2000以前的版本，例如7.0一般不存在多个版本，只有标准版跟桌面版。

用户如果不清楚该装什么版本的话，可按安装上的安装先决条件指示安装，一般在WIN2000 服务器版上装标准版，其他的系统装桌面版的就可以。

Windows 2000 的Server版本，可以安装SQL Server 2000的任何版本，Professional版本只能安装SQL Server 2000的个人版、开发版、评估版、MCDE。

所以，操作系统可能是Home版本，不支持SQL Server 2000的企业版本，选择安装个人版就可以了。

c).PS: XP Professional SP2，不支持SQL企业版。

d).SQL Server 2000 企业版(必须在WIN 2000 SERVER服务器版本上安装)作为生产数据库服务器使用。

支持SQL Server 2000中的所有可用功能，并可根据支持最大的Web 站点和企业联机事务处理（OLTP）及数据仓库系统所需的性能水平进行伸缩。

e).SQL Server 2000标准版(必须在WIN2000 SERVER服务器版本上安装)作为小工作组或部门的数据库服务器使用。

f).SQL Server 2000 个人版(可以在WINXP上安装)供移动的用户使用，这些用户有时从网络上断开，但所运行的应用程序需要SQL Server数据存储。

在客户端计算机上运行需要本地SQL Server数据存储的独立应用程序时也使用个人版。

g).SQL Server 2000开发版(可以在WINXP上安装)供程序员用来开发将SQL Server 2000用作数据存储的应用程序。

SQL数据库连接失败的解决办法In the process of using SQL Server, the most problem that users encounter is that the connection fails. Generally speaking, there are two ways to connect to the SQL Server, one is to use SQL built-in Server client tools, such as enterprise manager, query analyzer, profiler; two is the use of users to develop their own client programs, such as ASP, VB script program, the client program and the use of ODBC or OLE DB connection SQL Server. Next, we will talk about these two ways of connection, specifically how to solve the problem of connection failure.First, the client tool connection failedWhen using SQL Server's own client tool (for example, enterprise manager) to connect to SQL Server, the most common errors are as follows:1, SQL Server does not exist or access is deniedConnectionOpen (Connect ())2, user'sa'logon failed. Reason: not associated with trusted SQL Server connection.3, the timeout has expired.Here we are in turn explaining how to solve the three most common connection errors.The first error, "SQL Server does not exist or is denied access", is usually the most complex, the reason for the error isrelatively large, and there are more aspects to be examined. Generally speaking, there are several possibilities:1, the SQL Server name or IP address spelled incorrectly;2, server-side network configuration is wrong;3, the client network configuration is wrong.To solve this problem, we usually follow the following steps to find out the cause of the error step by step.First, check the network physical connection:Ping < server IP address >perhapsPing < server name >If Ping < server IP address > fail to indicate physical connection problem, check hardware equipment such as network card, HUB, router and so on. Another possibility is that firewall software is installed between the client and the server, such as ISA Server. Firewall software may mask the response to Ping, Telnet, and so on, when checking connection problems, we have to temporarily shut down firewall software, or open all closed ports.If Ping < server IP address > successful and Ping < server name > failed, then the name resolve problem, at this time to checkthe DNS service is normal. Sometimes the client and the server is not in the same LAN, this is probably not directly use the server name to identify the server, we can use the HOSTS file to name resolution, the specific method:1, use Notepad to open the HOSTS file (usually inC:\WINNT\system32\drivers\etc)2, add a IP address and server name corresponding records, such as:172.168.10.24 MyserverYou can also configure it in the SQL Server client network utility, which will be described in detail later.Next, check the SQL Server server working state using the telnet command:Telnet < server IP address > 1433If the command is executed successfully, can see the cursor in the upper left corner of the screen flash flashing, indicating that the SQL Server server is working, and is listening on port 1433 TCP/IP connection; if a command returns "cannot open connection" error message, the server does not start the SQL Server service, the server may not enable the TCP/IP protocol server, or not in the SQL Server default port 1433 monitor.Next, we'll check the server's network configuration on the server, check whether the named pipe is enabled, whether theTCP/IP protocol is enabled, and so on. We can use SQL Server own server network to use tools to check.Click: program > Microsoft SQL Server > server network using tools, after opening the tool to see the picture as shown in the following picture:From here, we can see what protocols have been enabled by the server. In general, we enable named pipes as well as TCP/IP protocols.Click on the TCP/IP protocol and select properties, so we can check the settings for the default port of the SQL Server service, as shown in the following figure:In general, we use the default port 1433 of SQL Server. If the hidden server is selected, it means that the client cannot see the server through the enumeration server, and it has a protective effect, but it doesn't affect the connection.Check out the server side network configuration, and then we'll go to the client to check the client's network configuration. We can also use SQL Server own client network using tools to check, the difference is that this is the client to run this tool.Click: program > Microsoft SQL Server > client network using tools, after opening the tool to see the picture as shown in the following picture:From here, we can see which protocols are enabled by the client.In general, we also need to enable named pipes as well as TCP/IP protocols.Click the TCP/IP protocol and select properties to check the settings for the client's default connection port, as shown in the following figure.The port must be consistent with the server.Click the alias tab, and you can also configure aliases for the server. The alias of the server is the name used to connect, and the server in the connection parameter is the real server name, both of which can be the same or different. As shown in the following figure, we can use Myserver instead of the real server name sql2kcn-02, and use the network library Named Pipes. The alias setting is similar to using the HOSTS file.Through the above examination, the cause of error 1 can be eliminated basically. Here's a more detailed description of how to solve the bug 2.When the user attempts to use SA in the query analyzer to connect to the SQL Server,Or use the SA in the enterprise manager to create a new SQL Server. When you register, you'll often encounter error information as shown in figure 2. The reason for this error is that the SQL Server uses a "Windows only" authentication method, so the user cannot connect with the login account of the SQL Server (such as SA). The solution is as follows:1, use the enterprise manager on the server side and choose to use Windows authentication to connect to SQL Server;2. Expand the SQL Server group, right-click the name of the SQL Server server, select properties, and then select the security tab;3, under authentication, select SQL, Server, and Windows".4. Restart the SQL Server service.In the above solution, if use Windows authentication in the first step SQL Server connection fails, then we will encounter a dilemma: first, the server allows only the authentication of Windows; secondly, even though the use of Windows authentication is still not connected to the server. This situation is visually called "locking yourself out of the door" because no user can use the connection in any way. In fact, we can change authentication to SQL, Server, and Windows hybrid validation by modifying a registry key, as shown below:1, click start, run, enter regedit, enter, and enter the registry editor;2, in turn expand the registry key, browse to the following registry key:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLSer ver]3, find the name "LoginMode" on the right of the screen anddouble-click edit double byte values;4, the value will be changed from 1 to 2, click "ok";5, close the registry editor;6. Restart the SQL Server service.At this point, the user can successfully use SA to create a new SQL Server registry in the enterprise manager, but still cannot use the Windows authentication mode to connect to SQL Server. This is because there are two default login accounts in SQL Server: BUILTIN\Administrators and machine name\Administrator are deleted. To restore these two accounts, you can use the following methods:1, open the enterprise manager, expand the server group, and then expand the server;2, expand security, right click login, and then click New login";3, in the name box, enter BUILTIN\Administrators;4, on the server roles tab, select System Administrators";5, click OK to exit;6, use the same method to add machine name \Administrator login.Following registry keyHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServ er\LoginModeThe value determines what authentication mode the SQL Server will take.This value is 1, indicating the use of the Windows authentication mode; the value is 2, indicating the use of mixed mode (Windows authentication and SQL Server authentication).After looking at how to solve the first two errors, let's look at the third errors shown in figure 3.If you encounter third errors, generally speaking, the client has found the server and can connect, but the connection time is greater than the allowable time to cause an error. This usually occurs when a user runs an enterprise manager on Internet to register another server on the same Internet, and a slow connection may cause the timeout error above. In some cases, such problems can also result from local network problems.To resolve such errors, you can modify the connection timeout settings for the client. By default, registered another SQL Server through the enterprise manager timeout is 4 seconds, while the query analyzer is 15 seconds (which is why the enterprise manager error occurs the possibility of more reasons). Specific steps for:1, in the enterprise manager, select the "tools" on the menu,and then select "options"";2, in the pop-up SQL Server enterprise manager properties window, click the advanced tab;3, in the connection settings under the "login timeout (seconds)" to the right of the box, enter a larger number, such as 20.The query analyzer can also be set in the same location.Two, the application connection failedThe above three error messages occur in the client tool that comes with SQL Server, and we will encounter similar error information in the application, for example:Microsoft, OLE, DB, Provider, for, SQL, Server (0x80004005)[DBNETLIB][ConnectionOpen (Connect ()).]Specified, SQL, server, not, found.Microsoft, OLE, DB, Provider, for, SQL, Server (0x80004005)User'sa'logon failed. Reason: not associated with trusted SQL Server connection.Microsoft, OLE, DB, Provider, for, ODBC, Drivers,error,'80004005'.[Microsoft][ODBC SQL Server Driver] timeout has expiredFirst, let's take a detailed look at the following diagram to see what makes the difference between using ODBC and using OLE DB to connect to SQL Server.From the figure above, we can see that in actual use, the application creates and uses various ADO objects, and the ADO object framework calls for the enjoyment of the OLE DB provider. In order to access the SQL Server database, OLE DB provides two different approaches: the OLE DB provider for SQL Server and the OLE DB provider for ODBC. These two different methods correspond to two different connection strings, and the standard connection string is written as follows:1, use the OLE DB provider for SQL Server:Using SQL Server authentication:oconn。

安装SQL2000数据库在Windows10出现⽆法定位序数1于动态链接库Windows Registry Editor Version 5.00[HKEY_CLASSES_ROOT\*\shell\runas]@="获取TrustedInstaller权限"[HKEY_CLASSES_ROOT\*\shell\runas\command]@="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F""IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"[HKEY_CLASSES_ROOT\Directory\shell\runas]@="获取TrustedInstaller权限""NoWorkingDirectory"=""[HKEY_CLASSES_ROOT\Directory\shell\runas\command]@="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t""IsolatedCommand"="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"在⾼版本Windows上安装SQL server2000提⽰：cnfgsvr.exe - 找不到序数⽆法定位序数 1 于动态链接库 C:\Windows\SYSTEM32\SQLUNIRL.dll 上。

Fly.Box企业网盘数据库安装常见问题2014/5/2Copyright © 2014 贵州友百利信息技术有限公司一、文件权限不够 (2)二、分别用Windows身份登录和Sql Server（sa）身份登录进行数据库附加尝试。

(5)三、如果数据库附加成功后显示如图所示“单个用户”或“Single User” (6)四、如果数据库附加成功后显示如图所示“只读”或“Read-Only” (8)SQL SERVER 数据库附加失败可以尝试以下几种方法：一、文件权限不够直接给Fly.Box.mdf和Fly.Box_log.ldf添加everyone 用户所有权限1．在Fly.Box.mdf点击右键->属性2．在弹出的属性窗口中选择“安全”，再点击“编辑”按钮。

3．在弹出的权限窗口中选择点击“添加”，在弹出的用户选择窗口中输入“everyone”,再点击“确定”按钮。

4．回到权限编辑窗口后，将“完全控制”中勾选“允许”，点击“确定”按钮。

5．再用同样的方法给“Fly.Box_log.ldf”添加“everyone”的“完全控制”权限。

二、分别用Windows身份登录和Sql Server（sa）身份登录进行数据库附加尝试。

三、如果数据库附加成功后显示如图所示“单个用户”或“Single User”在数据库上点击右键->属性在弹出的属性窗口中选择“选项”，修改限制访问为“MULTI_USER”，点击“确定”即可。

四、如果数据库附加成功后显示如图所示“只读”或“Read-Only”在数据库上点击右键->属性在弹出的属性窗口中选择“选项”，将“数据库为只读”修改为“False”，点击“确定”即可。

如果在点击确定时出现如图所示的错误提示：可能是文件“Fly.Box.mdf”或者“Fly.Box_log.ldf”为只读，只需要在这两个文件上点击右键，去掉这两个文件只读属性即可，再重复上一个步骤即可。