Full and Incremental Content Deployment in SharePoint 2010

While working with content deployment I came to know that we can do the full and incremental deployment but I was unable to find the option to do the same through central administration in SharePoint 2010. I came to know there was an option to do the same in central admin of SharePoint 2007.

Then I searched and got hold of an old screen from 2007 where I saw the option to do the same as shown below.The same when I did from the central admin of SharePoint 2010 I did not find any option.


SharePoint 2007 Content Deployment

SharePoint 2010 Content Deployment

These option screen shown above are available when u “create a new Job” as show in the screen below

So how do we create a specific Job of type Incremental or Full? After doing surfing I found out that it can be done using PowerShell. Yes we can create Jobs with using PowerShell rather than the step show in figure 2(Above). Note this script should be run after you have already created the content deployment Path as in my case “Local Deploy”.

New-SPContentDeploymentJob -Name " Local Deploy - Incremental" -SPContentDeploymentPath
"Local Deploy" -IncrementalEnabled:$true

Now if we create a job through UI in central admin by default it will create Incremental Only. Yes and how do we find this out?

To do that, run Get-SPContentDeploymentJob "Local Deploy - Incremental". You should notice the following line in your output:

So how do we create a Job with “Full Content Deployment”

New-SPContentDeploymentJob -Name " Local Deploy - Full" -SPContentDeploymentPath
"Local Deploy" -IncrementalEnabled:$false

Reference Take by : http://sharepointlearningcurve.blogspot.sg/2010/05/sp2010-content-deployment-jobs-missing.html 

SharePoint 2013 CU August 2013 – "Internet Information Services not installed"

Today it was time to update my SharePoint 2013 installation from March CU 2013 to August 2013 CU.

"Internet Information Service not installed"
After the patching I have to start the Config Wizard. I was a little surprised as it responds with a nice error –  I even tried the PowerShell command in case there is a difference, but no:

What? IIS not installed anymore? Something must be broken with the Patch.

But then I tried to reproduce my steps – of course it must be a user error. After reading the patch script (reading things sometimes helps), I noticed that the script disables the IIS Admin service… it didn't happen on other 12 machines I installed this CU only this one :)

SharePoint does not like that – set it back to Automatic start and start the service.

And then start the config wizard again... Happy Patching!!!

SharePoint 2013 geolocation column: a component is not installed

Today I was playing with the new geo location column. I added the Bing maps key, created a custom list and added the geo location column via code to that list. Upon submitting a new list item, I received an error, mentioning that a component was not installed, to be able to use geolocation. This is a strange error, because I was able to add the column programmatically, while adding content to the list, is not possible. After checking the Diagnostic log, I noticed the following error:

A required component for using a geolocation field is not installed: Microsoft SQL Server System CLR Types

This remembered me that I had read somewhere (this means: It’s not in the geo location MSDN documentation.It’s written in the documentation on mobile apps and geolocation) that the SQL Server System CLR Types needed to be installed on the Web Front End servers. The package that needs to be installed is called “SqlSysClrTypes.msi”, and depending on the version of SQL that is used

After the installation, I still couldn’t add any items to the list. An IIS Reset didn't work for me but a reboot did the trick.

Content deployment failed, client response text/html expected text/xml

Content deployment job 'NonEng' failed.The remote Web service request failed with this message: 'Exception from HRESULT: 0x80131904'; Details: '<detail><errorstring xmlns="http://schemas.microsoft.com/CmsPublishing/soap/">Exception from HRESULT: 0x80131904</errorstring><errorcode xmlns="http://schemas.microsoft.com/CmsPublishing/soap/">-2146232060</errorcode></detail>'.

Content deployment job 'Eng' failed.The remote Web service request failed with this message : 'Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'. '.

If you got these errors in your Content Deployment and wondering what changed, probably the target server is restarted by one of the Admins, and it might have caused this, for me at least it did.

All we have to do is to do a good old IISRESET on the target server and then run the job.

ProjectServer 2013 environment migration / rollover steps

