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

In this article, I will explain How to trace and solve the below error

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

connection-timeout-expired.png


Scenario

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 SharePoint Config Database transaction log (Full).

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

Note: When The transaction log for database ‘SharePoint_Config’ is full due to ‘LOG_BACKUP’ error is encountered. No transaction or backup action can be performed on ‘SharePoint_Config’ database.


In this article, I’ll show How to avoid falling into this issue (SharePoint_Config Database log file is Full) by following 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.

noteAs I have mentioned, if you 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 backup action on ‘SharePoint_Config’ database.

In this case, you will not be able to take a backup, and you should start from step 2 (Shrink the log file to reduce the physical file size) then go back to get a full database backup as a prerequisite for performing 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

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

Actually, it’s annoying message that appears every time I have opened the SQL Server Management Studio.

I just clicked OK and everything is working properly. but I am trying to find any solution avoid “Service ‘Microsoft.SqlServer.Management.IRegistrationService’ not found” error message permanently.


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”