Error creating Push subscription

Hi All,
I've had this problem for about 4 weeks, and I cna't seem
to find a solution! I'm trying to create a puch
subscription but get the following error when EM tries to
create the records:
FHQRY: Error 515: Cannot insert the value NULL into
column 'step_name', table 'msdb.dbo.sysjobsteps'; column
does not allow nulls. INSERT fails.
I'm running SQL 2000 sp3a on Win 2k sp4. Also I've updated
to MDAC 2.8. I've tried using the stored procs but still
get the same error.
Any suggestions as to why this is happening?
I was told from a nother forum that this kind of problem
occurred with a SP update SQL 7.0 and MS isued a patch.
Should this patch be applied to my server if available? as
it the replication was working prior to a major rebuild.
thanks for any help
Davej
There are probably some missing messages in the sysmessages table in the
master database. Some of the messages are used for dexcriptiosn of the
various replication jobs. You can run a profiler trace while the push
subscription is being created and probably captiure which message is
missing.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Error creating new push subscription after deleting the existing o

I created a transactional replication publication and pushed a subscriber,
and that works fine. I deleted existing push subscription in the publisher
with enterprise manager, and also deleted automatically generated replication
jobs related to that push subscription. I noticed that the push subscription
was not automatically deleted in the subscriber as it should. Moreover, when
I created a new push subscription with the same article, I encountered an
error. The error message is as following.
Subscriptions were created successfully at the following subscribers.
…
SQL Server Enterprise manager could not start the snapshot agent.
Error 14262:the specified @.job_id … does not exist.
Please help.
The error indicates that a replication agent job was deleted accidentally.
When this issue occurs, the most efficient way would be rebuilding the
replication from scratch.
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.