Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgment

I have an ASP.Net website that connects to SQL server always-on failover cluster instance.

But I have a strange behavior when I configured the Connection String inside Web.Config as SQL Authentication, the connection has been connected successfully.

Server=load balancer IP;Database=Database Name;User Id=User; Password=Password; 

Bu when I tried to configure the Connection String as Windows Authentication.

Server=load balancer IP;Database=Database Name;Integrated Security =true;

I got the following error.

Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.
This could be because the pre-login handshake failed or the server was unable to respond back in time.

connection-timeout-expired.png

I made sure that the application pool service account has elevated privilege with SQL Server as public server role and user mapping database. but unfortunately, the issue still persist.

Cause: Continue reading “Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgment”

The transaction log for database ‘SharePoint_Config’ is full due to LOG_BACKUP

One of the annoying issues that you may experience when you work with SharePoint Databases is The rapid growth of the transaction log for SharePoint_Config Database.

So you should regularly maintain the SharePoint_Config Database by taking a backup of the log files frequently to avoid the below-encountered error:

errorThe transaction log for database ‘SharePoint_Config’ is full due to ‘LOG_BACKUP’ (Microsoft SQL Server, Error : 9002)

The transaction log for database is full due to LOG_BACKUP 1

Once The transaction log for database ‘SharePoint_Config’ is full due to ‘LOG_BACKUP’ error is encountered. no transaction or action can be performed on ‘SharePoint_Config’ database.

In this article, I’ll show How to avoid falling into this issue by doing the below steps:

Steps:

  1. Take a Full database backup.
  2. Shrink the log file to reduce the physical file size (Only in exceptional circumstances).
  3. Create a LOG_BACKUP.
  4. Create a LOG_BACKUP Maintenance Plan.

noteIn case you have already got this error “The transaction log for database ‘SharePoint_Config’ is full due to ‘LOG_BACKUP’you will not be able to perform any transaction or action on ‘SharePoint_Config’ database as I above mentioned.

So you will not be able to take a backup, and in this case, you should start from step 2 (Shrink the log file to reduce the physical file size) then go back to get a full dattabase backup as prerequisite for perofmaing LOG_BACKUP.

Continue reading “The transaction log for database ‘SharePoint_Config’ is full due to LOG_BACKUP”

BACKUP LOG cannot be performed because there is no current database backup in SQL Server

I got the following error:

BACKUP LOG cannot be performed because there is no current database backup in SQL Server

BACKUP LOG cannot be performed because there is no current database backup SSMS1

When I tried to take a log Backup via Management Studio by doing the mentioned steps below: Continue reading “BACKUP LOG cannot be performed because there is no current database backup in SQL Server”

Service ‘Microsoft SqlServer Management IRegistrationService’ not found During opening SQL Management Studio

When I tried to open SQL Management Studio for SQL Server 2012, I got the following error:

Service 'Microsoft.SqlServer.Management.IRegistrationService' not found

microsoft.sqlserver.management. registration service not found

In my case, I pressed OK and everything is working properly.but I need to avoid showing this error again,

Cause: Continue reading “Service ‘Microsoft SqlServer Management IRegistrationService’ not found During opening SQL Management Studio”

SSRS Subscription Error: SQL Server Agent was unable to start

When I tried to start SSRS subscription to send weekly reports by e-mail where the prerequisites for SSRS subscription is to be sure that SQL Server Agent is working,so that I opened SQL Server Management Studio to check SQL Server Agent status but unfortunately it stopped !

sqlagent

It’s ease of cake  to start SQL Server Agent by right click and select start ! but In my case when I tried to start it I got the following information dialog

unabletostartagent

Cause: Continue reading “SSRS Subscription Error: SQL Server Agent was unable to start”

The report server cannot open a connection to the report server database in SSRS

When I tried to open the Report Manager URL, I got the following error :

The report server cannot open a connection to the report server database

The report server cannot open a connection to the report server databaseCause: Continue reading “The report server cannot open a connection to the report server database in SSRS”