Prev: stock WSS+WMSDE, search not working, error 80042616 in logs
Next: How to deploy application template core to WSS site
From: Gunther Rohrer on 26 Mar 2007 15:04
I have this error right now on my production site. It started
occuring after the DST patch was improperly installed last month. It
is global (all sites, all lists and libraries). I did some research
and found this command was receommended:

stsadm -o upgrade -forceupgrade

That didn't work on my production server, but when I restored the
messed up production portal to my dev server (and recreated the issue
there) I was able to fix dev by running the command. Since we are
about to upgrade our SPS2003 server to a new one in preperation for
MOSS, I tried restoring it there and running the command and it
worked, so we're just going to move to the new server and fix the
problem that way. If you don't have a different server to move to,
you could probable just back-up your system, rebuild the server
(including all SharePoint service packs/hotfixes you are currently
running) and then restore your SharePoint sites and run the command.
Obviously, before you go this route, you'll want to see if it works on
a test server.

From: Keith on 27 Mar 2007 21:43
Hi there,

It was advanced setup and nothing is in the event logs....

thanks

keith

"Misho" wrote:

> On Mar 23, 8:26 am, Keith <K...(a)discussions.microsoft.com> wrote:
> > All,
> >
> > Has anyone found a working fix as i have the same issue with the top level
> > site.
> >
> > thanks
> > keith
> > -------------------------------------
> >
> >
> >
> > "saquibir...(a)gmail.com" wrote:
> > > On Mar 7, 1:40 am, birdsn...(a)gmail.com wrote:
> > > > Thanks Brad, at least that tells me what the problem isn't...
> >
> > > > On Mar 5, 5:26 pm, "brad" <obha...(a)gmail.com> wrote:
> >
> > > > > Hi John,
> > > > > Just so you know your not alone, i also get in my log files similar
> > > > > errors to you but my sites seem to be ok. The errors i get in the 12
> > > > > hive log directory are:
> >
> > > > > Failed to look up string with key "XomlUrl", keyfile core.
> >
> > > > > Localized resource for token 'XomlUrl' could not be found for file
> > > > > with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server
> > > > > Extensions\12\Template\Features\Fields\fieldswss.xml
> >
> > > > > Failed to look up string with key "RulesUrl", keyfile core.
> >
> > > > > Localized resource for token 'RulesUrl' could not be found for file
> > > > > with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server
> > > > > Extensions\12\Template\Features\Fields\fieldswss.xml
> >
> > > > > I know this for sure happens happen at time of site deployment.
> > > > > So whilst it does not appear to cause any problems I really want to
> > > > > find out the cause / resolution on this, so I can get rid of these
> > > > > messages and be confident my instal is working fine.
> > > > > I am running this in a virtual machine if that makes any difference,
> > > > > virtual pc 2007
> >
> > > > > I may need to go back to a clean install and check it does not occur,
> > > > > i.e. is it something i have introduced through custom field
> > > > > definition, or changes to other files. And slowly repeat the steps I
> > > > > have so far undertaken and view the logs for the first time this
> > > > > occurs again.
> >
> > > > > So in summary, sorry I cannot help but rather than just view message
> > > > > and think, "yeah im getting that as well" i thought id post as i am
> > > > > sure other users will hit this error in the logs at somepoint in the
> > > > > future.
> > > > > regards
> > > > > Brad
> > > I think your backup and restore will work...!!! try on a test site...- Hide quoted text -
> >
> > - Show quoted text -
>
> Hi All,
>
> What kind of install WSS install did you use Basic or Advanced? Did
> you check the server event log?
>
> MD
>
>
First  |  Prev  | 
Pages: 1 2 3
Prev: stock WSS+WMSDE, search not working, error 80042616 in logs
Next: How to deploy application template core to WSS site