Microsoft KB Archive/934226

From BetaArchive Wiki

Article ID: 934226

Article Last Modified on 11/20/2007



APPLIES TO

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



Bug #: 50000958 (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.

SUMMARY

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


SYMPTOMS

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.


RESOLUTION

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

  • 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

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 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.maintenanceplantasks.dll 9.0.3156.0 296,304 15-Mar-2007 09:35 x86
Mssqlsystemresource.ldf Not Applicable 524,288 14-Mar-2007 18:46 Not Applicable
Mssqlsystemresource.mdf Not Applicable 40,173,568 14-Mar-2007 18:46 Not Applicable
Rdistcom.dll 2005.90.3156.0 644,464 15-Mar-2007 09:35 x86
Msmdlocal.dll 9.0.3156.0 15,930,224 15-Mar-2007 09:35 x86
Sqlaccess.dll 2005.90.3156.0 350,576 15-Mar-2007 09:35 x86
Sqlservr.exe 2005.90.3156.0 29,192,048 15-Mar-2007 09:35 x86
Sysdbupg.sql Not Applicable 510,622 14-Mar-2007 16:42 Not Applicable


WORKAROUND

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.


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 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

  1. Create a SQL Server login for a Windows group.
  2. Add a Windows account to the Windows group.
  3. 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.
  4. Create a private Database Mail profile by using the Windows group.
  5. Log in to the instance of SQL Server by using the Windows account.
  6. 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


Keywords: kbfix kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver kbsql2005mail KB934226