Add, Deploy, and Activate the SharePoint Solution Files using PowerShell

To install the solution files for AgilePoint BPMS using the PowerShell command line tool, do the following.

Prerequisites

• This topic is required for manual SharePoint Integration installation only. If you installed SharePoint Integration automatically, you can skip this topic.
• PowerShell is installed on the appropriate SharePoint machines.
• Log on to the SharePoint machine using a user account that belongs to the local system's Administrators group.

Navigation

1. Open the PowerShell command line tool.
   For SharePoint 2013, the default location is Start > Microsoft SharePoint 2013 Products > SharePoint 2013 Management Shell.

Instructions

1. On the primary SharePoint front-end web server, in the PowerShell command line tool, add the solution files to SharePoint.

   Add-SPSolution "[AgilePoint SharePoint Integration installation folder]\Ascentn.SharePoint.SettingsList.wsp"
   Add-SPSolution "[AgilePoint SharePoint Integration installation folder]\Ascentn.SharePoint.WebParts.wsp"
   Add-SPSolution "[AgilePoint SharePoint Integration installation folder]\Ascentn.SharePoint.WFIntegration.wsp"
   Add-SPSolution "[AgilePoint SharePoint Integration installation folder]\Ascentn.SharePoint.ListForm.wsp"

    
2. Example Path: C:\Program Files\AgilePoint\AgilePoint Integration for SharePoint
   This copies the wsp files from the installation folder (The default location is [AgilePoint installation folder]\AgilePoint Integration for SharePoint.), and adds them to SharePoint's Central Administration repository. You can specify a different path in the command.
3. On the primary SharePoint front-end web server in the PowerShell command line tool, deploy the solution files to SharePoint.
   Note: The command -CompatibilityLevel All applies only to SharePoint 2013 and later. Omit this command if you are using an earlier version of SharePoint.
   SharePoint Integration for AgilePoint:

   Install-SPSolution -WebApplication "[Site Collection URL]" -GACDeployment 
           -FullTrustBinDeployment -Identity Ascentn.SharePoint.SettingsList.wsp 
           -CompatibilityLevel All
   Install-SPSolution –WebApplication "[Site Collection URL]" -GACDeployment 
           -FullTrustBinDeployment -Identity Ascentn.SharePoint.WebParts.wsp 
           -CompatibilityLevel All
   Install-SPSolution –WebApplication "[Site Collection URL]" -GACDeployment 
           -FullTrustBinDeployment -Identity Ascentn.SharePoint.WFIntegration.wsp 
           -CompatibilityLevel All
   Install-SPSolution –WebApplication "[Site Collection URL]" -GACDeployment 
           -FullTrustBinDeployment -Identity Ascentn.SharePoint.ListForm.wsp 
           -CompatibilityLevel All

   Site Collection URL Example: http://mysharepoint:8080/sites/mysite
4. On each SharePoint machine that is a front-end web server, in the PowerShell command line tool, execute the following command:

   Install-SPApplicationContent

5. On the primary SharePoint front-end web server, , in the PowerShell command line tool, activate the features.

   Enable-SPFeature -Url "[Site Collection URL]" -Identity AgilePointSettingsListFeature
   Enable-SPFeature -Url "[Site Collection URL]" -Identity AgilePointWebParts
   Enable-SPFeature -Url "[Site Collection URL]" -Identity AgilePointWFIntegration
   Enable-SPFeature -Url "[Site Collection URL]" -Identity AgilePointListForm

   Site Collection URL Example: http://mysharepoint:8080/sites/mysite

Add site collection administrator error in SharePoint 2013?

Using STSADM.exe

stsadm.exe -o siteowner -url <url> [-ownerlogin <DOMAIN\name>] [-secondarylogin <DOMAIN\name>]

Using power shell

Set-SPSite -Identity "<SiteCollection>" -SecondaryOwnerAlias "<User>"

The specified database has an incorrect collation. Rebuild the database with the Latin1_General_CI_AS_KS_WS collation or create a new database

The specified database has an incorrect collation. Rebuild the database with the Latin1_General_CI_AS_KS_WS collation or create a new database

Problem:

 I have faced this error when I created a DB in the SQL server and then tried to create the Search Server DB name in the Search Server Configuration Page while configuring the Microsoft Search Server Express 2008.

Solution:

