SpotFire SharePoint Connector – error web player

We are having an issue with authentication when using the Spotfire SharePoint Connector.  This feature has been added to our Spotfire 6.5 environment and allows direct access between SharePoint and Spotfire. Firstly, to create Spotfire reports using SharePoint lists and also allows for reports built on Excel spreadsheets stored in SharePoint to be viewable using the Spotfire Web player (provided the Spotfire Admin  account has Power User access to the SharePoint site/library where the content is located).  By default reports built using .xlsx in SharePoint do not display in the Web Player due to an authentication issue.

We have solved the problem with the web player not working for some Spotfire reports based on .xlsx documents stored in SharePoint (using the SharePoint Connector in 6.5).  The Spotfire Admin account needs to have access to the site that stores the .xlsx and for some reason this wasn’t working when the access was granted via a SharePoint permission group – access needed to be granted directly to the site.  See below:


When the account was in the BI Power User group reports based on content in this site were not working in the web player.  Changing to the above the reports are working in the web player.

Note in these two cases I have granted the account Read access.  If Spotfire analyses are configured to connect directly to a list and include update functionality Spotfire Admin will require Contribute access.

tags: SpotFire SharePoint Connector – error web player,

The excel workbook shows error

The excel workbook shows error on my clients intranet homepage which is a excel web access webpart. Which checking the backend file and opening it with excel services has same error but when opened in excel it open fine.

Error: ” An Error has occurred. Please try again.

Investigations: The previous night there has been a power outage to the data center and next morning this is not working.

When the same file is renamed and saved again it works fine with excel web app so it could be something related to cache on the sever.

Then the eventlog on one of the frontend shows this error in application


 Error: Unable to create or access workbook cache at C:WINDOWSTEMPExcel ServerFileCacheSharedServices1-1078443246Ranges. Excel Services is unable to function without a workbook cache


Bang on !!! when verified the “ranges” folder is missing on one of the WFE and the same excel url is tested on other WFE’s  which also displays error. I suppose the cache for each excel file using excel service is stored only on one server irrespective of which WFE this file is served.

Restore the folders in the path of the cache resolved the issue:

C:WINDOWSTEMPExcel ServerFileCacheSharedServices1-1078443246

This path has the following folders “Images”, “Ranges”, “SavedWorkbooks”, “Workbooks”

In case if that is also not working for you, you could remove the whole directory “Excel Server” in windowstemp folder and make sure the excel service application pool account has access to recreated folder at that path and restart the IIS should create the folder back again and rebuilt the cache as necessary.

More Detailed description and resoulution at:

Removing a Corrupted Site Column in SharePoint 2010

Errors like correlation Id:

System.ArgumentException: Invalid field name: {GUID} [URL of list]  (ULS log)

 “Field type xxx is not installed properly. Go to the list settings page to delete this field.”

To determine what field is causing the error run this PowerShell script.  The PowerShell should terminate with an error, along with the name of the erroneous field.

$web = Get-SPWeb http://portal/site

$fields = $web.Fields

foreach ($field in $fields} {write-host $}

First you will need to determine the GUID ID for the corrupted column.  To do this you will run a PS script against the Site Collection to generate a report that lists all the fields, like so.

$web = Get-SPWeb http://portal/site

$web.AvailableFields.SchemaXml | Out-File c:tempfields.txt

Once done open up the fields.txt file and do a search for the corrupted column.

After determining the field name for the {GUID} I was then able to identify the problem column or content type. In my case the issue was with a column name “TypeTaxHTField0″ or simply Type. SharePoint by default appends the TaxHTField0 suffix to the end of all the static names.

Now that I have the Field Name Column, I needed a way to get into the lists settings to either delete or remove this column from the list. Since I was unable to access the list because of the correlation id, I had to determine the {GUID} of the list.

The way to get the {GUID} of the list I turned to PowerShell.

Below is the script I used to get the {GUID} of the list.

$site = Get-SPSite {URL OF YOUR SITE}

$web = $site.OpenWeb(“SUBSITE”)

$web.lists | Format-Table title,id



Once I got the {GUID} of the list I was then able to browse to the library settings by appending the {GUID} to the end of the list settings edit URL


