Archive for upgrade

SharePoint 2013 Migration: User not able to access after migration from SharePoint 2010 to SharePoint 2013

Scenario:

We have migrated our sites from SharePoint 2010 to SharePoint 2013. After migration, users are not able to access newly migrated site. If we delete user and provide access again, user able to access site. (Fortunately, this was happening on test migration)

Resolution:

The missing link was warning that we overlooked. When we ran PowerShell Test-SPContentDatabase cmdlet, we missed following warning:

Category : Configuration

Error : False

UpgradeBlocking : False

Message : The [SharePoint2013] web application is configured with claims authentication mode however the content database you are trying to attach is intended to be used against a windows classic authentication mode.

Remedy : There is an inconsistency between the authentication mode of target web application and the source web application. Ensure that the authentication mode setting in upgraded web application is the same as what you had in previous SharePoint 2010 web application. Refer to the link http://go.microsoft.com/fwlink/?LinkId=236865 for more information.

Locations :

In other words, SharePoint 2013 discourage classic mode authentication. If web application is created via Central Administration, claim based is the default and preferred method of authentication. If want to create web application with classic mode authentication, you need to use PowerShell cmdlets.

It goes like this:

  1. Create classic mode web application using PowerShell cmdlets
  2. Attach all content database with web application
  3. Convert classis mode web application to claim base authentication
  4. Configure Object cache

Create classic mode web application using PowerShell cmdlets

$ap = New-SPAuthenticationProvider -UseWindowsIntegratedAuthentication –DisableKerberos

New-SPWebApplication -Name “SharePoint – 2013” -ApplicationPool “SharePoint 2013 Web Apps” -ApplicationPoolAccount (Get-SPManagedAccount “domain\login”) -Port 80 -Url http://sharepoint2013 -AuthenticationMethod NTLM -AuthenticationProvider $ap -DatabaseName “WSS_Content_01”

Attach all content database with web application

Mount-SPContentDatabase “WSS_Content_2” -DatabaseServer “SQLDB2013” -WebApplication http://sharepoint2013

Convert classis mode web application to claim base authentication

Convert-SPWebApplication –Identity http://sharepoint2013 –To Claims -RetainPermissions –Force

Configure Object cache

$wa = Get-SPWebApplication -Identity http://sharepoint2013

$wa.Properties[“portalsuperuseraccount”] = “domain\login”

$wa.Properties[“portalsuperreaderaccount”] = “domain\login”

$wa.Update()

Make sure you enter user login using SharePoint 2013 claims encoding. It must be in this format “i:0#.w|contoso\chris” [For details, please visit] and don’t forget to restart IIS.


Advertisements

Leave a Comment

SharePoint 2013: After Upgrade, Images are not rendering

Scenario:

We have upgrade our SharePoint 2010 farm to SharePoint 2013. After upgrade, images stopped rendering in IE. Images are working fine in Chrome and Firefox but when opened in Internet Explorer, failed to render

Resolution:

It seems that SharePoint 2013 is adding two custom headers in HTTP request that are not recognized by IE. These custom headers were creating all the problem. Going into the web.config file of web application and commenting those custom headers solved the issue.

<customHeaders>

        <add name=”X-Content-Type-Options” value=”nosniff” />

        <add name=”X-MS-InvokeApp” value=”1; RequireReadOnly” />

</customHeaders>

A great post by Johan Olivier helped us a lot.

Leave a Comment

Upgrade Error: Access to this Web site has been blocked. Please contact the administrator to resolve this problem

We were trying to upgrade site gradually one by one from SharePoint 2003 to SharePoint 2007, one site after upgrade displayed following error message on access:

Access to this Web site has been blocked.

Please contact the administrator to resolve this problem.

Server event viewer has following entries:

Event Type:        Error

Event Source:     Office SharePoint Server

Event Category:  Records Center

Event ID:   7894

Date:        XXXXXXXX

Time:                XXXXXXXX

User:         N/A

Computer:  XXXXXXXX

Description:

