Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: The database mirroring session is suspended when you add more than one log transaction file to a folder on the principle server that does not exist on the mirror server in SQL Server 2005 or in SQL Server 2008

FIX: The database mirroring session is suspended when you add more than one log transaction file to a folder on the principle server that does not exist on the mirror server in SQL Server 2005 or in SQL Server 2008

Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.

↑ Back to the top

Symptoms

Consider the following scenario:
  • In Microsoft SQL Server 2005 or in Microsoft SQL Server 2008, you set up database mirroring between two servers.
  • You create a folder on the principle server. This folder does not exist on the mirror server.
  • You add more than one log transaction file to the folder.
In this scenario, the database mirroring session becomes suspended. Meanwhile, the following error message is logged in the SQL Server error log file on the principle server:
<Date><Time> spid28s Error: 1453, Severity: 16, State: 1.

<Date><Time> spid28s 'TCP://<server name>:5022', the remote mirroring partner for database 'test1', encountered error 5123, status 1, severity 16. Database mirroring has been suspended.


The following error message is logged in the SQL Server error log file on the mirror server:


<Date><Time> spid30s Error: 5123, Severity: 16, State: 1.

<Date><Time> spid30s CREATE FILE encountered operating system error 3(error not found) while attempting to open or create the physical file 'C:\temp\newfolder\test1_log5.ldf'.

<Date><Time> spid30s Error: 5123, Severity: 16, State: 1.

<Date><Time> spid30s CREATE FILE encountered operating system error 3(error not found) while attempting to open or create the physical file 'C:\temp\newfolder\test1_log5.ldf'.

<Date><Time> spid30s Error: 1454, Severity: 16, State: 1.

<Date><Time> spid30s While acting as a mirroring partner for database 'test1', server instance '<instance name>' encountered error 5123, status 1, severity 16. Database mirroring will be suspended. Try to resolve the error and resume mirroring.

When this problem occurs, you create the same folder on the mirror server and resume the mirror session. A non-yielding Scheduler error is generated, and a mini-dump file is generated in the SQL Server log folder. Additionally, SQL Server may stop responding.

↑ Back to the top

Resolution

SQL Server 2005 Service Pack 3


The fix for this issue was first released in Cumulative Update 6 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
974648 Cumulative update package 6 for SQL Server 2005 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

The release version of SQL Server 2008

Important You must install this fix if you are running the release version of SQL Server 2008.

The fix for this issue was first released in Cumulative Update 8. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
975976 Cumulative update package 8 for SQL Server 2008
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released

SQL Server 2008 Service Pack 1

Important You must install this fix if you are running SQL Server 2008 Service Pack 1.


The fix for this issue was first released in Cumulative Update 5 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
975977 Cumulative update package 5 for SQL Server 2008 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

For more informationabout the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems

For more informationabout how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

 For more information about the new features in SQL Server 2005 Service Pack 3 (SP3) and about the improvements in SQL Server 2005 SP3, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=131442
For more informationabout the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

 For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kb, kbfix, kbqfe, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 975681
Revision : 6
Created on : 9/29/2020
Published on : 9/29/2020
Exists online : False
Views : 312