SharePoint 2010/2013: Clearing the Configuration Cache

  • Stop the “SharePoint 2010 Timer” service.
  • Delete all the XML files in the config cache. There are loads of XML files that can be found in the folder “C:\ProgramData\Microsoft\SharePoint\Config\”. Note there seems to only ever be one folder under Config which has a GUID. There are other folders which map onto this folder, but this one seems to be on every environment whereas the other locations may be found in different places on some environments. Therefore deleting the files from this folder should work in all environments.
  • Edit the “cache.ini” file in the same folder that contained the XML files, setting the content to “1″ (without the double-quotes). This indicates that all cache settings need to be refreshed. Eventually this value gets automatically updated to another number when the cache is repopulated.
  • Start the “SharePoint 2010 Timer” service.

Did you forget the passphrase in SharePoint 2010 or 2013?

– Log in to the SharePoint server

– Run PowerShell as Administrator

– Type the following command and enter the new passphrase

$passphrase = ConvertTo-SecureString -asPlainText -Force

– Type the following command and confirm the passphrase

Set-SPPassPhrase -PassPhrase $passphrase -Confirm

 

Change SharePoint 2010 / 2013 Managed Account Passwords

– Check the account in Active Directory and make sure “User Cannot Change Password” is unchecked.

– Launch Central Administration

– Click on Security – Configure Managed Account

– Select and edit the Account

– Select “Change Password Now” and enter the new password

– Click OK

– If you get the following message is because the password was already changed in Active Directory

“”””The password does not meet the password policy requirements. Check ….”””””

– Go back to Configure Managed Account – Select and Edit the Account

– Click “Change password now”

– Select “Set account password to new value”

– Enter the new password (The same was set in Active Directory)

– Click OK

 

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

 

The view cannot be displayed because it exceeds the list view threshold (5000 items) enforce by the administrator.

Solution:

– Launch Central Administration
– Go to Manage Application under Application Management
– Select the Web Application
– Click on General Settings – Resource Throttling
– Change the List View Threshold to a higher number. Check the List View Threshold  for Auditors and Administrators as well if you like.

 

Hide View All Site Content and Recycle Bin in Quick Launch

1. Site Settings > Edit Page
2. Add a Content Editor Web Part anywhere in the page.
3. Click on Edit – Modify Shared Web Part.
4. Click on “Source Editor” button and copy and paste the following code.

<style>
.ms-recyclebin {
display:none;
}
</style>
<style>
.ms-quicklaunchheader{
display:none;
}
</style>

5. Click Save
6. Expand Layout section inside toolpane.
7. Check the Hidden checkbox and click OK.

How to resolve 2000 items resolution in SharePoint Business Connectivity Services (BCS)

http://community.dynamics.com/crm/b/marcellotonarelli/archive/2012/06/06/how-to-resolve-2000-items-resolution-in-sharepoint-business-connectivity-services-bcs.aspx#.UeWJG9JOzL8

If you are working with a larger external list (more than 2000 items) in dev environment it works perfectly, but when you work in production environment, it throws some of the following errors and added in SharePoint Logs.

·         Timeout expired. BDC Runtime Object Model has throttled the response. The response from the service took more than ’180000′ milliseconds. The limit can be changed via the “Set-SPBusinessDataCatalogThrottleConfig’ cmdlet.
·         WCF Service Connector has throttled the response. The response from the WCF service contains more than ’3000000′ bytes. The maximum amount of data that can be read through WCF Service Connector is ’3000000′ bytes. The limit can be changed via the ‘Set-SPBusinessDataCatalogThrottleConfig’ cmdlet.
·         Web Service Connector has throttled the response. The response from the web service contains more than ‘3000000’ bytes. The maximum amount of data that can be read through Web Service Connector is ‘3000000’ bytes. The limit can be changed via the ‘Set-SPBusinessDataCatalogThrottleConfig’ cmdlet.
·         Opening of a new connection is throttled. Maximum enabled connections ‘200’ for proxy are already been opened.
·         Database response throttled. Maximum number of rows that can be read through the database system utility is 2000.
This type of error normally occurs when BCS has throttled an external system call for taking too long, or trying to transfer too much data. By default this feature is enabled to prevent Denial of Service attacks that could adversely affect SharePoint or external system health by performing huge transactions. If you have a business need, you may want to increase the limits or disable them entirely, but keep in mind that you increase your farm’s exposure to Denial of Service threats.