http://URL OF SITE/SUBSITE/_layouts/listedit.aspx?List={GUID}

Once inside the list settings I was then able to make the necessary changes. For me all I needed to do was remove the “Type” column from the Metadata Navigation Settings by removing it from both “Configure Navigation Hierarchies” and “Configure Key Filters”

Once I removed the “Type” column from the Metadata Navigation I then deleted the “Type” column from my list and then re-added it. Once I re-added it back into the list, I then re-added it back into the Metadata Navigation. Ater doing so I was able to access the list without error. If you find you do not need that column at all, simply delete it from your list.

Another way to get the field name from “SharePoint Manager” (a tool can be found in ) Run this tool on a SP server and navigate to subsite and fields to get more richer information using object model.

Hopefully this helps others who encounter the same issues.

list view filters displaying few records

If you have a list with more than 5000 items and if the item threshold limit is 5000, even after using filter you may see it displays:

“This view cannot be displayed because it exceeds the list view threshold (5000 items) enforced by the administrator.”

“Displaying only the newest results below. To view all results, narrow your query by adding a filter.”

For a view to quickly filter through a large number of items, the first column that you specify in the filter must be indexed. Other columns you specify in the view filter may or may not be indexed, but the view does not use those indexes. You also need to make sure that the first column of the filter does not return more items than the List View Threshold, even if the final result of the filtered view returns less than the List View Threshold.

If the first column of the filter returns more items than the List View Threshold, you can use a filter with two or more columns. When you define a filtered view that uses two or more columns, using an AND operator will usually limit the total number of items returned. But even in this case, you still need to specify as the first column in the filter the column that most likely returns the lesser amount of data. Note that using an OR filter almost always increases the number of items returned and won’t be effective under these circumstances.

So sometimes if easy to switch the filters like if you would like to filter location and them by date range try switching the filters use date range first so that the filter results are less than threshold value and then use your other filters.

As we spoke how to create a index on a column:

1.Navigate to the site that contains the list or library.
2.Click its name on the Quick Launch, or click on the Settings menu , click View All Site Content, and then click the name.
3.Click List or Library > List Settings or Library Settings.
4.Under the Columns section, click Indexed columns.
5.On the Indexed Columns page, click Create a new index.
6.Do one of the following: To create a simple index:
1.In the Primary Column section, under Primary column for this index, select the column.
2.Click Create. To create a compound index:
3.In the Primary Column section, under Primary column for this index, select the column.
4.In the Secondary Column section, under Secondary column for this index, select a different column.
5.Click Create.

Office Web Apps Powershell Cmdlets

Import the module:

Import-Module -Name OfficeWebApps


Returns details about the OfficeWebAppsFarm object that the current server is a member of.


Returns the list of host domains that are on the Allow List for an Office Web Apps Server farm.


Returns details about the current server that is in an Office Web Apps Server farm.


Creates a new Office Web Apps Server farm on the local computer.


Adds a host domain to the Allow List for an Office Web Apps Server farm.


Adds the current server to an existing Office Web Apps Server farm.


Removes a host domain from the Allow List for an Office Web Apps Server farm.


Removes the current server from the Office Web Apps Server farm.


Removes all servers flagged as unhealthy from an Office Web Apps Server farm.


Configures the settings of an existing Office Web Apps Server farm.


Changes the settings of the current server that is in an Office Web Apps Server farm.

SharePoint Patching


SharePoint patching constitute of three types, Service Packs, Cumulative updates and hotfixes. Patching is considered a B2B (build to build) upgrade.

Service Packs

Generally service packs are not a set schedule but they are around 18 to 24 months. They fix all the bugs that have identified since the last service pack or RTM. Sometimes service packs introduce new features and functionality. These are thoroughly tested before release and it should immediately be tested in a test environment. Once tested for feature and functionality in test/non-prod environment they should be released to production at the earliest as service packs are dramatically affect performance and security.

Cumulative updates

