March 12, 2010 at 9:34 am
Hi,
i got a problem, that i cannot figure out.
I migrated databases from sql 2000 to a new system.
server 2008 r2 and sql 2008.
running clustered with 2 nodes.
every few hours at exact full time, lets say 4.00 pm or 0.00 am
one of the dbs is changing in recovery mode.
if i look in the logs, i always find:
'170(failed to retrieve text for this error. Reason: 15105)'
it looks like there is sometime a script who tries to backup the dbs.
i´m no employee from that company,
and the admins there do not want to check al the scripts...
there are several cron job server,
application server under apache and so on,
and i don´t know if it´s a sql server problem,
a db problem or caused by old admin scripts, who lock the database.
last week i wanted to create dummy dbs with the same name and recover them with bak files.
by exactly the three dbs i got the same message:
'170(failed to retrieve text for this error. Reason: 15105)'
so i migrated them in attaching the mdf and ldfs.
everything went fine until a enabled all of the logins
for the admintools and webserver...
since then, always at full time, sometimes,
the temdb log is not available,
and i need to set the clustered sql server offline and online...,
or the db central is in recovery mode,
and the db need to be set offline and online again...
if i look at the logs, it always seems, that a script tries to backup the database.
since today morning i found out,
that i cannot back up the three databases everytime.
today, at 6.pm there was again a failure, sql server was restartet.
for a few minutes i could back up one of the databases.
5 minutes later, this database and the other two
here some of the messages if i treid to backup the database:
03/11/2010 18:31:52,Backup,Unknown,The operating system returned the error '170(failed to retrieve text for this error. Reason: 15105)' while attempting 'FlushFileBuffers' on 'S:\MSSQL10.MSSQLSERVER\MSSQL\Backup\central_city\central_city_backup_2010_03_11_183110_1214200.bak'.
03/11/2010 18:31:52,Backup,Unknown,Error: 3634<c/> Severity: 16<c/> State: 2.
03/11/2010 18:31:51,Backup,Unknown,BACKUP failed to complete the command BACKUP DATABASE central_city. Check the backup application log for detailed messages.
03/11/2010 18:31:51,Backup,Unknown,Error: 3041<c/> Severity: 16<c/> State: 1.
03/11/2010 18:31:51,Backup,Unknown,BackupIoRequest::ReportIoError: write failure on backup device 'S:\MSSQL10.MSSQLSERVER\MSSQL\Backup\central_city\central_city_backup_2010_03_11_183110_1214200.bak'. Operating system error 170(failed to retrieve text for this error. Reason: 15105).
03/11/2010 18:31:51,Backup,Unknown,Error: 18210<c/> Severity: 16<c/> State: 1.
03/11/2010 18:31:47,Backup,Unknown,BackupIoRequest::ReportIoError: read failure on backup device 'S:\MSSQL10.MSSQLSERVER\MSSQL\Backup\central\central_backup_2010_03_11_183110_1136072.bak'. Operating system error 170(failed to retrieve text for this error. Reason: 15105).
03/11/2010 18:31:47,Backup,Unknown,Error: 18210<c/> Severity: 16<c/> State: 1.
any help is welcome!
mathias
March 12, 2010 at 9:38 am
The error 15105 means - the SQL service account does not have permission on the folder where the files are now. Can you check that and let us know...
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
March 12, 2010 at 10:48 am
hi,
the clustered s: drive got the default security settings.
sqlserver account is domain admin.
so localhost\administrator group should be no problem.
should i add the sqlserverice account separately?
March 12, 2010 at 11:09 am
another info.
the problem seems to be with three of several databases.
but one of them is only a test database of a production one on antoher server who is not migrated yet.
the only thing is, that one webserver got a test connection to this db an tells connection ok.
no one working on it and production environment has no info about this db.
one time i can backup, e.g. if sql server service restartet. minutes later same error. 170...
all of the three databases are attached through mdf and ldf.
i did not used the migration wizard or the possiblity in management studio.
other databases and new dbs got no problem.
is it possible that the dbs are incompatible to sql 2008 and need to be migrated through the assistants again?
i went dbcc checkdb and so on.
no problems found, consistent.
check integrity sometimes runs fine and tells success, almost again the same message.
if nothing seems to be done manually by the admins there,
a "full time", 6.pm or in the night, there are identically same messages
as i try to backup dbs...
yesterday at 9 pm we got the problem with the central db again.
heres the log output.
as mentioned, we got two problems. Maybe the same cause...
1. db central is changed to recovery mode, displayed as suspect and need to be set offline/online
2. tempdb log failed - no access for the system and sql server needs to be restartet
in both cases theres is the message 170... retrieve text...
like someone trying to backup with wrong syntex, path, etc....
by the way, today i realized that three dbs cannot be backup most time.
again with the same error...
yesterday the central db changed to suspect again.
we created a surveillance yesterday morning by nagios
and get informed.
the script in nagios tried to set the db central in this case offline
and online again.
i dialed in and saw that tha script was not able to set online (testdb is success),
but the db was changed to offline, no more suspect.
i now only have to set the db online manually...
heres the log from yesterday, 9 pm was the crash of the central db...
03/11/2010 21:01:21,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\Log\central_city_Log.LDF' at offset 0x0000000155e000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:21,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:21,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.1]
03/11/2010 21:01:21,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:21,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.8]
03/11/2010 21:01:21,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:21,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.8]
03/11/2010 21:01:21,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.8]
03/11/2010 21:01:21,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:21,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.20]
03/11/2010 21:01:21,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:21,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.8]
03/11/2010 21:01:21,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:21,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:21,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:21,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.8]
03/11/2010 21:01:21,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:21,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.20]
03/11/2010 21:01:21,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:20,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.20]
03/11/2010 21:01:20,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:20,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.20]
03/11/2010 21:01:20,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:20,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.20]
03/11/2010 21:01:20,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:20,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.1]
03/11/2010 21:01:20,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:20,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000001dfe6a000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.1]
03/11/2010 21:01:20,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000002a88ba000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x00000143a34000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x00000142f52000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000000185c4000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000001df702000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.20]
03/11/2010 21:01:20,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000002a821c000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000001deefe000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000002a7b12000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000001d9928000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000002a575a000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000001bd588000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000001c4c5c000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000001d0312000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x00000112baa000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.8]
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000001749be000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000000f1d42000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000002a8c90000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000001478e8000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000001e0002000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000000f3302000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:20,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.20]
03/11/2010 21:01:20,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x00000148102000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:20,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000001e0038000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000000f232e000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:19,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000002a8a52000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.1]
03/11/2010 21:01:19,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:19,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000000f2e6a000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000001e1a06000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000001dfef6000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000002a8936000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000000f2254000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.1]
03/11/2010 21:01:19,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000002a8bb8000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000001daad8000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.8]
03/11/2010 21:01:19,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000000f2de2000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000000f2a44000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000001dffa6000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.1]
03/11/2010 21:01:19,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:19,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000000f2a34000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,spid26s,Unknown,CHECKDB for database 'central' finished without errors on 2010-03-11 17:45:14.840 (local time). This is an informational message only; no user action is required.
03/11/2010 21:01:19,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.8]
03/11/2010 21:01:19,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\Log\central_city_Log.LDF' at offset 0x00000000021e00 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.1]
03/11/2010 21:01:19,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:19,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.1]
03/11/2010 21:01:19,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:19,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:19,spid26s,Unknown,Recovery completed for database central (database ID 13) in 3 second(s) (analysis 74 ms<c/> redo 1761 ms<c/> undo 357 ms.) This is an informational message only. No user action is required.
03/11/2010 21:01:19,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000000b5910000 succeeded after failing 2 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:19,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.8]
03/11/2010 21:01:19,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:19,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.8]
03/11/2010 21:01:19,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:19,Logon,Unknown,Login succeeded for user 'iusr_central'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:19,Logon,Unknown,Login failed for user 'iusr_central'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.20]
03/11/2010 21:01:19,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:19,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.20]
03/11/2010 21:01:19,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:18,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:18,spid25s,Unknown,Recovery of database 'central_city' (10) is 4% complete (approximately 8 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
03/11/2010 21:01:18,spid25s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\Log\central_city_Log.LDF' at offset 0x00000001c6f600 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:18,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:18,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:18,spid26s,Unknown,Recovery is writing a checkpoint in database 'central' (13). This is an informational message only. No user action is required.
03/11/2010 21:01:18,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.20]
03/11/2010 21:01:18,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:18,spid26s,Unknown,0 transactions rolled back in database 'central' (13). This is an informational message only. No user action is required.
03/11/2010 21:01:18,spid25s,Unknown,Recovery of database 'central_city' (10) is 0% complete (approximately 8 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
03/11/2010 21:01:18,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.1]
03/11/2010 21:01:18,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:18,spid26s,Unknown,4765 transactions rolled forward in database 'central' (13). This is an informational message only. No user action is required.
03/11/2010 21:01:18,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.20]
03/11/2010 21:01:18,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:18,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:17,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.1]
03/11/2010 21:01:17,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.1]
03/11/2010 21:01:17,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.1]
03/11/2010 21:01:17,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.20]
03/11/2010 21:01:17,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x0000007f1de000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x000000445ac000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x0000007d17e000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x0000007f4e4000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x0000007d514000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x0000004709a000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x0000004708a000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x00000048e12000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x00000045470000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.1]
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x0000004521a000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x000000453dc000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x0000007f642000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x0000007d6d2000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x0000007f06a000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x0000007d00a000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x0000007f6ca000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x0000007d768000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x00000047130000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x00000047120000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x00000046d16000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x0000004300c000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.8]
03/11/2010 21:01:17,spid26s,Unknown,A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central.mdf' at offset 0x00000046d06000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
03/11/2010 21:01:17,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.8]
03/11/2010 21:01:17,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:17,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.1]
03/11/2010 21:01:17,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:17,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.8]
03/11/2010 21:01:17,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:17,Logon,Unknown,Login succeeded for user 'iusr_central'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:17,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:16,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:16,spid26s,Unknown,Recovery of database 'central' (13) is 0% complete (approximately 9 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
03/11/2010 21:01:16,spid26s,Unknown,Recovery of database 'central' (13) is 0% complete (approximately 9 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
03/11/2010 21:01:16,spid25s,Unknown,Starting up database 'central_city'.
03/11/2010 21:01:16,spid26s,Unknown,Starting up database 'central'.
03/11/2010 21:01:16,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:15,spid91,Unknown,Database central was shutdown due to error 9001 in routine 'XdesRMFull::Commit'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
03/11/2010 21:01:15,spid91,Unknown,The log for database 'central' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
03/11/2010 21:01:15,spid91,Unknown,Error: 9001<c/> Severity: 21<c/> State: 4.
03/11/2010 21:01:15,spid5s,Unknown,Write error during log flush.
03/11/2010 21:01:15,spid5s,Unknown,LogWriter: Operating system error 170(failed to retrieve text for this error. Reason: 15105) encountered.
03/11/2010 21:01:15,spid5s,Unknown,Error: 17053<c/> Severity: 16<c/> State: 1.
03/11/2010 21:01:15,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
03/11/2010 21:01:15,Logon,Unknown,Login succeeded for user 'iusr_central'. Connection made using SQL Server authentication. [CLIENT: 172.16.0.5]
03/11/2010 21:01:15,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.8]
03/11/2010 21:01:15,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.1]
03/11/2010 21:01:15,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.8]
03/11/2010 21:01:14,Logon,Unknown,Login failed for user 'centralCity'. Reason: Failed to open the database specified in the login properties. [CLIENT: 172.16.50.8]
03/11/2010 21:01:14,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 40.
03/11/2010 21:01:14,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.8]
03/11/2010 21:01:14,Logon,Unknown,Login succeeded for user 'iusr_central'. Connection made using SQL Server authentication. [CLIENT: 172.16.0.5]
03/11/2010 21:01:14,spid117,Unknown,Database central_city was shutdown due to error 9001 in routine 'XdesRMFull::Commit'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
03/11/2010 21:01:14,spid117,Unknown,The log for database 'central_city' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
03/11/2010 21:01:14,spid117,Unknown,Error: 9001<c/> Severity: 21<c/> State: 4.
03/11/2010 21:01:14,spid5s,Unknown,Write error during log flush.
03/11/2010 21:01:14,spid5s,Unknown,LogWriter: Operating system error 170(failed to retrieve text for this error. Reason: 15105) encountered.
03/11/2010 21:01:14,spid5s,Unknown,Error: 17053<c/> Severity: 16<c/> State: 1.
03/11/2010 21:01:13,Logon,Unknown,Login succeeded for user 'centralCity'. Connection made using SQL Server authentication. [CLIENT: 172.16.50.20]
March 12, 2010 at 11:21 am
You have IO problems. Get some diagnostics running on those drives or, better idea, get the DBs onto different storage before they completely fail.
A read of the file 'S:\MSSQL10.MSSQLSERVER\MSSQL\DATA\central_city_Data.MDF' at offset 0x000002a88ba000 succeeded after failing 1 time(s) with error: 170(failed to retrieve text for this error. Reason: 15105). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected.
Basically you have a read to the data file that is intermittently failing. Fixing the drive problem must be your top priority. And get some backups run and put on another server ASAP.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 12, 2010 at 1:42 pm
hi,
ok. you think thats is it caused by io?
if got the newest 8gb fibre channel san
and there are nowhere any errors.
i shut down the second node,
maybe he is causing something...
March 12, 2010 at 1:56 pm
first node is shutdown...
any other suggestions?
can i do a check of the io?
Server 2008 r2 cluster check is with no error...
everything seems to be ok.
almost the other dbs have no problem.
is it possible that i have sometimes active directory auth failures,
or lets say no in time auth,
so that sql server serice cannot read the mdf or ldf like
in first answer mentioned?
March 12, 2010 at 3:49 pm
mathias-ruehn (3/12/2010)
first node is shutdown...any other suggestions?
can i do a check of the io?
Server 2008 r2 cluster check is with no error...
everything seems to be ok.
almost the other dbs have no problem.
is it possible that i have sometimes active directory auth failures,
or lets say no in time auth,
so that sql server serice cannot read the mdf or ldf like
in first answer mentioned?
Attach and Detach is not recommended for migration. Do you have good backups of these databases before migration? If you have backups restore them with other database names once you test everything is good on these databases, drop the databases which are causing issues and rename the new ones. If it was authentication problem then all the backups would have failed unless you are running backups for these failing databases with different account. It may be problem with disk or mdf and ldf files may be corrupt.
March 12, 2010 at 11:12 pm
hi gtr,
before migration i created new dbs with the same names
and tried to recover from backups who went good on the old sql server.
yes, that was different account on workgroup,
nothing with my new domain...
but in the recover process i got the same message 170 failed to retrieve text..
is it possible that they were corrupt before migration?
how do i check this?
dbcc check db no problem...
today morning i can backup (try) to a level between 30 up to 90 %,
then fails again.
In the morning there is less io stress in that company, so maybe cause of that.
can i reserve "io capacity" to sql system actions???
March 12, 2010 at 11:28 pm
changes to configuration:
1. first cluster node shutdown since yesterday evening 8.pm
2. deactivated filestream option since db failure central yesterday evening 9 pm. (with sql service restart)
no failure during the night - no admins at work :-)!
- but backup is not possible, runs longer, but fails in progress...
today morning 7 am
3. explicit added all cluster services and sql services accounts from domain into local administrator group...
4. i deactivate sql option "boost sql server priority"
no restart of sql service required? i thought so... 🙂
what about the sql global action "automatically set io affinity mask of all processors" ?
do you think deactivating io affinity could help?
now im looking at the dc...
March 12, 2010 at 11:46 pm
mathias-ruehn (3/12/2010)
hi gtr,before migration i created new dbs with the same names
and tried to recover from backups who went good on the old sql server.
yes, that was different account on workgroup,
nothing with my new domain...
but in the recover process i got the same message 170 failed to retrieve text..
is it possible that they were corrupt before migration?
how do i check this?
dbcc check db no problem...
today morning i can backup (try) to a level between 30 up to 90 %,
then fails again.
In the morning there is less io stress in that company, so maybe cause of that.
can i reserve "io capacity" to sql system actions???
Can you run select name, status, status2 from sys.sysdatabases on both servers and post the results here
March 12, 2010 at 11:52 pm
another info.
my dc is running 2003 r2 standard, 32 bit.
im now building a second dc under 2008 r2 64 bit
and migrate ad.
then remove 2003 r2 and change level to 2008...
i got another cluster, same hardware running fine in that company.
exact configuration, different app use...
but a dc running also 2008 r2.
i checked all logs and so on in 2003 r2 dc,
no problems.
but maybe there are some complications in the auth requests.
they are ok, but maybe this is causing the failures...
March 13, 2010 at 12:20 am
GTR (3/12/2010)
Attach and Detach is not recommended for migration.
Why not? Detach/attach and backup/restore will result in the same thing. A database converted to the new version on the new server. The only problem with detach/attach is that it doesn't leave a copy in the older version in case downgrades are necessary
Can you run select name, status, status2 from sys.sysdatabases on both servers and post the results here
sysdatabases is a deprecated system view that is included for backward compatibility only and should not be used for new development. On SQL 2005/2008 sys.databases should be used instead, not the least because it is monumentally easier to read.
SELECT state_desc from sys.databases.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 13, 2010 at 12:24 am
mathias-ruehn (3/12/2010)
but maybe there are some complications in the auth requests.they are ok, but maybe this is causing the failures...
No! The errors in your logs, the ones that I quoted are caused by some form of intermittent IO problem. The authentication problems are likely caused by the IO errors, not the other way around.
Does that database have auto-close enabled?
Is there a virus protector on that machine and, if so, have the SQL file types and directories been properly excluded?
- but backup is not possible, runs longer, but fails in progress...
What is the exact error message that you're getting?
what about the sql global action "automatically set io affinity mask of all processors" ?
do you think deactivating io affinity could help?
Leave it at default.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 13, 2010 at 12:32 am
GilaMonster (3/13/2010)
GTR (3/12/2010)
Attach and Detach is not recommended for migration.Why not? Detach/attach and backup/restore will result in the same thing. A database converted to the new version on the new server. The only problem with detach/attach is that it doesn't leave a copy in the older version in case downgrades are necessary
Yes, that is why, what if mdf and ldf files are corrupt while attaching detaching databases? That is why we have best practices am i wrong?
Viewing 15 posts - 1 through 15 (of 33 total)
You must be logged in to reply to this topic. Login to reply