This blog post will detail the PowerShell commands required to carry out an environment rollover / migration using Windows PowerShell where possible. The steps below use the 2 database approach to rollover over the Production environment to the Test / Development environment.

As a prerequisite I would recommend taking full backups of the Test / Dev farm to enable the environment to be rolled back if required. Use your usual farm backup procedures.

Test / Dev environment Prep

Firstly connect to the Test / Dev Application server and launch the SharePoint 2013 Management shell.

Type the following:

Dismount-SPProjectWebInstance -SiteCollection  <URL of Test / Dev PWA site that you want to refresh with the Production data and config>

Press Enter and then type Y and press Enter to remove the PWA instance

You can check in Central admin in the Project Server Service Application to check that the PWA site has been removed:

Using the SharePoint 2013 Management Shell remove the existing content database from the web application that hosted the PWA site collection that was removed in the previous step.

Type the following:

Dismount-SPContentDatabase “<Database name here>”

Press Enter and type Y to confirm then press Enter

Test / Dev environment SQL Prep

Take a backup of the 2 databases from the Production environment and copy these over to the Test / Dev SQL server and restore the databases. The databases required are:

Content database that contains the PWA site and Project Sites
Project Web App database
Make a note of the database names used when these databases are restored as they will be required later.

Test / Dev environment configuration

Using the SharePoint Management Shell, attach the restored content database to the web application that will host the PWA site collection.

Type the following:

Mount-SPContentDatabase “<content database name restored in previous step>” -DatabaseServer “<Test / DEV SQL Server>” –WebApplication <web application URL>

Press Enter:

Using the SharePoint 2013 Management Shell mount the restored Project Web App database to the web application.

Type the following command:

Mount-SPProjectDatabase -Name “Name of the restored Project Web App database to mount” –WebApplication “Web Application ULR that the Project Web App database will mount to” –DatabaseServer “Test / Dev SQL Server where the database was restored”

Press Enter:

Now using the SharePoint 2013 Management Shell provision the PWA site collection in the web application where the database was just attached to and using the Project Web App database that was restored previously. Please note, use the same PWA path name used in Production. For example if the instance is called /PWA in Production, use /PWA in the command below on the Test / Dev environment.

Type the following command:

Mount-SPProjectWebInstance –DatabaseName “Name of the restored Project Web App database to mount” –SiteCollection “web application URL + PWA path” –DatabaseServer “Test / Dev SQL Server where the database was restored”

Press Enter:

You can check the provisioning status of the PWA site using PowerShell or in Central admin in the Project Server Service Application to check that the PWA site has been created:

Type the following:

Get-SPProjectWebInstance –URL <PWA URL> | Select ProvisioningStatus

Or in Central Admin:


Post Provisioning

The Project Sites will need to be relinked using the “Bulk Update Connected SharePoint Sites” functionality in Central Admin on the newly provisioned Test / Dev PWA site.

The Project Server Cube settings will need to be updated – update the SQL AS server / cube name.

Any Excel services reports will need to be updated to use the ODC files from the Test / Dev environment as they will currently point to the Production ODC files. This is done by opening the Excel reports in Excel, changing the ODC file then saving the file back to the library.

SharePoint 2013 Certificate Error Causes Performance Issues

Whilst working with a SharePoint 2013 environment I experienced slow page load times and poor search performance.  After initial page loads performance was fine for several minutes before the performance issue returned.

Opening the Application log within Event Viewer showed the following critical error with the text

“A certificate validation operation took 30015.2428 milliseconds and has exceeded the execution time threshold.  If this continues to occur, it may represent a configuration issue.  Please see http://go.microsoft.com/fwlink/?LinkId=246987 for more details.”

The fix for the problem is to export the SharePoint Root Authority certificate using PowerShell and import it into the Trusted Root Certificate store.  Open the SharePoint 2013 Management Shell as an administrator.

$SProotCert = (Get-SPCertificateAuthority).RootCertificate
$SProotCert.Export(“Cer”) | Set-Content C:\Test\SProotCert.cer –Encoding Byte

Open the Certificates MMC by opening a Run command and type MMC.  Choose File -> Add/Remove Snap-in.  Select the Certificates Snap-in and click Add.  On the next screen select Computer account and click Next followed by Local computer and Ok.