Cumulative updates are normally released in every other even numbered month and they are attempt to fix bugs identified in those months plus they include fixes for all the previously fixed bugs as well. The size of these CU’s grows as they are being released. Unless if any current affected issues are resolved in production environment they are not generally necessary to install. Sometimes these Cu’s can break things if they don’t work properly. Patches cannot be uninstall and you will be helpless and wait till the next CU is released. Test the fix the CU is providing thoroughly in test farm and wait for a couple of weeks for any regression before updating to production.


Hotfix or a security patch. These are generally pushed through windows update. These attempt to fix any urgent security issues in SharePoint and are release as early as possible and could be the lease tested of all the patches. Install and run configuration wizard to complete the process. Fingers crossed and prey they should not break any other functionality.

SharePoint infamous direct URL’s

Force Page Edit Mode in SharePoint: http://host/sitecollection/page.aspx?ToolPaneView=2&pagemode=edit
Sign in as Different User:  http://host/sitecollection/_layouts/closeConnection.aspx?loginasanotheruser=true
Important: This option uses an unsupported browser feature which is unreliable and causes other issues. Currently this option does not work in IE 10 and Safari.
Web Part Maintenance Page:  HTTP://host/sitecollection/page.aspx ?contents=1
Show Page in Dialog View: HTTP://host/sitecollection/page.aspx?isdlg=1
Site Features: _layouts/ManageFeatures.aspx
SiteCollection Features: _layouts/ManageFeatures.aspx?Scope=Site
(the query string parameter is case sensitive. “Scope=site” throws an error)
Get the version of the SharePoint server (Patch level): /_vti_pvt/Service.cnf
Application page for registering SharePoint apps: /_layouts/15/appregnew.aspx
Save Site as a template:  /_layouts/savetmpl.aspx
Sign in as a different user: /_layouts/closeConnection.aspx?loginasanotheruser=true
Enable SharePoint designer:  /_layouts/SharePointDesignerSettings.aspx
Welcome Page (Default page settings): /_layouts/AreaWelcomePage.aspx
Change Site Master Page:  /_layouts/ChangeSiteMasterPage.aspx
Page Layouts and Site Templates: /_Layouts/AreaTemplateSettings.aspx
Master Pages library: /_catalogs/masterpage/Forms/AllItems.aspx
User Information List: _catalogs/users/simple.aspx
Quick Deploy List: Quick%20Deploy%20Items/AllItems.aspx
Open Page in Edit Mode:  ?ToolPaneView=2
Taxonomy Hidden List (MMS): Lists/TaxonomyHiddenList/AllItems.aspx
User Information List:  _catalogs/users/simple.aspx
Force displaying the user profile in the site collection:  /_layouts/userdisp.aspx?id={UserID}&Force=True
Note: Some URL’s I have not tested though.

Windows PowerShell script for AD DS Deployment

# Windows PowerShell script for AD DS Deployment

Import-Module ADDSDeployment
Install-ADDSForest `
-CreateDnsDelegation:$false `
-DatabasePath “C:WindowsNTDS” `
-DomainMode “Win2012R2” `
-DomainName “” `
-DomainNetbiosName “CONTOSO” `
-ForestMode “Win2012R2” `
-InstallDns:$true `
-LogPath “C:WindowsNTDS” `
-NoRebootOnCompletion:$false `
-SysvolPath “C:WindowsSYSVOL” `

SharePoint 2013 – Configure Access services On-Premise Installation

Hello Folks, I found the following documents and articles very helpful in setting up Access Services on SP 2013 On-Premise Installation



Between, We need to configure “apps for SharePoint” for Access service to work. Below are the some helpful links:


Hope this helps..:)

Flush BLOB cache in SharePoint

To flush the BLOB cache from web application

  1. Open a SharePoint Management Shell or ISE
  2. Copy the following code and paste it into a text editor, such as Notepad
  3. $webApp = Get-SPWebApplication "<WebApplicationURL>"
    Write-Host "Flushed the BLOB cache for:" $webApp
  4. Replace <WebApplicationURL> with the URL of the Web application whose BLOB cache you want to clear.
  5. Save the file, and name it FlushBLOBCache.ps1.


To flush the BLOB cache from ALL web application

           $wa = get-spwebapplicaton
           foreach($wapp in $wa)
            Write-Host "Flushed the BLOB cache for:" $wapp