SharePoint

SharePoint 2013 Upgrade Testing – My InfoPath Issue

I have been testing various features and functionally of a  recent SharePoint 2010 to SharePoint 2013 upgrade I preformed. When I encountered an issue involving a list item used heavily buy one of my departments.

The issue presented itself when the users attempted to create new work items and this is when SharePoint 2013 displayed an informative error messages telling me something went wrong.

I was able to obtain the correlation ID,

and after some filtering and digging in the ULS  (Unified Logging System) I was able to see that this list was created using InfoPath.

After seeking additional information from a few developers it was suggested that this form may need to be recreated. I was later to find out that other customer shave been facing issues with InfoPath and SharePoint 2013 forms.

The Office Team @ Microsoft has released a statement via their Blog that they are “evolving  forms technology” in an effort to streamline and deliver a more integrated  user experience.

In their own words:  “we’re retiring InfoPath and investing in new forms technology across SharePoint, Access, and Word. This means that InfoPath 2013 is the last release of the desktop client, and InfoPath Forms Services in SharePoint Server 2013 is the last release of InfoPath Forms Services.” 

I am taking that means the older forms used from back in Office SharePoint Server 2007 have been deprecated, eventually the rest.

That said here is a link to their blog post:
Update on InfoPath and SharePoint Forms

 

SharePoint List View Lookup Threshold

Testing a pilot of a recent SharePoint 2010 to SharePoint 2013 upgrade I encountered a message reading: “This view cannot be displayed because the number of lookup and workflow status columns it contains exceeds the threshold (8) enforced by the administrator”

This seems to be resource throttling introduced in the web application to limit the number of items in a list view, which roughly means “woah, whats with the large database query dude”

I was able to locate where this throttling setting is located.

Open Central Administration > Application Management > Manage Web Applications (choose the application)> General Settings (a drop-down list should show, now select) > Resource Throttling

Scroll down and locate ‘List View Lookup Threshold‘ The default value is 8

Honestly, I have no idea how large this should be. I didn’t design the list. However Microsoft has some details of creating lists here. The only major concern here is obvious “Resources”.

So what I did was double the value that was the default

Please note that this solution by far is not 100% correct as I just tossed resources at an issue to resolve it. However without prior knowledge of list design this solution works.

Error seen on end user side:

SharePoint 2010 to SharePoint 2013, Content Database Upgrade

I have been working on upgrading SharePoint 2010 to SharePoint 2013.  Here are some notes on steps taken to update a content database for your default web application.

Please note:  

  1. A backup of your default (primary) SharePoint 2010 content database is needed.
  2. These steps are for those who have already installed SharePoint and have a functioning central administration site working.

Step 1 – Backup of content database.

In order to upgrade and mount your SharePoint 2010 content database in SharePoint 2013 you will need to create a backup of the content database and restore this onto the database server chosen to server as your SharePoint 2013 database. While a new server is not required (space permitting) you may do this on the same database by restoring with a different name.

Step 2 – Create new (in my case) default application site

To attach the restored SharePoint 2010 database to the SharePoint 2013 installation, we need to create a new application site.

  • Open Central Administration
  • In Central Administration, select Application Management then select Manage Web Applications 
  • One under the Manage Web Applications, click  New to create a new web application
  • This bring you to the ‘Create New Application setup model.  There are many options here. In my case I am setting up just a new SharePoint site.
  • Create a new IIS website – For my setup I am keeping the default name. If the site runs on port 80 no need to change this. I am keeping the default site path, and being that this is part of an upgrade of a SharePoint 2010 database I am calling the database WSS_Content_delete_me as a reminded to delete later.
    Click OK and you will see the following popup
  • Followed by a message indicating that your application has been created.
  • We now want to make our way to Central Administration > Application Management and select, Manage content database 
  • Selecting the database we created above: ‘WSS_Content_delete_me’ we choose the option to remove the content database from the newly created application
  •  Click ‘ok’ to complete this action

Step 3 – Upgrade and Mount (attach) Database

The next steps require us to use SharePoint 2013’s Management Shell to mount the SharePoint 2010 database and in doing so upgrade it to function with SharePoint 2013.

We run the following command syntax to mount  the database:

To mount: Mount-SPContentDatabase -Name <database_name> -WebApplication http://<sharepoint_server_application>

To test: Test-SPContentDatabase -Name <database_name> -WebApplication http://<sharepoint_server_application>

Depending on the size of the content database, you may have to wait for a short period of time for the upgrade to complete.

* note * you may encounter error messages at the end of the upgrade once completed indicating customization’s that are not supported in SharePoint 2013.

SharePoint 2010 – Updating Webpart Solution

Similar to my previous post SharePoint 2010 – Deploying Webpart Solution, the upgrade process of a Webpart Solution you have a few steps to take to make this all happen.

As I did in my previous post:

I copied the webpart to the local disk of my SharePoint 2010 server. Placing it in a folder c:install this time around I am not going to be running the command Add-SPSolution c:installSharePointWebpart.wsp as it already exist. If you do you will get an error stating that the solution already exists.

What you will need to do is run the following command for example: Update-SPSolution –Identity SharePointWebpart.wsp –LiteralPath c:installSharePointWebpart.wsp –GACDeployment

For more info on features and solutions cmdlets: http://technet.microsoft.com/en-us/library/ff607724.aspx

SharePoint Document Library as a Network Drive

SharePoint can be fun if you just let it…

This post applies to SharePoint 2010 as I haven’t yet to play with the features of SharePoint 2013, although I am confident the same method would apply.

To map a SharePoint 2010 Document Library as a network drive you need to first copy the SharePoint document library URL. For example, I am using my document library from my ‘my sites’ location where I have “http://my.sites.jermsmit.domain/personal/jsmith/PersonalDocuments”.

I then open Windows Explorer, right click on Computer and select Map Network Drive

In the what network folder would you like to map?’ area I choose a drive letter that I would want “S” is a good choice as I have other mapped and its the next in the line for me. Choose what fits you best.

If you are in the same active directory domain you should not be prompt for a users and password. If you aren’t  just apply the domain/user and password you have been assigned for the SharePoint 2010 environment.

At this point you should be able to access your SharePoint 2010 document library contents right from Windows Explorer

– Jermal