Web analytics not logging the reports

Web analytics not logging the reports                         

                   

               

                  

                              

 Issue with the web analytics reports. it is not logging the statistics any more after a period of time. The running time for the Logging Extractor component should always be less than the threshold value. The issue is due to the  running time for the Logging Extractor component exceeds the threshold value. Before applying the below resolution, ensure that the issue is with the threshold only by checking the logs and rest.

Resolution: Add more staging databases for the Web Analytics service to balance the load.

1.   Verify that the user account that is performing this procedure is a member of the Farm Administrators group.

2.   On the Central Administration Home page, in the Application Management section, click Manage service applications.

3.   On the Manage Service Applications page, click the Web Analytics service for which you want to add more staging databases.                                

4.   On the ribbon, in the Operations group, click Properties.      

5.   In the Edit Web Analytics Service Application dialog box, click Next.
                      

6.   In the Edit Web Analytics Service Application Topology dialog box, click New, and then click Staging Database.

              

7.   In the Add New Database dialog box, type the database server name and the staging database name(New DB name), and then click OK.       

                                 

8.   In the Edit Web Analytics Service Application Topology dialog box, click Next.                          

                                   

9.   In the Edit Web Analytics Service Application dialog box, click OK.
                       

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Difference between Document Library and Lists in SharePoint

Difference between Document Library and Lists in SharePoint                

It’s a basic question that arises in mind that, what makes difference between those.

Lists:

1.     Can have attachments

2.     Have major versions only

3.     Do not have Check-in/Check-out features

4.     Upload Document is not available

5.     It store data in table structure

Libraries:

1.     Cannot have attachments (files are directly in the library)

2.     Have both minor (draft) and major (published) versioning

3.     Have Check-in/Check-Out

4.     Publishing Libraries can use Page Layouts

5.     Have Unique Document Ids out of the box

6.     Upload Document is available.

7.     It store document/files

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Cross farm service applications in SharePoint 2013

Cross farm service applications in SharePoint 2013

In SharePoint, we can use some service applications across farms. The below are the service applications that can share across farms. The other service applications apart from below can’t share across farms.

·         Business Data Connectivity

·         Machine Translation

·         Managed Metadata

·         User Profile

·         Search

·         Secure Store

Cross farm Service Applications Integration between two separate SharePoint farms

How to connect Different farms to use the service applications, below is the detailed Explanation from Issa.

http://blogs.technet.com/b/meamcs/archive/2013/09/03/cross-farm-service-applications-integration-between-two-separate-sharepoint-farms.aspx

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Issues Uploading Large Files To SharePoint

Issues Uploading Large Files To SharePoint

Generally, In SharePoint we encounter the below issues while uploading the larger files to SharePoint web site. The issues it could be many reasons. we come to know the Exact issue by checking the Application,ULS or any trace. Here in the below article, I am mentioning the general cause of the issues and the resolutions that Occur In my experience.Follow any below methods as per your issue.

·         "An unexpected error has occurred"

·         "The page cannot be displayed”

·         "An unknown error occurred"

·         "HTTP 404 – Page Not Found”

·        “Request timed Out’

1.Increase the maximum upload size for the web application

 Go to 'Start > All Programs > Administrative Tools > SharePoint Central Administration > Application Management'.

1.     Under SharePoint Web Application Management, click 'Web application general settings’.

2.     On the Web Application General Settings page, choose the appropriate web application.

3.        Under Maximum upload size, type the file size which you want to upload and click on OK. You can specify a maximum file size up to 2,047 megabytes.

                         

                                 

Note:

Any upload size which is below 250 MB is enforced directly through web app settings. Above 250 MB, you need to make a some small change to the web.config file to allow larger uploads. Repeat the steps listed below for all zones for your web app all the servers which host the web application role.

• Open the web.config from
• 'C:\Inetpub\wwwroot\wss\VirtualDirectories\<Virtual Directory>' folder and modify it as follows 

 <httpRuntime maxRequestLength="51200" /> with <httpRuntime      executionTimeout="999999" maxRequestLength="51200" />

