Showing posts with label Errors. Show all posts
Showing posts with label Errors. Show all posts

Wednesday, September 25, 2013

SharePoint 2010 - Object Cache: The super user account utilized by the cache is not configured.

Following error is appearing as warning on Web front ends 

Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources.
 To configure the account use the following command 'stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue account -url webappurl'. The account should be any account that has Full Control access to the SharePoint databases but is not an application pool account.
 Additional Data:
 Current default super user account: SHAREPOINT\system

If you think that having object caching isn't going to cause an issue with content use the following to resolve

1. Verify that you have the following administrative credentials:
To create the user accounts in Central Administration, you must be a member of the Farm Administrators group on the computer that is running the SharePoint Central Administration Web site.
2. On the Central Administration Web site, in the Application Management section, click Manage web applications.
3. Click the name of the Web application that you want to configure.
4. On the Web Applications tab, in the Policy group, click User Policy.
5. In the Policy for Web Application window, click Add Users.
6. From the Zones list, select All zones, and then click Next.
7. In the Users box, type the user name for the Portal Super User account. - domain\spsuperuser
8. Click the Check Names icon to ensure that the account name can be resolved by the authentication providers on the application server.
9. In the Choose Permissions section, check the Full Control - Has full control box.
10. Click Finish.
11. Repeat Steps 5 through 8 for the Portal Super Reader account.
12. In the Choose Permissions section, check the Full Read - Has full read-only access box. - domain\spsuperreader
13. Click Finish.
14. Make note of how the names for the Object Cache Super Reader and Object Cache Super User accounts are displayed in the User Name column. The displayed strings will be different depending on whether you are using claims authentication for the Web application.

Powershell to run 

$wa = Get-SPWebApplication -Identity "<App Identity from IIS>"
$wa.Properties["portalsuperuseraccount"] = "domain\spsuperuser"
$wa.Properties["portalsuperreaderaccount"] = "doamin\spsuperreader"

$wa.Update()

And to rollback ....

$wa = Get-SPWebApplication “http://urlofthewebapplication”
$wa.Properties.Remove("portalsuperuseraccount")
$wa.Properties.Remove("portalsuperreaderaccount")

$wa.Update()





Wednesday, January 30, 2013

SharePoint 2007 - stsadm error


After trying to restore a site collection from another environment I received the following error :


No content databases are available for this operation. Create a content database, and then try the operation again. To create a content database, click "Content databases" on the Application Management page, select the Web application to use, and then click "Add a content database".

Check CA and all was as expected, content DB's online.

I realised that the site collection had actually been restored before, even though it has a new name it had the same GUID within SharePoint and therefore needed to be on a new contentDB.



Wednesday, October 31, 2012

SharePoint 2007 "Code blocks are not allowed in this file" after saving a file from Word

Received the error after trying to save to a SharePoint document library via Word.
The method I used to resolve was to 

Go to Site Actions -> Site Settings.Click the "Reset to site definition" link.
The type in the link that is not working "Latest Documents/Forms/AllItems.aspx" and just reset this library 
This was fine for me as I didn't have any customizations as they will be reset.

Tuesday, August 28, 2012

SharePoint 2010 - Exception: Invalid object name 'Webs'.

After running SP 2010 Cumulative update package and attempting Wizard I ran into the following error on a development box

Exception: Invalid object name 'Webs'.


Not very clear error .... but after looking in the Upgrade.log I found the following error pointing to a ContentDB


[DEBUG] [8/24/2012 7:01:02 PM]: Retrieving site definition for language 1033...
[OWSTIMER] [SPUpgradeSession] [ERROR] [8/24/2012 7:01:02 PM]: Upgrade [SPContentDatabase Name=WSS_Content] failed.
[OWSTIMER] [SPUpgradeSession] [ERROR] [8/24/2012 7:01:02 PM]: Exception: Invalid object name 'Webs'.
[OWSTIMER] [SPUpgradeSession] [ERROR] [8/24/2012 7:01:02 PM]:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()

Armed with this information I checked the content DB in question using SQL loads of tables/stored procedures were missing - see pictures below

Other Tables contained many more as below
















As this was a development box I was able to remove the  web application and content DB - re-ran the upgrade wizard and all was good. 


Monday, February 13, 2012

SharePoint 2007 - Configuration must be performed in order for this product to operate properly

