I see error: 3624, Severity: 20, State: 1.in the sql server error logs on secondary host

I see this error: Error: 3624, Severity: 20, State: 1
Complete error in the error log is:
SQL Server Assertion: File: <loglock.cpp>, line=807 Failed Assertion = 'result == LCK_OK'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart
the server to ensure in-memory data structures are not corrupted.
SQL Server 2008 R2 with Service pack 2 installed and mirrored.
I see this error in the sql server dump file:
0:000> .ecxr
rax=00000000676a7a6a rbx=0000000003fd3250 rcx=000000001048aaa0
rdx=0000000000000000 rsi=0000000003bbef3c rdi=0000000000000440
rip=000007fefd10940d rsp=000000001048b0b0 rbp=000000001048ca50
r8=0000000000000000 r9=0000000000000000 r10=00000000c000007c
r11=00000000012e98d0 r12=00000000000007c0 r13=0000000000000000
r14=0000000000000000 r15=00000000000007c0
iopl=0         nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b             efl=00000206
KERNELBASE!RaiseException+0x39:
000007fe`fd10940d 4881c4c8000000 add     rsp,0C8h
0:000> kC 1000
Call Site
KERNELBASE!RaiseException
sqlservr!CDmpDump::Dump
sqlservr!SQLDumperLibraryInvoke
sqlservr!CImageHelper::DoMiniDump
sqlservr!stackTrace
sqlservr!utassert_fail
sqlservr!LogLockCollectionAcquire::Callback
sqlservr!LogLockCollection::ApplyLocks
sqlservr!LogLockCollection::Acquire
sqlservr!DBMRedoManager::AnalyzeLogRecord
sqlservr!DBMRedoManager::RunAnalysis
sqlservr!DBMRedoManager::ApplyLogSegment
sqlservr!DBMRedoManager::Execute
sqlservr!SubprocEntrypoint
sqlservr!SOS_Task::Param::Execute
sqlservr!SOS_Scheduler::RunTask
sqlservr!SOS_Scheduler::ProcessTasks
sqlservr!SchedulerManager::WorkerEntryPoint
sqlservr!SystemThread::RunWorker
sqlservr!SystemThreadDispatcher::ProcessWorker
sqlservr!SchedulerManager::ThreadEntryPoint
msvcr80!endthreadex
msvcr80!endthreadex
kernel32!BaseThreadInitThunk
ntdll!RtlUserThreadStart
Not sure what to infer from this. Any help would be appreciated.
Let me know if more info. is needed.
Thanks !!!

I did not have a chance to run that at the time the error happened, now everything is normal. Do you have any idea on what this means?
sqlservr!LogLockCollectionAcquire::Callback
I suggest you to run full DBCC CHECKDB , like I said assertion errors are basically related to Internal SQL Server problem
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Similar Messages

I am geeting problem whem i run bulk insert query i got error Location:_ bcpimp.cpp:1797 Expression:_ cbOutTemp cbOutputStr SPID:__ 52 Process ID:_ 2364 Msg 3624, Level 20, State 1, Line 3 A system assertion check has failed. Check the SQL Server error

Location: bcpimp.cpp:1797
Expression: cbOutTemp < cbOutputStr
SPID: 52
Process ID: 2364
Msg 3624, Level 20, State 1, Line 3
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to
Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.

If you check your sql server error log folder you will see dump files created. You need to send those dump files to Microsoft for inspection because outside of microsoft product support the symbols for reading the dumps are not available without which it
wont be easy to find the issue.
http://support.microsoft.com/kb/2028589
In the meantime check if you are on the latest version of Service Pack and if not apply the latest service pack. Majority of these kind of assertions are bugs which are solved in Service Packs/Cumulative Updates.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes in SQL Server 2012 Developer Edition

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: CROY-TOSH
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

Hi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Help with Error: 35285, Severity: 16, State: 1.

Hello, we started with a 2-node availability group with 1 primary replica and 1 secondary replica in synchronous mode. We then added 1 additional asynchronous replica to our availablility group. Since adding the asynchronous replica, the sql server log
on that replica has been getting constantly spammed with the error messages shown below. It is obsfuscating the sql server error log. What do these errors mean? Are they benign? Is there any way to turn them off or filter them from the log so that we can address
any real issues?
-AlwaysOn Availability Groups connection with primary database terminated for secondary database 'XXX' on the availability replica with Replica ID: {03735ddb-e7c3-4f10-ae49-e0e723d8bf1d}. This is an informational message only. No user action is required.
-A connection for availability group 'HADR' from availability replica 'REPLICA3' with id [BD58E2AB-63BC-41D8-95DA-93F6BDE8B2F4] to 'REPLICA1' with id [03735DDB-E7C3-4F10-AE49-E0E723D8BF1D] has been successfully established. This is an informational
message only. No user action is required.
-AlwaysOn Availability Groups connection with primary database established for secondary database 'XXX' on the availability replica with Replica ID: {03735ddb-e7c3-4f10-ae49-e0e723d8bf1d}. This is an informational message only. No user action is required.
-The recovery LSN (155:2565:1) was identified for the database with ID 24. This is an informational message only. No user action is required.
-Error: 35285, Severity: 16, State: 1.
Thanks for your help!

Perhaps this link helps you.
http://blogs.msdn.com/b/arvindsh/archive/2012/09/26/failover-cluster-instance-alwayson-availability-group-dr-scenario.aspx
This is expected and by-design, the logic being that the FCI already has automatic failover configured between the nodes. The current
implementation of AG doe not allow a failover outside of the FCI nodes.
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Reporting Services 2008 R2 configuration error: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

Hi, I am using SQL Server 2008 R2 and on one of our dev boxes I am trying to setup ReportServer using ReportingServices Configuration manager. This is was installed longtime back and during installation they created a service account for reporting services.
When I try to configure the service account I do not get the service account created during the installation in the pull down and if I were to use something different I get this "Named Pipes Provider, error: 40 - Could not open a connection to SQL Server"
error.
Thanks in advance...........
Ione

Hi,
Take a look at this blog - http://blogs.msdn.com/b/sql_protocols/archive/2007/03/31/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server.aspx
I hope it will help.

SQL server error log size is too big to handle

I am working with a large database on windows sql server 2008 R2 such that it has to run continuously 24x7 because of that it is not possible
to restart the server time to time. It is kind of monitoring system for big machines. Because of this SQL server error logs are growing too big even some times up to 60-70 GB at a limited sized hard drive. I can't delete them time to time manually. Can someone
please suggest a way using which I can stop creation of such error logs or recycle them after sometime. Most of the errors are of this kind --
Setting database option RECOVERY to simple for database db_name
P.S.- I have read limiting error logs to 6 etc. But that didn't help. It will be best if you could suggest some method to disable these logs.

Hi Mohit11,
According to your description, your SQL Server error logs are growing too big to handle at a limited sized hard drive, and you want to know how to stop the generation of such error logs or recycle them after sometime automatically without restarting the
SQL Server, right?
As others mentioned above, we may not be able to disable SQL server error log generation. However we can recycle the error logs automatically by running the
sp_cycle_errorlog on a fixed schedule (i.e. every two weeks) using SQL agent jobs so that the error logs will be recycled
automatically without restarting SQL Server.
And it is also very important for us to keep the error log files more readable. So we can increase the number of error logs a little more and run the sp_cycle_errorlog more frequently (i.e. daily), then each file will in a smaller size to be more readable
and we can recycle the log files automatically.
In addition, in order to avoid the size of all the log files growing into a too big size unexpected (sometime it may happen), we can run the following query in SQL Agent job to automatically delete all the old log files when the size of log files is larger
than some value we want to keep (i.e. 30GB):
--create a tample table to gather the information of error log files
CREATE TABLE #ErrorLog
Archieve INT,
Dt DATETIME,
FileSize INT
GO
INSERT INTO #ErrorLog
EXEC xp_enumerrorlogs
GO
--delete all the old log files if the size of all the log files is larger than 30GB
DECLARE @i int = 1;
DECLARE @Log_number int;
DECLARE @Log_Max_Size int = 30*1024; --here is the max size (M) of all the error log files we want to keep, change the value according to your requirement
DECLARE @SQLSTR VARCHAR(1000);
SET @Log_number = (SELECT COUNT(*) FROM #ErrorLog);
IF (SELECT COUNT(FileSize/1024/1024) FROM #ErrorLog) >= @Log_Max_Size
BEGIN
WHILE @i <= @Log_number
BEGIN
SET @SQLSTR = 'DEL C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG.' + CONVERT(VARCHAR,@i);
EXEC xp_cmdshell @SQLSTR;
SET @i =@i + 1;
END
END
DROP TABLE #ErrorLog
For more information about How to manage the SQL Server error log, please refer to the following article:
http://support.microsoft.com/kb/2199578
If you have any question, please feel free to let me know.
Regards,
Jerry Li

Non-SysAdmins get error 18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.

I have a SQL 2008 R2 system (10.50.4000) where I'm having problems connecting any user that is not a SysAdmin. Example: I setup a new SQL Login to use Windows Authentication and grant that user db_datareader on the target database. The user attempts
to connect using Excel client or Access or SQL Management Studio and receives Error 18456. The SQL Server Logs shows Error 18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.
The strange part is that if I temporarily grant the user the sysadmin server role then the user can connect successfully and retrieve data. But, if I take away that sysadmin server role then the user can no longer connect but again receives the Error
18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.
We've turned off UAC on the client machine to see if that was the problem, but no change.
I have dropped and re-added the user's SQL Login (and the related database user login info). No success.
The Ring Buffers output shows:
The Calling API Name: LookupAccountSidInternal
API Name: LookupAccountSid
Error Code: 0x534
Thanks for any help.
-Walt

Yes, you understand correctly. The user is logging onto a workstation (not the server) with a Windows Authenticated id. The user is using either Excel or Access or SSMS and connecting to the server using a Windows Authenticated SQL Login account.
If the account has sysadmin role (which is only for testing) then the connection is successful. If I take away sysadmin role from the account then the connection is unsuccessful and the SQL Server Log shows Error
18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.
(SQL Authentication is not an option here. I must use Windows Authentication).
Any other troubleshooting assistance you can offer would be appreciated. Thanks.
-Walt

Troubleshooting Error: 942, Severity: 14, State: 4

Hi all,
I'm in the process of decomission an old SQL Server 2000. I'm migrating the databases hosted in that instance one by one. I have managed various workaround to handle the changed server\instance name. When I complete the process for one database, I put it
offline in the SQL 2000.
I've a trouble with one database, when I put it offline I see into the profiler a lot of error like this (1 error every 1 seconds):
Error: 942, Severity: 14, State: 4
For what I know this error is because somthing is trying to access a database that is inaccessible (in my case offline) but I can't figure from which client the request came!
Please help!

Hello,
If you have the Audit Database Management event selected on Profiler then that error is expected whenever a database if offline.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Error: 697, Severity: 21, State: 1

Dear Experts,
I received the following error
Error: 697, Severity: 21, State: 1
An attempt was made to fetch logical page '2382' for database 'saptools' (5), object 'DBH_SNAP_TABLES' (2005579152), index 'DBH_SNAP_TABLES' (0), partition 'DBH_SNAP_TABLES_2005579152' (2005579152) from cache 'default data cache'. Wrong logical page '2398' was found in cache
Acc to Sybase troubleshooting guide, we can restart to clear the memory error.
I want to know if there is any alternative for fixing this error
What could be the root cause/reason for this error to occur?
Why I'm seeing "Wrong logical page '2398' was found in cache" ?
Any insight will be much appreciated
Attachment: errorlog
Regards,
Rajesh

Hello Rajesh,
Its Error:697 again
The Checktable output says:
Checking partition 'DBH_SNAP_TABLES_2005579152' (partition ID 2005579152) of table 'DBH_SNAP_TABLES'. The logical page size of this table is 16384 bytes.
Msg 697, Level 16, State 1:
Server 'E20', Line 1:
An attempt was made to fetch logical page '2382' for database 'saptools' (5), object 'DBH_SNAP_TABLES' (2005579152), index 'DBH_SNAP_TABLES' (-1), partition 'DBH_SNAP_TABLES_2005579152' (2005579152) from cache 'default data cache'. Wrong logical page '2398' was found in cache.
DBCC execution completed.
If DBCC printed error messages, contact a user with System Administrator (SA) role.
Explanation:
This error occurs when Adaptive Server tries to access an object   in cache but arrives at an invalid page. The page number is correct on disk, but it does not match the page number of the page in memory.
Error 697 results in a stack trace and breaks your connection to   Adaptive Server.
Action
Since the problem occurs in cache, it is a soft error. Shut down and restart Adaptive Server to clear the memory corruption.
PS: If this is not working out then you should try with the "saptools" restore from a good backup
Regards
Kiran K Adharapuram

Error while executing SSIS package - Error: 4014, Severity:20, State: 11. A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 109, output error: 0)

Hi,
We are getting the following error when running our SSIS packages on Microsoft SQL Server 2012 R2 on Windows Server 2008 R2 SP1:
Error: 4014, Severity:20, State: 11. A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 109, output error: 0)
SQL Server Data Tools and SQL Server Database Engine reside on the same server.
We tried the following:
Disabling TCP Chimney Offload
Installed Windows Server 2008 SP1
Splitting our SSIS code into multiple steps so it is not all one large continuous operation
The error occurs during a BulkDataLoad task.
Other options we are investigating with the engineering team (out-sourced, so delayed responses):
Firewall configurations (everything is local, so this should not make a difference)
Disabling the anti-virus scanner
Are there other things we can try?
Any insight is greatly appreciated.
Thanks!

Hi HenryKwan,
Based on the current information, the issue can be caused by many reasons. Please refer to the following tips:
Install the latest hotfix based on your SQL Server version. Ps: there is no SQL Server 2012 R2 version.
Change the MaxConcurrentExecutables property from -1 to another one based on the MAXDOP. For example, 8.
Set "RetainSameConnection" Property to FALSE on the all the connection managers.
Reference:
https://connect.microsoft.com/SQLServer/feedback/details/774370/ssis-packages-abort-with-unexpected-termination-message
If the issue is still existed, as Jakub suggested, please provide us more information about this issue.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Error: 28005, Severity: 16, State: 2...An exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impe

I've seen some similar questions, but want to make sure I can get an answer quickly and how to fix.
Thanks,
Paul
spid24s Error: 28005, Severity: 16, State: 2
spid24s An exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated,
or you do not have permission.

Hi Paul,
I also had the same error on one of my servers, and it was because the user that created the database no longer worked for the company.
So when his AD account got deleted, the database had NULL as owner
Using the following query I asked for the owners of the databases:
select name, suser_sname(sid) from master.dbo.sysdatabases
So changing the owner of the databases that had a NULL owner solved the issue for me.
use <databasesname>
go
exec sp_changedbowner 'sa'
Thanks for triggering the solution.
Peter

Error 4014 Severity 16 State A fatal error occurred while reading the input streamfrom the network

We encounter following error intermittently Error 4014 Severity 20 State 16 , A fatal error occurred while reading the input stream from the network
I have checked the RING_BUFFER_CONNECTIVITY from sys.dm_os_ring_buffers, we are able to find the remote_host IP where connections are being closed/killed, the error being logged in sys.dm_os_ring_buffers, comes from multiple remote_host, we have raised
to O/s and Networking Team they seem to have no clue, why this error occurs
Server: Virtual Machine
Operating System: WINDOW 2008 R2 SP1
MSSQL 2008 STD ED SP3 10.0.5850.0
Database mirroring is configured for the application database.
Antivirus enable on the database server
How do we find the cause for this error being logged in SQL server logs, is this error due to SQL database mirroring or memory issue?
What needs to be checked on the O/s and Network, I have been checking on the internet and everywhere it is pointing to NIC drivers or security patches
Also in the system events following error was being logged, but after restarting the vm service this error has not re-occurred
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the VMTools service
Kindly suggest on Error 4014 Severity 20 State 16, A fatal error how to resolve
[email protected]

Hello,
Could you try to use Network Monitor or WireShark to examine if the connections resets are coming from a client computer
or from the host where SQL Server is installed?
Network Monitor can be downloaded from the following link:
http://www.microsoft.com/en-us/download/details.aspx?id=4865
If you use Network Monitor trace you will identify connection resets by looking for “TCP: Flags=,,R.A” at the description column on the Frame Summary. Once you find the flag, the Source column will tell you the identity of the host resetting the connection,
maybe is not the SQL Server host.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Sql server 2008 R2 SP2 -Error: 18056, Severity: 20, State: 29

HI ,
I am getting this error in sql server 2008 R2 SP2 version .
The client was unable to reuse a session with <SPID>, which had been reset for connection pooling. The failure ID is 29. This error may have been caused by an earlier operation failing. Check the error logs for failed
operations immediately before this error message.
I am getting same error messages but only SPID are different as of my knowledge this error will resolve in SP@ version but seeing now so please let me know how to resolve the issue
Thanks!
Regards,
Suresh

Have you upgraded to cu1 for sp2 yet?
Check this bug - http://support.microsoft.com/kb/2543687
More information -
http://blogs.msdn.com/b/psssql/archive/2013/02/13/breaking-down-18065.aspx
How are you trying to connect? Could you take a look at the physical SQL Server Error log and see if you find any other error?
Check this part of the blog (http://blogs.msdn.com/b/psssql/archive/2010/05/05/error-18056-can-be-unwanted-noise-in-certain-scenarios.aspx)
"If the above error message (note that the state number should reflect 29) is the only message in the SQL Server Errorlog along with no other errors noticed in the environment
(connectivity failures to the SQL instance in question, degraded performance, high CPU usage, Out of Memory errors), then this message can be treated as benign and safely ignored."
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Error: 18210, Severity: 16, State: 1.

We are getting below error while running red gate backup.
BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'SQLBACKUP_******'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.)
I am not getting any clue to resolve this error.

Hello,
Try to reduce the actual values on the following backup parameters as a workaround: max transfer size and limit the number
of threads.
Monitor memory consumption on that server, this may be a possible cause.
Make sure the backup destination is not full.
Examine SQL Server error log and look for error messages prior in time to the one you posted.
Provide the logs created by this backup tool to RedGate Support.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Cannot connect to SERVER. Login failed for user 'DOMAIN\user'. (Microsoft SQL Server, Error 18456) - SQL Server 2012 on Windows Server 2008 R2

I've seen multiple blogs and forums with similar problems and SQL 2012 or 2008. But no solutions that work for me.
I have installed SQL Server in mixed mode (SQL and Windows authentication). I can create new Login accounts in either mode. However, I cannot get an AD security group Login account to work. I am trying to add group 'DOMAIN\Domain Admins' or 'SERVER\Administrators'
as a Login so that any of the domain's administrator accounts can open SQL Server Management Studio and act as an 'sa' account on this server.
I have deleted the SQL account 'DOMAIN\Domain Admins'.
I have restarted SQL.
I have restarted the Win2K8r2 server.
I have launched SSMS as Administrator from the desktop of SERVER.
I have launched SSMS as another user (and used 'DOMAIN\user' to lauch it) from the desktop of SERVER.
I can create a login account named 'DOMAIN\user' (who happens to be a member of the 'DOMAIN\Domain Admins' group) and give this account 'sa' security, and when I do that, this account works as expected...
How do I add a security group as a Login account and give all members of that group the ability to be an 'sa' account?

Hi geoperkins,
Are you getting the following error message?
Error: 18456, Severity: 14, State: 11
Login failed for user <Domain\user>. Reason: Token-based server access validation failed with an infrastructure error.
If that is the case, the issue could be due to that the Windows login has no profile or that permissions could not be checked due to UAC. Please disable UAC firstly and check if it is successful to log in SQL Server.
Another reason could be that the domain controller could not be reached. You may need to resort to re-creating the login. Create a new group in AD, add users to the new group, then add the group to the local admin group and create login for the group in SQL
Server.
There is a connect item describing similar issue for your reference.
https://connect.microsoft.com/SQLServer/feedback/details/680705/cant-login-to-sql-using-windows-authentication-when-user-is-in-a-domain-security-group
For more details about above error, please review the following blog.
http://sqlblogcasts.com/blogs/simons/archive/2011/02/01/solution-login-failed-for-user-x-reason-token-based-server-access-validation-failed-and-error-18456.aspx
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

I see error: 3624, Severity: 20, State: 1.in the sql server error logs on secondary host

Similar Messages

Maybe you are looking for