1. The problem is the database created has incorrect collation.

2. We have to change the collation to Latin1_General_CI_AS_KS_WS collation which is specified while configuring the web applications or search server DB in SharePoint.

3.  Connect to the SQL server -> Select the Database created.

4. Right Click on the Database -> Properties -> Select Options page -> Change the collation as shown below:

 

5. Now try to configure the Search or Web Application in SharePoint, it will work as expected.

SharePoint 2013: Setting up User Profile Synchronization (1/2)

Open SharePoint 2013 Central Administration site, and then click Manage Service Applications section, click Configure Syncronization Connections under User Profile Service .
Please note that only one user profile has been imported to SharePoint 2013.

For importing new profiles to SharePoint you have to create a new connection to, in the most times, Active Directory.
So, please click on “Create New Connection”

But you will receive an error that says “Cannot navigate to the requested page because the service is not running”.
This means, that you have to start the service under “Services on Server”.

You have to fill the password. BUT be aware the user needs “Replicating domain changes”. This is a requirement because without this, you can’t import changes from SP to AD, or AD to SP.

If you don’t know how to do it, please connect to your Domain Controller and click on “Active Directory for Users and Computers”.
Made a right-click on the domain and click to “Delegate Control”

And give your user who has to replicate domain changes the adequate right.

Then under “Services under Server” please start the User Profile Synchronization Service but be aware, it will take more than 5 minutes before start. So, if it does not start directly do not panic.

Now, you can make a new connection to your Active Directory.
Please provide:

• A connection Name: SPPIRATE AD 
• Type: Active Directory
• Forest name: SPPIRATE.NET
• Account Name: DOMAIN\USER
• Password: PASSWORD

Under populate containers; please choose what exactly you need. In the earlier version of SharePoint (2007) you couldn’t choose your containers and it was a real disillusion, because it took everything Even Service Accounts.
But there is a workaround for this: http://www.gknzcfc.net/subsite/user-profile-syncronization-importing-different-ou-in-sharepoint-2007.html

And you can now Start a Profile Synchronization.

And you can see that our imported User Profiles has been updated from 1 to 4. Meaning that the users has with their profile has been imported to SharePoint 2013.

You can now made a search on a specific user and you will be prompted with that user.

        

Send me the comments.

Listing all webparts of all pages in all webs in a site collection.

 Listing all webparts of all pages in all webs in a site collection.

# Basis: http://www.glynblogs.com/2011/07/listing-all-web-parts-in-a-site-collection-with-powershell.html
# Modified by http://sharepoint.stackexchange.com/users/2509/tarjeieo
function EnumAllWebPartsOfSiteCollection($Url) {
    $site = new-object Microsoft.SharePoint.SPSite $Url 
    $allFiles = @()
    foreach($web in $site.AllWebs) {
        Write-Host "Processing Web:" $web.Url -NoNewLine
        if ([Microsoft.SharePoint.Publishing.PublishingWeb]::IsPublishingWeb($web)) {
            $pWeb = [Microsoft.SharePoint.Publishing.PublishingWeb]::GetPublishingWeb($web)
            $pages = $pWeb.PagesList

            foreach ($item in $pages.Items) {
                $allFiles += $item.File
            }
        }
        $pages = $null
        $pages = $web.Lists["Site Pages"]
        if ($pages) {
            foreach ($item in $pages.Items) {
                $allFiles += $item.File
            }
        }
        foreach ($file in $web.Files) {
            $allFiles += $file
        }
        $web.Dispose()
        Write-Host " - completed"
    }
    foreach ($file in $allFiles) {
        $fileUrl = $Url + $file.ServerRelativeUrl
        $manager = $file.GetLimitedWebPartManager([System.Web.UI.WebControls.Webparts.PersonalizationScope]::Shared);
        $wps = $manager.webparts
        $manager.Dispose()
        $wps | select-object @{Expression={$file.Web.Url};Label="Web URL"},@{Expression={$fileUrl};Label="Page URL"}, DisplayTitle, IsVisible, @{Expression={$_.GetType().ToString()};Label="Type"}
    }
    $site.Dispose()
}

$row = EnumAllWebPartsOfSiteCollection('http://test:1337')
$row | Out-GridView

Attach or detach content databases in SharePoint 2013

