Gorgo.Live.ToString()

Mariusz, Gorzoch tech Blog

SPPersistedObject – once deployed – DO NOT CHANGE IT

with one comment

and if you will do this, then don’t be surprised that “Sharepoint timer job will stop working” and in addition you will start seeing errors like that in you Sharpeoint “Log” :

High File system cache monitor encoutered error, flushing in memory cache
High The WebUrls field in the Hempel.OneHempel.ArticlePage200.TEMPLATE.Admin.AP200.AP200JobSettings class has been deleted. The old value will be preserved in the UpgradedPersistedFields collection under the WebUrls key. Consider writing upgrade code to copy this value to a new location.
High The ArchiveArticles field in the Hempel.OneHempel.ArticlePage200.TEMPLATE.Admin.AP200.AP200JobSettings class has been deleted. The old value will be preserved in the UpgradedPersistedFields collection under the ArchiveArticles key. Consider writing upgrade code to copy this value to a new location.
High The DeleteArtciles field in the Hempel.OneHempel.ArticlePage200.TEMPLATE.Admin.AP200.AP200JobSettings class has been deleted. The old value will be preserved in the UpgradedPersistedFields collection under the DeleteArtciles key. Consider writing upgrade code to copy this value to a new location.
High Flushing the xml document cache.
High Flushing the xml document cache.
High Flushing the xml document cache.
High File system cache monitor encoutered error, flushing in memory cache
High File system cache monitor encoutered error, flushing in memory cache
High Exception in RefreshCache. Exception message :Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
Unexpected The timer service could not initialize its configuration, please check the configuration database. Will retry later.

 

happy I found solution for that… but unfortunately to apply it you need to brake “no one is allowed to touch database” rule!. If you can live with that, then :

  • Stop your SharePoint timer job
  • go to your “SharePoint config db”
  • open “object” table
  • find you persistent objects by “name” (select * from Objects where name ‘’%youObjectClassName%’”
  • delete what you get
  • now, go to the “C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\<ContentDBGuid>\ and delete all “.xml” files you find there (be sure to not delete folder as you will get into the problem trying to restore name of it) <- in this step you clearing local cache
  • start your “Sharepoint timer job”

in my case, this bring my timer job to live again. Ufffff

Advertisements

Written by Mariusz Gorzoch

12 May 2010 at 14:21

Posted in Bez kategorii

One Response

Subscribe to comments with RSS.


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 )

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s

%d bloggers like this: