Skip to main content

Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 199 The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).

Hi guys!

Here's another quick and easy post.

Scenario
I was trying to copy a SQL agent job from one server to another by just copying the script of that SQL job. You can copy any script by right clicking a job > Script job as > create to > new query window.

I pasted the job on a different server and tried to execute it and received this error:

Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 199 The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).

This error message is simply saying for the variable '@owner_login_name', the user account associated with the variable is incorrect because it does not exist.

Fix
Simply update the variable for '@owner_login_name' to a valid user account for the current SQL instance.

Now when you execute the script again to create the SQL agent job your results will be:

Command(s) completed successfully.


If you have any further questions, please post below.

Thank you and Happy reading,


-marshé hutchinson
#learnSQLwithme
Labels:

Comments

  1. JAYJanuary 30, 2024 at 12:39 PM

    Hi I have a similar error

    I was trying to copy a SQL agent job from one server to another by just copying the script of that SQL job. You can copy any script by right clicking a job > Script job as > create to > new query window.

    I pasted the job on a different server and tried to execute it and received this error:

    Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 251
    The specified '@notify_email.operator_name' is invalid (valid values are returned by sp_help_operator).

    Above is the error I encounter.

    Please help me out with this error.

    ReplyDelete
    Replies
    1. MarsheJanuary 30, 2024 at 1:27 PM

      Hi Jay. Did you check if:
      1. there's already a SQL job with the same name on the new server?
      2. the new server name was updated in your script or is the script still showing the old server name?
      3. your SQL account has permissions to execute the script on the server?

      Delete

Post a Comment

Popular posts from this blog

Executed as user: . Incorrect syntax near ''. [SQLSTATE 42000] (Error 102). The step failed.

Hi everyone! Today's post is about an all too common problem... syntax issues. Whether you fat-finger your keyboard or are always in a rush, chances are you have already encountered many syntax errors. But if you are a newbie,  your syntax error is just around the corner. No worries, this is an easy fix. Syntax errors just let you know part of your code or script is incorrect. Scenario I have a SQL agent job that is using the SQL command line to perform index maintenance, but it is failing. Here's my code : sqlcmd -E -S $(ESCAPE_SQUOTE(SRVR)) -d master -Q "EXECUTE dbo.IndexOptimize @Databases = ' databaseName ', @FragmentationLow = NULL, @FragmentationMedium = 'INDEX_REORGANIZE,INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE', @FragmentationHigh = 'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE', @FragmentationLevel1 = 5, @FragmentationLevel2 = 30, @UpdateStatistics = 'ALL',@WaitAtLowPriorityMaxDuration = 180, @WaitAtLowPriorityAbortA...
Post a Comment
Read more

How to export SQL agent jobs from your SQL Server instance

Hi everyone! As a database administrator, you always need a copy of your data and data processes for: migrating servers disaster recovery backup procedures/best practices This post covers a simple Powershell script. The script is to take a backup of all the SQL agent jobs on your SQL server instance. If you ever needed to recreate all the jobs on another server, all you would have to do is execute the SQL script. I. In SSMS (SQL Server Management Studio), create an empty .SQL file and save it with this naming convention: I.e. SqlAgentJobs_PROD01.sql } This file will represent all the SQL agent jobs on the primary production SQL server. II. Copy the "SqlAgentJobs_PROD01.sql" file from above to a network share. III. Run the Powershell script below in  Powershell ISE as administrator: ##migrating jobs from one server to another with the replace command $SqlConnection = New-Object System.Data.SqlClient.SqlConnection $SqlConnection.ConnectionStrin...
Post a Comment
Read more