• Perform an IISReset and you should be good to go.

2.  Increase the connection time-out setting in IIS

while uploading large files, there are chances that the request will timeout. By default, the IIS connection time-out setting is 120 seconds. Follow these steps to increase the connection time-out setting,

·         Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

·         Right-click the virtual server that you want to configure, and then click Properties.

·         Click the Web Site tab. Under Connections, type the number of seconds that you want in the Connection time-out box,
and then click OK.

              

                                                   

          

                                                

3.  Increase the maximum upload size in the web.config file of web application

In the web.config file of web application which has issues to upload larger files or getting the error the page can’t be displayed. Increase the value of the Upload size.

4.Explorer view or Web client issues

While trying to use the explorer view, you may see the following error

“Error 0x800700DF: The file size exceeds the limit allowed and cannot be saved” message

If this is the case then the issue is most likely caused by a local restriction set on Web Client service. By default, Web Client file size limit is set to around 47 Mb. To increase this limit:

• Click Start, click Run, type regedit, and then click OK.
• In Registry Editor, locate the following registry key
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClientParameters
• Right click on the FileSizeLimitInBytes and then click Modify.
• In the Value data box, click on Decimal, and type 4294967295 and then click OK.
• Quit Registry Editor
• Restart Web Client service from Services.msc

5.Increase the default chunk size for large files

The large-file-chunk-size property sets the amount of data that can be read from server running SQL Server at one time.

• If you have a file that is greater than your chunk size (such as 70 MB when the chunk size is set to 5 MB), the file would be read in 14 chunks (70 / 5).
• The chunk size is not related to the maximum upload file size.
• The chunk size simply specifies the amount of data that can be read from a file at one time. By default, the large-file-chunk-size property is set to 5 MB.
• Check if the 'large-file-chunk-size' property is set or not

    Stsadm -o getproperty -propertyname large-file-chunk-size

• In order to set the large–file–chunk–size property, we need to use the command line. This property is configured for a server or server farm, and cannot be configured for an individual web app server. To set this property, use the following syntax:

   Stsadm.exe –o setproperty –pn large–file–chunk–size –pv <size in bytes>

• After making a change to this property, perform an IISreset /noforce.

6.Add the execution Timeout value  

Increase the execution timeout for the upload page (upload.aspx) to prevent timeouts on the page..

• Navigate to 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS' folder on the SharePoint server.
• Open the 'web.config' file in notepad or any other text editor and add the execution Timeout parameter. For example, replace the value as follows

Existing code

<location path="upload.aspx">

    <system.web>

      <httpRuntime maxRequestLength="2097151" />

    </system.web>

</location>

Replacement code

<location path="upload.aspx">

    <system.web>

      <httpRuntime executionTimeout="999999" maxRequestLength="2097151" />

    </system.web>

</location>

• Open the 'web.config' file from the 'C:\Inetpub\wwwroot\wss\Virtual Directories\<Virtual Directory>'folder and modify it as follows 

  Existing line :  <httpRuntime maxRequestLength="51200" /> 
  Replacement line : <httpRuntime executionTimeout="999999" maxRequestLength="51200" />

  

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Site Collection Admin Can't Delete or modify Site

Site Collection Admin Can't Delete or modify Site

         

The SharePoint farm administrator or site collection administrator can't do any changes in the site still has full permissions.

Issue: The site is locked.

Solution: Go into Central Admin unlock the site.

Application Management->Site Collection Quotas and Locks->Choose the site and then pick Not locked->Click on OK

Environment: MOSS 2007 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

How to create a SharePoint 2010 farm with no GUIDs using Power Shell

1       How to create a SharePoint 2010 farm with no GUIDs using Power Shell

A very detailed and useful article Written by Todd Klindt. If use the PSCONFIG.exe it will create the GUID at the end of databases. To avoid this we can use power shell commands.

http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=241

   2.  removing the GUID out of the AdminContent database in SharePoint 2010

http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=233

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

There was an error opening the document. The file size exceeds the limit allowed and cannot be saved PDF Error

