Monday, February 3, 2014

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

Sunday, February 2, 2014

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

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

Tuesday, January 28, 2014

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

Monday, January 27, 2014

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

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

Importing a site, list, or document library in SharePoint 2013

Importing a site, list, or document library in SharePoint 2013


You can use Windows Power Shell to manually import a site, list, or document library

To import a site, list or document library by using Windows Power Shell

On the Start menu, click All Programs, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Management Shell.


At the Power Shell command prompt, type the following command:

Import-SPWeb -Identity  <SiteURL>  -Path <ExportFileName>  [-Force] [-NoFileCompression] [-Verbose]

Where:
  • <SiteURL> is the URL for the site that you are importing to.
  • <ExportFileName> is the name of the file that you are exporting.


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

To export a site, list, or document library in SharePoint 2013

To export a site, list, or document library in SharePoint 2013



You can use power shell or Central Administration to export a site, list, or document library. You can only export one site, list, or document library at a time.


Using power shell:

At  Power Shell command prompt, type the following command:

Export-SPWeb -Identity <SiteURL> -Path <Path and File Name> [-ItemUrl <URL of Site, List, or Library>] [-IncludeUserSecurity] [-IncludeVersions] [-NoFileCompression] [-GradualDelete] [-Verbose]

Where:

<SiteURL> is URL for the site, list, or library that you are exporting.
<Path and FileName> is path and name for the site, list, or library that you are exporting.
<URL of Site, List, or Library> is the URL for the site, list, or library where you are exporting.


To export a site, list, or document library by using Central Administration

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

2.   Start SharePoint 2013 Central Administration.
For Windows Server 2008 R2:
§  Click Start, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Central Administration.
For Windows Server 2012:
§  On the Start screen, click SharePoint 2013 Central Administration.
If SharePoint 2013 Central Administration is not on the Start screen:
§  Right-click Computer, click All apps, and then click SharePoint 2013 Central Administration.

3.   In Central Administration, on the home page, click Backup and Restore.

4.   On the Backup and Restore page, in the Granular Backup section, click Export a site or list.

5.   On the Site or List Export page, in the Site Collection section, select the site collection from the Site Collection list, and then select the site from the Site list.

6.   If you are exporting a site, skip this step, Select the list or document library from the List list.

7.   In the File Location section, in the Filename box, type the UNC path of the shared folder and the file to which you want to export the list or document library. The file name must use the .cmp extension.

8.   If the file already exists and you want to use this file, select the Overwrite existing files check box. Otherwise, specify a different file name.

9.   If you want to export all the security and permissions settings with the list or library, in the Export Full Security section, select the Export full security check box.

10.               If you want to specify which version of the list or library to export, select one of the following versions from the Export versions list:
·        All Versions
·        Last Major
·        Current Version
·        Last Major and Last Minor

11.               When you have specified the settings that you want, click Start Export.

12.               You can view the status of all backup jobs at the top of the Granular Backup Job Status page. You can view the status of the current backup job in theContent Export section of the page. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.



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

Monday, January 20, 2014

Windows Power Shell Remoting in SharePoint 2010

Windows Power Shell Remoting in SharePoint 2010
                     

A very detailed article, how to configure and administer the power shell to another machine remotely.

SharePoint 2013 commands must be run on a SharePoint 2013 server.
The commands cannot be run from a client. Power Shell 3 does provide a remoting capability whereby commands can be executed from a client to run on the server. This is a Power Shell function and not specific to SharePoint 2013, and many of the SharePoint 2013 cmdlets will not function through this remoting interface.


http://blogs.msdn.com/b/opal/archive/2010/03/07/sharepoint-2010-with-windows-powershell-remoting-step-by-step.aspx

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

Thursday, January 16, 2014

Configuring the Excel Services Service Application in SharePoint 2013

Configuring the Excel Services Service Application in SharePoint 2013

The following steps describe how to create the Excel Services service application

