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

event id 101 task start failed - task scheduler event id 101 launch failure

Hello again. This post is related to automating SQL server tasks with Task Scheduler. In this example I was tasked with exporting SQL server agent jobs twice a month. To achieve this, I setup a task scheduler task that ran a PowerShell script that: establishes a local connection to the SQL server. cleans the file before writing to the .sql file to avoid adding on (appending) results on subsequent runs of the task scheduler task. when a connection is established, export the SQL agent jobs on the server to a .sql file on a remote server. sends a confirmation email via the SQL server database mail profile that the SQL agent jobs were exported to the specified remote server path. That was a mouthful. Now that you know my task scheduler task is calling a PowerShell script, let's get back to why it is failing.  The good news is this error is not related to the script. The error launch failure means the task could not even run. This is most likely due to a permissi
Post a Comment
Read more

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