Article ID: 915306
Article Last Modified on 11/4/2007
APPLIES TO
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
Bug: #378 (SQL Hotfix)
Notice
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.
This article describes the following about this hotfix release:
- The issues that are fixed by this hotfix package
- The prerequisites for installing the hotfix package
- Whether you must restart the computer after you install the hotfix package
- Whether the hotfix package is replaced by any other hotfix package
- Whether you must make any registry changes
- The files that are contained in the hotfix package
SYMPTOMS
When you synchronize a SQL Server 2005-based merge publication, the merge agent fails. Additionally, you see an error message that resembles the following in the SQL Server 2005 error log file.
This problem occurs if the following conditions are true:
- The merge agent user accesses the publication by using a publication access list (PAL) user account.
- The publication has three or more multilevel merge replication filters.
- Changes are moved out of a partition during synchronization.
CAUSE
This issue occurs because the merge agent uses the sp_executesql stored procedure to access metadata tables. However, PAL users does not have access to user tables.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for SQL Server 2005. For more information, 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
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
There are no prerequisites for this hotfix.
Restart information
You do not have to restart the computer after you apply this hotfix.
Registry information
You do not have to change the registry.
Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build. The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Microsoft.sqlserver.replication.dll | 2005.90.1528.0 | 1,608,408 | 17-Feb-2006 | 17:18 | x86 |
| Microsoft.sqlserver.smo.dll | 9.0.1528.0 | 1,559,256 | 17-Feb-2006 | 17:18 | x86 |
| Msmdlocal.dll | 9.0.1528.0 | 15,588,568 | 17-Feb-2006 | 17:19 | x86 |
| Msmdredir.dll | 9.0.1528.0 | 3,927,256 | 17-Feb-2006 | 17:19 | x86 |
| Mssqlsystemresource.ldf | Not Applicable | 524,288 | 17-Feb-2006 | 14:58 | Not Applicable |
| Mssqlsystemresource.mdf | Not Applicable | 39,845,888 | 17-Feb-2006 | 14:58 | Not Applicable |
| Osql.exe | 2005.90.1528.0 | 51,416 | 17-Feb-2006 | 17:18 | x86 |
| Replrec.dll | 2005.90.1528.0 | 781,016 | 17-Feb-2006 | 17:18 | x86 |
| Sqlaccess.dll | 2005.90.1528.0 | 349,400 | 17-Feb-2006 | 17:18 | x86 |
| Sqldiag.exe | 2005.90.1528.0 | 960,216 | 17-Feb-2006 | 17:18 | x86 |
| Sqlservr.exe | 2005.90.1528.0 | 28,778,256 | 17-Feb-2006 | 17:19 | x86 |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about the naming schema for Microsoft 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
Keywords: kbfix kbexpertiseadvanced kbtshoot kbhotfixserver kbqfe kbpubtypekc KB915306
