Setuser failed?

Hi,

I have recently migrated from sql server 2000 to 2005.
One of my old jobs is currenty failing with

Msg 15157, Sev 11, State 1: Setuser failed because of one of the
following reasons: the database principal 'sa' does not exist, its
corresponding server principal does not have server access, this type
of database principal cannot be impersonated, or you do not have
permission. [SQLSTATE 42000]

The jobs calls a procedure that again uses sp_makewebtask. It is this
proc that throws the above error.

Someone with a clue on what I should do to resolve this?

Regards,

.

Relevant Pages

  • CUPS problem printing pictures is very slow
    ... all jobs) and everything is working very well, ... # Server name ... # Browse order (BrowseOrder) ... # Whether or not to use implicit classes. ...
    (Debian-User)
  • CUPS problem printing is slow
    ... all jobs) and everything is working very well, ... # Server name ... # Browse order (BrowseOrder) ... # Whether or not to use implicit classes. ...
    (Debian-User)
  • Re: strange problem with send() and recv()
    ... > I try to write a simple tcp based job queue server. ... > get commands from a client and store them in a queue. ... > The client can query the server about the jobs currently queued. ...
    (comp.lang.c)
  • Re: /etc/cron.daily/apt hangs [deviated discussion]
    ... you're the first one I know of who expects jobs in cron.daily to be run ... it caused by a sleep like in the apt script, a slow network or something else) ... Who "switches on" a Unix box??! ... Ubuntu Server (ironic that now, ...
    (Ubuntu)
  • Re: Copying large quantity of files taking forever
    ... The utility xxcopy.exe is known for baulking at large copy jobs. ... copying from another Windows server and even moving from another ... are running Windows Server 2000 or 2003 server. ... at top speed, don't keep more than 10,000 entries in a single folder. ...
    (microsoft.public.windows.server.general)