Right-click on Trusted Root Certificates and choose All Tasks -> Import

Complete the wizard by loading the certificate you exported using PowerShell.  Repeat the process on all SharePoint servers experiencing the issue.

These steps fixed the error on most of our SharePoint servers, but it remained on two.  In order to fix the error on the two remaining servers I configured proxy access through Internet Explorer, then from an elevated command prompt ran “netsh winhttp import proxy source=ie”  This configures Windows to use the IE proxy configuration as a default.  The servers were then able to access the internet and verify the certificates.

Re-Create (Generate) SharePoint Root Authority "local" certificate

If your are looking to re-create (re-generate) your SharePoint Root Authority "local" certificate, here are the commands to do so...

I accidentally deleted mine, so I exported from other farm members

To Export:
-------------
$rootCert = (Get-SPCertificateAuthority).RootCertificate
$rootCert.Export("Cert") | Set-Content C:\Temp\FarmRoot.cer -Encoding byte

To Import:
-------------
$rootCert = Get-PfxCertificate C:\Temp\FarmRoot.cer
New-SPTrustedRootAuthority  -Certificate $rootCert

Delete all sites from a site collection

$url = "http://yourweb.com"
$subsites = ((Get-SPWeb $url).Site).allwebs | ?{$_.url -like $url +"/*"}

foreach($subsite in $subsites) { Remove-SPWeb $subsite.url }

Here you go, full script of deleting all subsites / webs under a site collection, you can also add your subsite to delete the childs of that subsite only.

SharePoint 2013: The number of Distributed Cache hosts in the farm exceeds the recommended value

1. Verify that you have the following memberships:
   • securityadmin fixed server role on the SQL Server instance.
   • db_owner fixed database role on all databases that are to be updated.
   • Administrators group on the server on which you are running the Windows PowerShell cmdlets.
   • Farm Administrators group.
   An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.
   
   
2. Start the SharePoint 2013 Management Shell.
   • For Windows Server 2008 R2:
     • On the Start menu, click All Programs, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Management Shell.
   • For Windows Server 2012:
     1. On the Start screen, click SharePoint 2013 Management Shell.
        If SharePoint 2013 Management Shell is not on the Start screen:
     2. Right-click Computer, click All apps, and then click SharePoint 2013 Management Shell.

How SharePoint farm locates its configuration database

Did you ever wonder how SharePoint farm locates its configuration database. It’s not in a web.config or in any other configuration files. It’s actually a lot simpler than it probably should have been. SharePoint actually stores the connection to the configuration database in the registry (see dsn key).

SharePoint 2007: HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure\ConfigDB

SharePoint 2010: HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\Secure\ConfigDB

SharePoint 2013: HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\Secure\ConfigDB (this one I have not actually checked, but I am betting it’s still there)

Scary, isn’t it?

MOSS 2007 An update conflict has occurred, and you must re-try this action

To resolve this issue, clear the file system cache on all servers in the server farm on which the Windows SharePoint Services Timer service is running. To do this, follow these steps:

1. Stop the Timer service. To do this, follow these steps:
   1. Click Start, point to Administrative Tools, and then click Services.
   2. Right-click Windows SharePoint Services Timer, and then click Stop.
   3. Close the Services console.
2. On the computer that is running Microsoft Office SharePoint Server 2007 and on which the Central Administration site is hosted, click Start, click Run, type explorer, and then press ENTER.
3. In Windows Explorer, locate and then double-click the following folder:
   Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\GUID
   Notes
   • The Drive placeholder specifies the letter of the drive on which Windows is installed. By default, Windows is installed on drive C.
   • The GUID placeholder specifies the GUID folder.
   • The Application Data folder may be hidden. To view the hidden folder, follow these steps:
     1. On the Tools menu, click Folder Options.
     2. Click the View tab.
     3. In the Advanced settings list, click Show hidden files and folders under Hidden files and folders, and then click OK.
   • In Windows Server 2008, the configuration cache is in the following location:
     Drive:\ProgramData\Microsoft\SharePoint\Config\GUID
