Sharepoint 2010 Secure Store: An error occurred during the “Generate Key” process. Please try again or contact your administrator
By peter.stilgoe
“Sharepoint 2010 Secure Store: An error occurred during the “Generate Key” process. Please try again or contact your administrator”
Things to check:
– Ensure the logged in user is a member of the farm administrators group
– In my case the ‘Sharepoint Webservices Root’ application pool had stopped on one of my app servers
STSADM -o backup -directory: Error Cannot open backup device Operating system error 5 (error not found)
By peter.stilgoe
STSADM -o backup -directory: Error Cannot open backup device Operating system error 5 (error not found)
Ensure the SQL service account is a domain account and it has permissions to
the Shared folder.
Also ensure the account used to execute the backup command has the correct rights on the DB’s as per MS recommendations ie. Owner, creator etc.
More From pstilgoe
Excel Web Services: Error http://myserver:56737/SharedServices1/ExcelCalculationServer/ExcelService.asmx exception: The request failed with HTTP status 403: Forbidden (Forbidden port)
By peter.stilgoe
Im having a problem on a MOSS 2007 farm where if I try & open a spreadsheet in Excel web services I get the error:
Excel Web Access
An error has occurred.
Please contact your system administrator if this problem persists
And in the Sharepoint logs:
Error http://myserver:56737/SharedServices1/ExcelCalculationServer/ExcelService.asmx exception: The request failed with HTTP status 403: Forbidden (Forbidden port)
If I search Google there doesnt appear to be any results for the error ‘The request failed with HTTP status 403: Forbidden (Forbidden port)’ and Im really stumped now.
If anyones got any ideas much appreciated !
TIA……..
UPDATE: If you get this problem the solution in my case was to by pass the proxy for local requests, this was done by editting the web.config for the relevant web app & adding:
<system.net> <defaultProxy> <proxy proxyaddress="http://<ProxyServer>:<port>" bypassonlocal = "true"/> </defaultProxy> </system.net>
Some more info about bypassonlocal can be found here: ByPassOnLocal MS KB
More From pstilgoe
Sharepoint 2010: Create site from site template where alternate CSS url is set – unexpected error occured accessing site settings
By peter.stilgoe
When you create a site template in Sharepoint 2010 where the template is taken from a site that has an alternate CSS url set, you find on the newly created site that when you try & access ‘Site Settings’ or ‘View all site content’ you get the ‘An unexpected error occured’.
In your logs you get something like:
System.Web.HttpException: Error executing child request for /sites/SiteName/Style Library/site-style.css
This appears to be a bug, you can fix the site by running the following Powershell script:
$w = Get-SPWeb http://YourServer/YourWeb; $w.AlternateHeader = $null; $w.Update()
More From pstilgoe
Sharepoint 2010 Error: An exception occurred when trying to issue security token Event ID 8306 and Event ID 7557
By peter.stilgoe
After creating a new secure store service application everytime I clicked manage it would say I dont have correct permissions no matter who I was logged in as. In the event logs I was getting the following errors:
Event ID 8306: An exception occurred when trying to issue security token: The server was unable to process the request due to an internal error.
Event ID 7557: The Secure Store Service application Secure Store Service Application is not accessible. The server was unable to process the request due to an internal error
The solution was that the ‘Claims to Windows Token Service’ wasn’t started on the Sharepoint server(s). Once I started this & restarted the Sharepoint services I was able to manage my secure store service application.
More From pstilgoe
Sharepoint 2010: Some or all identity references could not be translated
By peter.stilgoe
When adding a managed account in Sharepoint 2010 I was getting the following error:
The specified user *********\sv-2010devappsrvappcore could not be found. Some or all identity references could not be translated.
It seems like its related to the length of the username, something 20 chars or less seems to work.
More From pstilgoe
Sharepoint 2010: Adding a new managed account from different domain errors with access denied
By peter.stilgoe
For example you are running Sharepoint 2010 in the a 1 way trust environment & you want to add a new managed account to your Sharepoint farm from your internal domain. This should be fairly simple by going Central Admin –> Security –> Configure Managed Account –> Register Managed Account
User name: domain\accountname
Password: *********
However no matter what I tried doing this in cental admin always returned the error:
An error occurred while getting information about the user
To get round this you need to add the account using powershell.
- Log onto you server using an account from your internal domain (you need to do this so it can retrieve the info it needs from this domain)
- In powershell
$cred = Get-Credential
Now a login prompt will pop up, enter the managed account details here you are wishing to add domain\username, enter password & click OK
- Now enter
New-SPManagedAccount –Credential $cred
Your managed account will now be added, you can check this in central admin or powershell using
Get-SPManagedAccount
SharePoint 2010 CU upgrade error – keyword not supported failoverpartner
By peter.stilgoe
When applying updates to your Sharepoint 2010 farm you may get the following error in the Sharepoint Configuration Wizard:
An exception of type System.ArgumentException was thrown. Additional exception information: Keyword not supported ‘failoverpartner’.
This means youve got mirroring enabled on your Sharepoint databases and Sharepoint CU updates dont install on mirrored databases.
To find out what sharepoint databases are mirrored/failover you can use the following powershell command:
get-spdatabase | select name, failoverserver
You can turn off the failover for you content databases in central admin aswell as your service application databases. However all other databases need to be turned on & off using powershell.
To Turn Off Mirroring /Failover on your database:
$database = Get-SPDatabase | where { $_.Name -eq "ASharePointDB" }
$database.AddFailoverServiceInstance("")
$database.Update();
To Turn On Mirroring /Failover on your database:
$database = Get-SPDatabase | where { $_.Name -eq "ASharePointDB" }
$database.AddFailoverServiceInstance("FailoverSQLServerName\OptionalInstanceIfUsed")
$database.Update();
Unable to add selected web part
By peter.stilgoe
Unable to add selected web part(s)
QueryListPart: A Web Part or Web Form Control on this page cannot be displayed or imported. The type could not be found or it is not registered as safe.
- Make sure the webpart is registered as safe in the web.config
- Make sure the assembly is accessible and in the bin folder
- Make sure the assembly name in the *.webpart definition file, matches the assembly name in the safe control element in web.config
- Make sure you don’t have more than one *.webpart file for the same web part in the web part catalog. This may happen if you changed the name of the *.webpart file.
- Restart IIS to start clean. Attach the debugger to the w3wp.exe process and try to load the page with the rogue web part. This way you can determine the exact location of the assembly you are loading.
- Check if the web part class exists by opening the assembly with reflector. This might sound funny, but in a bigger team, when different versions of assemblies are flying around it is very easy to overlook something and to use the wrong version, which so happens does not contain the web part class at all.
Thanks to http://www.mikhaildikov.com/
More From pstilgoe
Error (Exception from HRESULT: 0×80004004 (E_ABORT))
By peter.stilgoe
This error usually occurs in Sharepoint when the transaction log is full or no drive space available to it on the SQL server in your farm.
You will usually get the error when trying to create new content etc.
More From pstilgoe
An error occurred processing the data view. The XslText property is empty
By peter.stilgoe
If you are getting the error:
‘An error occurred processing the data view. The XslText property is empty’
You have probably inserted an extra dataview on your page, check your page & remove the extra data view you accidentally inserted & your error will go away.
More From pstilgoe
Sharepoint Javascript Error: ‘style.display’ is not null or not an object
By peter.stilgoe
If you are receiving the following error when trying to access the ‘edit’ menu of a webpart on a page:
‘style.display’ is not null or not an object
It is likely that you have some random/extra code in another webpart on the page, this typically happens if you cut & paste text from another location onto the page & it also brings over some formatting chars which upsets Sharepoint. Either:
a) Remove the offending text from another webpart on the page
b) Use something other than IE like Firefox or Google Chrome, typically using another web browser you will be able to edit the troublesome webpart.
More From pstilgoe
After restoring a site collection to a new location you get error The file /_catalogs/masterpage/blahblah.aspx does not exist.
By peter.stilgoe
How To Fix Publishing Pages Page Layout URL
The scenario when moving you want to move a publishing site collection that is your root site collection to a new location
ie http://rootsc —> http://sites/rootsc
You expect a simple backup & restore to the new location to do the job. However once your restore is complete you try to load your site collection in its new location & you get:
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
You click ‘View Source’ in IE & you get:
The file /_catalogs/masterpage/blahblah.aspx does not exist.
at Microsoft.SharePoint.ApplicationRuntime.SPRequestModuleData.GetWebPartPageData(HttpContext context, String path, Boolean throwIfFileNotFound)
The problem is that your publishing pages are still looking at the old location for the master page files etc using the old URL. Fortunately Gary Lapointe MVP has written a script to parse through the whole site collection & update the paths accordingly.
The utility runs as an STSADM command & is called gl-fixpublishingpagespagelayouturl
K2 deployment error: The partner transaction manager has disabled its support for remote/network transactions
By peter.stilgoe
When deploying a new K2 workflow / process you get an error message containing:
The partner transaction manager has disabled its support for remote/network transactions
First check on the application server(s):
1. Go to “Administrative Tools > Services”
2. Turn on the “Distribute Transaction Coordinator” Service if it is not running
If you still get the error:
First verify the “Distribute Transaction Coordinator” Service is
running on both database server and application servers
1. Go to “Administrative Tools > Services”
2. Turn on the “Distribute Transaction Coordinator” Service if it is not running
If it is running and its not running on the same server as the SQL Server:
1. Go to “Administrative Tools > Component Services”
2. On the left navigation tree, go to “Component Services > Computers
> My Computer” (you may need to double click and wait as some nodes
need time to expand)
3. Right click on “My Computer”, select “Properties”
4. Select “MSDTC” tab
5. Click “Security Configuration”
6. Make sure you check “Network DTC Access”, “Allow Remote Client”,
“Allow Inbound/Outbound”, “Enable TIP” (Some option may not be
necessary, have a try to get your configuration)
7. The service will restart
8. YOU MAY NEED TO REBOOT YOUR SERVER IF IT STILL DOESN’T WORK
On the application server(s) use the same above procedure to open the
“Security Configuration” setting, make sure you check “Network DTC
Access”, “Allow Inbound/Outbound” option, restart service and computer
if necessary.
On you SQL server service manager, click “Service” dropdown, select
“Distribute Transaction Coordinator”, it should be also running on
your server computer
More From pstilgoe
Deploying K2 process: Error occurred adding the feature to the farm Server was unable to process request. —> Access denied.
By peter.stilgoe
When deploying a K2 process you get the following error:
Task Error: System.Exception: Error occurred adding the feature to the farm. —> System.Web.Services.Protocols.SoapException: Server was unable to process request. —> Access denied.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
This is normally a permission problem & you should check the following & make any changes that are required:
1) Check that the MOSS app pool account has Site Collection and Farm Admin Rights and is also a local administrator.
2)Check that the MOSS app pool account is given dbo permission on the SP Admin Config database.
3)Check that the MOSS app pool account is granted modify permissions: [Program Files]\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\ and \12\ISAPI folders.
4) Make sure the MOSS app pool account is given K2 export rights.
5) Make sure the “K2 Workflow Integration Content Types” in Central Admin > K2 for SharePoint has been activated.
You may also need to to do an iisreset.
If all of the above are present you should be able to publish your workflow without experiencing the above error.
More From pstilgoe
Error: Cannot retrieve the information for application credential key
By peter.stilgoe
If you are receiving the error Cannot retrieve the information for application credential key. the problem is that the credentials could not be encrypted because no credential key has been established; to establish a credential key you must run STSADM -o setappassword -password
After you have established a credential key to encrypt the logon identity password you will be able to run STSADM -o setproperty -url http://server:port -pn “peoplepicker-searchadforests” -pv “domain:bar.foo.corp.com”, LoginName, P@ssword.
For detailed information on support for cross-forest deployments visit http://blogs.msdn.com/sharepoint/archive/2006/03/15/552331.aspx
Microsoft.SharePoint.SPException: A duplicate name “Report” was found
By peter.stilgoe
When you try to activate ‘Office SharePoint Server Enterprise Site Features’ you get the following error:
Office SharePoint Server Enterprise Site Collection features12/09/2008 16:00:51.91
w3wp.exe (0x1FB8) 0x17B8 Windows SharePoint Services
General 8grz High The feature
’8581a8a7-cf16-4770-ac54-260265ddb0b2′ depends on feature
’43f41342-1a37-4372-8ca0-b44d881e4434′ which failed to activate:
Microsoft.SharePoint.SPException: A duplicate name “Report” was found.
The problem occurs if you have created a custom content type called ‘Report’ this is because when you activate ‘Office SharePoint Server Enterprise Site Features’ it trys to create a system content type called ‘Report’. The workaround is to rename your custom content type from ‘Report’ to something similar.



January 9th, 2012
