Could not find the destination item or folder on this server

Could not find the destination item or folder on this server            

Could not find the destination item or folder on this server when using send to other location to copy documents from one web app to other web app. we can send the Docs between different Doc library within the same web app.

Cause: Basically it was a by default stuff by MS. Send to other Locations is works with in different web application if you have the office 2007 client installed on your machine otherwise it will not work.

 MS Article:  http://office.microsoft.com/en-001/sharepoint-server-help/copy-a-file-to-another-library-or-send-to-location-HA101782473.aspx

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

The spelling check cannot be completed because there is no dictionary installed for the current language pack in SharePoint

The spelling check cannot be completed because there is no dictionary installed for the current language pack in SharePoint

             

If you are receiving the following error trying to use the spell check feature in SharePoint 2010 or SharePoint 2013,Ensure the following steps done correctly.

1.   Ensure that the spell checking feature is activated.

Central administration->system settings->manage farm      features(under farm management)

2.   This feature requires that the Users group on the local server has Read permission to the OFFICE14/OFFICE15 folder in your installation path

                    

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

Web.config files in SharePoint

Web.config files in SharePoint

                            

web.config files are contained in the following folders within the file system, I am giving A brief explanation on which web. Config do what as per my experience.

1.    Local Drive:\Inetpub\wwwroot — The web.config file of the top-level content root folder that defines configuration settings for the virtual server of the default Web site in the Windows SharePoint Services deployment. In addition, the content root folder includes a \wpresources folder that contains a web.config file used in Web Part resources.

2.    Local Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\wpresources — A web.config file that is used in Web Part resources for the Global Assembly Cache (GAC).

3.    Local Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12,14 or 15\CONFIG — The web.config file and other .config files that together define configuration settings for extending other virtual servers.

4.    Local Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12,14 or 15\ISAPI — The web. Config file that defines configuration settings for the /_vti_bin virtual directory.

5.    Local Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12,14 or 15\TEMPLATE\LAYOUTS — The web. Config file that defines configuration settings for the /_layouts virtual directory.

6.    Local Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12,14 or 15\TEMPLATE\ADMIN\Locale_ID — The web. Config file that defines configuration settings for pages used in SharePoint Central Administration.

When a virtual server is extended with Windows SharePoint Services, a top-level web. Config file is placed within the content root folder of the extended virtual server, which defines configuration settings for the server such as HTTP handling for Web Parts. Another web. Config file used for Web Part resources is placed in a \wpresources folder within the same content root folder.

Important  The web. Config files in the \wpresources folders should not be modified. The settings of these files disallow pages or items that can be compiled. If these settings are changed, the security state for the compiled code will be very different from the security state for code that runs from the Local Drive:\Inetpub\wwwroot directory.

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

You need to have a machine administrator privileges to run this cmdlet

You need to have a machine administrator privileges to run this cmdlet

                  

Many times, when we run the power shell cmdlet, we get the error in power shell with not good red color ”need to have machine administrator privileges”. Even though we logged into the server with our Admin account and account added in local administrator group of server and has special privileges.

Solution: This is a very know issue, that we get the error when we run the management shell or power shell with our account.

We need to run the power shell with the built-in Administrator. Check the below screen to run.

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

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 !!!!!