4. Back up the Cache.ini file.
5. Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt. 
   
   Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
6. Double-click the Cache.ini file.
7. On the Edit menu, click Select All.
8. On the Edit menu, click Delete.
9. Type 1, and then click Save on the File menu.
10. On the File menu, click Exit.
11. Start the Timer service. To do this, follow these steps:
    1. Click Start, point to Administrative Tools, and then click Services.
    2. Right-click Windows SharePoint Services Timer, and then click Start.
    3. Close the Services console.
    Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
12.  Make sure that the Cache.ini file has been updated. For example it should no longer be 1 if the cache has been updated.
13. Click Start, point to Programs, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.
14. Click the Operations tab, and then click Timer job status under Global Configuration.
15. In the list of timer jobs, verify that the status of the Config Refresh entry is Succeeded.
16. On the File menu, click Close.

SharePoint Offline and Manual Prerequisite Procedures

Installing the Roles and Features for SharePoint 2013 on Windows Server 2012 Offline with PowerShell

To install the Roles/Features required by SharePoint 2013 on Windows Server 2012 in an offline environment, you need to have access to the Windows Server 2012 installation media.

For the purposes of example, assume you have mounted the Windows Server 2012 installation media (ISO) to the D: drive of the server. Please note that you can also copy the files locally or specify a UNC path where the installation files are stored. You need to specify

Open an elevated PowerShell prompt (i.e. Run as Administrator) and execute the following:

Import-Module ServerManager

Add-WindowsFeature Net-Framework-Features,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-Auth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase,Application-Server,AS-Web-Support,AS-TCP-Port-Sharing,AS-WAS-Support, AS-HTTP-Activation,AS-TCP-Activation,AS-Named-Pipes,AS-Net-Framework,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Scripting,Windows-Identity-Foundation,Server-Media-Foundation,Xps-Viewer –Source D:\sources\sxs


Your server will require a reboot after running this PowerShell code.

Everything is fine, but we had a small problem getting your license.SharePoint 2013 Apps

I was try to Add Apps from SharePoint store, but I am unable to add it. I was getting below error message


“Everything is fine, but we had a small problem getting your license. Please go back to the SharePoint Store to get this app again and you won't be charged for it. "

I am using SharePoint 2013 on my local server. I configure everything correctly I rechecked, but nothing is working for me.



Solution:

I was using system account or farm account. Then I use different account for it, it’s working for me.



The System Account cannot be used to get apps from the app store...

Database is in compatibility range and upgrade is recommended

I had moved the SharePoint content databases from one farm to another recently. After the migration was completed I browsed to Central Adminitration -> Upgrade and Migration -> Review Database Status. The migrated Sharepoint content database had the Status as "Database is in compatibility range and upgrade is recommended".

This indicated I had to manually upgrade these content databases.

This was because I moved the content databases from SharePoint 2010 SP1 to SharePoint 2010 SP2.

This is how it should be solved if I am not wrong:

Test-SPContentDatabase -Name ContentDBName -WebApplication http://webapp/ > c:\result1.txt (to confirm that there are no Upgrade Blocking categories that equal true)

Upgrade-SPContentDatabase -Name ContentDBName (Depending on the size of the database, this process could take long time)

Once completed 100% the database upgrade, browse to Central Administration -> Upgrade and Migration -> Review Database Status. Confirm that the content database now has Status as "No action required".

How to: Change the Distributed Cache Service managed account 2013

When you get the annoying pink marker in CA and one of the issues it warns you about, is that ‘the farm account should not be used for other services’ In my case, the scripted install had set the ‘Distributed Cache Service (Windows Service)’ to use the  farm account as managed account. As the 2013 Central Admin is (or tries to be) helpful, it gives you the direct link to the: ‘Security’ – ‘General Security’ – ‘Configure Service Accounts’ and tells you to change it there.

To fix it, just click the link, find the service in the dropdown and select another Managed account in the lower dropdown. Then click ok…..but nooo…that one wont fly.
Changing the service account on this service cannot be done this way and has to be done using PowerShell…thats what you get back.

Well…after some short researching I found this to work ok: (first load the snapin, add-pssnapin microsoft.sharepoint.powershell)

$farm = Get-SPFarm
$cacheService = $farm.Services | where {$_.Name -eq "AppFabricCachingService"}
$accnt = Get-SPManagedAccount -Identity <domain\user>
$cacheService.ProcessIdentity.CurrentIdentityType = "SpecificUser"
$cacheService.ProcessIdentity.ManagedAccount = $accnt
$cacheService.ProcessIdentity.Update()
$cacheService.ProcessIdentity.Deploy()

(Where <domain\user> is the domain name and user name of the managed account you want to use instead.)

Note: Beware of the doublequotes if you copy the code…

Fix: Cannot use the special principal ‘sa’. Microsoft SQL Server, Error: 15405

When importing a database in your SQL instance you would find yourself with Cannot use the special principal 'sa'. Microsoft SQL Server, Error: 15405 popping out when setting the sa user as the DBO of the database. To fix this,

Open SQL Management Studio and Click New Query. Type:

USE mydatabase
 exec sp_changedbowner 'sa', 'true'

Getting more than 30 Days of SharePoint Usage Report Data

One of the clients that I was working with needed some extensibility to the out of the box SharePoint Usage Reports.

The data displayed on the reports didn’t meet their requirements, first, they needed to match the data with the user data in SAP in order to get the reports by Region and other parameters, and second, they needed historical data, and not only the last 30 days of information.

The first requirement was not a problem, and at the beginning we didn’t think the second would be a problem either, but oh we were wrong.

Using the out of the box usage reports provided by SharePoint was of course not even an option, we needed a way to get the data and create our own reports.

I spent some time doing research and this is what I found:

• Using the Object Model. The SPWeb object contains the method GetUsageData(). This is the method called by the Usage Repor pages in sharePoint. It Returns a table that contains information about the usage of a Web site, based on a time interval. Unfurtunately there are only two options for the time interval, either today or last month. So, no way to get more than 30 days of information using the Object model.
• Web Services. No web service exposes usage report data, so I thought about using owssvr.dll, but again, you can only get the last 30 days of data.

Usage Report data is stored in log files in the IIS and also in the Shared Services database, and not only for the last 30 days, but for all the time since the usage reports were activated, so how is it possible that SharePoint doesn’t have a way to expose this data? Well, that’s how the world works.

Working directly with the SharePoint Databases is not supported by Microsoft, so it seemed that my only option was to create a program to read the IIS files. Have you taken a look at those files? Well, they are quite a mess and I didn’t want to have to do anything with them. So I consulted one of my closest friends: “Reflector”, and once again he gave me the solution I was looking for

I found out that the PortalContext object contains a reference to the Shared Services Database through the property “AnalyticsSqlSession”, using this property you get a connection to the database without having to worry about server name, database name, etc.

Since all the usage data is stored in the Shared Services database this was definitely helpful, but let’s not forget that working directly with the databases is not supported, and although I was not accessing directly the database using SQL server, I was however connecting to it and making some queries (READ ONLY).

We presented our solution to Microsoft, and to our surprise, the solution was accepted because somehow we were using the Object Model to get the data, nice!

Having the solution and Microsoft approval, everything got easier. These are the tables in the database that are related to the usage reports:

As you can see, everything is in there! We can do the queries we want and get the data we are looking for.

Going back to the AnalyticsSqlSession property of the PortalContext object, this is how I got it:

Worked like a charm!

SharePoint 2010: Create new Search Services with Custom DB names Powershell

When you try to create Search services in SharePoint 2010 using the wizard, it gives you nightmare with the Database names with horrible GUIDs...

here is a simple script to ease your life:

## Parameters used

## change the variables below to your own servers and naming conventions



$databaseServerName = "shrpt-db-server"

$searchServerName = "shrpt-apps-server"

$searchSAName = "Search Service Application"

$saAppPoolName = "SharePoint Web Services Default"

$searchDBName = "Search_Services_Application_DB"



## First remove the old search

