Complete a full database consistency check (DBCC CHECKDB). This is a severe error condition that threatens database integrity and must be corrected immediately. Additional messages in the SQL Server error log or system event log may provide more detail. It occurred during a read of page (1:2064) in database ID 21 at offset 0x00000001020000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\some_database.mdf'. 21:02:07.34 spid7s SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:2064 actual 0:0). 21:02:04.28 spid7s Performing replication job security meta-data upgrades. With that being the best answer, the behavior I witnessed isn’t supposed to happen and thus I turned to the SQL Error Logs to find some info Reason: Server is in script upgrade mode. I restarted the service and tried again… same result, so it’s Google-time best hit: Weird SQL Server Error: Unable to Connect to Server. The strange thing is that SQL Server seemed to have stopped after that, something that isn’t supposed to happen. The very “well” documented error about the fact that SQL Server is running some scripts and rather has no-one mesh around (unless you’re on a DAC). Only administrator can connect at this time. So f.k Windows Update and download SQL2k8SP2 and install it.Ī couple of days later I needed SQL Server on that machine, I did the net start mssqlserver trick and tried to connect using Management Studio directly after that. NET Framework was installed, it kept failing. NET Framework 4 installed… then even after. It came via Windows Update started with offering the service pack without. Service Pack 2 for SQL Server 2008 annoyed me on one of my machines (development system, SQL Server doesn’t autostart).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |