mylifeinaminute.com

More fun SharePoint errors in the system log. If you’re seeing 10016/17 errors in the Event Log and want to resolve them, perform the steps outlined in KB920783.

Note that these errors are more of a nuisance than anything. The existence of these errors is expected and will not impact the functionality of your farm. That being said, less errors being generated is a “good thing” in my mind.

zevenseas has released their SharePoint LifeCycle Management solution to CodePlex.  The LifeCycle Management solution can be used to track unused SharePoint sites as well as capture and automatically back-up sites.  Actions can be defined to use against your unused sites, such as emailing the site owner, locking the site, or even deleting it.

What are you waiting for?  Go check it out!

When cleaning up a number of older databases in a QA/Staging environment (databases dating back to 2003), we managed to delete the default database for the SharePoint database system account. After deleting the database, the user will longer be able to perform actions on the SQL instance (login, view databases, etc.) when logging on through Management Studio.  To fix this error, log on to your SQL server as another administrative user (like the “sa” account), and execute the following:

sp_defaultdb 'SQLSERVER\dbuser', <DEFAULT DB>

Replacing with the new default database name.

There are times when strange errors can occur in your SharePoint environment, especially after making configuration changes such as adding a new Web Application role to an existing farm server or even updating an Alternate Access Mapping (AAM).  Clearing the configuration cache can also help with problems relating to the ULS logs growing at an exponential rate, especially when the “Config Refresh” timer job cannot complete successfully.

Clearing the SharePoint configuration cache can sometimes help alleviate these issues.  To clear the configuration cache, you can follow the procedures outlined in KB939308.