1.    Log onto your SharePoint box as the Farm account.
2.    Open SharePoint Central Administration, and then select Manage service applications under the Application Management heading.
3.    From the Manage service applications screen, click the New button in the Ribbon. From the menu, select Excel Services Application.
                  

4.    For Name, enter Excel Services.
              

5.    Scroll down to Application Pool and select “Use existing application pool.”
6.    From the drop-down, select Default SharePoint Service App Pool.
7.    Leave the default of “Add this service application’s proxy to the farm’s default proxy list.”
8.    Click OK at the bottom of the page.

 To start the service application

10. From the left-hand menu, click Application Management.
11. Under the Service Applications section, click “Manage services on server.”
12. Find Excel Calculation Services and click Start to the right of it.
               
    
13. The Excel Services service application is now up and running, configured for SharePoint Users
14. should now be able to upload basic workbooks and view them inside of SharePoint.

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

Wednesday, January 15, 2014

create a new Farm Administrator via Power Shell

create a new Farm Administrator via Power Shell

Copy the below script and paste in noted pad as .PS1

Add-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue
# Creates a new Farm Administrator
$newFarmAdministrator = Read-Host -Prompt 'Please provide the name of the new Farm Administrator in the form of DOMAIN\Username'
$caWebApp = Get-SPWebApplication -IncludeCentralAdministration | where-object {$_.DisplayName -eq "SharePoint Central Administration v4"}
$caSite = $caWebApp.Sites[0]
$caWeb = $caSite.RootWeb

$farmAdministrators = $caWeb.SiteGroups["Farm Administrators"]
$farmAdministrators.AddUser($newFarmAdministrator, "", $newFarmAdministrator, "Configured via PowerShell")

$caWeb.Dispose()
$caSite.Dispose()

$caDB = Get-SPContentDatabase -WebApplication $caWebApp
Add-SPShellAdmin -Database $caDB -Username $newFarmAdministrator



Once copied as .PS1 run the script.


Note: The user must exist in AD before run the script.

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

Vulnerabilities in Microsoft Word and Office web apps could allow remote code execution MS14-001

Vulnerabilities in Microsoft Word and Office web apps could allow remote code execution MS14-001: January 14, 2014

Link: http://technet.microsoft.com/en-us/security/bulletin/MS14-001

Known issues and additional information about this security update

The following articles contain additional information about this security update as it relates to individual product versions. The articles may contain known issue information. If this is the case, the known issue is listed below each article link.
·         2827224 MS14-001: Description of the security update for Word 2013: January 14, 2014

·         2837577 MS14-001: Description of the security update for Word Automation Services in SharePoint Server 2010: January 14, 2014

Note: After you install this security update on all SharePoint servers and SharePoint services, you have to run the PSconfig tool to complete the installation.

·         2837596 MS14-001: Description of the security update for Word Web App: January 14, 2014

·         2837615 MS14-001: Description of the security update for Office Compatibility Pack: January 14, 2014

·         2837617 MS14-001: Description of the security update for Word 2007: January 14, 2014

·         2837625 MS14-001: Description of the security update for Word Automation Services in Microsoft SharePoint Server 2013: January 14, 2014

Note After you install this security update on all SharePoint servers and SharePoint services, you have to run the PSconfig tool to complete the installation.

·         2863834 MS14-001: Description of the security update for Word 2013 primary interop assembly (PIA): January 14, 2014

·         2863866 MS14-001: Description of the security update for Word 2003: January 14, 2014

·         2863867 MS14-001: Description of the security update for Microsoft Word Viewer: January 14, 2014

·         2863879 MS14-001: Description of the security update for Office Web Apps Server 2013: January 14, 2014


·         2863901 MS14-001: Description of the security update for Microsoft Office 2010: January 14, 2014

·         2863902 MS14-001: Description of the security update for Word 2010 Service Pack 1 and Service Pack 2: January 14, 2014

ShareThis

X