SharePoint 2013

  Applies to: SharePoint Server 2013, SharePoint Foundation 2013
Topic Last Modified: 2013-12-18
Summary: Learn how to attach and detach content databases to your SharePoint 2013 farm.
You can attach or detach SharePoint 2013 content databases by using the SharePoint Central Administration website or Windows PowerShell 3.0
In this article:

• Before you begin
• Attaching and detaching content databases
  
  • To attach a content database by using Central Administration
  • To detach a content database by using Central Administration
  • To attach or detach a content database by using Windows PowerShell

Before you begin

---

Before you begin this operation, review the following information:

• If you want to create a new content database while you attach it, the SharePoint farm service account must be a member of the SQL Server dbcreator fixed server role. To attach a content database to a web application, the SharePoint farm service account must have db_owner permission for the content database.
• If the database already exists, it must be the same version as the SharePoint 2013 farm or this operation will fail. To attach a content database that is a different version than the farm, use the To attach or detach a content database by using Windows PowerShell procedure in the following section.

Note:

Because SharePoint 2013 runs as websites in Internet Information Services (IIS), administrators and users depend on the accessibility features that browsers provide. SharePoint 2013 supports the accessibility features of supported browsers. For more information, see the following resources: Plan browser support Accessibility for SharePoint 2013 Accessibility features in SharePoint 2013 Products Keyboard shortcuts Touch

Attaching and detaching content databases

---

You might want to attach or detach content databases for the following reasons. You want to add a new content database for new site collections to keep content databases at a manageable size. You are restoring a content database from another farm and you want the sites that it contains to be accessed from a web application. You have archived site collections out of a content database and then detach the content database from the web application. For more information, see Move site collections between databases in SharePoint 2013
The steps to add a database and to attach a database are very similar. For more information about how to add a database, see Add content databases in SharePoint 2013.
To attach a content database by using Central Administration

1. Verify that the user account that is being used to perform this operation is a member of the Farm Administrators SharePoint 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.
   For more information about how to interact with Windows Server 2012, see Common Management Tasks and Navigation in Windows Server 2012.
3. On the SharePoint Central Administration website, click Application Management.
4. On the Application Management page, in the Databases section, click Manage content databases.
5. On the Manage Content Databases page, click Add a content database.
6. On the Add Content Database page:
   
   1. Use the web Application drop-down menu to select the web application to which you want to attach a content database.
   2. Specify the database server that hosts the database.
   3. Specify the database name. If the database does not already exist, it will be created.
   4. Specify the authentication method for the database, and supply an account name and password if you are using SQL authentication.
      
      

      Important:
      The account name and password must already exist as a SQL Server login. We recommend that you use Windows authentication instead of SQL authentication because, by default, SQL authentication sends a nonencrypted password to the computer that is running SQL Server. If you use SQL authentication, the SQL account requires the same SQL permissions as the SharePoint farm service account.

   5. Click OK.

To detach a content database by using Central Administration

1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
2. On the SharePoint Central Administration website, click Application Management.
3. On the Application Management page, in the Databases section, click Manage content databases.
4. Select the web application for which you want to detach a content database.
5. Click the content database that you want to detach.
6. On the Manage Content Database Settings page, select the Remove content database check box.
   If the content database contains data, you will receive a warning. Click OK to continue with the operation.
7. Click OK to confirm the detachment, or click Cancel to stop the operation without detaching the database.
   After detaching the content database in Central Administration, the content database still exists in SQL Server. If you want to permanently remove the content database, you must do so by using a SQL Server procedure.

To attach or detach a content database by using Windows PowerShell

1. Verify that you have the following memberships:
   
   • securityadmin fixed server role on the SQL Server instance.
   • db_owner fixed database role on all databases that are to be updated.
   • Administrators group on the server on which you are running the Windows PowerShell cmdlets.
   An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 Products cmdlets.
   

   Note:
   If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about Windows PowerShell permissions, see Add-SPShellAdmin.

