Article ID: 2297903 - Last Review: November 15, 2010 - Revision: 3.0

FIX: Event ID 322 is logged when a server audit is output in SQL Server 2008 or SQL Server 2008 R2

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Microsoft distributes Microsoft SQL Server 2008 R2 and 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 R2 or SQL Server 2008 fix release.

On This Page

Expand all | Collapse all

SYMPTOMS

Consider the following scenario. You create a server audit on a computer that is running Microsoft SQL Server 2008 or Microsoft SQL Server 2008 R2. You specify "Application log" as the audit destination for the server audit. Every time that the server audit is output in this scenario, an error that resembles the following is logged in the Application log:

Event Type: Error

Event Source: SQLSERVERAGENT

Event Category: Alert Engine

Event ID: 322

Date: <Date>

Time: <Time>

User: N/A

Computer: <Computer name>

Description: The data portion of event 33205 from MSSQLSERVER is invalid.

Therefore, lots of errors are logged after SQL Server 2008 or SQL Server 2008 R2 runs for some time.
Back to the top

RESOLUTION

Cumulative update information

SQL Server 2008 Service Pack 1

The fix for this issue was first released in Cumulative Update 10 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:
2279604  (http://support.microsoft.com/kb/2279604/en-US/ ) Cumulative update 10 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. 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:
970365  (http://support.microsoft.com/kb/970365/en-US/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2289254  (http://support.microsoft.com/kb/2289254/ ) Cumulative update 1 for SQL Server 2008 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 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:
2402659  (http://support.microsoft.com/kb/2402659]/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released

SQL Server 2008 R2 Service Pack 3

The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2261464  (http://support.microsoft.com/kb/2261464/ ) Cumulative Update Package 3 for SQL Server 2008 R2
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 R2 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:
981356  (http://support.microsoft.com/kb/981356/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
Back to the top

MORE INFORMATION

For more information about SQL Server Audit, visit the following websites:

Understanding SQL Server Audit (http://msdn.microsoft.com/en-us/library/cc280386.aspx)

How to: Create a Server Audit and Server Audit Specification (http://msdn.microsoft.com/en-us/library/cc280525.aspx)
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 information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897  (http://support.microsoft.com/kb/935897/ ) An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems

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  (http://support.microsoft.com/kb/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  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates
Back to the top
APPLIES TO
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Workgroup
Back to the top
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2297903
Back to the top