Records Center processing for site collection http://abc/sites/xyz failed.

Access to this Web site has been blocked.

Please contact the administrator to resolve this problem.

   at Microsoft.SharePoint.Library.SPRequest.OpenWebInternal(String bstrUrl, Guid& pguidID, String& pbstrRequestAccessEmail, UInt32& pwebVersion, String& pbstrServerRelativeUrl, UInt32& pnLanguage, UInt32& pnLocale, String& pbstrDefaultTheme, String& pbstrDefaultThemeCSSUrl, String& pbstrAlternateCSSUrl, String& pbstrCustomizedCssFileList, String& pbstrCustomJSUrl, String& pbstrAlternateHeaderUrl, String& pbstrMasterUrl, String& pbstrCustomMasterUrl, String& pbstrSiteLogoUrl, String& pbstrSiteLogoDescription, Object& pvarUser, Boolean& pvarIsAuditor, Int32& plSiteFlags)

   at Microsoft.SharePoint.SPWeb.InitWebPublic()

   at Microsoft.SharePoint.SPWeb.get_ServerRelativeUrl()

   at Microsoft.SharePoint.SPWeb.get_Url()

   at Microsoft.SharePoint.SPWeb.GetProperties()

   at Microsoft.SharePoint.Utilities.SPPropertyBag..ctor(GetProperties getProperties, UpdateProperties updateProperties)

   at Microsoft.SharePoint.SPWeb.get_Properties()

   at Microsoft.Office.RecordsManagement.Holds.Hold.HasRecordsCenter(SPSite site)

   at Microsoft.Office.RecordsManagement.Internal.RecordsRepositoryJobDefinition.Execute(Guid targetInstanceId)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

Event Type:        Error

Event Source:     Office SharePoint Server

Event Category:  Information Policy Management

Event ID:   5016

Date:        XXXXXXX

Time:                XXXXXXX

User:         N/A

Computer:  XXXXXXX

Description:

Expiration Service for site http://abc/sites/xyz failed.

Access to this Web site has been blocked.

Please contact the administrator to resolve this problem.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

Event Type:        Error

Event Source:     Office SharePoint Server

Event Category:  Records Center

Event ID:   7892

Date:        XXXXXXX

Time:                XXXXXXX

User:         N/A

Computer:  XXXXXXX

Description:

HoldProcessAndReport for site http://abc/sites/xyz failed.

Access to this Web site has been blocked.

Please contact the administrator to resolve this problem.

   at Microsoft.SharePoint.Library.SPRequest.OpenWebInternal(String bstrUrl, Guid& pguidID, String& pbstrRequestAccessEmail, UInt32& pwebVersion, String& pbstrServerRelativeUrl, UInt32& pnLanguage, UInt32& pnLocale, String& pbstrDefaultTheme, String& pbstrDefaultThemeCSSUrl, String& pbstrAlternateCSSUrl, String& pbstrCustomizedCssFileList, String& pbstrCustomJSUrl, String& pbstrAlternateHeaderUrl, String& pbstrMasterUrl, String& pbstrCustomMasterUrl, String& pbstrSiteLogoUrl, String& pbstrSiteLogoDescription, Object& pvarUser, Boolean& pvarIsAuditor, Int32& plSiteFlags)

   at Microsoft.SharePoint.SPWeb.InitWebPublic()

   at Microsoft.SharePoint.SPWeb.get_ServerRelativeUrl()

   at Microsoft.SharePoint.SPWeb.get_Url()

   at Microsoft.SharePoint.SPWeb.GetProperties()

   at Microsoft.SharePoint.Utilities.SPPropertyBag..ctor(GetProperties getProperties, UpdateProperties updateProperties)

   at Microsoft.SharePoint.SPWeb.get_Properties()

   at Microsoft.Office.RecordsManagement.Holds.Hold.HasRecordsCenter(SPSite site)

   at Microsoft.Office.RecordsManagement.Internal.HoldReportJobDefinition.Execute(Guid targetInstanceId)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

Event Type:        Error

Event Source:     Office SharePoint Server

