This post is a follow-on to my Must-Know Visual Studio debugging tips article; I'm separating out my SharePoint debugging tips focused on list, feature, and solution deployment that don't relate to Visual Studio.
Here you go:
- Try activating your feature without the –force attribute; you'll likely need to deactivate the feature first
- Try uninstalling and reinstalling the feature
- If something stuck and rebooting seems to clear some kind of cache deep inside SharePoint, stop IIS and restart the various SharePoint Windows services
@echo Stopping services...
iisreset /stop /noforce
net stop "Windows SharePoint Services Timer"
net stop "Windows SharePoint Services Administration"
net stop "Office SharePoint Server Search"
net stop "Windows SharePoint Services Search"
net stop "Windows SharePoint Services Tracing"
@echo Starting services...
net start "Windows SharePoint Services Tracing"
net start "Windows SharePoint Services Search"
net start "Office SharePoint Server Search"
net start "Windows SharePoint Services Administration"
net start "Windows SharePoint Services Timer"
- Create a new list from your list definition (or at least, a new list item)
- Rebuild your solution and redeploy
Hi Michael, I would just like to state that ever since I found this post in March 2011 I have used your tip several times on crucial occasions and so, yes, someone (over in Holland) surely found it useful!ReplyDelete
Thanks for the positive feedback, happy to help!ReplyDelete
I've learned some good stuff here I do appreciate your efforts to create one of these magnificent informative websites.ReplyDelete