2. On the Start menu, click All Programs.
3. Click Microsoft SharePoint 2013 Products.
4. Click SharePoint 2013 Management Shell.
5. At the Windows PowerShell command prompt, type the appropriate command
   To attach an existing content database:
   
   Copy

   Mount-SPContentDatabase "<ContentDb>" -DatabaseServer "<DbServer>" -WebApplication http://SiteName
   

   
   Where:
   
   • <ContentDb> is the content database to be attached.
   • <DbServer> is the name of the database server.
   • http://SiteName is the name of the web application to which the content database is being attached.
   
   To detach a content database:
   
   Copy

   Dismount-SPContentDatabase "<ContentdBName>"
   

   
   Where <ContentdBName> is the name of the content database.
   

   Important:
   If you have multiple content databases that have the same name, you must use the content database GUID in this command instead of using the content database name. To retrieve the GUID of the content database, run the Get-SPContentDatabase cmdlet with no arguments.

   The Dismount-SPContentDatabase cmdlet detaches the content database from the web application, but it does not delete the content database from SQL Server. After a content database is detached, you cannot delete it by using Windows PowerShell 3.0. You can only remove it by using SQL Server tools. If you want to delete the content database from SQL Server while you detach it, use the Remove-SPContentDatabase cmdlet instead.

For more information, see Dismount-SPContentDatabase and Mount-SPContentDatabase.

Note:
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.

how to attach the sharepoint 2013 content database

Attaching and Detaching a Sharepoint Content Database to a Webapplication

                A common scenario where we might have to attach and detach a database is when the webapplication is down due to some reason.And because of this you are not able to access any of the site collections in this particular web application.

Usually this happens when a lot of team members login to the development server with the service account(which is not recommended) and carry out different activities and somehow the webpplications gets corrupted and wont be accessible though it shows up in the Central Administration console.
In case you have already spent more than an hour to bring your webpplication up and still there are no results you can follow the below steps,

1) Delete the existing web application
2)Create a new web application at the same port
3)Add your old content database to the same webapplication

Detailed steps


1) Delete the existing web application

i) Browse to Central Administration -> Application Management -> Manage Content Databases.

ii) Select the webpplication you are planning to delete.Make a note of the associated database and copy it to a notepad.

iii) Browse to Central Administration -> Application Management -> Manage web Applications.

iv) Select the web application which is having the issue -> Delete.

v) A prompt box pops up.Make the selection as shown below.

vi) Now your webapplication and the associated IIS website is also deleted.But your contnet database is still intact in the SQL database.

2)Create a new web application at the same port

i) Browse to Central Administration -> Application Management ->New

ii) Create a new Web Application at the same port where you deleted your old web application.

3)Add your old content database to the same webapplication

i) Browse to Central Administration -> Application Management -> Manage Content Databases.

ii) Select the webpplication you just created -> Add a content database.

iii) The Add Content database page shows up.

iv) Copy and paste the database name which you had copied in step 1. Click OK.

v) Now you would see two content databases for your webapplication.Your old content database is now connected to new web application you created in step 2.

You should be able to access your old site collections now with the same URL. 

Moving or Renaming a Web Application Content Database

When creating a web application in SharePoint 2013 it will communicate with SQL Server to create the supporting content database. Depending on what steps are used to create the Web Apps it sometimes creates the SharePoint database with a not-so-'friendly' database name and it may contain a ginormous GUID, (which I pronounce Goo-id) as part of the database name. When working with these databases it can become challenging to specify the name of the database within PowerShell or SQL Server so you'll want to rename the database to a more user-friendly name. You may also decide you need to move the database to a different location on your hard drives, but you don't want to recreate the Web App.

This blog article is going to walk you through the steps you can take to move or rename these databases.

There are six general steps required to either move or rename SharePoint Web App content databases:

1. Take the database offline and remove it from within SharePoint.

2. Backup the Database (Optional step, but I strongly recommend it, in case there are problems).

3. Detach the database from within SQL Server.

4. Rename the database files (.ldf, and .mdf) associated with the database and rename the database to match the database file names. Or if you are moving the database files to a new location, copy the database files to the new location.

5. In SQL Server attach the moved and/or renamed database back to SQL Server.

6. Add the renamed or moved database back to Web Application.

In SharePoint:

1. Central Administration->Application Management->Manage Content Databases.

2. Choose the correct Web Application using the Web Application dropdown box on the right side of screen.

3. Click the name of the database that you want to move or rename.

4. Click from Ready to Offline in the Database Status dropdown.

5. Click checkbox next to Remove content database (This is not going to delete the DB in SQL).

6. Click Ok on the warning popup box indicating sites will no longer be available.

7. Click Ok.

