Sometimes when backing up or restoring I would get an error that a .bak file could not be found or accessed.
This error could often be fixed by restarting the “Windows SharePoint Services Timer”. For some reason it can time out in backup jobs once in a while, and a restart of it can do wonders.
You can do it through services under “Administrative Tools” or run the following 2 lines in a command prompt:
net stop “Windows SharePoint Services Timer”
net start “Windows SharePoint Services Timer”
Next time you get the problem, try it out. It fixed a problem for me. Offcourse there can be loads of other problems, but this one was my fix.
Related posts:
- Error when updating Windows SharePoint Services 3.0 with SP2 – An update conflict has occurred, and you must re-try this action. The object SPSearchDatabase…
- stsadm is not recognized as an internal or external command, operable program or batch file.
- Clone SharePoint (MOSS / WSS) stand-alone developer virtual machine (Rename SharePoint Server)
- Access SharePoint API from Console Program – Program Against the WSS Object Model
- Missing websites in the SharePoint flyout menus for everyone but the site collection owner
0 Responses
Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.