Hello all,
I have a job I created with user A, but I need user B to be able to execute
this job programatically. I've given user B permission to EXECUTE the
"msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
error thrown. The following is the error I get when I run it with user B.
This error does not appear when I run it with user A.
The specified @.job_name ('MyJobName') does not exist.
After doing some research by looking at the system sprocs, I found that the
error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
researched that sproc and then found the system code that is throwing the
error, listed below.
-- Check if the job name is ambiguous
IF ((SELECT COUNT(*)
FROM msdb.dbo.sysjobs_view
WHERE (name = @.job_name)) > 1)
BEGIN
RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
@.name_of_name_parameter)
RETURN(1) -- Failure
END
I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
were returned. So it appears that the view is filtering the results by user
and the job is not found which is causing the error.
Do you guys know of a way I can make this work? I would appreciate any help.
Thanks!
Johnny
Hi Johnny,
Only members of the sysadmin fixed role or the jobowner can start a job.
HTH
Adam
Adam J Warne, MCDBA
"Johnny" wrote:
> Hello all,
> I have a job I created with user A, but I need user B to be able to execute
> this job programatically. I've given user B permission to EXECUTE the
> "msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
> error thrown. The following is the error I get when I run it with user B.
> This error does not appear when I run it with user A.
> The specified @.job_name ('MyJobName') does not exist.
> After doing some research by looking at the system sprocs, I found that the
> error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
> researched that sproc and then found the system code that is throwing the
> error, listed below.
> -- Check if the job name is ambiguous
> IF ((SELECT COUNT(*)
> FROM msdb.dbo.sysjobs_view
> WHERE (name = @.job_name)) > 1)
> BEGIN
> RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
> @.name_of_name_parameter)
> RETURN(1) -- Failure
> END
>
> I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
> were returned. So it appears that the view is filtering the results by user
> and the job is not found which is causing the error.
> Do you guys know of a way I can make this work? I would appreciate any help.
> Thanks!
> Johnny
>
|||Thanks. I didnt want to do that but I guess I have no choice.
Johnny
"Adam Warne" wrote:
[vbcol=seagreen]
> Hi Johnny,
> Only members of the sysadmin fixed role or the jobowner can start a job.
> HTH
> Adam
> --
> Adam J Warne, MCDBA
>
> "Johnny" wrote:
Showing posts with label job. Show all posts
Showing posts with label job. Show all posts
Sunday, March 25, 2012
Can't start a job that was created by user A from user B
Hello all,
I have a job I created with user A, but I need user B to be able to execute
this job programatically. I've given user B permission to EXECUTE the
"msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
error thrown. The following is the error I get when I run it with user B.
This error does not appear when I run it with user A.
The specified @.job_name ('MyJobName') does not exist.
After doing some research by looking at the system sprocs, I found that the
error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
researched that sproc and then found the system code that is throwing the
error, listed below.
-- Check if the job name is ambiguous
IF ((SELECT COUNT(*)
FROM msdb.dbo.sysjobs_view
WHERE (name = @.job_name)) > 1)
BEGIN
RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
@.name_of_name_parameter)
RETURN(1) -- Failure
END
I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
were returned. So it appears that the view is filtering the results by user
and the job is not found which is causing the error.
Do you guys know of a way I can make this work? I would appreciate any help.
Thanks!
JohnnyHi Johnny,
Only members of the sysadmin fixed role or the jobowner can start a job.
HTH
Adam
--
Adam J Warne, MCDBA
"Johnny" wrote:
> Hello all,
> I have a job I created with user A, but I need user B to be able to execut
e
> this job programatically. I've given user B permission to EXECUTE the
> "msdb.dbo.sp_start_job" sproc and the user is able to execute it but with
an
> error thrown. The following is the error I get when I run it with user B.
> This error does not appear when I run it with user A.
> The specified @.job_name ('MyJobName') does not exist.
> After doing some research by looking at the system sprocs, I found that th
e
> error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'.
I
> researched that sproc and then found the system code that is throwing the
> error, listed below.
> -- Check if the job name is ambiguous
> IF ((SELECT COUNT(*)
> FROM msdb.dbo.sysjobs_view
> WHERE (name = @.job_name)) > 1)
> BEGIN
> RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
> @.name_of_name_parameter)
> RETURN(1) -- Failure
> END
>
> I performed a SELECT * query to the sysjobs_view view with user B and 0 ro
ws
> were returned. So it appears that the view is filtering the results by use
r
> and the job is not found which is causing the error.
> Do you guys know of a way I can make this work? I would appreciate any hel
p.
> Thanks!
> Johnny
>|||Thanks. I didnt want to do that but I guess I have no choice.
Johnny
"Adam Warne" wrote:
[vbcol=seagreen]
> Hi Johnny,
> Only members of the sysadmin fixed role or the jobowner can start a job.
> HTH
> Adam
> --
> Adam J Warne, MCDBA
>
> "Johnny" wrote:
>
I have a job I created with user A, but I need user B to be able to execute
this job programatically. I've given user B permission to EXECUTE the
"msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
error thrown. The following is the error I get when I run it with user B.
This error does not appear when I run it with user A.
The specified @.job_name ('MyJobName') does not exist.
After doing some research by looking at the system sprocs, I found that the
error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
researched that sproc and then found the system code that is throwing the
error, listed below.
-- Check if the job name is ambiguous
IF ((SELECT COUNT(*)
FROM msdb.dbo.sysjobs_view
WHERE (name = @.job_name)) > 1)
BEGIN
RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
@.name_of_name_parameter)
RETURN(1) -- Failure
END
I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
were returned. So it appears that the view is filtering the results by user
and the job is not found which is causing the error.
Do you guys know of a way I can make this work? I would appreciate any help.
Thanks!
JohnnyHi Johnny,
Only members of the sysadmin fixed role or the jobowner can start a job.
HTH
Adam
--
Adam J Warne, MCDBA
"Johnny" wrote:
> Hello all,
> I have a job I created with user A, but I need user B to be able to execut
e
> this job programatically. I've given user B permission to EXECUTE the
> "msdb.dbo.sp_start_job" sproc and the user is able to execute it but with
an
> error thrown. The following is the error I get when I run it with user B.
> This error does not appear when I run it with user A.
> The specified @.job_name ('MyJobName') does not exist.
> After doing some research by looking at the system sprocs, I found that th
e
> error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'.
I
> researched that sproc and then found the system code that is throwing the
> error, listed below.
> -- Check if the job name is ambiguous
> IF ((SELECT COUNT(*)
> FROM msdb.dbo.sysjobs_view
> WHERE (name = @.job_name)) > 1)
> BEGIN
> RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
> @.name_of_name_parameter)
> RETURN(1) -- Failure
> END
>
> I performed a SELECT * query to the sysjobs_view view with user B and 0 ro
ws
> were returned. So it appears that the view is filtering the results by use
r
> and the job is not found which is causing the error.
> Do you guys know of a way I can make this work? I would appreciate any hel
p.
> Thanks!
> Johnny
>|||Thanks. I didnt want to do that but I guess I have no choice.
Johnny
"Adam Warne" wrote:
[vbcol=seagreen]
> Hi Johnny,
> Only members of the sysadmin fixed role or the jobowner can start a job.
> HTH
> Adam
> --
> Adam J Warne, MCDBA
>
> "Johnny" wrote:
>
Can't start a job that was created by user A from user B
Hello all,
I have a job I created with user A, but I need user B to be able to execute
this job programatically. I've given user B permission to EXECUTE the
"msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
error thrown. The following is the error I get when I run it with user B.
This error does not appear when I run it with user A.
The specified @.job_name ('MyJobName') does not exist.
After doing some research by looking at the system sprocs, I found that the
error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
researched that sproc and then found the system code that is throwing the
error, listed below.
-- Check if the job name is ambiguous
IF ((SELECT COUNT(*)
FROM msdb.dbo.sysjobs_view
WHERE (name = @.job_name)) > 1)
BEGIN
RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
@.name_of_name_parameter)
RETURN(1) -- Failure
END
I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
were returned. So it appears that the view is filtering the results by user
and the job is not found which is causing the error.
Do you guys know of a way I can make this work? I would appreciate any help.
Thanks!
JohnnyHi Johnny,
Only members of the sysadmin fixed role or the jobowner can start a job.
HTH
Adam
--
Adam J Warne, MCDBA
"Johnny" wrote:
> Hello all,
> I have a job I created with user A, but I need user B to be able to execute
> this job programatically. I've given user B permission to EXECUTE the
> "msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
> error thrown. The following is the error I get when I run it with user B.
> This error does not appear when I run it with user A.
> The specified @.job_name ('MyJobName') does not exist.
> After doing some research by looking at the system sprocs, I found that the
> error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
> researched that sproc and then found the system code that is throwing the
> error, listed below.
> -- Check if the job name is ambiguous
> IF ((SELECT COUNT(*)
> FROM msdb.dbo.sysjobs_view
> WHERE (name = @.job_name)) > 1)
> BEGIN
> RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
> @.name_of_name_parameter)
> RETURN(1) -- Failure
> END
>
> I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
> were returned. So it appears that the view is filtering the results by user
> and the job is not found which is causing the error.
> Do you guys know of a way I can make this work? I would appreciate any help.
> Thanks!
> Johnny
>|||Thanks. I didnt want to do that but I guess I have no choice.
Johnny
"Adam Warne" wrote:
> Hi Johnny,
> Only members of the sysadmin fixed role or the jobowner can start a job.
> HTH
> Adam
> --
> Adam J Warne, MCDBA
>
> "Johnny" wrote:
> > Hello all,
> >
> > I have a job I created with user A, but I need user B to be able to execute
> > this job programatically. I've given user B permission to EXECUTE the
> > "msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
> > error thrown. The following is the error I get when I run it with user B.
> > This error does not appear when I run it with user A.
> >
> > The specified @.job_name ('MyJobName') does not exist.
> >
> > After doing some research by looking at the system sprocs, I found that the
> > error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
> > researched that sproc and then found the system code that is throwing the
> > error, listed below.
> >
> > -- Check if the job name is ambiguous
> > IF ((SELECT COUNT(*)
> > FROM msdb.dbo.sysjobs_view
> > WHERE (name = @.job_name)) > 1)
> > BEGIN
> > RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
> > @.name_of_name_parameter)
> > RETURN(1) -- Failure
> > END
> >
> >
> > I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
> > were returned. So it appears that the view is filtering the results by user
> > and the job is not found which is causing the error.
> >
> > Do you guys know of a way I can make this work? I would appreciate any help.
> > Thanks!
> >
> > Johnny
> >sql
I have a job I created with user A, but I need user B to be able to execute
this job programatically. I've given user B permission to EXECUTE the
"msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
error thrown. The following is the error I get when I run it with user B.
This error does not appear when I run it with user A.
The specified @.job_name ('MyJobName') does not exist.
After doing some research by looking at the system sprocs, I found that the
error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
researched that sproc and then found the system code that is throwing the
error, listed below.
-- Check if the job name is ambiguous
IF ((SELECT COUNT(*)
FROM msdb.dbo.sysjobs_view
WHERE (name = @.job_name)) > 1)
BEGIN
RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
@.name_of_name_parameter)
RETURN(1) -- Failure
END
I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
were returned. So it appears that the view is filtering the results by user
and the job is not found which is causing the error.
Do you guys know of a way I can make this work? I would appreciate any help.
Thanks!
JohnnyHi Johnny,
Only members of the sysadmin fixed role or the jobowner can start a job.
HTH
Adam
--
Adam J Warne, MCDBA
"Johnny" wrote:
> Hello all,
> I have a job I created with user A, but I need user B to be able to execute
> this job programatically. I've given user B permission to EXECUTE the
> "msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
> error thrown. The following is the error I get when I run it with user B.
> This error does not appear when I run it with user A.
> The specified @.job_name ('MyJobName') does not exist.
> After doing some research by looking at the system sprocs, I found that the
> error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
> researched that sproc and then found the system code that is throwing the
> error, listed below.
> -- Check if the job name is ambiguous
> IF ((SELECT COUNT(*)
> FROM msdb.dbo.sysjobs_view
> WHERE (name = @.job_name)) > 1)
> BEGIN
> RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
> @.name_of_name_parameter)
> RETURN(1) -- Failure
> END
>
> I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
> were returned. So it appears that the view is filtering the results by user
> and the job is not found which is causing the error.
> Do you guys know of a way I can make this work? I would appreciate any help.
> Thanks!
> Johnny
>|||Thanks. I didnt want to do that but I guess I have no choice.
Johnny
"Adam Warne" wrote:
> Hi Johnny,
> Only members of the sysadmin fixed role or the jobowner can start a job.
> HTH
> Adam
> --
> Adam J Warne, MCDBA
>
> "Johnny" wrote:
> > Hello all,
> >
> > I have a job I created with user A, but I need user B to be able to execute
> > this job programatically. I've given user B permission to EXECUTE the
> > "msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
> > error thrown. The following is the error I get when I run it with user B.
> > This error does not appear when I run it with user A.
> >
> > The specified @.job_name ('MyJobName') does not exist.
> >
> > After doing some research by looking at the system sprocs, I found that the
> > error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
> > researched that sproc and then found the system code that is throwing the
> > error, listed below.
> >
> > -- Check if the job name is ambiguous
> > IF ((SELECT COUNT(*)
> > FROM msdb.dbo.sysjobs_view
> > WHERE (name = @.job_name)) > 1)
> > BEGIN
> > RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
> > @.name_of_name_parameter)
> > RETURN(1) -- Failure
> > END
> >
> >
> > I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
> > were returned. So it appears that the view is filtering the results by user
> > and the job is not found which is causing the error.
> >
> > Do you guys know of a way I can make this work? I would appreciate any help.
> > Thanks!
> >
> > Johnny
> >sql
Thursday, March 22, 2012
Can't send operator email in SQL Sever 2005
I have set up Database Mail
I have sent a test message successfully
I have set up a Operator
When I create a test job to send a test message to the operator the
TSQL is
EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris Auer',@.body=N'wewqe'
When I run that query I get
Msg 14636, Level 16, State 1, Procedure sp_send_dbmail, Line 94
No global profile is configured. Specify a profile name in the
@.profile_name parameter.
In the job log I have this
Executing the query "EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris
Auer',@.body=N'wewqe'
" failed with the following error: "No global profile is configured.
Specify a profile name in the @.profile_name parameter.". Possible
failure reasons: Problems with the query, "ResultSet" property not set
correctly, parameters not set correctly, or connection not established
correctly.
What is a global profile?
I have already made the registry change to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.1\SQLServerAgent
I made DatabaseMailProfile my default profile name in Database Mail and
I made UseDatabaseMail = 1
Any ideas, thanks. This is driving me up a wall.'
Chris Auer
Looks like you only need to specify a profile name or define a default
profile.
Right-click Database Mail, select Configure Database Mail and select Manage
profile security. Here you have the choice to configure your profiles as
public, private and/or default.
If you do not have a default profile configured you will need to specify the
@.profile_name parameter. This is the same name under 'Profile name' on the
Database Mail Configuration Wizard.
Also, take a look at 'Database Mail [SQL Server], security on BOL.
Ben Nevarez, MCDBA, OCP
"Chris Auer" <chris.auer@.gmail.com> wrote in message
news:1132958108.969902.311470@.g44g2000cwa.googlegr oups.com...
>I have set up Database Mail
> I have sent a test message successfully
> I have set up a Operator
> When I create a test job to send a test message to the operator the
> TSQL is
> EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris Auer',@.body=N'wewqe'
> When I run that query I get
> Msg 14636, Level 16, State 1, Procedure sp_send_dbmail, Line 94
> No global profile is configured. Specify a profile name in the
> @.profile_name parameter.
> In the job log I have this
> Executing the query "EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris
> Auer',@.body=N'wewqe'
> " failed with the following error: "No global profile is configured.
> Specify a profile name in the @.profile_name parameter.". Possible
> failure reasons: Problems with the query, "ResultSet" property not set
> correctly, parameters not set correctly, or connection not established
> correctly.
>
> What is a global profile?
> I have already made the registry change to
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\MSSQL.1\SQLServerAgent
> I made DatabaseMailProfile my default profile name in Database Mail and
> I made UseDatabaseMail = 1
> Any ideas, thanks. This is driving me up a wall.'
> Chris Auer
>
|||I also have the exact same problem, and is driving me nuts too. I have
created a default, private profile for the agent to use, however it still
fails.
I get the same error message. I can send database mail, but the agent fails.
I've tried public default profiles and they fail too. The agent account is
setup in msdb in the DatabaseMailUser role.
The interseting thing is that the 'Test' button is dimmed on the SQL Agent,
Alert System, Mail Session page even though the correct profile is selected!
Please, any help will be greatly appreciated.
Jim
"Ben Nevarez" wrote:
> Looks like you only need to specify a profile name or define a default
> profile.
> Right-click Database Mail, select Configure Database Mail and select Manage
> profile security. Here you have the choice to configure your profiles as
> public, private and/or default.
> If you do not have a default profile configured you will need to specify the
> @.profile_name parameter. This is the same name under 'Profile name' on the
> Database Mail Configuration Wizard.
> Also, take a look at 'Database Mail [SQL Server], security on BOL.
> Ben Nevarez, MCDBA, OCP
>
> "Chris Auer" <chris.auer@.gmail.com> wrote in message
> news:1132958108.969902.311470@.g44g2000cwa.googlegr oups.com...
>
>
I have sent a test message successfully
I have set up a Operator
When I create a test job to send a test message to the operator the
TSQL is
EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris Auer',@.body=N'wewqe'
When I run that query I get
Msg 14636, Level 16, State 1, Procedure sp_send_dbmail, Line 94
No global profile is configured. Specify a profile name in the
@.profile_name parameter.
In the job log I have this
Executing the query "EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris
Auer',@.body=N'wewqe'
" failed with the following error: "No global profile is configured.
Specify a profile name in the @.profile_name parameter.". Possible
failure reasons: Problems with the query, "ResultSet" property not set
correctly, parameters not set correctly, or connection not established
correctly.
What is a global profile?
I have already made the registry change to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.1\SQLServerAgent
I made DatabaseMailProfile my default profile name in Database Mail and
I made UseDatabaseMail = 1
Any ideas, thanks. This is driving me up a wall.'
Chris Auer
Looks like you only need to specify a profile name or define a default
profile.
Right-click Database Mail, select Configure Database Mail and select Manage
profile security. Here you have the choice to configure your profiles as
public, private and/or default.
If you do not have a default profile configured you will need to specify the
@.profile_name parameter. This is the same name under 'Profile name' on the
Database Mail Configuration Wizard.
Also, take a look at 'Database Mail [SQL Server], security on BOL.
Ben Nevarez, MCDBA, OCP
"Chris Auer" <chris.auer@.gmail.com> wrote in message
news:1132958108.969902.311470@.g44g2000cwa.googlegr oups.com...
>I have set up Database Mail
> I have sent a test message successfully
> I have set up a Operator
> When I create a test job to send a test message to the operator the
> TSQL is
> EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris Auer',@.body=N'wewqe'
> When I run that query I get
> Msg 14636, Level 16, State 1, Procedure sp_send_dbmail, Line 94
> No global profile is configured. Specify a profile name in the
> @.profile_name parameter.
> In the job log I have this
> Executing the query "EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris
> Auer',@.body=N'wewqe'
> " failed with the following error: "No global profile is configured.
> Specify a profile name in the @.profile_name parameter.". Possible
> failure reasons: Problems with the query, "ResultSet" property not set
> correctly, parameters not set correctly, or connection not established
> correctly.
>
> What is a global profile?
> I have already made the registry change to
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\MSSQL.1\SQLServerAgent
> I made DatabaseMailProfile my default profile name in Database Mail and
> I made UseDatabaseMail = 1
> Any ideas, thanks. This is driving me up a wall.'
> Chris Auer
>
|||I also have the exact same problem, and is driving me nuts too. I have
created a default, private profile for the agent to use, however it still
fails.
I get the same error message. I can send database mail, but the agent fails.
I've tried public default profiles and they fail too. The agent account is
setup in msdb in the DatabaseMailUser role.
The interseting thing is that the 'Test' button is dimmed on the SQL Agent,
Alert System, Mail Session page even though the correct profile is selected!
Please, any help will be greatly appreciated.
Jim
"Ben Nevarez" wrote:
> Looks like you only need to specify a profile name or define a default
> profile.
> Right-click Database Mail, select Configure Database Mail and select Manage
> profile security. Here you have the choice to configure your profiles as
> public, private and/or default.
> If you do not have a default profile configured you will need to specify the
> @.profile_name parameter. This is the same name under 'Profile name' on the
> Database Mail Configuration Wizard.
> Also, take a look at 'Database Mail [SQL Server], security on BOL.
> Ben Nevarez, MCDBA, OCP
>
> "Chris Auer" <chris.auer@.gmail.com> wrote in message
> news:1132958108.969902.311470@.g44g2000cwa.googlegr oups.com...
>
>
Can't send operator email in SQL Sever 2005
I have set up Database Mail
I have sent a test message successfully
I have set up a Operator
When I create a test job to send a test message to the operator the
TSQL is
EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris Auer',@.body=N'wewqe'
When I run that query I get
Msg 14636, Level 16, State 1, Procedure sp_send_dbmail, Line 94
No global profile is configured. Specify a profile name in the
@.profile_name parameter.
In the job log I have this
Executing the query "EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris
Auer',@.body=N'wewqe'
" failed with the following error: "No global profile is configured.
Specify a profile name in the @.profile_name parameter.". Possible
failure reasons: Problems with the query, "ResultSet" property not set
correctly, parameters not set correctly, or connection not established
correctly.
What is a global profile?
I have already made the registry change to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.1\SQLServerAgent
I made DatabaseMailProfile my default profile name in Database Mail and
I made UseDatabaseMail = 1
Any ideas, thanks. This is driving me up a wall.'
Chris AuerLooks like you only need to specify a profile name or define a default
profile.
Right-click Database Mail, select Configure Database Mail and select Manage
profile security. Here you have the choice to configure your profiles as
public, private and/or default.
If you do not have a default profile configured you will need to specify the
@.profile_name parameter. This is the same name under 'Profile name' on the
Database Mail Configuration Wizard.
Also, take a look at 'Database Mail [SQL Server], security on BOL.
Ben Nevarez, MCDBA, OCP
"Chris Auer" <chris.auer@.gmail.com> wrote in message
news:1132958108.969902.311470@.g44g2000cwa.googlegroups.com...
>I have set up Database Mail
> I have sent a test message successfully
> I have set up a Operator
> When I create a test job to send a test message to the operator the
> TSQL is
> EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris Auer',@.body=N'wewqe'
> When I run that query I get
> Msg 14636, Level 16, State 1, Procedure sp_send_dbmail, Line 94
> No global profile is configured. Specify a profile name in the
> @.profile_name parameter.
> In the job log I have this
> Executing the query "EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris
> Auer',@.body=N'wewqe'
> " failed with the following error: "No global profile is configured.
> Specify a profile name in the @.profile_name parameter.". Possible
> failure reasons: Problems with the query, "ResultSet" property not set
> correctly, parameters not set correctly, or connection not established
> correctly.
>
> What is a global profile?
> I have already made the registry change to
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\MSSQL.1\SQLServerAgent
> I made DatabaseMailProfile my default profile name in Database Mail and
> I made UseDatabaseMail = 1
> Any ideas, thanks. This is driving me up a wall.'
> Chris Auer
>|||I also have the exact same problem, and is driving me nuts too. I have
created a default, private profile for the agent to use, however it still
fails.
I get the same error message. I can send database mail, but the agent fails.
I've tried public default profiles and they fail too. The agent account is
setup in msdb in the DatabaseMailUser role.
The interseting thing is that the 'Test' button is dimmed on the SQL Agent,
Alert System, Mail Session page even though the correct profile is selected!
Please, any help will be greatly appreciated.
Jim
"Ben Nevarez" wrote:
> Looks like you only need to specify a profile name or define a default
> profile.
> Right-click Database Mail, select Configure Database Mail and select Manage
> profile security. Here you have the choice to configure your profiles as
> public, private and/or default.
> If you do not have a default profile configured you will need to specify the
> @.profile_name parameter. This is the same name under 'Profile name' on the
> Database Mail Configuration Wizard.
> Also, take a look at 'Database Mail [SQL Server], security on BOL.
> Ben Nevarez, MCDBA, OCP
>
> "Chris Auer" <chris.auer@.gmail.com> wrote in message
> news:1132958108.969902.311470@.g44g2000cwa.googlegroups.com...
> >I have set up Database Mail
> > I have sent a test message successfully
> > I have set up a Operator
> >
> > When I create a test job to send a test message to the operator the
> > TSQL is
> >
> > EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris Auer',@.body=N'wewqe'
> >
> > When I run that query I get
> >
> > Msg 14636, Level 16, State 1, Procedure sp_send_dbmail, Line 94
> > No global profile is configured. Specify a profile name in the
> > @.profile_name parameter.
> >
> > In the job log I have this
> >
> > Executing the query "EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris
> > Auer',@.body=N'wewqe'
> > " failed with the following error: "No global profile is configured.
> > Specify a profile name in the @.profile_name parameter.". Possible
> > failure reasons: Problems with the query, "ResultSet" property not set
> > correctly, parameters not set correctly, or connection not established
> > correctly.
> >
> >
> > What is a global profile?
> >
> > I have already made the registry change to
> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> > Server\MSSQL.1\SQLServerAgent
> > I made DatabaseMailProfile my default profile name in Database Mail and
> > I made UseDatabaseMail = 1
> >
> > Any ideas, thanks. This is driving me up a wall.'
> >
> > Chris Auer
> >
>
>sql
I have sent a test message successfully
I have set up a Operator
When I create a test job to send a test message to the operator the
TSQL is
EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris Auer',@.body=N'wewqe'
When I run that query I get
Msg 14636, Level 16, State 1, Procedure sp_send_dbmail, Line 94
No global profile is configured. Specify a profile name in the
@.profile_name parameter.
In the job log I have this
Executing the query "EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris
Auer',@.body=N'wewqe'
" failed with the following error: "No global profile is configured.
Specify a profile name in the @.profile_name parameter.". Possible
failure reasons: Problems with the query, "ResultSet" property not set
correctly, parameters not set correctly, or connection not established
correctly.
What is a global profile?
I have already made the registry change to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.1\SQLServerAgent
I made DatabaseMailProfile my default profile name in Database Mail and
I made UseDatabaseMail = 1
Any ideas, thanks. This is driving me up a wall.'
Chris AuerLooks like you only need to specify a profile name or define a default
profile.
Right-click Database Mail, select Configure Database Mail and select Manage
profile security. Here you have the choice to configure your profiles as
public, private and/or default.
If you do not have a default profile configured you will need to specify the
@.profile_name parameter. This is the same name under 'Profile name' on the
Database Mail Configuration Wizard.
Also, take a look at 'Database Mail [SQL Server], security on BOL.
Ben Nevarez, MCDBA, OCP
"Chris Auer" <chris.auer@.gmail.com> wrote in message
news:1132958108.969902.311470@.g44g2000cwa.googlegroups.com...
>I have set up Database Mail
> I have sent a test message successfully
> I have set up a Operator
> When I create a test job to send a test message to the operator the
> TSQL is
> EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris Auer',@.body=N'wewqe'
> When I run that query I get
> Msg 14636, Level 16, State 1, Procedure sp_send_dbmail, Line 94
> No global profile is configured. Specify a profile name in the
> @.profile_name parameter.
> In the job log I have this
> Executing the query "EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris
> Auer',@.body=N'wewqe'
> " failed with the following error: "No global profile is configured.
> Specify a profile name in the @.profile_name parameter.". Possible
> failure reasons: Problems with the query, "ResultSet" property not set
> correctly, parameters not set correctly, or connection not established
> correctly.
>
> What is a global profile?
> I have already made the registry change to
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\MSSQL.1\SQLServerAgent
> I made DatabaseMailProfile my default profile name in Database Mail and
> I made UseDatabaseMail = 1
> Any ideas, thanks. This is driving me up a wall.'
> Chris Auer
>|||I also have the exact same problem, and is driving me nuts too. I have
created a default, private profile for the agent to use, however it still
fails.
I get the same error message. I can send database mail, but the agent fails.
I've tried public default profiles and they fail too. The agent account is
setup in msdb in the DatabaseMailUser role.
The interseting thing is that the 'Test' button is dimmed on the SQL Agent,
Alert System, Mail Session page even though the correct profile is selected!
Please, any help will be greatly appreciated.
Jim
"Ben Nevarez" wrote:
> Looks like you only need to specify a profile name or define a default
> profile.
> Right-click Database Mail, select Configure Database Mail and select Manage
> profile security. Here you have the choice to configure your profiles as
> public, private and/or default.
> If you do not have a default profile configured you will need to specify the
> @.profile_name parameter. This is the same name under 'Profile name' on the
> Database Mail Configuration Wizard.
> Also, take a look at 'Database Mail [SQL Server], security on BOL.
> Ben Nevarez, MCDBA, OCP
>
> "Chris Auer" <chris.auer@.gmail.com> wrote in message
> news:1132958108.969902.311470@.g44g2000cwa.googlegroups.com...
> >I have set up Database Mail
> > I have sent a test message successfully
> > I have set up a Operator
> >
> > When I create a test job to send a test message to the operator the
> > TSQL is
> >
> > EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris Auer',@.body=N'wewqe'
> >
> > When I run that query I get
> >
> > Msg 14636, Level 16, State 1, Procedure sp_send_dbmail, Line 94
> > No global profile is configured. Specify a profile name in the
> > @.profile_name parameter.
> >
> > In the job log I have this
> >
> > Executing the query "EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris
> > Auer',@.body=N'wewqe'
> > " failed with the following error: "No global profile is configured.
> > Specify a profile name in the @.profile_name parameter.". Possible
> > failure reasons: Problems with the query, "ResultSet" property not set
> > correctly, parameters not set correctly, or connection not established
> > correctly.
> >
> >
> > What is a global profile?
> >
> > I have already made the registry change to
> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> > Server\MSSQL.1\SQLServerAgent
> > I made DatabaseMailProfile my default profile name in Database Mail and
> > I made UseDatabaseMail = 1
> >
> > Any ideas, thanks. This is driving me up a wall.'
> >
> > Chris Auer
> >
>
>sql
Can't send operator email in SQL Sever 2005
I have set up Database Mail
I have sent a test message successfully
I have set up a Operator
When I create a test job to send a test message to the operator the
TSQL is
EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris Auer',@.body=N'wewqe'
When I run that query I get
Msg 14636, Level 16, State 1, Procedure sp_send_dbmail, Line 94
No global profile is configured. Specify a profile name in the
@.profile_name parameter.
In the job log I have this
Executing the query "EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris
Auer',@.body=N'wewqe'
" failed with the following error: "No global profile is configured.
Specify a profile name in the @.profile_name parameter.". Possible
failure reasons: Problems with the query, "ResultSet" property not set
correctly, parameters not set correctly, or connection not established
correctly.
What is a global profile?
I have already made the registry change to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL
Server\MSSQL.1\SQLServerAgent
I made DatabaseMailProfile my default profile name in Database Mail and
I made UseDatabaseMail = 1
Any ideas, thanks. This is driving me up a wall.'
Chris AuerLooks like you only need to specify a profile name or define a default
profile.
Right-click Database Mail, select Configure Database Mail and select Manage
profile security. Here you have the choice to configure your profiles as
public, private and/or default.
If you do not have a default profile configured you will need to specify the
@.profile_name parameter. This is the same name under 'Profile name' on the
Database Mail Configuration Wizard.
Also, take a look at 'Database Mail [SQL Server], security on BOL.
Ben Nevarez, MCDBA, OCP
"Chris Auer" <chris.auer@.gmail.com> wrote in message
news:1132958108.969902.311470@.g44g2000cwa.googlegroups.com...
>I have set up Database Mail
> I have sent a test message successfully
> I have set up a Operator
> When I create a test job to send a test message to the operator the
> TSQL is
> EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris Auer',@.body=N'wewqe'
> When I run that query I get
> Msg 14636, Level 16, State 1, Procedure sp_send_dbmail, Line 94
> No global profile is configured. Specify a profile name in the
> @.profile_name parameter.
> In the job log I have this
> Executing the query "EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris
> Auer',@.body=N'wewqe'
> " failed with the following error: "No global profile is configured.
> Specify a profile name in the @.profile_name parameter.". Possible
> failure reasons: Problems with the query, "ResultSet" property not set
> correctly, parameters not set correctly, or connection not established
> correctly.
>
> What is a global profile?
> I have already made the registry change to
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL
> Server\MSSQL.1\SQLServerAgent
> I made DatabaseMailProfile my default profile name in Database Mail and
> I made UseDatabaseMail = 1
> Any ideas, thanks. This is driving me up a wall.'
> Chris Auer
>|||I also have the exact same problem, and is driving me nuts too. I have
created a default, private profile for the agent to use, however it still
fails.
I get the same error message. I can send database mail, but the agent fails
.
I've tried public default profiles and they fail too. The agent account is
setup in msdb in the DatabaseMailUser role.
The interseting thing is that the 'Test' button is dimmed on the SQL Agent,
Alert System, Mail Session page even though the correct profile is selected!
Please, any help will be greatly appreciated.
Jim
"Ben Nevarez" wrote:
> Looks like you only need to specify a profile name or define a default
> profile.
> Right-click Database Mail, select Configure Database Mail and select Manag
e
> profile security. Here you have the choice to configure your profiles as
> public, private and/or default.
> If you do not have a default profile configured you will need to specify t
he
> @.profile_name parameter. This is the same name under 'Profile name' on the
> Database Mail Configuration Wizard.
> Also, take a look at 'Database Mail [SQL Server], security on BOL.
> Ben Nevarez, MCDBA, OCP
>
> "Chris Auer" <chris.auer@.gmail.com> wrote in message
> news:1132958108.969902.311470@.g44g2000cwa.googlegroups.com...
>
>
I have sent a test message successfully
I have set up a Operator
When I create a test job to send a test message to the operator the
TSQL is
EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris Auer',@.body=N'wewqe'
When I run that query I get
Msg 14636, Level 16, State 1, Procedure sp_send_dbmail, Line 94
No global profile is configured. Specify a profile name in the
@.profile_name parameter.
In the job log I have this
Executing the query "EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris
Auer',@.body=N'wewqe'
" failed with the following error: "No global profile is configured.
Specify a profile name in the @.profile_name parameter.". Possible
failure reasons: Problems with the query, "ResultSet" property not set
correctly, parameters not set correctly, or connection not established
correctly.
What is a global profile?
I have already made the registry change to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL
Server\MSSQL.1\SQLServerAgent
I made DatabaseMailProfile my default profile name in Database Mail and
I made UseDatabaseMail = 1
Any ideas, thanks. This is driving me up a wall.'
Chris AuerLooks like you only need to specify a profile name or define a default
profile.
Right-click Database Mail, select Configure Database Mail and select Manage
profile security. Here you have the choice to configure your profiles as
public, private and/or default.
If you do not have a default profile configured you will need to specify the
@.profile_name parameter. This is the same name under 'Profile name' on the
Database Mail Configuration Wizard.
Also, take a look at 'Database Mail [SQL Server], security on BOL.
Ben Nevarez, MCDBA, OCP
"Chris Auer" <chris.auer@.gmail.com> wrote in message
news:1132958108.969902.311470@.g44g2000cwa.googlegroups.com...
>I have set up Database Mail
> I have sent a test message successfully
> I have set up a Operator
> When I create a test job to send a test message to the operator the
> TSQL is
> EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris Auer',@.body=N'wewqe'
> When I run that query I get
> Msg 14636, Level 16, State 1, Procedure sp_send_dbmail, Line 94
> No global profile is configured. Specify a profile name in the
> @.profile_name parameter.
> In the job log I have this
> Executing the query "EXECUTE msdb.dbo.sp_notify_operator @.name=N'Chris
> Auer',@.body=N'wewqe'
> " failed with the following error: "No global profile is configured.
> Specify a profile name in the @.profile_name parameter.". Possible
> failure reasons: Problems with the query, "ResultSet" property not set
> correctly, parameters not set correctly, or connection not established
> correctly.
>
> What is a global profile?
> I have already made the registry change to
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL
> Server\MSSQL.1\SQLServerAgent
> I made DatabaseMailProfile my default profile name in Database Mail and
> I made UseDatabaseMail = 1
> Any ideas, thanks. This is driving me up a wall.'
> Chris Auer
>|||I also have the exact same problem, and is driving me nuts too. I have
created a default, private profile for the agent to use, however it still
fails.
I get the same error message. I can send database mail, but the agent fails
.
I've tried public default profiles and they fail too. The agent account is
setup in msdb in the DatabaseMailUser role.
The interseting thing is that the 'Test' button is dimmed on the SQL Agent,
Alert System, Mail Session page even though the correct profile is selected!
Please, any help will be greatly appreciated.
Jim
"Ben Nevarez" wrote:
> Looks like you only need to specify a profile name or define a default
> profile.
> Right-click Database Mail, select Configure Database Mail and select Manag
e
> profile security. Here you have the choice to configure your profiles as
> public, private and/or default.
> If you do not have a default profile configured you will need to specify t
he
> @.profile_name parameter. This is the same name under 'Profile name' on the
> Database Mail Configuration Wizard.
> Also, take a look at 'Database Mail [SQL Server], security on BOL.
> Ben Nevarez, MCDBA, OCP
>
> "Chris Auer" <chris.auer@.gmail.com> wrote in message
> news:1132958108.969902.311470@.g44g2000cwa.googlegroups.com...
>
>
Tuesday, March 20, 2012
Cant see the username in the Owner Combo box during job creation
Hi
use dbname
go
Select * from sysusers
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>What version of SQL Server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>|||Hi All
Am trying to schedule a job , but when I try selecting the username for
the Owner... I dont see the username in th list , I cant even type the
name of the user in the combo box ...
The username exists in the logins of my SQL Server...
Could you please help !!!!!!!
Thanks|||Hi
use dbname
go
Select * from sysusers
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>|||What version of SQL Server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>sql
use dbname
go
Select * from sysusers
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>What version of SQL Server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>|||Hi All
Am trying to schedule a job , but when I try selecting the username for
the Owner... I dont see the username in th list , I cant even type the
name of the user in the combo box ...
The username exists in the logins of my SQL Server...
Could you please help !!!!!!!
Thanks|||Hi
use dbname
go
Select * from sysusers
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>|||What version of SQL Server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>sql
Cant see the username in the Owner Combo box during job creation
Hi All
Am trying to schedule a job , but when I try selecting the username for
the Owner... I dont see the username in th list , I cant even type the
name of the user in the combo box ...
The username exists in the logins of my SQL Server...
Could you please help !!!!!!!
ThanksHi
use dbname
go
Select * from sysusers
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>|||What version of SQL Server?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>
Am trying to schedule a job , but when I try selecting the username for
the Owner... I dont see the username in th list , I cant even type the
name of the user in the combo box ...
The username exists in the logins of my SQL Server...
Could you please help !!!!!!!
ThanksHi
use dbname
go
Select * from sysusers
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>|||What version of SQL Server?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>
Monday, March 19, 2012
Cant schedule a job to run a package
I have schedule a job to run a package but it failed on cmd.exe...I am not a sys_admin...
Please let me know if I have to be a sys_admin or not?If its scheduled then the MS Agent Service must be running under a domain account and any resources this package utlises must be accessible by this domain account|||Are you scheduling the job within sql server or the os ?|||I try to schedule it with SQL not OS.|||it failed on cmd.exe
Can you be more specific about this ?
Please let me know if I have to be a sys_admin or not?If its scheduled then the MS Agent Service must be running under a domain account and any resources this package utlises must be accessible by this domain account|||Are you scheduling the job within sql server or the os ?|||I try to schedule it with SQL not OS.|||it failed on cmd.exe
Can you be more specific about this ?
Can't run the scheduled SQL Agent Job?
Hi,
I'm tried to run the job that created from maintenance plan. It fail and give me the following message:
[298] SQLServer Error: 15404, Could not obtain information about Windows NT group/user 'DOMAIN\MYNAME', error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)
We are using the Windows Autheniciaton mode only and my id is set as sysadmin, setadmin, processadmin in the server roles.
I don't why I can't run the job, I check the SQL agent services is login using LOCALSYSTEM.
I try to the NT admin account to login the box, but still getting the same error message.
Any idea?
Thanks!
use a local login for the SQLAgent and try to schedule it again.|||Hi,
What is local login? we only setup use the windows authenication mode for the sql server?
Thanks!
|||this may help u : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=102884&SiteID=1
change the owner of the job
Madhu
|||Is the SQL Server machine in the same domain as the user mentioned in the error message?
The 0x5 error code means access denied - the DC doesn't allow you to query the user information. If there are different domains involved, you may need to set the trust between them.
Also, what did you say you tried at the end of your message? There is a word missing I think.
Thanks
Laurentiu
Sunday, March 11, 2012
Can't run my scheduled job which accesses a linked server: other options?
I have a stored procedure in a database on a server, and this stored
procedure uses a linked server.
The login I was given is only granted DBO permissions on this database.
I am trying to set this up so that the above stored procedure runs once
per month, so I naturally tried to set up a Job which would do this.
I have discovered from another group that:
"You cannot access a linked server from a TSQL jobstep if you aren't
sy
min."
So: How can I automatically run this stored procedure once per month
under these conditions?
Thanks,
RyanIn SQL 2000, change the job owner to symin.
In SQL 2005, change the job security context.
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
<ryan_willow@.hotmail.com> wrote in message
news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
>I have a stored procedure in a database on a server, and this stored
> procedure uses a linked server.
> The login I was given is only granted DBO permissions on this database.
> I am trying to set this up so that the above stored procedure runs once
> per month, so I naturally tried to set up a Job which would do this.
> I have discovered from another group that:
> "You cannot access a linked server from a TSQL jobstep if you aren't
> symin."
> So: How can I automatically run this stored procedure once per month
> under these conditions?
> Thanks,
> Ryan
>|||I'm in SQL 2000.
I cannot change the job owner because my permissions do not allow this.
Apparently a dbo user named 'User' can only create a job with owner
'User'. I am trying to implement this without having to step outside
my dbo security level. Is this going to be possible, and if so how?
Thanks.
Arnie Rowland wrote:
> In SQL 2000, change the job owner to symin.
> In SQL 2005, change the job security context.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> <ryan_willow@.hotmail.com> wrote in message
> news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...|||That will not be possible without coordination with the server
administrator. Since Jobs have the potential for significant performance
issues as well as security issues for the server, the security context for
Jobs is symin. (in SQL2000).
And of course a SQL Server Administrator is probably not going to allow you
to have permission to create or change a job because of the potential that
it could execute any code or activity under the symin security context.
Jobs are a 'Server' level activity -NOT a database level activity. Even if a
job is confined to a single database, it still operates as a server level
activity.
That changes with SQL 2005.
--
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"Ryan" <ryan_willow@.hotmail.com> wrote in message
news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
> I'm in SQL 2000.
> I cannot change the job owner because my permissions do not allow this.
> Apparently a dbo user named 'User' can only create a job with owner
> 'User'. I am trying to implement this without having to step outside
> my dbo security level. Is this going to be possible, and if so how?
> Thanks.
> Arnie Rowland wrote:
>|||Very informative, thanks Arnie.
Arnie Rowland wrote:
> That will not be possible without coordination with the server
> administrator. Since Jobs have the potential for significant performance
> issues as well as security issues for the server, the security context for
> Jobs is symin. (in SQL2000).
> And of course a SQL Server Administrator is probably not going to allow yo
u
> to have permission to create or change a job because of the potential that
> it could execute any code or activity under the symin security context.
> Jobs are a 'Server' level activity -NOT a database level activity. Even if
a
> job is confined to a single database, it still operates as a server level
> activity.
> That changes with SQL 2005.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> "Ryan" <ryan_willow@.hotmail.com> wrote in message
> news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
procedure uses a linked server.
The login I was given is only granted DBO permissions on this database.
I am trying to set this up so that the above stored procedure runs once
per month, so I naturally tried to set up a Job which would do this.
I have discovered from another group that:
"You cannot access a linked server from a TSQL jobstep if you aren't
sy
min."So: How can I automatically run this stored procedure once per month
under these conditions?
Thanks,
RyanIn SQL 2000, change the job owner to sy
min.In SQL 2005, change the job security context.
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
<ryan_willow@.hotmail.com> wrote in message
news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
>I have a stored procedure in a database on a server, and this stored
> procedure uses a linked server.
> The login I was given is only granted DBO permissions on this database.
> I am trying to set this up so that the above stored procedure runs once
> per month, so I naturally tried to set up a Job which would do this.
> I have discovered from another group that:
> "You cannot access a linked server from a TSQL jobstep if you aren't
> sy
min."> So: How can I automatically run this stored procedure once per month
> under these conditions?
> Thanks,
> Ryan
>|||I'm in SQL 2000.
I cannot change the job owner because my permissions do not allow this.
Apparently a dbo user named 'User' can only create a job with owner
'User'. I am trying to implement this without having to step outside
my dbo security level. Is this going to be possible, and if so how?
Thanks.
Arnie Rowland wrote:
> In SQL 2000, change the job owner to sy
min.> In SQL 2005, change the job security context.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> <ryan_willow@.hotmail.com> wrote in message
> news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...|||That will not be possible without coordination with the server
administrator. Since Jobs have the potential for significant performance
issues as well as security issues for the server, the security context for
Jobs is sy
min. (in SQL2000).And of course a SQL Server Administrator is probably not going to allow you
to have permission to create or change a job because of the potential that
it could execute any code or activity under the sy
min security context.Jobs are a 'Server' level activity -NOT a database level activity. Even if a
job is confined to a single database, it still operates as a server level
activity.
That changes with SQL 2005.
--
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"Ryan" <ryan_willow@.hotmail.com> wrote in message
news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
> I'm in SQL 2000.
> I cannot change the job owner because my permissions do not allow this.
> Apparently a dbo user named 'User' can only create a job with owner
> 'User'. I am trying to implement this without having to step outside
> my dbo security level. Is this going to be possible, and if so how?
> Thanks.
> Arnie Rowland wrote:
>|||Very informative, thanks Arnie.
Arnie Rowland wrote:
> That will not be possible without coordination with the server
> administrator. Since Jobs have the potential for significant performance
> issues as well as security issues for the server, the security context for
> Jobs is sy
min. (in SQL2000).> And of course a SQL Server Administrator is probably not going to allow yo
u
> to have permission to create or change a job because of the potential that
> it could execute any code or activity under the sy
min security context.> Jobs are a 'Server' level activity -NOT a database level activity. Even if
a
> job is confined to a single database, it still operates as a server level
> activity.
> That changes with SQL 2005.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> "Ryan" <ryan_willow@.hotmail.com> wrote in message
> news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
Can't run my scheduled job which accesses a linked server: other options?
In SQL 2000, change the job owner to sysadmin.
In SQL 2005, change the job security context.
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
<ryan_willow@.hotmail.com> wrote in message
news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
>I have a stored procedure in a database on a server, and this stored
> procedure uses a linked server.
> The login I was given is only granted DBO permissions on this database.
> I am trying to set this up so that the above stored procedure runs once
> per month, so I naturally tried to set up a Job which would do this.
> I have discovered from another group that:
> "You cannot access a linked server from a TSQL jobstep if you aren't
> sysadmin."
> So: How can I automatically run this stored procedure once per month
> under these conditions?
> Thanks,
> Ryan
>I'm in SQL 2000.
I cannot change the job owner because my permissions do not allow this.
Apparently a dbo user named 'User' can only create a job with owner
'User'. I am trying to implement this without having to step outside
my dbo security level. Is this going to be possible, and if so how?
Thanks.
Arnie Rowland wrote:[vbcol=seagreen]
> In SQL 2000, change the job owner to sysadmin.
> In SQL 2005, change the job security context.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> <ryan_willow@.hotmail.com> wrote in message
> news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...|||That will not be possible without coordination with the server
administrator. Since Jobs have the potential for significant performance
issues as well as security issues for the server, the security context for
Jobs is sysadmin. (in SQL2000).
And of course a SQL Server Administrator is probably not going to allow you
to have permission to create or change a job because of the potential that
it could execute any code or activity under the sysadmin security context.
Jobs are a 'Server' level activity -NOT a database level activity. Even if a
job is confined to a single database, it still operates as a server level
activity.
That changes with SQL 2005.
--
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"Ryan" <ryan_willow@.hotmail.com> wrote in message
news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
> I'm in SQL 2000.
> I cannot change the job owner because my permissions do not allow this.
> Apparently a dbo user named 'User' can only create a job with owner
> 'User'. I am trying to implement this without having to step outside
> my dbo security level. Is this going to be possible, and if so how?
> Thanks.
> Arnie Rowland wrote:
>|||Very informative, thanks Arnie.
Arnie Rowland wrote:[vbcol=seagreen]
> That will not be possible without coordination with the server
> administrator. Since Jobs have the potential for significant performance
> issues as well as security issues for the server, the security context for
> Jobs is sysadmin. (in SQL2000).
> And of course a SQL Server Administrator is probably not going to allow yo
u
> to have permission to create or change a job because of the potential that
> it could execute any code or activity under the sysadmin security context.
> Jobs are a 'Server' level activity -NOT a database level activity. Even if
a
> job is confined to a single database, it still operates as a server level
> activity.
> That changes with SQL 2005.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> "Ryan" <ryan_willow@.hotmail.com> wrote in message
> news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...|||I have a stored procedure in a database on a server, and this stored
procedure uses a linked server.
The login I was given is only granted DBO permissions on this database.
I am trying to set this up so that the above stored procedure runs once
per month, so I naturally tried to set up a Job which would do this.
I have discovered from another group that:
"You cannot access a linked server from a TSQL jobstep if you aren't
sysadmin."
So: How can I automatically run this stored procedure once per month
under these conditions?
Thanks,
Ryan|||In SQL 2000, change the job owner to sysadmin.
In SQL 2005, change the job security context.
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
<ryan_willow@.hotmail.com> wrote in message
news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
>I have a stored procedure in a database on a server, and this stored
> procedure uses a linked server.
> The login I was given is only granted DBO permissions on this database.
> I am trying to set this up so that the above stored procedure runs once
> per month, so I naturally tried to set up a Job which would do this.
> I have discovered from another group that:
> "You cannot access a linked server from a TSQL jobstep if you aren't
> sysadmin."
> So: How can I automatically run this stored procedure once per month
> under these conditions?
> Thanks,
> Ryan
>|||I'm in SQL 2000.
I cannot change the job owner because my permissions do not allow this.
Apparently a dbo user named 'User' can only create a job with owner
'User'. I am trying to implement this without having to step outside
my dbo security level. Is this going to be possible, and if so how?
Thanks.
Arnie Rowland wrote:[vbcol=seagreen]
> In SQL 2000, change the job owner to sysadmin.
> In SQL 2005, change the job security context.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> <ryan_willow@.hotmail.com> wrote in message
> news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...|||That will not be possible without coordination with the server
administrator. Since Jobs have the potential for significant performance
issues as well as security issues for the server, the security context for
Jobs is sysadmin. (in SQL2000).
And of course a SQL Server Administrator is probably not going to allow you
to have permission to create or change a job because of the potential that
it could execute any code or activity under the sysadmin security context.
Jobs are a 'Server' level activity -NOT a database level activity. Even if a
job is confined to a single database, it still operates as a server level
activity.
That changes with SQL 2005.
--
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"Ryan" <ryan_willow@.hotmail.com> wrote in message
news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
> I'm in SQL 2000.
> I cannot change the job owner because my permissions do not allow this.
> Apparently a dbo user named 'User' can only create a job with owner
> 'User'. I am trying to implement this without having to step outside
> my dbo security level. Is this going to be possible, and if so how?
> Thanks.
> Arnie Rowland wrote:
>|||Very informative, thanks Arnie.
Arnie Rowland wrote:[vbcol=seagreen]
> That will not be possible without coordination with the server
> administrator. Since Jobs have the potential for significant performance
> issues as well as security issues for the server, the security context for
> Jobs is sysadmin. (in SQL2000).
> And of course a SQL Server Administrator is probably not going to allow yo
u
> to have permission to create or change a job because of the potential that
> it could execute any code or activity under the sysadmin security context.
> Jobs are a 'Server' level activity -NOT a database level activity. Even if
a
> job is confined to a single database, it still operates as a server level
> activity.
> That changes with SQL 2005.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> "Ryan" <ryan_willow@.hotmail.com> wrote in message
> news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
In SQL 2005, change the job security context.
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
<ryan_willow@.hotmail.com> wrote in message
news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
>I have a stored procedure in a database on a server, and this stored
> procedure uses a linked server.
> The login I was given is only granted DBO permissions on this database.
> I am trying to set this up so that the above stored procedure runs once
> per month, so I naturally tried to set up a Job which would do this.
> I have discovered from another group that:
> "You cannot access a linked server from a TSQL jobstep if you aren't
> sysadmin."
> So: How can I automatically run this stored procedure once per month
> under these conditions?
> Thanks,
> Ryan
>I'm in SQL 2000.
I cannot change the job owner because my permissions do not allow this.
Apparently a dbo user named 'User' can only create a job with owner
'User'. I am trying to implement this without having to step outside
my dbo security level. Is this going to be possible, and if so how?
Thanks.
Arnie Rowland wrote:[vbcol=seagreen]
> In SQL 2000, change the job owner to sysadmin.
> In SQL 2005, change the job security context.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> <ryan_willow@.hotmail.com> wrote in message
> news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...|||That will not be possible without coordination with the server
administrator. Since Jobs have the potential for significant performance
issues as well as security issues for the server, the security context for
Jobs is sysadmin. (in SQL2000).
And of course a SQL Server Administrator is probably not going to allow you
to have permission to create or change a job because of the potential that
it could execute any code or activity under the sysadmin security context.
Jobs are a 'Server' level activity -NOT a database level activity. Even if a
job is confined to a single database, it still operates as a server level
activity.
That changes with SQL 2005.
--
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"Ryan" <ryan_willow@.hotmail.com> wrote in message
news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
> I'm in SQL 2000.
> I cannot change the job owner because my permissions do not allow this.
> Apparently a dbo user named 'User' can only create a job with owner
> 'User'. I am trying to implement this without having to step outside
> my dbo security level. Is this going to be possible, and if so how?
> Thanks.
> Arnie Rowland wrote:
>|||Very informative, thanks Arnie.
Arnie Rowland wrote:[vbcol=seagreen]
> That will not be possible without coordination with the server
> administrator. Since Jobs have the potential for significant performance
> issues as well as security issues for the server, the security context for
> Jobs is sysadmin. (in SQL2000).
> And of course a SQL Server Administrator is probably not going to allow yo
u
> to have permission to create or change a job because of the potential that
> it could execute any code or activity under the sysadmin security context.
> Jobs are a 'Server' level activity -NOT a database level activity. Even if
a
> job is confined to a single database, it still operates as a server level
> activity.
> That changes with SQL 2005.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> "Ryan" <ryan_willow@.hotmail.com> wrote in message
> news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...|||I have a stored procedure in a database on a server, and this stored
procedure uses a linked server.
The login I was given is only granted DBO permissions on this database.
I am trying to set this up so that the above stored procedure runs once
per month, so I naturally tried to set up a Job which would do this.
I have discovered from another group that:
"You cannot access a linked server from a TSQL jobstep if you aren't
sysadmin."
So: How can I automatically run this stored procedure once per month
under these conditions?
Thanks,
Ryan|||In SQL 2000, change the job owner to sysadmin.
In SQL 2005, change the job security context.
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
<ryan_willow@.hotmail.com> wrote in message
news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
>I have a stored procedure in a database on a server, and this stored
> procedure uses a linked server.
> The login I was given is only granted DBO permissions on this database.
> I am trying to set this up so that the above stored procedure runs once
> per month, so I naturally tried to set up a Job which would do this.
> I have discovered from another group that:
> "You cannot access a linked server from a TSQL jobstep if you aren't
> sysadmin."
> So: How can I automatically run this stored procedure once per month
> under these conditions?
> Thanks,
> Ryan
>|||I'm in SQL 2000.
I cannot change the job owner because my permissions do not allow this.
Apparently a dbo user named 'User' can only create a job with owner
'User'. I am trying to implement this without having to step outside
my dbo security level. Is this going to be possible, and if so how?
Thanks.
Arnie Rowland wrote:[vbcol=seagreen]
> In SQL 2000, change the job owner to sysadmin.
> In SQL 2005, change the job security context.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> <ryan_willow@.hotmail.com> wrote in message
> news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...|||That will not be possible without coordination with the server
administrator. Since Jobs have the potential for significant performance
issues as well as security issues for the server, the security context for
Jobs is sysadmin. (in SQL2000).
And of course a SQL Server Administrator is probably not going to allow you
to have permission to create or change a job because of the potential that
it could execute any code or activity under the sysadmin security context.
Jobs are a 'Server' level activity -NOT a database level activity. Even if a
job is confined to a single database, it still operates as a server level
activity.
That changes with SQL 2005.
--
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"Ryan" <ryan_willow@.hotmail.com> wrote in message
news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
> I'm in SQL 2000.
> I cannot change the job owner because my permissions do not allow this.
> Apparently a dbo user named 'User' can only create a job with owner
> 'User'. I am trying to implement this without having to step outside
> my dbo security level. Is this going to be possible, and if so how?
> Thanks.
> Arnie Rowland wrote:
>|||Very informative, thanks Arnie.
Arnie Rowland wrote:[vbcol=seagreen]
> That will not be possible without coordination with the server
> administrator. Since Jobs have the potential for significant performance
> issues as well as security issues for the server, the security context for
> Jobs is sysadmin. (in SQL2000).
> And of course a SQL Server Administrator is probably not going to allow yo
u
> to have permission to create or change a job because of the potential that
> it could execute any code or activity under the sysadmin security context.
> Jobs are a 'Server' level activity -NOT a database level activity. Even if
a
> job is confined to a single database, it still operates as a server level
> activity.
> That changes with SQL 2005.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> "Ryan" <ryan_willow@.hotmail.com> wrote in message
> news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
Can't run my scheduled job which accesses a linked server: other options?
I have a stored procedure in a database on a server, and this stored
procedure uses a linked server.
The login I was given is only granted DBO permissions on this database.
I am trying to set this up so that the above stored procedure runs once
per month, so I naturally tried to set up a Job which would do this.
I have discovered from another group that:
"You cannot access a linked server from a TSQL jobstep if you aren't
sysadmin."
So: How can I automatically run this stored procedure once per month
under these conditions?
Thanks,
RyanIn SQL 2000, change the job owner to sysadmin.
In SQL 2005, change the job security context.
--
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another Certification Exam
<ryan_willow@.hotmail.com> wrote in message
news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
>I have a stored procedure in a database on a server, and this stored
> procedure uses a linked server.
> The login I was given is only granted DBO permissions on this database.
> I am trying to set this up so that the above stored procedure runs once
> per month, so I naturally tried to set up a Job which would do this.
> I have discovered from another group that:
> "You cannot access a linked server from a TSQL jobstep if you aren't
> sysadmin."
> So: How can I automatically run this stored procedure once per month
> under these conditions?
> Thanks,
> Ryan
>|||I'm in SQL 2000.
I cannot change the job owner because my permissions do not allow this.
Apparently a dbo user named 'User' can only create a job with owner
'User'. I am trying to implement this without having to step outside
my dbo security level. Is this going to be possible, and if so how?
Thanks.
Arnie Rowland wrote:
> In SQL 2000, change the job owner to sysadmin.
> In SQL 2005, change the job security context.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another Certification Exam
>
> <ryan_willow@.hotmail.com> wrote in message
> news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
> >I have a stored procedure in a database on a server, and this stored
> > procedure uses a linked server.
> >
> > The login I was given is only granted DBO permissions on this database.
> >
> > I am trying to set this up so that the above stored procedure runs once
> > per month, so I naturally tried to set up a Job which would do this.
> >
> > I have discovered from another group that:
> > "You cannot access a linked server from a TSQL jobstep if you aren't
> > sysadmin."
> >
> > So: How can I automatically run this stored procedure once per month
> > under these conditions?
> >
> > Thanks,
> > Ryan
> >|||That will not be possible without coordination with the server
administrator. Since Jobs have the potential for significant performance
issues as well as security issues for the server, the security context for
Jobs is sysadmin. (in SQL2000).
And of course a SQL Server Administrator is probably not going to allow you
to have permission to create or change a job because of the potential that
it could execute any code or activity under the sysadmin security context.
Jobs are a 'Server' level activity -NOT a database level activity. Even if a
job is confined to a single database, it still operates as a server level
activity.
That changes with SQL 2005.
--
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another Certification Exam
"Ryan" <ryan_willow@.hotmail.com> wrote in message
news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
> I'm in SQL 2000.
> I cannot change the job owner because my permissions do not allow this.
> Apparently a dbo user named 'User' can only create a job with owner
> 'User'. I am trying to implement this without having to step outside
> my dbo security level. Is this going to be possible, and if so how?
> Thanks.
> Arnie Rowland wrote:
>> In SQL 2000, change the job owner to sysadmin.
>> In SQL 2005, change the job security context.
>> --
>> Arnie Rowland, YACE*
>> "To be successful, your heart must accompany your knowledge."
>> *Yet Another Certification Exam
>>
>> <ryan_willow@.hotmail.com> wrote in message
>> news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
>> >I have a stored procedure in a database on a server, and this stored
>> > procedure uses a linked server.
>> >
>> > The login I was given is only granted DBO permissions on this database.
>> >
>> > I am trying to set this up so that the above stored procedure runs once
>> > per month, so I naturally tried to set up a Job which would do this.
>> >
>> > I have discovered from another group that:
>> > "You cannot access a linked server from a TSQL jobstep if you aren't
>> > sysadmin."
>> >
>> > So: How can I automatically run this stored procedure once per month
>> > under these conditions?
>> >
>> > Thanks,
>> > Ryan
>> >
>|||Very informative, thanks Arnie.
Arnie Rowland wrote:
> That will not be possible without coordination with the server
> administrator. Since Jobs have the potential for significant performance
> issues as well as security issues for the server, the security context for
> Jobs is sysadmin. (in SQL2000).
> And of course a SQL Server Administrator is probably not going to allow you
> to have permission to create or change a job because of the potential that
> it could execute any code or activity under the sysadmin security context.
> Jobs are a 'Server' level activity -NOT a database level activity. Even if a
> job is confined to a single database, it still operates as a server level
> activity.
> That changes with SQL 2005.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another Certification Exam
>
> "Ryan" <ryan_willow@.hotmail.com> wrote in message
> news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
> > I'm in SQL 2000.
> >
> > I cannot change the job owner because my permissions do not allow this.
> > Apparently a dbo user named 'User' can only create a job with owner
> > 'User'. I am trying to implement this without having to step outside
> > my dbo security level. Is this going to be possible, and if so how?
> >
> > Thanks.
> >
> > Arnie Rowland wrote:
> >> In SQL 2000, change the job owner to sysadmin.
> >>
> >> In SQL 2005, change the job security context.
> >>
> >> --
> >> Arnie Rowland, YACE*
> >> "To be successful, your heart must accompany your knowledge."
> >>
> >> *Yet Another Certification Exam
> >>
> >>
> >> <ryan_willow@.hotmail.com> wrote in message
> >> news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
> >> >I have a stored procedure in a database on a server, and this stored
> >> > procedure uses a linked server.
> >> >
> >> > The login I was given is only granted DBO permissions on this database.
> >> >
> >> > I am trying to set this up so that the above stored procedure runs once
> >> > per month, so I naturally tried to set up a Job which would do this.
> >> >
> >> > I have discovered from another group that:
> >> > "You cannot access a linked server from a TSQL jobstep if you aren't
> >> > sysadmin."
> >> >
> >> > So: How can I automatically run this stored procedure once per month
> >> > under these conditions?
> >> >
> >> > Thanks,
> >> > Ryan
> >> >
> >
procedure uses a linked server.
The login I was given is only granted DBO permissions on this database.
I am trying to set this up so that the above stored procedure runs once
per month, so I naturally tried to set up a Job which would do this.
I have discovered from another group that:
"You cannot access a linked server from a TSQL jobstep if you aren't
sysadmin."
So: How can I automatically run this stored procedure once per month
under these conditions?
Thanks,
RyanIn SQL 2000, change the job owner to sysadmin.
In SQL 2005, change the job security context.
--
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another Certification Exam
<ryan_willow@.hotmail.com> wrote in message
news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
>I have a stored procedure in a database on a server, and this stored
> procedure uses a linked server.
> The login I was given is only granted DBO permissions on this database.
> I am trying to set this up so that the above stored procedure runs once
> per month, so I naturally tried to set up a Job which would do this.
> I have discovered from another group that:
> "You cannot access a linked server from a TSQL jobstep if you aren't
> sysadmin."
> So: How can I automatically run this stored procedure once per month
> under these conditions?
> Thanks,
> Ryan
>|||I'm in SQL 2000.
I cannot change the job owner because my permissions do not allow this.
Apparently a dbo user named 'User' can only create a job with owner
'User'. I am trying to implement this without having to step outside
my dbo security level. Is this going to be possible, and if so how?
Thanks.
Arnie Rowland wrote:
> In SQL 2000, change the job owner to sysadmin.
> In SQL 2005, change the job security context.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another Certification Exam
>
> <ryan_willow@.hotmail.com> wrote in message
> news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
> >I have a stored procedure in a database on a server, and this stored
> > procedure uses a linked server.
> >
> > The login I was given is only granted DBO permissions on this database.
> >
> > I am trying to set this up so that the above stored procedure runs once
> > per month, so I naturally tried to set up a Job which would do this.
> >
> > I have discovered from another group that:
> > "You cannot access a linked server from a TSQL jobstep if you aren't
> > sysadmin."
> >
> > So: How can I automatically run this stored procedure once per month
> > under these conditions?
> >
> > Thanks,
> > Ryan
> >|||That will not be possible without coordination with the server
administrator. Since Jobs have the potential for significant performance
issues as well as security issues for the server, the security context for
Jobs is sysadmin. (in SQL2000).
And of course a SQL Server Administrator is probably not going to allow you
to have permission to create or change a job because of the potential that
it could execute any code or activity under the sysadmin security context.
Jobs are a 'Server' level activity -NOT a database level activity. Even if a
job is confined to a single database, it still operates as a server level
activity.
That changes with SQL 2005.
--
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another Certification Exam
"Ryan" <ryan_willow@.hotmail.com> wrote in message
news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
> I'm in SQL 2000.
> I cannot change the job owner because my permissions do not allow this.
> Apparently a dbo user named 'User' can only create a job with owner
> 'User'. I am trying to implement this without having to step outside
> my dbo security level. Is this going to be possible, and if so how?
> Thanks.
> Arnie Rowland wrote:
>> In SQL 2000, change the job owner to sysadmin.
>> In SQL 2005, change the job security context.
>> --
>> Arnie Rowland, YACE*
>> "To be successful, your heart must accompany your knowledge."
>> *Yet Another Certification Exam
>>
>> <ryan_willow@.hotmail.com> wrote in message
>> news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
>> >I have a stored procedure in a database on a server, and this stored
>> > procedure uses a linked server.
>> >
>> > The login I was given is only granted DBO permissions on this database.
>> >
>> > I am trying to set this up so that the above stored procedure runs once
>> > per month, so I naturally tried to set up a Job which would do this.
>> >
>> > I have discovered from another group that:
>> > "You cannot access a linked server from a TSQL jobstep if you aren't
>> > sysadmin."
>> >
>> > So: How can I automatically run this stored procedure once per month
>> > under these conditions?
>> >
>> > Thanks,
>> > Ryan
>> >
>|||Very informative, thanks Arnie.
Arnie Rowland wrote:
> That will not be possible without coordination with the server
> administrator. Since Jobs have the potential for significant performance
> issues as well as security issues for the server, the security context for
> Jobs is sysadmin. (in SQL2000).
> And of course a SQL Server Administrator is probably not going to allow you
> to have permission to create or change a job because of the potential that
> it could execute any code or activity under the sysadmin security context.
> Jobs are a 'Server' level activity -NOT a database level activity. Even if a
> job is confined to a single database, it still operates as a server level
> activity.
> That changes with SQL 2005.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another Certification Exam
>
> "Ryan" <ryan_willow@.hotmail.com> wrote in message
> news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
> > I'm in SQL 2000.
> >
> > I cannot change the job owner because my permissions do not allow this.
> > Apparently a dbo user named 'User' can only create a job with owner
> > 'User'. I am trying to implement this without having to step outside
> > my dbo security level. Is this going to be possible, and if so how?
> >
> > Thanks.
> >
> > Arnie Rowland wrote:
> >> In SQL 2000, change the job owner to sysadmin.
> >>
> >> In SQL 2005, change the job security context.
> >>
> >> --
> >> Arnie Rowland, YACE*
> >> "To be successful, your heart must accompany your knowledge."
> >>
> >> *Yet Another Certification Exam
> >>
> >>
> >> <ryan_willow@.hotmail.com> wrote in message
> >> news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
> >> >I have a stored procedure in a database on a server, and this stored
> >> > procedure uses a linked server.
> >> >
> >> > The login I was given is only granted DBO permissions on this database.
> >> >
> >> > I am trying to set this up so that the above stored procedure runs once
> >> > per month, so I naturally tried to set up a Job which would do this.
> >> >
> >> > I have discovered from another group that:
> >> > "You cannot access a linked server from a TSQL jobstep if you aren't
> >> > sysadmin."
> >> >
> >> > So: How can I automatically run this stored procedure once per month
> >> > under these conditions?
> >> >
> >> > Thanks,
> >> > Ryan
> >> >
> >
Can't run dts package job
I setup a job which call a dts package (I try to call it from file system and from SSIS Package Store with the same result) and it doesn't run.
If you take a look from the SQL Server Agent you could see this >>
2012-06-17 09:01:02 - ! [LOG] Step 1 of job 'prueba' (0x85B4D5E843DB3145A6A1A6A0A43D04F3) cannot be run because the DTS subsystem failed to load. The job has been suspended
Any ideas?This was happening to people that installed to a drive other than C:. Did you install to a different drive? It's a bug in setup. If so, you can fix it by changing the dbo.syssubsystems table in MSDB for the dts subsystem.
Look to see where it's pointing. It should be something like this:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\SQLDTSSS90.DLL
If the drive is different then the one you installed on, correct it. It should work then.
Please let me know if this worked.
Thanks,|||I saw what you said. I installed SQL in D drive in a directory called SQL_Server. The path you told me was right but the path in the agent_exe field was wrong.
Thanks for your help.|||Excellent! Glad to help out.|||
This was a dts in SQL 2005, right? If so, how did you get to the dbo.syssubsystems table? I know its in the MSDB but I can't get access to that table, even as an admin of the box. Any ideas?
|||Hi,
I have a similar situation. We have program files on C:\ and Data files on D:\. I ran the following sql to update the syssubsystems table, but I still get the " 2007-01-22 12:13:37 - ! [LOG] Step 1 of job 'MaintenancePlan 1' (0xC433119AFB756E4E844D94759A65B68A) cannot be run because the SSIS subsystem failed to load. The job has been suspended" message.
INSERT INTO [msdb].[dbo].[syssubsystems]
([subsystem_id]
,[subsystem]
,[description_id]
,[subsystem_dll]
,[agent_exe]
,[start_entry_point]
,[event_entry_point]
,[stop_entry_point]
,[max_worker_threads])
VALUES
(11
,'SSIS'
,14538
,'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\SQLDTSSS90.DLL'
,'C:\Program Files\Microsoft SQL Server\90\DTS\Connections\Binn\DTExec.exe'
,'DtsStart'
,'DtsEvent'
,'DtsStop'
,200);
Do I need to restart the Intergration services service?
Paul
|||janislkovach wrote:
This was a dts in SQL 2005, right? If so, how did you get to the dbo.syssubsystems table? I know its in the MSDB but I can't get access to that table, even as an admin of the box. Any ideas?
Did you log in as a SQL Server admin?|||
Yes I can login to the box with Domain admin, then onto the Database engine with the SA id and password. I run the sqlagent job as a 'SQL Server Intergration Services package' and it fails with the 'failed to load susbsystem message'. If I run it as an 'Operating system(CmdExec)' i.e dtexec / SQL "[package name]" etc, then it works.
I can obviously get round the problem this way, but it's frustrating it doesn't work as it should. I think it started to happen after SP1 was installed.
Is it something to do with what account Integration Services runs under? As all the other SQL server service run as domain admin, my intergration Services service runs as NT authority\network service. Should I run this as domain admin also?
One further thing, when comparing other boxes with my problem box, is that I have DTEXEC.exe & DTAttach(and associated Dll's) in C:\Program Files\Microsoft SQL Server\90\DTS\Connections\Binn on the problem box whereas they are in C:\Program Files\Microsoft SQL Server\90\DTS\Binn in all other ones. Is this my problem? Can I simply move them to C:\Program Files\Microsoft SQL Server\90\DTS\Binn?
Can't run dts package job
I setup a job which call a dts package (I try to call it from file system and from SSIS Package Store with the same result) and it doesn't run.
If you take a look from the SQL Server Agent you could see this >>
2012-06-17 09:01:02 - ! [LOG] Step 1 of job 'prueba' (0x85B4D5E843DB3145A6A1A6A0A43D04F3) cannot be run because the DTS subsystem failed to load. The job has been suspended
Any ideas?This was happening to people that installed to a drive other than C:. Did you install to a different drive? It's a bug in setup. If so, you can fix it by changing the dbo.syssubsystems table in MSDB for the dts subsystem.
Look to see where it's pointing. It should be something like this:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\SQLDTSSS90.DLL
If the drive is different then the one you installed on, correct it. It should work then.
Please let me know if this worked.
Thanks,|||I saw what you said. I installed SQL in D drive in a directory called SQL_Server. The path you told me was right but the path in the agent_exe field was wrong.
Thanks for your help.|||Excellent! Glad to help out.|||
This was a dts in SQL 2005, right? If so, how did you get to the dbo.syssubsystems table? I know its in the MSDB but I can't get access to that table, even as an admin of the box. Any ideas?
|||Hi,
I have a similar situation. We have program files on C:\ and Data files on D:\. I ran the following sql to update the syssubsystems table, but I still get the " 2007-01-22 12:13:37 - ! [LOG] Step 1 of job 'MaintenancePlan 1' (0xC433119AFB756E4E844D94759A65B68A) cannot be run because the SSIS subsystem failed to load. The job has been suspended" message.
INSERT INTO [msdb].[dbo].[syssubsystems]
([subsystem_id]
,[subsystem]
,[description_id]
,[subsystem_dll]
,[agent_exe]
,[start_entry_point]
,[event_entry_point]
,[stop_entry_point]
,[max_worker_threads])
VALUES
(11
,'SSIS'
,14538
,'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\SQLDTSSS90.DLL'
,'C:\Program Files\Microsoft SQL Server\90\DTS\Connections\Binn\DTExec.exe'
,'DtsStart'
,'DtsEvent'
,'DtsStop'
,200);
Do I need to restart the Intergration services service?
Paul
|||janislkovach wrote:
This was a dts in SQL 2005, right? If so, how did you get to the dbo.syssubsystems table? I know its in the MSDB but I can't get access to that table, even as an admin of the box. Any ideas?
Did you log in as a SQL Server admin?|||
Yes I can login to the box with Domain admin, then onto the Database engine with the SA id and password. I run the sqlagent job as a 'SQL Server Intergration Services package' and it fails with the 'failed to load susbsystem message'. If I run it as an 'Operating system(CmdExec)' i.e dtexec / SQL "[package name]" etc, then it works.
I can obviously get round the problem this way, but it's frustrating it doesn't work as it should. I think it started to happen after SP1 was installed.
Is it something to do with what account Integration Services runs under? As all the other SQL server service run as domain admin, my intergration Services service runs as NT authority\network service. Should I run this as domain admin also?
One further thing, when comparing other boxes with my problem box, is that I have DTEXEC.exe & DTAttach(and associated Dll's) in C:\Program Files\Microsoft SQL Server\90\DTS\Connections\Binn on the problem box whereas they are in C:\Program Files\Microsoft SQL Server\90\DTS\Binn in all other ones. Is this my problem? Can I simply move them to C:\Program Files\Microsoft SQL Server\90\DTS\Binn?
Can't run dts package job
I setup a job which call a dts package (I try to call it from file system and from SSIS Package Store with the same result) and it doesn't run.
If you take a look from the SQL Server Agent you could see this >>
2012-06-17 09:01:02 - ! [LOG] Step 1 of job 'prueba' (0x85B4D5E843DB3145A6A1A6A0A43D04F3) cannot be run because the DTS subsystem failed to load. The job has been suspended
Any ideas?This was happening to people that installed to a drive other than C:. Did you install to a different drive? It's a bug in setup. If so, you can fix it by changing the dbo.syssubsystems table in MSDB for the dts subsystem.
Look to see where it's pointing. It should be something like this:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\SQLDTSSS90.DLL
If the drive is different then the one you installed on, correct it. It should work then.
Please let me know if this worked.
Thanks,|||I saw what you said. I installed SQL in D drive in a directory called SQL_Server. The path you told me was right but the path in the agent_exe field was wrong.
Thanks for your help.|||Excellent! Glad to help out.|||
This was a dts in SQL 2005, right? If so, how did you get to the dbo.syssubsystems table? I know its in the MSDB but I can't get access to that table, even as an admin of the box. Any ideas?
|||Hi,
I have a similar situation. We have program files on C:\ and Data files on D:\. I ran the following sql to update the syssubsystems table, but I still get the " 2007-01-22 12:13:37 - ! [LOG] Step 1 of job 'MaintenancePlan 1' (0xC433119AFB756E4E844D94759A65B68A) cannot be run because the SSIS subsystem failed to load. The job has been suspended" message.
INSERT INTO [msdb].[dbo].[syssubsystems]
([subsystem_id]
,[subsystem]
,[description_id]
,[subsystem_dll]
,[agent_exe]
,[start_entry_point]
,[event_entry_point]
,[stop_entry_point]
,[max_worker_threads])
VALUES
(11
,'SSIS'
,14538
,'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\SQLDTSSS90.DLL'
,'C:\Program Files\Microsoft SQL Server\90\DTS\Connections\Binn\DTExec.exe'
,'DtsStart'
,'DtsEvent'
,'DtsStop'
,200);
Do I need to restart the Intergration services service?
Paul
|||This was a dts in SQL 2005, right? If so, how did you get to the dbo.syssubsystems table? I know its in the MSDB but I can't get access to that table, even as an admin of the box. Any ideas?
Did you log in as a SQL Server admin?|||
Yes I can login to the box with Domain admin, then onto the Database engine with the SA id and password. I run the sqlagent job as a 'SQL Server Intergration Services package' and it fails with the 'failed to load susbsystem message'. If I run it as an 'Operating system(CmdExec)' i.e dtexec / SQL "[package name]" etc, then it works.
I can obviously get round the problem this way, but it's frustrating it doesn't work as it should. I think it started to happen after SP1 was installed.
Is it something to do with what account Integration Services runs under? As all the other SQL server service run as domain admin, my intergration Services service runs as NT authority\network service. Should I run this as domain admin also?
One further thing, when comparing other boxes with my problem box, is that I have DTEXEC.exe & DTAttach(and associated Dll's) in C:\Program Files\Microsoft SQL Server\90\DTS\Connections\Binn on the problem box whereas they are in C:\Program Files\Microsoft SQL Server\90\DTS\Binn in all other ones. Is this my problem? Can I simply move them to C:\Program Files\Microsoft SQL Server\90\DTS\Binn?
Thursday, March 8, 2012
CAN'T remove "Execute job" from alert in SS 2005?
This is kind of strange. On a SQL 2005 SP2 box, I've set up a few alerts to
monitor tran log growth. If they reach the threshold the alerts will fire
and send emails and kick off a tran log dump job. Now I want to remove the
job by unchecking the "Execute job" box from the "Response" node. after
clicking OK and going back to revisit it, the job is still checked. I've
tested this on a few other SQL instances - all are the same. From my
machine, I tested on a SQL 2000 server and it works as expected.
The alert is scripted below. I have also tried to change @.job_id to null in
a hope that the sproc will make it unchecked. But still the old job exists
in the alert.
EXEC msdb.dbo.sp_add_alert @.name=N'test',
@.message_id=0,
@.severity=0,
@.enabled=1,
@.delay_between_responses=0,
@.include_event_description_in=1,
@.category_name=N'[Uncategorized]',
@.performance_condition=N'SQLServer:Databases|Log File(s) Used Size
(KB)|tempdb|>|100000',
@.job_id=N'4d9d9fde-0fed-4d79-b894-0a04ae0d2b85'
I tend to believe this is a SQL 2005 bug. Has anyone else seen or can anyone
duplicate the same problem?
RickIt is not strange if it's a bug. :-) confirmed for ss2005. someone already
reported in April 2007.
"YPD" <y.ding@.neu.edu> wrote in message
news:C272B7CA-23BD-497A-AACC-C84E60A5030E@.microsoft.com...
> This is kind of strange. On a SQL 2005 SP2 box, I've set up a few alerts
> to monitor tran log growth. If they reach the threshold the alerts will
> fire and send emails and kick off a tran log dump job. Now I want to
> remove the job by unchecking the "Execute job" box from the "Response"
> node. after clicking OK and going back to revisit it, the job is still
> checked. I've tested this on a few other SQL instances - all are the same.
> From my machine, I tested on a SQL 2000 server and it works as expected.
> The alert is scripted below. I have also tried to change @.job_id to null
> in a hope that the sproc will make it unchecked. But still the old job
> exists in the alert.
> EXEC msdb.dbo.sp_add_alert @.name=N'test',
> @.message_id=0,
> @.severity=0,
> @.enabled=1,
> @.delay_between_responses=0,
> @.include_event_description_in=1,
> @.category_name=N'[Uncategorized]',
> @.performance_condition=N'SQLServer:Databases|Log File(s) Used Size
> (KB)|tempdb|>|100000',
> @.job_id=N'4d9d9fde-0fed-4d79-b894-0a04ae0d2b85'
> I tend to believe this is a SQL 2005 bug. Has anyone else seen or can
> anyone duplicate the same problem?
>
> Rick
monitor tran log growth. If they reach the threshold the alerts will fire
and send emails and kick off a tran log dump job. Now I want to remove the
job by unchecking the "Execute job" box from the "Response" node. after
clicking OK and going back to revisit it, the job is still checked. I've
tested this on a few other SQL instances - all are the same. From my
machine, I tested on a SQL 2000 server and it works as expected.
The alert is scripted below. I have also tried to change @.job_id to null in
a hope that the sproc will make it unchecked. But still the old job exists
in the alert.
EXEC msdb.dbo.sp_add_alert @.name=N'test',
@.message_id=0,
@.severity=0,
@.enabled=1,
@.delay_between_responses=0,
@.include_event_description_in=1,
@.category_name=N'[Uncategorized]',
@.performance_condition=N'SQLServer:Databases|Log File(s) Used Size
(KB)|tempdb|>|100000',
@.job_id=N'4d9d9fde-0fed-4d79-b894-0a04ae0d2b85'
I tend to believe this is a SQL 2005 bug. Has anyone else seen or can anyone
duplicate the same problem?
RickIt is not strange if it's a bug. :-) confirmed for ss2005. someone already
reported in April 2007.
"YPD" <y.ding@.neu.edu> wrote in message
news:C272B7CA-23BD-497A-AACC-C84E60A5030E@.microsoft.com...
> This is kind of strange. On a SQL 2005 SP2 box, I've set up a few alerts
> to monitor tran log growth. If they reach the threshold the alerts will
> fire and send emails and kick off a tran log dump job. Now I want to
> remove the job by unchecking the "Execute job" box from the "Response"
> node. after clicking OK and going back to revisit it, the job is still
> checked. I've tested this on a few other SQL instances - all are the same.
> From my machine, I tested on a SQL 2000 server and it works as expected.
> The alert is scripted below. I have also tried to change @.job_id to null
> in a hope that the sproc will make it unchecked. But still the old job
> exists in the alert.
> EXEC msdb.dbo.sp_add_alert @.name=N'test',
> @.message_id=0,
> @.severity=0,
> @.enabled=1,
> @.delay_between_responses=0,
> @.include_event_description_in=1,
> @.category_name=N'[Uncategorized]',
> @.performance_condition=N'SQLServer:Databases|Log File(s) Used Size
> (KB)|tempdb|>|100000',
> @.job_id=N'4d9d9fde-0fed-4d79-b894-0a04ae0d2b85'
> I tend to believe this is a SQL 2005 bug. Has anyone else seen or can
> anyone duplicate the same problem?
>
> Rick
Friday, February 24, 2012
Cant modify or delete an existing job
Folks, i have rebuilt my old server machine and i've restored the MSDB over the new machine. Now when i try to edit or delete any of the jobs that come from the RESTORE; i get the following error message:
I never setup multiserver administration.
However i can create and delete new jobs.
How do i remove these older jobs.
Howdy!This happened to me once, when a machine was renamed. I think it is as simple as updating the sysjobs table to reflect the new server name (originating_server column). Make sure you have a good backup, before you do this, however.|||sorry: the error message is:
error 14274: Cannot add, update, or delete a job that originated from anMSX server.
Thanx, MCrowley. I would try this when the users are off the machine.
Howdy.|||My experience was the exact same as MCrowley's; I think I went in and hand-edited the jobs in the msdb database (through EM; it was a long time ago). You may need to set the switch to allow updating of system tables, but I don't recall that I had to do that.
Regards,
hmscott
sorry: the error message is:
error 14274: Cannot add, update, or delete a job that originated from anMSX server.
Thanx, MCrowley. I would try this when the users are off the machine.
Howdy.|||i am squared. thanx.
USE MASTER
GO
sp_configure 'allow updates' ,1
GO
RECONFIGURE WITH OVERRIDE
GO
USE MSDB
go
update sysjobs set originating_server='myserver'
GO
USE MASTER
GO
sp_configure 'allow updates' ,0
GO
RECONFIGURE WITH OVERRIDE
--HOWDY!|||Just had the same problem on a rebuilt server - the above script sorted it out.
thanks,
Paul.
I never setup multiserver administration.
However i can create and delete new jobs.
How do i remove these older jobs.
Howdy!This happened to me once, when a machine was renamed. I think it is as simple as updating the sysjobs table to reflect the new server name (originating_server column). Make sure you have a good backup, before you do this, however.|||sorry: the error message is:
error 14274: Cannot add, update, or delete a job that originated from anMSX server.
Thanx, MCrowley. I would try this when the users are off the machine.
Howdy.|||My experience was the exact same as MCrowley's; I think I went in and hand-edited the jobs in the msdb database (through EM; it was a long time ago). You may need to set the switch to allow updating of system tables, but I don't recall that I had to do that.
Regards,
hmscott
sorry: the error message is:
error 14274: Cannot add, update, or delete a job that originated from anMSX server.
Thanx, MCrowley. I would try this when the users are off the machine.
Howdy.|||i am squared. thanx.
USE MASTER
GO
sp_configure 'allow updates' ,1
GO
RECONFIGURE WITH OVERRIDE
GO
USE MSDB
go
update sysjobs set originating_server='myserver'
GO
USE MASTER
GO
sp_configure 'allow updates' ,0
GO
RECONFIGURE WITH OVERRIDE
--HOWDY!|||Just had the same problem on a rebuilt server - the above script sorted it out.
thanks,
Paul.
can't manully start jobs
The job in SQL server agent won't manully start after installed SP3 for SQL
server 2000. But scheduled jobs are runing fine automatically.
Thanks for any reply.What errors do you get? What is in the SQLAgent.out file in
the Log directory?
-Sue
On Mon, 7 Nov 2005 08:16:15 -0800, new
<new@.discussions.microsoft.com> wrote:
>The job in SQL server agent won't manully start after installed SP3 for SQL
>server 2000. But scheduled jobs are runing fine automatically.
>Thanks for any reply.|||This may be a given, but make sure that the EM registration for this instanc
e
has the proper rights to exe jobs. If you are using Windows Authentication o
n
this registration, then make sure the win login you are using has sa. Some
permission levels allow you to view jobs, but can not execute them.
Thanks,
Rick MCP
"new" wrote:
> The job in SQL server agent won't manully start after installed SP3 for SQ
L
> server 2000. But scheduled jobs are runing fine automatically.
> Thanks for any reply.
server 2000. But scheduled jobs are runing fine automatically.
Thanks for any reply.What errors do you get? What is in the SQLAgent.out file in
the Log directory?
-Sue
On Mon, 7 Nov 2005 08:16:15 -0800, new
<new@.discussions.microsoft.com> wrote:
>The job in SQL server agent won't manully start after installed SP3 for SQL
>server 2000. But scheduled jobs are runing fine automatically.
>Thanks for any reply.|||This may be a given, but make sure that the EM registration for this instanc
e
has the proper rights to exe jobs. If you are using Windows Authentication o
n
this registration, then make sure the win login you are using has sa. Some
permission levels allow you to view jobs, but can not execute them.
Thanks,
Rick MCP
"new" wrote:
> The job in SQL server agent won't manully start after installed SP3 for SQ
L
> server 2000. But scheduled jobs are runing fine automatically.
> Thanks for any reply.
can't manully start jobs
The job in SQL server agent won't manully start after installed SP3 for SQL
server 2000. But scheduled jobs are runing fine automatically.
Thanks for any reply.
What errors do you get? What is in the SQLAgent.out file in
the Log directory?
-Sue
On Mon, 7 Nov 2005 08:16:15 -0800, new
<new@.discussions.microsoft.com> wrote:
>The job in SQL server agent won't manully start after installed SP3 for SQL
>server 2000. But scheduled jobs are runing fine automatically.
>Thanks for any reply.
|||This may be a given, but make sure that the EM registration for this instance
has the proper rights to exe jobs. If you are using Windows Authentication on
this registration, then make sure the win login you are using has sa. Some
permission levels allow you to view jobs, but can not execute them.
Thanks,
Rick MCP
"new" wrote:
> The job in SQL server agent won't manully start after installed SP3 for SQL
> server 2000. But scheduled jobs are runing fine automatically.
> Thanks for any reply.
server 2000. But scheduled jobs are runing fine automatically.
Thanks for any reply.
What errors do you get? What is in the SQLAgent.out file in
the Log directory?
-Sue
On Mon, 7 Nov 2005 08:16:15 -0800, new
<new@.discussions.microsoft.com> wrote:
>The job in SQL server agent won't manully start after installed SP3 for SQL
>server 2000. But scheduled jobs are runing fine automatically.
>Thanks for any reply.
|||This may be a given, but make sure that the EM registration for this instance
has the proper rights to exe jobs. If you are using Windows Authentication on
this registration, then make sure the win login you are using has sa. Some
permission levels allow you to view jobs, but can not execute them.
Thanks,
Rick MCP
"new" wrote:
> The job in SQL server agent won't manully start after installed SP3 for SQL
> server 2000. But scheduled jobs are runing fine automatically.
> Thanks for any reply.
Subscribe to:
Posts (Atom)