Bug in SP4

Hi,
I met a bug in SP4. I did the same test on two machines. One is a windows
2003 server wint SQL Server 2000 Enterprise SP3, another is a SQL Server 200
0
develope SP3. Both machines can't run any jobs by sp_start_job stored
procedure after installation of SP4. Same to sp_stop_job. The error is:
Server: Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
Line 61
The specified @.job_name ('test1') does not exist.
Both stored procedures run well in SP3, but not in SP4. I am sure it's a bug
in SP4.
BillBill,
I just tested this on w2000, SP4, and was able to start a job. Is it maybe
that you were using a non-sysadmin login, so didn't have access to the
msdb.sysjobs_view (used by sp_start_job)? Try select from sysjobs_view and
then from sysjobs to see.
"Bill Wang" wrote:

> Hi,
> I met a bug in SP4. I did the same test on two machines. One is a windo
ws
> 2003 server wint SQL Server 2000 Enterprise SP3, another is a SQL Server 2
000
> develope SP3. Both machines can't run any jobs by sp_start_job stored
> procedure after installation of SP4. Same to sp_stop_job. The error is:
> Server: Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
> Line 61
> The specified @.job_name ('test1') does not exist.
> Both stored procedures run well in SP3, but not in SP4. I am sure it's a b
ug
> in SP4.
> Bill|||Thanks, Mary.
I tested the select from sysjobs and sysjobs_view. No permission issues on
these two table/view. Itested SP4 with sa. Before installation of SP4, I can
run these stored procedure, then install SP4 and run it with same user. It
failed with the error.
Did you install other hotfix after SP4 ?
Thanks!
Bill
"Mary" wrote:
[vbcol=seagreen]
> Bill,
> I just tested this on w2000, SP4, and was able to start a job. Is it mayb
e
> that you were using a non-sysadmin login, so didn't have access to the
> msdb.sysjobs_view (used by sp_start_job)? Try select from sysjobs_view an
d
> then from sysjobs to see.
> "Bill Wang" wrote:
>|||Sorry, if you create a new job after SP4, it's OK. But you can't run any job
s
by sp_start_job on old jobs created on SP3.
Bill
"Mary" wrote:
[vbcol=seagreen]
> Bill,
> I just tested this on w2000, SP4, and was able to start a job. Is it mayb
e
> that you were using a non-sysadmin login, so didn't have access to the
> msdb.sysjobs_view (used by sp_start_job)? Try select from sysjobs_view an
d
> then from sysjobs to see.
> "Bill Wang" wrote:
>|||I tried this using Dev Edition on XP and didn't see this behaviour. After
upgrading from SP3 to SP4 calls to sp_start_job either from another job or
Query Analyzer ran fine (all jobs owned by sa). What collation is your
sevrer and are your jobs owned by sa or another user? Are you calling
sp_start_job when logged in as a sysadmin?
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Bill Wang" <BillWang@.discussions.microsoft.com> wrote in message
news:13316834-4E2C-4AF2-B838-1CD16C106C7B@.microsoft.com...[vbcol=seagreen]
> Sorry, if you create a new job after SP4, it's OK. But you can't run any
> jobs
> by sp_start_job on old jobs created on SP3.
> Bill
> "Mary" wrote:
>