Event Category:  Information Policy Management

Event ID:   3763

Date:        XXXXXXX

Time:                XXXXXXX

User:         N/A

Computer:  XXXXXXX

Description:

Processing policy updates for site http://abc/sites/xyz failed.

Access to this Web site has been blocked.

Please contact the administrator to resolve this problem.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Resolution:

“Central Administration > Application Management > Site Collection Quotas and Locks” and select “Not locked”

Comments (2)

After upgrade, Internet Users Cannot Access SharePoint 2003 sites

Scenario:

Our SharePoint 2003 URL is exposed to internet. Let it be http://share.companyname.com .

 Our SharePoint 2003 was running on port 80. When we upgraded using gradual approach, SharePoint 2003 was moved to another port, say, 42154 and new MOSS 2007 started running on port 80.

Now, the functionality is that when we try to access a SharePoint 2003, we are redirected. Like if when we tried to access http://share.compantname/sites/abc , we were redirected to SharePoint 2003 and URL turns out to be http://share:42154/sites/abc. This works find for intranet users but for internet users http://share:42154/sites/abc is not Fully Qualified Domain Name (FQDN), so they get stuck with page not found error.

 

Workaround:                                  

What we did was used SSL for port 42154. One can do this by going to IIS Manager, select Web Site running SharePoint 2003. Right click and click on properties. In front of TCP PORT: 42154, you have SSL Port: test box. Write 443. You will be able to access SharePoint 2003 sites using httpS://share.companyname.com/sites/abc

 

What went wrong?

When started Upgrade by clicking on “Begin Upgrade”, we didn’t put host header name and did not exposed that host header to internet

 

 

For more explanation, kindly visit the heading “Determine and create new domain names (gradual upgrade only)” at the following link:

http://office.microsoft.com/download/afile.aspx?AssetID=AM101638521033

Leave a Comment

Upgrading from SharePoint 2003 to MOSS 2007 Using Gradual Approach

Of all the three upgrade techniques, my favorite is database migration but of our client requirement was Gradual Upgrade. These steps are done for upgrade from WSS2.0/SharePoint 2003 to WSS3.0/MOSS 2007 in a single form environment. For different architecture, you may need some more steps. Also, we have to face with almost zero customization. Steps for upgrading from SharePoint Portal Server 2003 to Microsoft Office SharePoint Server 2007 using the gradual approach are as under:

 

1. Download and install Microsoft .NET Framework Version 3.0 Redistributable Package (x86) from the following URL:

 

http://www.microsoft.com/downloads/details.aspx?FamilyID=10CC340B-F857-4A14-83F5-25634C3BF043&displaylang=en 

 

2. Run PreScan.exe. The steps for running PreScan can be found at the following URL:

 

https://farhanfaiz.wordpress.com/2008/05/15/sharepoint-upgrade-prescanexe/

 

Remove all the error that are mentioned by PreScan. 

 

3. Install Microsoft Office SharePoint Server 2007. The steps for installing MOSS 2007 are as under: 

a. Run setup.exe file, enter product key and accept License Terms.

b. First important thing to do is to choose your upgrade approach. We will select gradual approach and click install now.

  

 

 

 

 

 

 

 

 

 

 

 

 

  

 

c. After installation, you get the completion screen.  Don’t uncheck “Run the SharePoint Products and Technologies Configuration Wizard nowand click close.

 

 

 

 

 

 

 

 

 

 

 

 

 

  

 

d. Odds are you will get a screen that says you must Reboot to complete setup. If so, click “Yes”.

  

4. SharePoint Products and Technologies Configuration Wizard will run.

a. This will take you to “Welcome to SharePoint Products and Technologies” screen. Click “Next”.

 

 

 

 

 

 

 

 

 

 

 

 

 

  

 

b. It will ask about restarting server services. Click “Yes”.

c. On the language pack screen click OK. If you have any language packs to install, this is the time to do it.

d. On the “Connect to a server farm” screen, choose “No, I want to create a new server farm and click “Next”.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

  

