Showing posts with label SharePoint 2013 issue. Show all posts
Showing posts with label SharePoint 2013 issue. Show all posts

Thursday, May 23, 2013

Error exporting the list named “Announcements” at the URL: Lists/Announcements while saving site as template in SharePoint

One of my client having a requirement that to create sub sites programmatically using SharePoint site template location in solution gallery. We need to create a site with some lists and libraries and save it as site template by navigating to site settings and clicking on save site as template link. By doing this I got an error saying that,
Error exporting the list named “Announcements” at the URL: Lists/Announcements

Tried to rename the list, but got the same error with another list. By Checking the logs I have found the error message below,
SPSolutionExporter: System.NullReferenceException: Object reference not set to an instance of an object.

After some troubleshooting on the issue, I have found that few of custom content types not set to defaults in site and site collection level.

To fix this issue run the following power shell commands to disable and enable the content type feature.

Disable-SPFeature –Identity ctypes –url “Site Collection URL

Enable-SPFeature –Identity ctypes –url “Site Collection URL

After running this power shell commands there is no change in content types. Now we can save the site template with out any issues.

Monday, May 13, 2013

SharePoint 2013 Excel Services: We don’t know what happened. But something went wrong

While working with SharePoint 2013, checking the audit log reports in excel got the error as shown below. I have already configured the excel service as shown in the msdn

Checked the event logs, shows the error below.
Unable to access the workbook cache “C:\Windows\TEMP\Excel Server\FileCache\d8746073-d542-5f43-9b0d-45d345fd9f43\Workbooks. Excel Services Application unable to function without a workbook cache.

 After some troubleshoot found that the root problem is that to create or access the workbook. This is a permission issue. As a managed account, the Excel Services application pool is a member of WSS_WPG security group, to execute the permissions on the Temp folder.

To fix the issue I have followed the steps below,

Start -> run -> enter “%WINDIR%\Temp folder.

Click on properties, select security tab, click on Edit button

Add Modify permissions to WSS_WPG group and do IISRESET.

Now everything will work as expected.

Here we can grant permissions to each and every application pool. Here I just granted the permissions to the WSS_WPG group in other managed accounts need to create temporary cache files.


Thursday, May 9, 2013

SharePoint 2013-"The blob cache is not enabled in this web application. Image renditions will not be generated until the blob cache is enabled. For information on turning on the blob cache, please review the product documentation."

Image Rendition is new feature in SharePoint 2013, those users can re size the images to a fix predefined position to use them in web parts or pages. So that it can help us to improve the user experience of site by changing the image sizes. Using Image renditions we can save the image in different number of scaled variations. Dynamic rendering of the image will effect on the performance of the site. We can fix this by using image rendition.
We have to enable BLOB cache for image rendition. We can check Image rendition in Site Settings -> Image rendition in “Look and Feel” group.

 An Error message will be shown on the top of the page saying that “The blob cache is not enabled in this web application. Image renditions will not be generated until the blob cache is enabled. For information on turning on the blob cache, please review the product documentation”, if we are not enabled the blob cache.

Blob cache is a disk based caching feature. It will eliminate the database round trips in SharePoint. It will load the data from DB and saves on the web client and serves from cache. Generally Blob cache objects are images, Audio or Video files.
To enable Blob cache, Go to IISManger (Run -> inetmgr)

Go to site that need to enable Blob cache. Explore the site, find the web.config file.

Search for “BlobCache”, go to end of the line and make “enabled” value from “false” to “true” 


To use image rendition, publishing feature must be activated in the site.

Monday, May 6, 2013

“We’re having a problem opening this location in File Explorer, Add this web site to your Trusted sites list and try again” error while uploading multiple documents in SharePoint 2013

In SharePoint 2013 document library, to upload multiple documents , we need to select upload button on the top ribbon and click on the link “Upload Files using Windows Explorer Instead” in Add a document popup.




By clicking on the link, popup window has shown with error message “We’re having a problem opening this location in file explorer , Add this web site to your Trusted sites list and try again” as shown below.


I have added the site in IE trusted sites (Internet Options -> Security ->Trusted sites), But still iam getting the same error.
After goggling some time I have found that we need to enable the “Web client” service in windows services.
Go to Run, Type “services.msc”, press Enter


Check WebClient service, Right click on it, select Start.


If you not able to find web client service in services, need to add “Desktop Experience” feature in “User Interface and Infrastructure”.























After starting the “WebClient” service, refresh the browser and click on the link “Upload Files using Windows Explorer Instead”. Now it will open folder associated to Document library.


Monday, April 29, 2013

"The Content has expired and can no longer be used" error in share point 2013

While accessing a SharePoint site, I got an error “The Content has expired and can no longer be used” as shown below.

I have check the error in log files, it has been logged as,

System.Runtime.InteropServices.COMException: The context has expired and can no longer be used. (Exception from HRESULT: 0×80090317), StackTrace:
 at Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity(SPSite site, String name, Boolean bNotGlobalAdminCode, String strUrl, Boolean bNotAddToContext, Byte[] UserToken, SPAppPrincipalToken appPrincipalToken, String userName, Boolean bIgnoreTokenTimeout, Boolean bAsAnonymous)
 at Microsoft.SharePoint.SPSite.get_Request()

The basic cause for this error, the clock settings for SharePoint is not sync with the clock settings for server. To fix this go to Central Administration -> Application Management -> select Web application -> on the ribbon General settings tab -> select General settings -> update the time zone with the share point server as shown below.



Disable/ Increase the “Web page Security validation” in general settings for SharePoint web application. Central Administration -> Application Management -> Manage Web Application -> Select Web application -> on the ribbon select “General settings” -> Off the Security validation/Increase security validation expire time as shown below. Disabling the "Web Page Security Validation" will not be preferred option. 




Wednesday, April 24, 2013

"there are no addresses available for this application" error in SharePoint managed metadata service

In SharePoint 2013, After Configuring the managed metadata service app in SharePoint 2013, when click on “Properties” on the top ribbon for managed metadata service app, it is showing a popup box with the message “there are no addresses available for this application” as shown below.



For Managed metadata service app properties, it is showing the error message “The managed Metadata Service or Connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started. Please Contact your Administrator”.



In the error message itself SharePoint providing the solution. I was checked the Managed Metadata service (Central Administration -> manage Services on server -> Managed metadata service). It was stopped. Started the service.



Check the application pools in IISManager, started the Application pools in IISManager.



If still getting the same issue, just do IISRESET.  
Finally managed metadata service is working like charm.