There was an error opening the document. The file size exceeds the limit allowed and cannot be saved PDF Error 

                              

When opening a pdf file from SharePoint, you get an error message and the file will not open. "There was an error opening the document. The file size exceeds the limit allowed and cannot be saved".

Issue: This is caused by a download limit in the registry settings.  It is not related to the file size upload limit set in SharePoint central admin.

Solution: Make a change in the registry settings.
 

·         Go to run and type regedit.

·         Find this path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters

·         Right click on the FileSizeLimitInBytes and click Modify

·         Click on Decimal

·         In the Value data box, type 4294967295, and then click OK. Note this sets the maximum you can download from the WebDAV to 4 gig at one time,

Note: restart your computer if necessary or re-start WEBCLIENT service

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

People Search Not Working SharePoint 2013

People Search Not Working SharePoint 2013                  

               

No people show up in the people search.  You have everything set up correctly for User profiles and search application.

Issue: In my case, it was that the default content access account did not have correct permissions set in the My Site service application.  It was also that I didn't tell the search content sources that there was a My Site. I also added a crawl rule, but I suspect this was overkill and would have worked with the first two steps.

Resolution:

Set the permissions for the search crawler to Retrieve People Data. Go into Application Management -> Manage Service Applications page.  Highlight the User Profile Service Application line.  In the ribbon, click on Administrators.  Add the Default content access account (check what it is on the front page of the Search Administration page) and make sure that Retrieve People Data for Search Crawlers is checked.  Click on OK.

Make sure you type the sharepoint://hostname into the content sources.  This tells the search that this is not just content - it is a My Site service app.  If you don't add it, but just list the URL of the My Site Host, the crawler will crawl the content, but not the profiles.


Create a crawl rule. Go to Search Administration -> Crawl Rules -> Add Crawl Rule. In the Path box, type sharepoint://<hostname>, where <hostname> is the URL for the Web application where you deployed the My Sites site collection.

Do a full crawl.

MS Article: http://technet.microsoft.com/en-us/library/hh582311.aspx  

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Windows Power Shell for SharePoint Command Builder

 Windows Power Shell for SharePoint Command Builder

                

Very useful to get the power shell command easily for SharePoint.

http://www.microsoft.com/resources/technet/en-us/office/media/windowspowershell/windowspowershellcommandbuilder.html

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

The Search request was unable to connect to search service

The Search request was unable to connect to search service

While we try for the search in the site, it comes with the below error,

   sorry something went wrong

   The Search request was unable to connect to search service                    

                        

Solution: The issue is due to the web site that we are searching is not connected with the Search service application. To connect the site with the search application, Follow the below steps.

·        Go to central administration->Application management->manage web applications

·        Select web application which you need search

                 

·        Click on Service connections on Ribbon

·        Check the Search service application is in connection with the website.                 

·        If not then connect the search service application with the website, to do this, check the box of search service application and Ok.                

           

·        Once done, you were able to connect the search service to web site. 

Note: If two sites are created with the Enterprise search template in same farm, This error should occur.

If search service is in stopped state also, this issue could occur    

                                 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help

SharePoint default page not loading by default.aspx

I find that I can't browse SharePoint 80 or SharePoint Central Administration v4 or any sites using the default URL (http://webserver/). I’m trying to do this locally from the actual server SharePoint is running on. It gives a HTTP 404 'Webpage cannot be found' error in IE. If I want to view either of these, I have to specifically type default.aspx manually:

http://webserver/default.aspx to view the SharePoint 80 site
http://webserver:port/default.aspx to view central admin. 

                       

It is the same when using local host instead of web server. I again will have to enter default.aspx to come the pages up.

Here are some things I've tried already but had no luck:

Added http://webserver and other relevant names in Alternate Access Mappings
Ensured Default.aspx is top of the list in 'Default Documents' in IIS7
Checked the hosts file
Set DisableloopbackCheck in registry and restarted.

Solution: I resolve the issue once I run the products and technologies wizard. Once the wizard is successful, All the sites including central admin came up by default without manually typing the default.aspx.

 Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!