Microsoft KB Archive/940941

From BetaArchive Wiki
Knowledge Base


FIX: Some events are not logged correctly when you enable SQL Server event forwarding on a SQL Server Agent of SQL Server 2000 to forward events to SQL Server 2005

Article ID: 940941

Article Last Modified on 11/20/2007



APPLIES TO

  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems



Bug #: 50001622 (SQL Hotfix)

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.

SYMPTOMS

Consider the following scenario:

  • You enable SQL Server event forwarding on a SQL Server Agent of SQL Server 2000. The events are forwarded from SQL Server 2000 to SQL Server 2005.
  • The event that is generated on the computer that is running SQL Server 2000 has an event ID of 17055.
  • You set up a SQL Server Agent alert on the computer that is running SQL Server 2005. This alert notifies e-mail operators about the events that are forwarded to SQL Server 2005.

In this scenario, the event that is forwarded to SQL Server 2005 is logged in the Application log and resembles the following: Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
The description for Event ID (17055) in Source (MSSQLSERVER) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details.

The SQL Server Agent alert that e-mail operators receive resembles the following:

DATE/TIME: Date Time
DESCRIPTION: Failed to formate SQL Server message. Error 317.
COMMENT: (None)
JOB RUN: (None)

CAUSE

This problem occurs because the message format that SQL Server 2000 uses differs from the message format that SQL Server 2005 uses. When SQL Server Agent detects the different message format, SQL Server Agent logs the Error event in the Application log. Therefore, the specific string is not found in a message, and SQL Server 2005 does not send a message notification.

RESOLUTION

The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

943656 Cumulative update package 5 for SQL Server 2005 Service Pack 2


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:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released


Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

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 what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

943656 Cumulative update package 5 for SQL Server 2005 Service Pack 2


REFERENCES

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released


For more information about 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 information about how to obtain SQL Server 2005 Service Pack 2, 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 and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:

For more information about 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


Keywords: kbfix kbqfe kbpubtypekc kbhotfixrollup kbexpertiseadvanced kbhotfixserver kbsql2005tool KB940941