您好，请您先
sql2005配置管理器打不开，该如何解决呢？
sql2005配置管理器打不开 老是显示“无法连接到WMI提供程序。您没有权限或者该服务器无法访问。请注意你只能使用SQL Server 配置管理器来管理SQL Server 2005服务器。找不到指定的模块。[0x8007007e]”，请问，该如何解决呢
问题补充：上面的问题我自己解决了：检查一下 windows下的system32 中是否有framedyn.dll这个系统文件就可以了。
我的是XP系统，
安装sql2005开发板后，打开vs2005新建项目的时候，里面的内容和以前的vs2005不一样了，只有商业智能项目、CSharp、其他项目类型，VS2005不能用了，我需要卸载VS2005然后重新安装吗？？？
最佳答案没有启动TCP-IP协议，启动SQL Server 配置管理器
在里面找到TCP-IP协议，启动协议才可以正常使用SQL2005功能。
上面报错是不是你不是管理员造成或者没有安装好，版本不对？参考帮助。参考资料：http://www./a/fuwuyuxiazai/zaixianjishushouce/shujukuwenti/.html
您觉得最佳答案好不好？
目前有 2 个人评价
提问者对最佳回答的评论：
很感谢贵网站！
共 3 条我一直用SQL2000还没有用过SQL2005SQL2000 通用要启用TCP-IP协议的
对最佳答案的评论:
评论字数200字以内
快到期问题
总积分排行
26428 2718
12991 2569
10941 1771后使用快捷导航没有帐号？
只需一步，快速开始
查看: 5029|回复: 0
UID帖子阅读权限20精华贴数技术排名22114 专家积分2 社区排名2629520 技术积分122 社区积分0 注册时间
精华贴数专家积分2 技术积分122 社区积分0 注册时间
论坛徽章:0
本帖最后由 lefux 于
17:25 编辑
MS SQL Server 复制技术分为四种：快照复制、事物复制、可更新事物复制、合并复制。
中文版的靠翻译，粘贴个英文版的解析如下：
Snapshot publication:
The Publisher sends a snapshot of the published data to Subscribers at scheduled intervals.
Transactional publication:
The Publisher streams transactions to the Subscribers after they receive an initial snapshot of the published data.
Transactional publication with updatable subscriptions:
The Publisher streams transactions to SQL Server Subscribers after they receive an initial snapshot of the published data. Transactions originating at the Subscriber are applied at the Publisher.
Merge publication:
The Publisher and Subscribers can update the published data independently after the Subscribers receive an initial snapshot of the published data. Changes are merged periodically. Microsoft SQL Server Compact Edition can only subscribe to merge publications.
简单列举复制技术注意事项：
1、安装时请注意勾选复制服务勾选框。并配置SQL Agent服务为自动启动.
2、安装完成后，配置SQL服务和SQL Agent代理服务等服务器配置如下。
&&1）配置SQL服务和SQL代理服务的启动账户为本机登陆用户和自动启动.
&&2)&&配置数据库TCP/IP端口。
3、配置复制环境，更改打包文件路劲。
事物复制错误收集以及解决方法(英文版)：
解决链接地址：
1、Procedure or function 'sp_MSins_Sync_XXX' expects parameter , which was not supplied. (Source: MSSQLServer, Error number: 201)
2、Could not locate text information records for the column &XmlContent_nvarchar&, ID 2 during command construction. (Source: MSSQLServer
3、Unable&&to open the physical file. Operating system error 5: &5(Access is denied.)&.&&(Microsoft SQL Server, Error: 5120)
4、Invalid character value for cast specification
报错的事物ID：0x0000, Command ID: 2)
sp_browsereplcmds '0x1B00','0x1B00'
{CALL [dbo].[sp_MSdel_dboXXX] (2474322,{b 'b0a'},%p)} 2
select&&* from MSrepl_commands
where xact_seqno = 0x
and command_id in(
删除改命令
Delete MSrepl_commands
where xact_seqno = 0x1B79000E
and command_id in(
5、The Process is running and is waiting for a response from the server
重启SQL Server服务
6、Explicit value must be specified for identity column in tableXXX的解决方法
把自增ID改成UUID。。。。
7、一个项目的同步不能删除时：
可以暂停SQL 代理服务，然后删除。
8、The problem is the snapshop agent fails during the replication with the error:
Message: Script failed for Table 'dbo.sysdiagrams'.
解决方法：
So I figured out the answer to my own problem. I had restored a SQL 2005 database in SQL 2008 and assumed it was now a SQL 2008 database. Using the T-SQL statement
&SELECT compatibility_level from sys.databases WHERE name='XYZ'&
I discovered the compatibility mode on the database was 80, which is the lowest compatibility mode and explains the SQL 2000 error. I used the statement
&ALTER DATABASE XYZ SET COMPATIBILITY_LEVEL = 100&
to make the database compatible with SQL 2008 only and prevent the error I mentioned previously from occurring during snapshot creation. I hope that helps the next person who encounters this problem.
Now if I can just get the subscriber synchronization to pick up all of my stored procedures I'll be set...
链接地址：
9、SQL Server：错误18483 未能连接到服务器，“服务器名”因为distributor_admin 未在该服务器上定义为远程登录。
10、SQL2008 connot connect to wmi provider，，无法连接到WMI 提供程序 请注意，你只能使用SQL Server 配置管理器来管理SQL Server 2005服务器。找不到指定的模块。[0x8007007e] 拿多个版本的XP尝试 安装后SQL老是出这问题 太急了 请教高手帮忙
解决方法：
在连接数据库应该经常遇到的问题，尤其是对盗版的xp系统而言。
这主要是通过Java 或者vc连接数据库遇到的问题
解决问题的方法：
检查一下 windows下的system32 中是否有framedyn.dll这个系统文件，如果没有到system32 下的wbem文件中拷贝framedyn.dll到system32 目录下
我就是这样解决的，希望能帮到你们
解决方法：
以管理员身份运行“命令提示符”（在附件下面），进入后执行以下命令
&&1)cd /d C:\Program Files\Microsoft SQL Server\90\Shared
&&2)mofcomp &C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof&
当看到有如下信息时表明操作成功
MOF file has been successfully parsed
Storing data in the repository...
解决方法可以，但思路错了，这个问题出现是因为的的系统变量设置不好，好好设置你的环境变量“path”，否则你的其他程序也会出问题。
在path中加上%system%\wbem
&%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\W&
参考网址：
11、Explicit value must be specified for identity column in table XXX either when IDENTITY_INSERT is set to ON or when a replication user is inserting into a NOT FOR REPLICATION identity column.
解决：这个错误通常情况是因为同步的一个表中有触发器向另外一个带自增列的表插入数据造成的。
可以通过事务序列号和命令ID找到这个同步的表，然后查看这个表的触发器，把插入带自增列的表改成为UUID，或者设置同步表的触发器对同步的数据不起作用。
12、The procedure 'sp_addsubscription' cannot be executed within a transaction.
13、The subscription to this publication is not active yet. No user action is required
I need help with this ASAP please.
I have updatable transactional replication between two SQL 2005. I did modified replicated tables, added new articles and so.... Everything went very well.
Then I added new table to publication which was not different then previously added... Table exists in subscription database and I created article with &Keep existing object unchanged& as all other created before.
I noticed table triggers on subscriber were not created so I noticed something is wrong...
I started receive message &The Subscription to this publication is not active yet. No user action is required.& in replication monitor... There are not changes synchronize anymore. Synchronization agent is running continuously. I restarted Log Reader and Queue Reader..
I ran also Snapshot agent with result &A snapshot was not generated because no subscriptions needed initialization.&.
Here is the problem. I cannot recreate subscription or invalidate it. I have only one subscriber but I cannot run full snapshot because db is so big (1.3TB) and it will never end. I did first activation from backup but it is impossible now because user cannot stop working.
Is there any way how to rollback this one article and make subscription synchronize? I have in syssubscriptions status 1 for this specific article... Simple update in table/view doesn't work.
Thank you so much
14、Script failed for Table Table 'dbo.XXX'.
Source: Microsoft.SqlServer.Smo
Target Site: System.Collections.Generic.IEnumerable`1[System.String] ScriptWithList(Microsoft.SqlServer.Management.Smo.DependencyCollection, Microsoft.SqlServer.Management.Smo.SqlSmoObject[])
Message: Script failed for Table 'dbo.XXX'.
So I figured out the answer to my own problem. I had restored a SQL 2005 database in SQL 2008 and assumed it was now a SQL 2008 database. Using the T-SQL statement &SELECT compatibility_level from sys.databases WHERE name='XYZ'& I discovered the compatibility mode on the database was 80, which is the lowest compatibility mode and explains the SQL 2000 error. I used the statement &ALTER DATABASE XYZ SET COMPATIBILITY_LEVEL = 100& to make the database compatible with SQL 2008 only and prevent the error I mentioned previously from occurring during snapshot creation. I hope that helps the next person who encounters this problem.
Now if I can just get the subscriber synchronization to pick up all of my stored procedures I'll be set...
15、Could not find stored procedure ''.
Could not find stored procedure 'sp_MSrepl_addpublication'.
Changed database context to 'aimoo_website1'. (.Net SqlClient Data Provider)
解决方法：清除数据库的发布环境。
EXEC sp_removedbreplication @dbname = 'dbname'
16、===================================
Error connecting to XXX.
===================================
A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (.Net SqlClient Data Provider)
------------------------------
For help, click:
------------------------------
Server Name: 172.16.110.4,1689
Error Number: 10054
Severity: 20
------------------------------
Program Location:
& &at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
& &at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
& &at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
& &at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
& &at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()
& &at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
& &at System.Data.SqlClient.TdsParserStateObject.ReadByte()
& &at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
& &at System.Data.pleteLogin(Boolean enlistOK)
& &at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
& &at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
& &at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
& &at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
& &at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
& &at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
& &at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
& &at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
& &at System.Data.SqlClient.SqlConnection.Open()
& &at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
& &at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ConnectToServer(Object connectionInfo, IDbConnection liveConnection, Boolean validateConnection)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\SycAttackProtect{DWORD} = 0
主要收集MS SQL Sever复制错误，并做归类
欢迎后续...和大家一起补充，以上是我平时记录下来的，大体信息....若有疑问，可以讨论...
1、 同步错误号:08S01自定义错误描述:数据库事物日志空间不足，同步错误详细：Communication link failure sp_MSreleasesnapshotdeliverysessionlock Communication link failure Communication link failure
2、 同步错误号:10054自定义错误描述:远程主机强迫关闭了一个现有的连接.，同步错误详细：The process could not bulk copy into table '&dbo&.&XXX&'. 远程主机强迫关闭了一个现有的连接。 未指定的错误 Failed to send batch after max errors TCP Provider: 远程主机强迫关闭了一个现有的连接。 Communication link failure
3、 同步错误号:121自定义错误描述:信号灯超时时间已到.，同步错误详细：TCP Provider: 信号灯超时时间已到 TCP Provider: 信号灯超时时间已到 Communication link failure
4、 同步错误号:64自定义错误描述:指定的网络名不再可用.，同步错误详细：TCP Provider: 指定的网络名不再可用。 TCP Provider: 指定的网络名不再可用。 Communication link failure
5、 同步错误号:HYT00自定义错误描述:由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败.，同步错误详细：The process could not connect to Subscriber XXX. TCP Provider: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. Login timeout expired
6、 同步错误号:9002自定义错误描述:数据库事物日志空间不足,请检查，同步错误详细：The transaction log for database 'XXX is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases if COLUMNPROPERTY( OBJECT_ID('MSreplication_subscriptions'),'distribution_agent','AllowsNull') && 1 BEGIN alter table MSreplication_subscriptions alter column distribution_agent sysname null end&&The transaction log for database 'XXX' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
7、 同步错误号:20001自定义错误描述:进程不能够分配内存，同步错误详细：The process could not allocate memory. if @@trancount & 0 rollback tran
8、 同步错误号:20598自定义错误描述:指定的行在订阅服务器没有找到.，同步错误详细：应用复制的命令时在订阅服务器上找不到该行。 应用复制的命令时在订阅服务器上找不到该行。 应用复制的命令时在订阅服务器上找不到该行。
9、 同步错误号:20084自定义错误描述:sa 登录订阅服务器失败.，同步错误详细：The process could not connect to Subscriber XXX. Login failed for user 'sa'.
10、 同步错误号:4902自定义错误描述:无法找到表对象，同步错误详细：Cannot find the object &dbo.XXX& because it does not exist or you do not have permissions. if @@trancount & 0 rollback tran Cannot find the object &dbo.XXX& because it does not exist or you do not have permissions.
11、 同步错误号:3616自定义错误描述:触发器执行期间出现错误，同步错误详细：An error was raised during trigger execution. The batch has been aborted and the user transaction, if any, has been rolled back. CREATE TABLE [dbo].[EC_Country](& &[SeqID_int] [int] NOT NULL,& &[Name_nvarchar] [nvarchar](50) COLLATE Chinese_PRC_CI_AS NULL,& &[WebSiteID_smallint] [smallint] NULL,& &[Typeid_int] [int] NULL,& &[Parentid_int] [int] NULL,& &[IsEnabled_bit] [bit] NULL,& &[SortOrder_int] [int] NULL,& &[Continent_nvarchar] [nvarchar](50) COLLATE Chinese_PRC_CI_AS NULL,& &[DParentID_int] [int] NULL,& &[CountryCode_nvarchar] [nvarchar](50) COLLATE Chinese_PRC_CI_AS NULL,& &[ShortCode_nvarchar] [nvarchar](50) COLLATE Chinese_PR An error was raised during trigger execution. The batch has been aborted and the user transaction, if any, has been rolled back.
12、 同步错误号:20007自定义错误描述:一个或多个所需参数没有值，同步错误详细：No value given for one or more required parameters. No value given for one or more required parameters.
13、 同步错误号:20049自定义错误描述:一个或多个所需参数没有值，同步错误详细：No value given for one or more required parameters. No value given for one or more required parameters.
14、 同步错误号:8144自定义错误描述:指定的参数太多,考虑重新生成存储过程，同步错误详细：为过程或函数 sp_MSupd_dboXXX 指定了过多的参数。 if @@trancount & 0 rollback tran 为过程或函数 sp_MSupd_dboXXX 指定了过多的参数。
15、 同步错误号:4060自定义错误描述:其它错误，同步错误详细：The process could not access database 'TLMS' on server 'XXX'. Cannot open database &XXX& requested by the login. The login failed. Login failed for user 'sa'.
16、 同步错误号:845自定义错误描述:未归类的同步错误号，同步错误详细：Time-out occurred while waiting for buffer latch type 3 for page (1:1504368), database ID 6. if @@trancount & 0 rollback tran Time-out occurred while waiting for buffer latch type 3 for page (1:1504368), database ID 6.
17、 同步错误号:2627自定义错误描述:违反主键约束，同步错误详细：违反了 PRIMARY KEY 约束 'PK_XXX'。不能在对象 'dbo.XXX' 中插入重复键。
&&nbsp|&&nbsp&&nbsp|&&nbsp&&nbsp|&&nbsp&&nbsp
itpub.net All Right Reserved. 北京皓辰网域网络信息技术有限公司版权所有　　　　
　北京市公安局海淀分局网监中心备案编号：　广播电视节目制作经营许可证：编号（京）字第1149号cncqw 的BLOG
用户名：cncqw
文章数：20
访问量：86529
注册日期：
阅读量：48099
阅读量：2494
51CTO推荐博文
花了很长时间才安装好Microsoft SQL Server2008R2，刚开始还可以运行，可以第二次运行就出问题了。弹出的提示框如下：
出现这个问题应该是在配置安装SQL Server 2008时，把所有的服务都设置成了手动或者禁止，只需手动启动即可。
首先要知道安装时使用&SQL Server 身份验证&还是&Windows身份验证&？我在安装的时候配置的是使用两种方式验证。
如果安装使使用&SQL Server 身份验证&的话请在安装完成后按以下步骤设置一下：
一、开始菜单&&Microsoft SQL Server 2008&&配置工具&&SQL Server 配置管理器（本地）&&SQL Server 服务，启动SQL Server (MSSQLSERVER)服务和SQL Server 代理(MSSQLSERVER)服务。
二、SQL Server 网络配置&&MSSQLSERVER的协议，启动TCP/IP即可。
然后重新连接服务器，问题就解决了。
了这篇文章
类别：┆阅读(0)┆评论(0)打开SQL server 2005的SQL server management studio 界面时，弹出“连接到服务器”对话框，_百度知道
打开SQL server 2005的SQL server management studio 界面时，弹出“连接到服务器”对话框，
用前者可以连接上，用后者则会弹出错误提示：“已成功与服务器建立连接，但是在登录过程中发生错误”。为什么在“身份认证”选项中有windows身份认证和SQL server 身份验证两种，请问两者有什么区别
提问者采纳
就必须先跟服务器断开连接是两种不同的登录方式而已你是先用windows身份认证，这时你要再用SQL server 身份验认证时，认证听过后就连接上了
还是搞不清楚为什么要有两种不同的身份验证，我要做一个WEB应用程序，也不知道怎么连接数据库。还有我怎么跟服务器断开连接？初学者很多不懂请多包涵，呵呵
打开左上角的文件，里面有断开连接的选项
谢谢，断开连接了，但是还是连接不了，会弹出用户“sa登录失败”的消息。
比较多文字，干脆发这个给你
谢谢你，设置好了。
提问者评价
其他类似问题
按默认排序
其他1条回答
这样与系统无关了身份认证有两种 win和sql ,可以把sql身份验证关了,建了AD管理的,2个都开.如果没有开启sql验证,一般我都用sql身份验证,用win身份证的也有sql身份验证在安装时设置,你可以百度一下我就不多说了,以前叫混合身份验证,安装后也可以用win进去后再设置,你是用sa登录不进去的.对于网络上程序使用数据库.对于一些企业
您可能关注的推广
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