SharePoint / Office 365 / Azure Blog

1. Make sure the account running the SharePoint Timer service is the account which has the administrator Full Control permission over the site and the full permission over the content database. 2. Use Windows Explorer to open the 'Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\ <GUID>' folder. 3. Back up the .xml files and then delete the .xml files. 4. Open the Cache.ini file and then change the content of the Cache.ini setting to 1. 5. Click Start, point to Administrative Tools, and then click Services. 6. Restart the following Windows Services in the order shown: 1) Windows SharePoint Services Timer service. 2) Windows SharePoint Services Administration service. Thanks XI – BUNG – YU http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/4f1b3aaf-7173-4151-874b-5740bff4b14f

p until today I haven't found time to explore the obscure corners of the SharePoint 2010 Client Object Model. Keeping an eye on my Twitter client, I noticed   Waldek Mastykarz   mention trying to use it in an anonymous portal context - and hitting an error doing so. Problems such as these easily catch my interest (that's my favorite way of learning new stuff), so I set out to try the same myself. I whipped up an empty SP2010 team site, created a dummy list and added an item to that. I then went on to create a simple SilverLight package, such as: public partial class MainPage : UserControl {     private ListItemCollection _items;     public MainPage()     {         InitializeComponent();         var context = new ClientContext(" http://sp10dev");      ...