SQL Server Troubleshooting

An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database

An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database

This short blog post helps you troubleshoot the below error message in SQL Server Reporting Services (SSRS): An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseError) Get Online Help For more information about this…

A network-related or instance-specific error occurred while establishing a connection to SQL Server

A network-related or instance-specific error occurred while establishing a connection to SQL Server

Under certain circumstances, there are cases where you might try to connect to a SQL Server instance and get the error message: “A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is…

SQL Server 2008 R2 Service Pack Installation Fails – Element not found. (Exception from HRESULT: 0x80070490)

In case you are trying to install a SQL Server 2008 R2 service pack in a clustered SQL Server environment and the installation fails reporting something similar to the below: Final result: The patch installer has failed to update the shared features. To determine the reason for failure, review the…

The transaction log for database ‘dbname’ is full due to ‘XTP_CHECKPOINT’‏

When using In-Memory OLTP in SQL Server 2014, under certain conditions you might get the below error message: The transaction log for database ‘[database_name]’ is full due to ‘XTP_CHECKPOINT’‏  This was fixed in Cumulative Update 3 for SQL Server 2014 SP1 More information about the fix can be found here.