Tuesday, November 3, 2015

SharePoint 2013: PowerShell to change site logo for all site collections/sites within a particular Web Application

Quick Post: You can use PowerShell in SharePoint 2013 to change the site logo for all site collections and sites within a particular web application. Copy/paste the following into a text file and rename it with a .ps1 extension.

Wednesday, October 7, 2015

SharePoint 2013: "The e-mail message cannot be sent. Make sure the e-mail has a valid recipient."

Recently, I ran into an issue in SharePoint 2013 in which a SharePoint workflow would not send email notifications to a few users selected via an InfoPath people picker control. The only thing that fixed it for me was the following.

1) Go directly to the All People list of the root site collection by using the following URL format.

2) Find the users experiencing the issue and remove them.

3) Add permissions to the site for each user again, as needed.

If this issue is occurring to many users throughout your entire SharePoint site collection hierarchy, you can apply the following farm wide fix:

1) stsadm.exe -o sync -deleteolddatabases 0

2) Manually run the User Profile to SharePoint Full Synchronization timer job. This job will take some time to run, but should fix the issue throughout the entire farm.

Wednesday, June 24, 2015

InfoPath 2013: Open web browser form directly with link in SharePoint workflow email

This may have already been blogged on hundred other sites, but I wanted to make sure it was on my blog as well, for future reference.

While building a SharePoint Designer 2013 workflow, you can create a link within the body of an email alert to open a web browser form directly. Simply follow these steps:

1) In the email body of the workflow, place your cursor where you want to create the link, and click the hyperlink icon to add a new hyperlink (see screenshot below). For the Text to display field, I usually select the Name from the source. For the Address field, click the ellipses button. Complete the next steps in this blog post to get the URL you need for your string build.

2) Open a new instance of the web browser form published to your form library. Copy the URL in the address bar, and paste it to notepad.

3) In notepad, change XsnLocation to XmlLocation, and remove the entire XmlLocation up to where "&DefaultItemOpen=1" begins. You will replace this path in your string build with the Encoded Absolute URL field from the source.

4) Copy/paste your new URL in the String Builder area for the Address field in Step 1. Be sure to add the Encoded Absolute URL field from source for the XmlLocation removed in Step 3.

See screenshot below for an example of a string build for the Address field.

Wednesday, April 22, 2015

Project Server 2013: AD sync for security groups and Enterprise Resource Pool not running after migrating from Project Server 2010

After migrating a PWA instance from Project Server 2010 to Project Server 2013, you may encounter an issue that the scheduled AD syncs for security groups and the Enterprise Resource Pool no longer run. Furthermore, if you look at the Job Definitions, you will notice that the following jobs are missing:

"Project Web App: Synchronization of AD with security groups job for http://url/pwa"
"Project Web App: Synchronization of AD with the Enterprise Resource Pool job for http://url/pwa"

Fortunately, this is an easy fix.

Under the Project Server service application, find the instance that is experiencing the issue. Select Edit in the drop-down menu, and then the Edit button. Project Server 2013 will perform a quick re-provision on the instance. Once finished, the jobs should now appear under Job Definitions and the sync operations should work fine.

Monday, March 2, 2015

Project Server 2013: Queue Jobs hung on "Waiting To Be Processed" after provisioning PWA instance

After recently provisioning a PWA instance based on the restored content DBs of an instance from another farm, I noticed the job queue was hung with all jobs having the status of "Waiting To Be Processed". If the issue still exists after performing a simple restart of the Microsoft Project Server Queue Service 2013 service, it can be fixed most of the time by using PowerShell.

1. $serviceapp = get-spserviceapplication | ? {$_.TypeName -like "*Project*"}
2. $pwainstances = $serviceapp.Sitecollection
3. $pwainstances

You will see the details of each PWA instance in your farm. For the instance experiencing the issue, the IsOnline status should be False, as shown in the screenshot below.

This status means that the PWA instance was not provisioned correctly and is not completely online.

Resolution: Re-Provision the PWA instance in-place using PowerShell.

4. Upgrade-SPProjectWebInstance -Identity "http://url/pwa"
5. Type "y" to confirm and hit Enter.

When done, you should see the following message: Upgrade of single project site completed.

6. $pwainstances

IsOnline status should now be True.

The job queue will automatically resume to normal operation.

Thursday, February 19, 2015

SharePoint 2013 eDiscovery: Error adding My Site Host as a new Source

When trying to add your My Site Host as a new Source to use for eDiscovery in SharePoint 2013, you receive the following error:

A colleague of mine, Judy Lancaster, found the solution.

1) Go to the Site Settings of your My Site Host.
2) Under the Search section, select Search and offline availability.
3) Select Yes to Allow this site to appear in search results?.

Should be able to add it as a new Source now.

Monday, February 16, 2015

Project Server 2013: Project data not showing in BI reports after migrating from Project Server 2010

Recently, upon migrating a PWA instance from Project Server 2010 to Project Server 2013, I noticed the BI reports were showing blank for Project data. For example, the SimpleProjectsList sample report would successfully open without any errors, but it was just blank. Furthermore, I could successfully connect to the PWA site and get Project data via an OData Data Feed using my Excel 2013 client application.

After opening a ticket with Microsoft, we discovered the projects were not published correctly. We managed to publish the 400+ projects correctly using an Microsoft issued application named ProjTool. You can download ProjTool and user instructions in the zip file below.


Hope this helps others facing this same issue.