Problem Description
Resolution
At some point, I realized that this was a site collection specific issue. This site collection had its own dedicated database. I had to detach and attach the content database of this site collection from the web application using Powershell(read dismount and mount)to resolve this issue.
Few weeks back I had done a detach/attach of the same content database from Central Administration. I think performing dismount and mount from Central Administration console led to this behavior. I still find this weird though.
P.S.: Please make a note of the Content DB name before you start this operation
Dismount-SPContentDatabase"<ContentDBName>"
Mount-SPContentDatabase"< ContentDBName >" -DatabaseServer"<DBServerNAme>" -WebApplicationhttp://SiteName
No comments:
Post a Comment