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 the 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
When you try to use Database Mail to send an e-mail message in Microsoft SQL Server 2005, you receive the following error message:
TITLE: Microsoft SQL Server Management Studio ------------------------------ An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) ------------------------------ ADDITIONAL INFORMATION:
profile name is not valid (Microsoft SQL Server, Error: 14607)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=14607&LinkId=20476 ------------------------------ BUTTONS:OK ------------------------------
This problem occurs if the following conditions are true:
You log in to the instance of SQL Server by using a Microsoft Windows account.
You send the e-mail message by using a private Database Mail profile.
A supported hotfix is 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 software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
SQL Server 2005 Service Pack 2
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
You do not have to restart the computer after you apply this hotfix.
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 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.
To work around this problem, use one of the following techniques:
Grant permissions to the private Database Mail profile by using individual Windows accounts instead of by using Windows groups.
Use a public Database Mail profile.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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
Steps to reproduce the problem
Create a SQL Server login for a Windows group.
Add a Windows account to the Windows group.
Grant the permission for the DatabaseMailUserRole role in the msdb database to the Windows group. The Windows account is granted the permission through the Windows group.
Create a private Database Mail profile by using the Windows group.
Log in to the instance of SQL Server by using the Windows account.
Send an e-mail message by using the private Database Mail profile.
This hotfix is also included in the cumulative update package (build 3161) for SQL Server 2005 Service Pack 2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
935356 Cumulative update package (build 3161) for SQL Server 2005 Service Pack 2 is available