No global profile is configured. Specify a profile name in the @profile_name parameter

At some time in the past, I set up a maintenance plan in one SQL Server instance for rapidly tuning up a set of databases with some simple tasks such as index rebuild, etc., and I got the error message: “No global profile is configured. Specify a profile name in the @profile_name parameter”.

Whenever you set up a maintenance plan is always a good idea to add in the end the “Notify Operator” Task in order to get notified on the outcome of the maintenance plan’s execution.

Here’s a screenshot of my simple maintenance task:

Even though the first three tasks were executed successfully, when I checked the history of the job that undertakes the execution of the maintenance plan, there was an error message on the last task that is the “Notify Operator” Task.

A part of the error message is the following:

“No global profile is configured. Specify a profile name in the @profile_name parameter.”

How to Resolve the Issue

So, what does the above error message tell us? It actually says that upon the task’s execution, it cannot find a Database Mail profile in order to use it for sending the email notification.

To overcome this problem, you can set one of the available Database Mail profiles as the default one.

In SQL Server SSMS, you can do this in the following way:

1. In Management — Database Mail, double-click or right-click and choose “Configure Database Mail”. Then click on Next.
2. Then click on Manage profile security.
3. Click on Next.
4. Then you will see a list with all the available database mail profiles. You have the option to select one of these profiles to be the Default Profile (be selecting ‘Yes’ in the combo box).
5. Click on Next.
6. Click on Finish.

That should do it!

At least in my scenario I tried it and worked perfectly! 🙂

Of course, the above assumes that you have at least one Database Mail profile up and working! 🙂

Read Also

Feel free to check our other relevant articles on SQL Server troubleshooting:

• How to Resolve: Cannot Connect to WMI Provider (SQL Server Configuration Manager)
• Error converting data type varchar to numeric
• Error converting data type varchar to float
• SQLServerAgent could not be started (reason: Unable to connect to server ‘(local)’; SQLServerAgent cannot start)
• ORDER BY items must appear in the select list if SELECT DISTINCT is specified
• There is no SQL Server Failover Cluster Available to Join
• There is insufficient system memory in resource pool ‘internal’ to run this query.
• … all SQL Server troubleshooting articles

Featured Database Productivity Tools

Snippets Generator: Create and modify T-SQL snippets for use in SQL Management Studio, fast, easy and efficiently.

Learn more

Dynamic SQL Generator: Convert static T-SQL code to dynamic and vice versa, easily and fast.

Learn more

Subscribe to our newsletterand stay up to date!

Check out our latest software releases!

Check our eBooks!

Rate this article: (1 votes, average: 5.00 out of 5)

Loading...

Reference: SQLNetHub.com (https://www.sqlnethub.com)

© SQLNetHub