In SQL Server:

1. Locate and right-click on the current database name in SQL Server Management Studio.

2. Click Tasks, then click Back Up… to open the Back Up Database configuration dialog box.

3. Verify Backup Type is Full, and that 'database' is selected within database component area. Make a note of the location of where the backup file will be created, then Click Ok to complete the backup of content database.

4. Right-click the current database name in SQL Server Management Studio and click Properties, then click Files, then locate and note the Path of each database file located in the details pane of the Database Properties window. (you will be renaming and/or moving these files later)

5. Right-click the current database name in SQL Server Management Studio and click Tasks, then Detach…

6. In the Detach Database dialog box, select the Drop Connections checkbox and click Ok.

Note: The current database name will no longer be available in SQL Server Management Studio.

In Windows Explorer:

1. Open Windows Explorer and locate the path of the database files you noted in the earlier step.

2. Locate the files you noted earlier and right-click the files and rename to reflect the new database name. (It is best practice to keep the default file extensions of these files) If you are moving the database files, copy the database files to the new location.

3. Close Windows Explorer and return to SQL Server Management Studio.

In SQL Server:

1. In the left pane of the SQL Server Management Studio, right-click Databases and click Attach…

2. Click the Add button and locate the directory that contains the .mdf file you previously located in Windows Explorer and click on it to highlight it. You will see the .ldf file was also added to the files associated with this database.

3. Click the filename in the Attach As area within the Databases to attach section and specify the new database name to be seen in SQL Server and SharePoint

4. In the details pane of the Attach Database dialog box, under the Current File Path section, locate the new path, and click on the new file names of both the .mdf and .ldf files. Then click Ok.

In SharePoint:

1. Central Administration->Application Management->Manage Content Databases:

2. Choose the correct Web Application using the Web Application dropdown box on the right side of screen

3. Click Add a Content Database

4. Type in the new database name in the Database Name box and click Ok

Congratulations, you have now successfully renamed and/or moved the SharePoint content database and its associated files.

Accepting the comments. Thanks.

Create a SharePoint Web Application from a SQL database backup

Create a SharePoint Web Application from a SQL database backup

To set a new environment from a database backup there are some step that are necessary to follow. The first step is restoring the SQL database backup.

Verify that the user account performing this procedure is a member of the sysadmin fixed server role.
If the Windows SharePoint Services Timer service is running, stop the service and wait for several minutes for any currently running stored procedures to finish. Do not restart the service until after you restore the content databases.
Start SQL Server Management Studio and connect to the database server. Expand Object Explorer, right click on Databases and select Restore Database.
On the Destination for restore add To database name, e.g., WSS_Content_80.
On the Source for restore select From device and point to the backup file.
Click on the restore check box.
Click OK to complete the recovery operation..
Start the Windows SharePoint Services Timer service.
The next step in the process is creating your Web Application, if you haven’t any yet, to host our Site Collections.

Note: The Web Application must be empty, with no Site Collections added, otherwise this will not work as it should!

Open the Central Administration.
Under Application Management, click Manage web applications.
On the Web Applications tab, click New.
Set the IIS Web Site Port
On the Database Name and Authentication group set append the selected Port to the end of the Database Name.
Select OK to initiate the creation process.
Click OK.
Our new Web Application will now be listed alongside our SharePoint Central Administration V4 Web Application under Central Administration/ Application Management / Manage web applications.

Open the SharePoint 2010 Management Shell with administration privileges and execute the following command to test the content database.

Execute the script:

Test-SPContentDatabase –name [SPContentDatabase] –WebApplication http://[server]:[port]/
 [SPContentDatabase] – in this example I’ll use WSS_Content_80

This is what you will see after executing the command line.You’ll see that you get an error, but this is more like a warning and does not affect anything on the site.

Change the above command line to Mount-SPContentDatabase –name [SPContentDatabase] –WebApplication http://[server]:[port]/.

Note: you can have more information about Test-SPContentDatabase and Mount-SPContentDatabase here and here.

The content database was successfully attached to our Web Application and before accessing the site we only need two more steps.


Go back to the Central Administration.
On the left menu click Application Management.

Under Service Collections group, click on Change site collection administrator.

Change the Primary and Secondary Site Collection Administrator for users from your network.
Click OK.

Now it is time to open your browser and you’re good to start using it.