到目前为止,我尝试修复该应用程序,但没有帮助。我也遇到过类似的问题,但使用的是更新版本的 SSMS,但我的版本没有他们提到的文件,例如: 一种解决方案是找到一个名为
ssms.exe.config
的文件(在我的例子中称为 ssmsee.exe.
),以删除我的配置文件中没有的行。
另一个解决方案是将文件从目录复制:C\Program Files(86)....IDE\PrivateAssemblies\Interop 到另一个文件夹,但我没有文件夹 PrivateAssemblies,甚至没有他们提到的文件。
我设法找到了日志文件,但我自己无法理解它,请参见下文
2024-07-03 11:17:58.51 Server Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86)
Dec 10 2010 10:56:29
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 6.2 (Build 9200: )
2024-07-03 11:17:58.51 Server (c) 2005 Microsoft Corporation.
2024-07-03 11:17:58.51 Server All rights reserved.
2024-07-03 11:17:58.51 Server Server process ID is 4140.
2024-07-03 11:17:58.51 Server Authentication mode is MIXED.
2024-07-03 11:17:58.51 Server Logging SQL Server messages in file 'c:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2024-07-03 11:17:58.51 Server This instance of SQL Server last reported using a process ID of 4396 at 7/3/2024 11:17:14 AM (local) 7/3/2024 9:17:14 AM (UTC). This is an informational message only; no user action is required.
2024-07-03 11:17:58.51 Server Registry startup parameters:
2024-07-03 11:17:58.51 Server -d c:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2024-07-03 11:17:58.51 Server -e c:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2024-07-03 11:17:58.51 Server -l c:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2024-07-03 11:17:58.54 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2024-07-03 11:17:58.54 Server Detected 12 CPUs. This is an informational message; no user action is required.
2024-07-03 11:18:00.61 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2024-07-03 11:18:00.80 Server Database mirroring has been enabled on this instance of SQL Server.
2024-07-03 11:18:00.82 spid5s Starting up database 'master'.
2024-07-03 11:18:00.85 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2024-07-03 11:18:00.91 spid5s SQL Trace ID 1 was started by login "sa".
2024-07-03 11:18:00.91 spid5s Starting up database 'mssqlsystemresource'.
2024-07-03 11:18:00.91 spid5s The resource database build version is 9.00.5000. This is an informational message only. No user action is required.
2024-07-03 11:18:00.96 spid8s Starting up database 'model'.
2024-07-03 11:18:00.96 spid5s Server name is 'ZAFSIZ-W002\SQLEXPRESS'. This is an informational message only. No user action is required.
2024-07-03 11:18:00.96 spid5s Starting up database 'msdb'.
2024-07-03 11:18:00.99 spid8s Clearing tempdb database.
2024-07-03 11:18:01.13 Server A self-generated certificate was successfully loaded for encryption.
2024-07-03 11:18:01.15 spid8s Starting up database 'tempdb'.
2024-07-03 11:18:01.16 Server Server is listening on [ 'any' <ipv6> 62548].
2024-07-03 11:18:01.16 Server Server is listening on [ 'any' <ipv4> 62548].
2024-07-03 11:18:01.16 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2024-07-03 11:18:01.16 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2024-07-03 11:18:01.16 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2024-07-03 11:18:01.18 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2024-07-03 11:18:01.18 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2024-07-03 11:18:01.18 spid5s Recovery is complete. This is an informational message only. No user action is required.
2024-07-03 11:18:01.18 spid11s The Service Broker protocol transport is disabled or not configured.
2024-07-03 11:18:01.18 spid11s The Database Mirroring protocol transport is disabled or not configured.
2024-07-03 11:18:01.19 spid11s Service Broker manager has started.
2024-07-03 11:23:00.75 spid11s Service Broker manager has shut down.
2024-07-03 11:23:00.80 spid5s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
2024-07-03 11:23:00.82 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
@Thom A 的解决方案非常有效。当我找到 2012 版本的副本后,我就能够将数据库恢复到那里,现在一切都恢复正常了。