## This will require an id - namely a guid so get the service guid before doing this



$spapp = Get-SPServiceApplication -Name $searchSAName

Remove-SPServiceApplication $spapp -RemoveData



##START SEARCH

Write-Host "Creating Search Service and Proxy..."

Write-Host "  Starting Services..."

Start-SPEnterpriseSearchServiceInstance $searchServerName

Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $searchServerName



Write-Host "  Creating Search Application..."

$searchApp = New-SPEnterpriseSearchServiceApplication -Name $searchSAName -ApplicationPool $saAppPoolName -DatabaseServer $databaseServerName -DatabaseName $searchDBName

$searchInstance = Get-SPEnterpriseSearchServiceInstance $searchServerName



Write-Host "  Creating Administration Component..."

$searchApp | Get-SPEnterpriseSearchAdministrationComponent | Set-SPEnterpriseSearchAdministrationComponent -SearchServiceInstance $searchInstance



##Crawl



Write-Host "  Creating Crawl Component..."

$InitialCrawlTopology = $searchApp | Get-SPEnterpriseSearchCrawlTopology -Active

$CrawlTopology = $searchApp | New-SPEnterpriseSearchCrawlTopology

$CrawlDatabase = ([array]($searchApp | Get-SPEnterpriseSearchCrawlDatabase))[0]

$CrawlComponent = New-SPEnterpriseSearchCrawlComponent -CrawlTopology $CrawlTopology -CrawlDatabase $CrawlDatabase -SearchServiceInstance $searchInstance

$CrawlTopology | Set-SPEnterpriseSearchCrawlTopology -Active



Write-Host -ForegroundColor white "  Waiting for the old crawl topology to become inactive" -NoNewline

do {write-host -NoNewline .;Start-Sleep 6;} while ($InitialCrawlTopology.State -ne "Inactive")

$InitialCrawlTopology | Remove-SPEnterpriseSearchCrawlTopology -Confirm:$false

Write-Host  



##Query



Write-Host "  Creating Query Component..."

$InitialQueryTopology = $searchApp | Get-SPEnterpriseSearchQueryTopology -Active

$QueryTopology = $searchApp | New-SPEnterpriseSearchQueryTopology -Partitions 1

$IndexPartition= (Get-SPEnterpriseSearchIndexPartition -QueryTopology $QueryTopology)

$QueryComponent = New-SPEnterpriseSearchQuerycomponent -QueryTopology $QueryTopology -IndexPartition $IndexPartition -SearchServiceInstance $searchInstance

$PropertyDatabase = ([array]($searchApp | Get-SPEnterpriseSearchPropertyDatabase))[0]

$IndexPartition | Set-SPEnterpriseSearchIndexPartition -PropertyDatabase $PropertyDatabase

$QueryTopology | Set-SPEnterpriseSearchQueryTopology -Active

## Proxy



Write-Host "  Creating Proxy..."

$searchAppProxy = New-SPEnterpriseSearchServiceApplicationProxy -Name "$searchSAName Proxy" -SearchApplication $searchSAName > $null



#####END SEARCH   

There was a problem retrieving data for this field. Updating values in this field is disabled temporarily. You can still update values in other fields.

While trying to update user profile of a user in SharePoint 2010 I got this error  "There was a problem retrieving data for this field. Updating values in this field is disabled temporarily. You can still update values in other fields.".

The SharePoint farm was using cross-farm services. The "Managed Metadata Web Service" was shared between the farms. This issue can be resolved by enabling "This service application is the default storage location for Keywords." option for the "Managed Metadata Web Service Proxy".

SharePoint Excel Serivces Error

So if you have seen this error:

Excel Services:

We're sorry. We ran into a problem completing your request. Please try that again in a few minutes.

Believe me even if you tried again in few minutes it might not work...

Few suggestions:
Check in central admin if your excel services is running.
Check if you have an Excel Service application in your service applications.

In Central Administration

Go to Application Management

And then in Manage Web Application



I select my web site (Share Point - 80) and then select 'Service Connection'

Finally I Checked Excel Service Application And it work for me.