e. Specify the name of the SQL server and the account password that SharePoint will use and click “Next”.

 

 

 

 

 

 

 

 

 

 

 

 

 

  

 

f. It will inquire about the central administrator port, change it or use the default. Select “Authentication Provider” according to you needs. We selected NTLM.

g. Screen with options you selected will appear. Click “Next” to start the configuration.

h. Once this finishes, it will display a Configuration Successful screen with the information of the settings. Click “Finish”.

i. You will be automatically taken to SharePoint Central Administration 2007.

 

5. The steps for SharePoint Central Administration are as under: 

a. Move from Operation to “Services on server” under “Topology and Services”.

b. Under the server role section you will notice several options. We selected “Single Server”.

c. Now for the options at the bottom we need to get all of them started.

d. Click on “Start” for Document Conversions Load Balancer Service

e. Click on “Start” for Document Conversions Launcher Service by selecting the server and clicking on “OK”.

h. Click start for Windows SharePoint Services Search and fill out your service accounts in the form domain\username and the enter password. Accept the other defaults and click Start.

 

6. We are now ready to go on performing a gradual upgrade. The steps for upgrading sites one by one are as under: 

 

a. The first step is move from Central Administration > Operations > Site Content Upgrade Status.   

b. Select Begin Upgrade under actions. (If you SharePoint 2003 is 

exposed to internet, do check the URL :

https://farhanfaiz.wordpress.com/2008/08/16/after-upgrade-internet-users-cannot-access-sharepoint-2003-sites/)

c. List of sites will appear with the options Database names, Refresh site list, Revert Site, Upgrade settings, Site Content Upgrade Status and Finalize Upgrade.

e. Select “\” root site first to start upgrade. This will result in the following actions:

                                               I.    MOSS 2007 will occupy the port on which SharePoint 2003 is running.

                                               II.    SharePoint 2003 with all the contents will be shifted to a new port, say, 5417.

                                              III.    Shared Service Provider for MOSS 2007 will be created with the same name as that SharePoint 2003 virtual server.

                                              IV.    When a user tries to access a site which is not upgrade to MOSS 2007, he will be redirected to SharePoint 2003.

                                              V.    Select the sites one by one to upgrade from SharePoint 2003 to MOSS 2007.

                                             VI.    When all the sites upgraded from SharePoint 2003 to MOSS 2007, click “Finalize Upgrade”.

 

7. Post Upgrade steps are as under:

 

a. Uninstall SharePoint portal Server 2003 (Stop SharePoint Portal Server Search Service first).

b. Delete Portal Configuration and Content Databases.

Comments (3)

SharePoint 2003 to MOSS 2007 Upgrade: Database migration

Of all the three upgrade techniques, my favorite is database migration. Database migration can be defined as “Requires the server administrator to install the new version on a separate farm or separate hardware, and then manually migrate the databases into the new environment.”

 

Database Migration enables moving to new farm or new hardware while SharePoint Portal Server 2003 environment is available and is untouched by upgrade. Microsoft says that database migration is a “Complex process that requires many manual steps and a higher risk of error. Requires additional manual steps to retain original URLs for sites. Search scopes must be re-created and search settings must be reapplied. Requires new server farm, and twice the amount of SQL Server storage space”. My advise is don’t be afraid and do try.

 

These steps are done for upgrade from WSS2.0/SharePoint 2003 to WSS3.0/MOSS 2007 in a single form environment. For different architecture, you may need some more steps. The steps are under: 

·     Get ready your MOSS 2007 environment.

·     Run PreScan on SharePoint Portal Server 2003.

·     Set the content database of SharePoint Portal Server 2003 as read only.

·     Take back up of content database of SharePoint Portal Server 2003.

·     Restore back up on SQL Server attached with MOSS 2007.

·     Create web application in MOSS 2007.

·     Remove content database of the newly created web application in MOSS 2007.

·     Attach restore database with the newly created web application in MOSS 2007.

 

And that’s itJ.

 

I am not going into the details of creating MOSS 2007 environment. We will start from the second step:

 

Run PreScan on SharePoint Portal Server 2003:

 

The first step is to run PreScan.exe. For details kindly visit the following blog:

 

https://farhanfaiz.wordpress.com/2008/05/15/sharepoint-upgrade-prescanexe/

 

Set the content database of SharePoint Portal Server 2003 as read only:

The content database of SharePoint Portal Server 2003 ends with 1_SITE like Abc1_SITE.

 

The steps for setting database as read only are:

 

For SQL Server 2000

 

1.     In Microsoft® SQL Server™ Enterprise Manager, right-click the name of the database that you want to set to read-only, and then click Properties.

2.     In the Properties dialog box, click the Options tab.

3.     Under Access, select the Read-only check box, and then click OK.

 

 

For Server 2005

1.     In Microsoft SQL Server Management Studio, right-click the name of the database that you want to set to read-only, and then click Properties.

2.     In the left pane, click Options.

3.     In the right pane, under Other options, under State, next to Database Read-Only, click the down arrow, and then select True.

 

Take back up of content database of SharePoint Portal Server 2003:

 

For details kindly visit the following blog:

 

https://farhanfaiz.wordpress.com/2008/05/16/sharepoint-2003moss-2007-take-back-up-of-content-database-in-sql-server-2000-and-sql-server-2005/

 

Let the name of the back be “Portal_Site.bak”. Wait after this. The time of database backup depends upon the system power and database size.

 

 

Restore back up on SQL Server attached with MOSS 2007:

 

The first step in restoring database is to create a database in SQL Server 2005. Let the newly created database name is “Portal_Site_Restore”.

 

1.     Expand Database “Portal_Site_Restore”, right-click the database you want to restore, point to Tasks, point to Restore, and then click Database. The Restore Database dialog box appears.

2.     On the General page, the name of the restoring database appears in the To database list box.

3.     In the To a point in time text box (if using SQL Server 2005 Enterprise Edition), retain the default (Most recent possible).

4.     To specify the source and location of the backup sets to restore, click From device, and then specify the database backup path (in our case, it is “Portal_Site.bak”) in the list box.

5.     In the Select the backup sets to restore grid, select the backup path.

6.     From the options tab, select “overwrite existing database”.

7.     Specify the paths for .ldf and .mdf in the options tab.

8.     Click OK to start the restore process.

 

Wait after this. The time of restoring database depends upon the system power and database size.

 

 

Create web application in MOSS 2007

 

In the SharePoint Central Administration, move to “Application Management” and click on “Create or extend Web application” under “SharePoint Web Application Management”.

 

Again click on “Create Web application”. Set the settings according to your own needs (do check the name of the web application and content database. Let the name of the web application be “http://servername:1234” and the name of the content database be “WSS_Content_1234”) and click OK. Don’t create any site collection.

 

 

Remove content database of the newly created web application in MOSS 2007

 

We can do that using Central Administrator or stsadm utility. I will like to do that using stsadm. Central Administration is easy. You will be able to learn that if you know how to do it using stsadm.

 

The command for removing content database using stsadm is ‘deletecontentdb’. The description is as under:

 

stsadm.exe -o deletecontentdb

-url <URL name>

-databasename <database name>

[-databaseserver] <database server name>

 

Parameter name

Value

Required?

Description

url

A valid URL, such as http://serverame:1234

Yes

Specifies the Web application from which the content database will be detached.

databasename

A valid database name, such as “WSS_Content_1234”

Yes

Specifies the name of content database to be detached.

databaseserver

A valid database server, such as “SQLServer1”

No

Database server name to be detached.

 

A typical command will be like:

 

stsadm.exe -o deletecontentdb -databasename WSS_Content_1234 -url http://servername:1234

 

Attach restore database with the newly created web application in MOSS 2007

 

We can do that using Central Administrator or stsadm utility. I will like to do that using stsadm. Central Administration is easy. You will be able to learn that if you know how to do it using stsadm.

 

The command for removing content database using stsadm is ‘addcontentdb’. The description is as under:

 

stsadm.exe -o addcontentdb

-url <URL name>

-databasename <database name>

[-databaseserver <database server name>]

[-databaseuser <database username>]

[-databasepassword <database password>]

[-sitewarning <site warning count>]

[-sitemax <site max count>]

 

Parameter name

Value

Required?

Description

url

A valid URL 

Yes

URL of

the Web

application

to which

the content

database is

being

added.

databasename

A valid

database name

Yes

Database

name.

databaseserver

A valid

database

server name

No

Database

server

name. The

default

server

is used

if a

value

not

provided.

databaseuser

A valid user

name in the

form “domain\login”

No

Account

used for

SQL authentication. Must be

used in

conjunction

with the

database

password parameter.

databasepassword

A valid

SQL

password

No

The database

password parameter should only

be used

where Windows authentication is not

implemented.

sitewarning

A valid

integer

number,

such as

10

No

Integer number

of site

collections allowed in

the content

database

prior to

generating

a warning

event in the

Windows event log.

sitemax

A valid

integer

number,

such as

10

No

Specifies

the maximum

number of site collections allowed in

the content

database.

 A typical command will be like:

 

stsadm.exe -o addcontentdb -url http://servername:1234 –databasename Portal_Site_Restore

 

Wait after this command. The time of adding content database depends upon the system power and database size.

 

 

http://office.microsoft.com/download/afile.aspx?AssetID=AM101638521033

 

http://technet.microsoft.com/en-us/library/cc263422.aspx

 

http://technet.microsoft.com/en-us/library/cc262449.aspx

 

 

Comments (55)

SharePoint 2003/MOSS 2007: Take back up of content database in SQL Server 2000 and SQL Server 2005

 

The content database of SharePoint Portal Server 2003 ends with 1_SITE like Abc1_SITE and for MOSS 2007 the convention is WSS_Content_ (followed by large string of numbers).

 

In order to take the backup of this database either it is in SQL Server 2000 or SQL Server 2005 follows the steps:

 

For SQL Server 2000

 

1.     On your database server, click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.

2.     In SQL Server Enterprise Manager, click the plus sign next to Microsoft SQL Servers.

3.     Click the plus sign next to SQL Server Group.

4.     Click the plus sign next to (local) (Windows NT).

5.     Click the plus sign next to Databases.

6.     Right-click the database you want to back up, point to All Tasks, and then click Backup Database.

7.     In the SQL Server Backup dialog box, in the Name box, specify a name for the backup, and then in the Backup area, select Database – complete.

8.     In the Destination area, either select an existing destination, or:

a.     Click Add.

b.     In the Select Backup Destination box, select File Name, and then next to the File Name box, click the Browse button.

c.      In the Backup Device Location – (local) dialog box, in the File name box, type a file name, and then click OK.

d.     Click OK again to close the Select Backup Destination dialog box.

9.     Click OK to start the backup process.

10.    Click OK to acknowledge that the backup process has completed.

Repeat these steps to back up the databases that are used by SharePoint Portal Server 2003 in your environment, except for the configuration and component settings (search) databases.

 

 

For SQL Server 2005

 

1.     On your database server, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.

2.     In the Connect to Server box, fill in the connection information, and then click Connect.

3.     After connecting to the appropriate instance of the SQL Server 2005 Database Engine, in Object Explorer, click the server name to expand the server tree.

4.     Expand Databases, right-click the database you want to back up, point to Tasks, and then click Back Up. The Back Up Database dialog box appears.

5.     In the Source section, in the Database box, verify the database name.

6.     In the Backup type box, select Full.

7.     Under Backup component, click Database.

8.     In the Name text box, either accept the default backup set name that is suggested or type a different name for the backup set.

9.     In the Destination section, choose the type of backup destination by clicking Disk or Tape, and then select a destination. To create a different destination, click Add.

10.    Click OK to start the backup process.

 

http://office.microsoft.com/download/afile.aspx?AssetID=AM101638521033

Leave a Comment

Older Posts »