Jens,

Looks like the problem is with the scheduler service itself.
Scheduling the job manually using the wizard generates the exact same error.
However, if you are logged on with admin rights, everything works okay.

This tells me that the credentials are stored in tha local secutiry database.
The database purges old information after some time by itself (don't know how long).
Admin rights are needed to overwrite information in this database.

I am not sure where we go from here. The only thing I can think of is
to figure out a way to change the database refresh interval if possible
or delete the credentials from it when the job is deleted.

I guess I am expecting magic or miracle here. [Big Grin] [Big Grin]

Thanks,
Anupam