To change that limit to a higher value, you need to be Farm Administrator and only can do the required changes using public APIs or PowerShell (SharePoint Designer and Central Administration UI won’t do it).
Normally when you start creating external lists you will notice that out of the box SharePoint limits external lists to 2,000 items, these are generally the first 2,000 items from the external content source. This limit is placed on External Content Types created in SharePoint Designer. The Business Connectivity Service Application has two limits, one for External Content Types created using SharePoint Designer and one for External Content Types created using code (Visual Studio). These limits can be changed using PowerShell as seen in the example below
$bcs = Get-SPServiceApplicationProxy | where{$_.GetType().FullName -eq (‘Microsoft.SharePoint.BusinessData.SharedService.’ + ‘BdcServiceApplicationProxy’)}
$BCSThrottle = Get-SPBusinessDataCatalogThrottleConfig -Scope database -ThrottleType items -ServiceApplicationProxy $bcs
$BCSThrottle
This will output the current limits. By default 2,000 with a maximum of 1,000,000 items if usingVisual Studio. You can change the default values using the commands below. In this example we have increase the default limit to 20,000 items
Set-SPBusinessDataCatalogThrottleConfig -Identity $BCSThrottle -Maximum 1000000 -Default 20000
You now need to get the BCS Throttle Config data again
$BCSThrottle = Get-SPBusinessDataCatalogThrottleConfig -Scope database -ThrottleType items -ServiceApplicationProxy $bcs
Now run the command below to check your new limit.
$BCSThrottle

Scope        : Database
ThrottleType : Items
Enforced     : True
Default      : 20000
Max          : 1000000

This will increase the amount of items that can be retrieved in the browser, however there will still be a limit on the amount of items that can be taken offline using Outlook or SharePoint Workspace. This limit is still going to be 2,000 items. Unfortunately this has to be changed on each client by making a change to the registry. (thanks for Shane Young for blogging about thishttp://msmvps.com/blogs/shane/archive/2010/10/19/bcs-and-sharepoint-workspaces-limited-to-2000-items-from-external-list.aspx )
Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\
Create a new “Key Business Data” with another sub-key “Synchronization”  (remove the quotes of course) Now create a new Dword called “Query Instances Limit” set the decimal value to the number of items you want a user to be able to take offline. This is up to 30,000 with SharePoint Workspace.
Hope this was helpful! Stay tuned for more learning posts on BCS and External Lists.

Configuring an Account for Unattended Report Processing

You can configure a special account to use for unattended report processing (that is, to support subscriptions, scheduled report history generation, and scheduled updates to a report execution snapshot). This account is used for special-case reports that do not use credentials, which is an uncommon scenario for most reports.

To specify the account, use the -e argument of rsconfig. Specifying the -e argument for rsconfig directs the utility to write the account information to the configuration file. You do not need to specify a path to rsreportserver.config. Follow these steps to configure the account.

  1. Create a domain account that has access only to computers and servers that provide data or services to a report server.
  2. Open a command prompt: On the Start menu, click Run, type cmd in the text box, and then click OK.
  3. Type the following command to configure the account:rsconfig –e –m<computername> –s<sqlservername> –u<domain/username> –p<password>

http://msdn.microsoft.com/en-us/library/aa972235(v=sql.80).aspx

 

Reporting Services 2008 – The report server installation is not initialized

If you get an error similar to the one below when trying to setup the report server.

The application domain WindowsService_1 failed to initialize. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedException: The report server installation is not initialized. at Microsoft.ReportingServices.Library.ConnectionManager.b_2() at Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.<>c_DisplayClass1.b__0(Object state) at System.Security.SecurityContext.Run(SecurityContext securityContext, ContextCallback callback, Object state) at Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.Run(ContextBody callback) at Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey() at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage() at Microsoft.ReportingServices.Library.ServiceController.ServiceStartThread(Object firstStart).

Then try deleting the Encryption Keys by following the steps below:

– Click on Start – All Programs – Microsoft SQL Server 2008 R2 – Configuration Tools – Reporting Services Configuration Manager
– Click on Connect
– Click on Encryption Keys
– Click on Delete

Check the article below to find more information about deleting / re-creating the encryption keys
http://msdn.microsoft.com/en-us/library/ms156010.aspx