Select the product you need help with
FIX: Error message when you send an e-mail by using a private Database Mail profile in SQL Server 2005 or in SQL Server 2008: "profile name is not valid"Article ID: 971402 - View products that this article applies to. 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. On This PageSYMPTOMSYou create a non-administrator Windows account that is a member of multiple Windows groups. These Windows groups have the same permission setting. In Microsoft SQL Server 2005 or in Microsoft SQL Server 2008, you add these Windows groups as SQL Server logins. You configure Database Mail accounts and profiles by using these SQL Server logins. When you use Database Mail to send an e-mail, you receive Error 14607 in the following scenarios: Scenario 1 You create a private Database Mail profile that uses the Windows account as the Simple Mail Transfer Protocol (SMTP) account. You configure the private profile for one of the Windows groups that was not first added as a SQL Server login. When you send an e-mail by using the profile, you receive the following error message: Msg 14607, Level 16, State 1, Procedure sp_send_dbmail, Line 136 profile name is not valid You create two private Database Mail profiles that use the Windows account as the SMTP account. You configure the private profile for one of the Windows groups. When you send an e-mail by using the nondefault instance in the two private profiles, you receive the following error message: Msg 14607, Level 16, State 1, Procedure sp_send_dbmail, Line 136 profile name is not valid Scenario 3 You create a private Database Mail profile that uses the Windows account as the SMTP account. You configure the private profile for one of the Windows groups. Then, you explicitly add the Windows account as a SQL Server login. When you send an e-mail by using the profile, you receive the following error message: Msg 515, Level 16, State 2, Procedure sp_validate_user, Line 19 Cannot insert the value NULL into column 'permission path', table '@temp'; column does not allow nulls. INSERT fails. The statement has been terminated. Msg 14607, Level 16, State 1, Procedure sp_send_dbmail, Line 136 profile name is not valid RESOLUTIONCumulative update informationThe release version of SQL Server 2008Important You must install this cumulative update package if your computer is running the release version of SQL Server 2008.The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base: 971490 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:
(http://support.microsoft.com/kb/971490/
)
Cumulative update package 6 for SQL Server 2008956909
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was releasedSQL Server 2008 Service Pack 1Important You must install this cumulative update package if your computer is running SQL Server 2008 Service Pack 1.The fix for this issue was also released in Cumulative Update 3 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: 971491 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. 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:
(http://support.microsoft.com/kb/971491/LN/
)
Cumulative update package 3 for SQL Server 2008 Service Pack 1970365
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/970365/LN/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
SQL Server 2005 Service Pack 3Important You must install this cumulative update package if your computer is running SQL Server 2005 Service Pack 3.The fix for this issue was first released in Cumulative Update 4 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 970279
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:
(http://support.microsoft.com/kb/970279
/LN/
)
Cumulative update package 4 for SQL Server 2005 Service Pack 3960598
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/960598/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. REFERENCES
For more information about the list of builds that are available after SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
960598
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:
(http://support.microsoft.com/kb/960598/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
935897
For more information about how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
913089 For more information about the new features and the new improvements in SQL Server 2005 Service Pack 3, visit the following Microsoft Web site:
(http://support.microsoft.com/kb/913089/
)
How to obtain the latest service pack for SQL Server 2005
http://go.microsoft.com/fwlink/?LinkId=131442
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:
(http://go.microsoft.com/fwlink/?LinkId=131442)
822499
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
PropertiesArticle ID: 971402 - Last Review: July 21, 2009 - Revision: 2.0 APPLIES TO
|
Back to the top
