That doesn't seem correct ;-) 

Have you enabled logging so that you have somthing more to go on then that error? Is everything else working as intended?

/Marcus

Do you share database with any other site? The ScheduledJob will be triggered for all sites using the specific database an perhaps some of those sites does not have Find installed?

/Henrik

The log does not show any errors and it is only one site using the db.

It seems there is more than site that has connection to the DB, You can find it by do profiling on sql server and add Server name, Host name,  database name and filter on netSchedulerGetNext or netSchedulerList stored procedure. And when the scheduler service run the job you will see which server name and host name call on these stored procedure.

A college of me got the site running. She stopped the site, but I could not se that solving the problem. I saw in the event log that the scheduled job failed on some other sites that was stopped on the IIS. After I disabled scheduled job on these sites, I saw that the episerver find index job worked. My question is: Could this also be a part of the problem? If a site fails, wont the other sites run their scheduled jobs?

Looks like the scheduled job runs randomly, In the scheduled job debug it now says: 

#INF# [_LM_W3SVC_21_ROOT] New scheduled job 04.10.2012 12:31:18 (8de3f2b0-6e12-4
716-a6f9-736f7e2f8944)

That is a while a go. I have tried to change the time on the job, but it wont run on that exact time? Anybody got a clue?

Hi all, 

i am experiencing a very similar issue to this where the schedule job runs fine manually but fails with an error relating to can't find the Episerver.find.dll when the schedule runs (set for 1hour). I must note that the schedule job doesn't always fail it happens randomly. It's a load balanced environment.

Did you manage to resolve this issue? Can you detail how I can set up error logging for Episerver.find please

thanks

paul