Received this error when trying to upgrade a 2007 farm from 12.0.06545 to 12.0.06565 on a test environment.


I had run all patches on the farm both WSS and MOSS and could not see why the configuration wizard would not complete - my first reaction was to try re-installing patches but all stated "Already Installed".


I then checked the servers in farm via CA and saw the following - see version numbers






From the screen shot you can see the versions are not displaying correctly and this was causing the wizard to fail, even though all had been installed !!


After a few reboots, IIS resets I realised that the issue was the timer job on the offending server was not running (not on purpose). As soon as this was started the version upgraded and wizard run correctly.

Thursday, February 9, 2012

SharePoint 2007 - Errors after patch deployment

Recently we started seeing the following errors appearing in our SharePoint 2007 environment and sites not able to be created.:



  • The element 'FormTemplatesList' of type 'ListInstance' for feature 'IPFSWebFeatures' (id: a0e5a010-1329-49d4-9e09-f280cdbed37d) threw an exception during activation: Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))
  • Failed to activate template-associated site-collection-scoped features for template 'STS#0' in site
  • Failed to apply template "STS#0" to web at URL 
  • Feature Activation: Failed to ensure feature dependencies for feature 'PublishingSite
  • Feature Activation: Failed to ensure feature dependencies for feature 'PremiumSite'



In our environment  by mistake one of the servers in the farm had a latest patch downloaded to it - in this case 12.0.0.6565 - and the rest of the servers were on 12.0.0.6545. However we were not aware the patch had been deployed to the above errors were the only indication something had changed in the farm as via CA it still displayed the old version number.


Out first thought was to run the wizard on the affected servers which proceeded in upgrading the server to the patch and then also all the content databases in the farm .... not ideal and against all Microsoft best practices. Once we realised there was no way to roll back we upgraded the rest of the farm and the errors above disappeared.


Its seems the errors were around mismatches in dlls 









Friday, January 27, 2012

SharePoint Disable Loopback on server


This needs to be actioned to resolve 401 errors (access denied from Web Server and putting a logon failure in eventlog)




Setting the DisableLoopbackCheck registry entry in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa registry subkey to 1. 


To set the DisableLoopbackCheck registry entry to 1, follow these steps on the client computer: 


1. Click Start, click Run, type regedit, and then click OK.  
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa 
3. Right-click Lsa, point to New, and then click DWORD Value.  
4. Type DisableLoopbackCheck, and then press ENTER.  
5. Right-click DisableLoopbackCheck, and then click Modify. 
6. In the Value data box, type 1, and then click OK.  
7. Exit Registry Editor. 
8. Restart the computer. 


Note You must restart the server for this change to take effect. 

Thursday, January 26, 2012

500 Service Unavailable - ISA 2006 and SharePoint 2007

Using SharePoint 2007 and ISA 2006 I came across an issue where external users of a site were recieivng the error "500 Service Unavailable" - even though the site was available and working. After some digging around I found the following resolved my issue 


I was required to switch off "verify normalisation" on ISA - it seems its an incompatibly between ISA 2006 and SharePoint 2007 










Wednesday, January 25, 2012

SharePoint 2007 - Central Admin stops working when installing search


On a couple of occasions when going through initial configuration of search- Central Admin stops working - cannot access.
Don't panic - What actually happened in my instances whilst  using Windows 2008 is that if you setup the Search service it writes an entry in its local host file. For example on myServerA we set up appserver to be index server, sharepoint adds following entry to host files


fy80::49e2:5150:a356:32ac%10 myServerA 


What sharepoint is actually doing is reading the Link-local IPv6 Address which is not quite right.


This just needs to be manually replaced in host file 
127.0.0.1 localhost myServerA 

SharePoint 2010 - "There was an error saving the picture. Please try again later. "

Found this issue when editing user profiles of other people - resolved with the following CU
http://support.microsoft.com/kb/2597014

SharePoint 2010 - The specified value for the LocStringId parameter is outside the

Came across this error installing a new Farm after putting on SP1 -  Noticed the error when accessing "Manage Services on Server " 


My Resolution - Check Service Packs  - I had just installed SP1 and for some reason had not taken the SharePoint Server (office) patch properly to resolve took the following action and worked for me
  • Install SharePoint Foundation 2010 SP1
  • RESTART OS
  • Install SharePoint Server 2010 SP1
  • IISRESET
  • Run psconfig -cmd upgrade -inplace b2b -wait