"Server for a long time, SQLEXPRESS service can not start"
1. Open SQL Server 2005 attempts to connect to a server discovery hint Error ( This is also the kind of hint that starts SQL Server service in the service) reads: "Windows cannot the local computer starts SQL Server (MSSQLSERVER). For more information, consult the system event log. If this is a non- Microsoft Service, contact your service vendor and refer to the specific service error code 3417.
2. Often this non-warning problem, are particularly difficult to solve, many people have chosen to re-install SQL, but reloading SQL is also cumbersome, here's how to Troubleshoot COM + issues when you reload SQL 2005 :
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/59/DC/wKioL1TtlHqhTo7iAAFIb4DFTkI514.jpg "style=" float: none; "title=" 1.jpg "alt=" Wkiol1ttlhqhto7iaafib4dftki514.jpg "/>
3. Here, we do not choose to re-install, but also to solve the problem
first, we need to understand why: because NTFS System, due to the long-term use of SQL, and happened to disk cleanup, so some of the SQL files are compressed by the system, and can not be decompressed when used, the solution is as follows:
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/59/DF/wKiom1Ttk3ChVMbXAAOgxXc70vg305.jpg "style=" float: none; "title=" 2.jpg "alt=" wkiom1ttk3chvmbxaaogxxc70vg305.jpg "height=" 473 "width=" 887 "/>
selected For files covered under SQL Server, select Properties-General-advanced-" compress contents to save disk space " Check the checkmark to go, click OK.
This is the first step, if this can solve the problem, you do not have to look at the second step.
Step Two, find a backup database or find the same version the Master database source files below SQL, namely:master.mdf and mastlog.ldf , are copied over to the current two files.
4. Start SQL Server service, and by the way, see if the SQL Server Agent service is started, and if not, start together.
5. We open SQL SERVER 2005 found that some databases do not exist, and some databases have only empty file names ( can not ), do not exist only need to find the source database files MDF and LDF files, Re-attach it to normal use. Of course there will be additional failures, for example:
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/59/DC/wKioL1TtlHrT7AY3AAEH7Q2gSPs652.jpg "style=" float: none; "title=" 3.jpg "alt=" wkiol1ttlhrt7ay3aaeh7q2gsps652.jpg "height=" 326 "width=" 598 "/>
but those databases with an empty file name, whether you delete or detach, prompt a variety of errors, such as:" when you detach a database, you are prompted that the database is being used for replication (error code:3724) and cannot be deleted ."
This problem is very troublesome, how to do? We select the database, right - task -go offline and then click Delete, then we re-attach the database to normal use.
6. Here is a noteworthy problem is: The server database is not afraid of power outages, not afraid to break the network, it is afraid no backup!
This article is from the "kingboat" blog, make sure to keep this source http://sdbzwh.blog.51cto.com/4593374/1615290
IBM server, SQLEXPRESS service issues