Home > SharePoint > Deploying custom timer job on SharePoint farm – Troubleshooting

Deploying custom timer job on SharePoint farm – Troubleshooting

I was working on SharePoint timer jobs and was stuck into it.

Scenario :

We have web app level feature having timer job which runs on all the server in farm.
I changed few logic’s in custom timer job code. New logic is running only on One of three server. (App,WFE1,WFE2).
I deployed the solution on app server using wsp builder and stsadm commands.

Solution :

copying the solution from http://www.codeproject.com/KB/sharepoint/debugging-sharepointjobs.aspx

Cached Assemblies!

Any time you update your custom timer job class and deploy the assembly to the global assembly cache, you must restart all the timer services in the farm. If you don’t restart the timer service, it will run the old copy of your timer job class. Yes, the timer service caches the assemblies. Restarting the SharePoint timer service is the only way to refresh the assembly cache and force it to use your updated assembly.

After restarting OWS Timer service on all servers , it worked out for me 🙂 HuRraY..

Special thanks to Mr. Shoaib Adil for assisting me.

  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: