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.
Wednesday, April 22, 2015
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.
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.
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.
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.
ProjTool.zip
Hope this helps others facing this same issue.
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.
ProjTool.zip
Hope this helps others facing this same issue.
Thursday, November 13, 2014
SharePoint 2013: “Nice-to-Haves”
I've been working with SharePoint 2013 for about a year now,
and it’s been quite the adventure...or not. From the revamped user interface to the new Search
configuration via PowerShell, sometimes I just can’t help but shake my head at some of the unnecessary
complexities that Microsoft bestows upon us SharePoint Admins. I have compiled the
following list of key pieces of functionality that I would consider to be “nice-to-haves”
while working with SharePoint 2013. By the looks of it, I’ll probably be
posting a Part 2 of this topic within the next six months. Ugh!
- Why has the Check-Out dialog box disappeared?
I have opened a case with Microsoft regarding this issue. Their response thus far:
"I would like to inform you that we have been discussing this known issue with our Product group and are in process of evaluating the same. As this issue stands as an integration with Adobe, we are planning as to how best we can address this issue making sure that future fix doesn’t break it."
Fingers crossed they provide a fix soon.
- No Site Permissions listed in the site settings drop-down menu? One extra click to see who has access to your site.
- Bring back the tabs for the top level navigation items!
- Upon selecting the ‘new document’ link to create a new page, please prompt me so I can select the type of page I actually want.
- It would be nice to still have the ability to create and modify the Search topology via the GUI.
- Better support for non-office files, such as .dwg.
- Contribute (not Edit) as the default permission level for all Members groups. Why change it now?
- Deleting ‘Profiles Missing from Import’ actually works as intended, particularly for those who have disabled the My Site Cleanup Job.
- Org Chart on everyone's own My Site by default.
SharePoint used to be fun…really fun. Not so much now days. :(
- Why has the Check-Out dialog box disappeared?
I have opened a case with Microsoft regarding this issue. Their response thus far:
"I would like to inform you that we have been discussing this known issue with our Product group and are in process of evaluating the same. As this issue stands as an integration with Adobe, we are planning as to how best we can address this issue making sure that future fix doesn’t break it."
Fingers crossed they provide a fix soon.
- No Site Permissions listed in the site settings drop-down menu? One extra click to see who has access to your site.
- Bring back the tabs for the top level navigation items!
- Upon selecting the ‘new document’ link to create a new page, please prompt me so I can select the type of page I actually want.
- It would be nice to still have the ability to create and modify the Search topology via the GUI.
- Better support for non-office files, such as .dwg.
- Contribute (not Edit) as the default permission level for all Members groups. Why change it now?
- Deleting ‘Profiles Missing from Import’ actually works as intended, particularly for those who have disabled the My Site Cleanup Job.
- Org Chart on everyone's own My Site by default.
SharePoint used to be fun…really fun. Not so much now days. :(
Thursday, July 24, 2014
SharePoint 2013 Search: "The server is unavailable and could not be accessed. The server is probably disconnected from the network."
I recently experienced an issue of of a single content source not crawling in the SharePoint 2013 Search Service Application. The crawl log gave the following error:
"The server is unavailable and could not be accessed. The server is probably disconnected from the network."
I had already added the infamous DisableLoopBackCheck fix when I initially deployed the farm, so I knew that wasn't going to be the solution.
The following steps fixed the issue for me:
1) Open the registry on the Central Administration server.
2) Navigate to HKLM\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0.
3) Right-click MSV1_0 and add a new Multi-String Value. Give it a name of BackConnectionHostNames.
4) Double-click to modify the newly created BackConnectionHostNames item. Add the FQDN of each web application you want to crawl, one per line. Select OK.
5) Perform an IIS reset.
Should be able to successfully crawl the content source now.
"The server is unavailable and could not be accessed. The server is probably disconnected from the network."
I had already added the infamous DisableLoopBackCheck fix when I initially deployed the farm, so I knew that wasn't going to be the solution.
The following steps fixed the issue for me:
1) Open the registry on the Central Administration server.
2) Navigate to HKLM\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0.
3) Right-click MSV1_0 and add a new Multi-String Value. Give it a name of BackConnectionHostNames.
4) Double-click to modify the newly created BackConnectionHostNames item. Add the FQDN of each web application you want to crawl, one per line. Select OK.
5) Perform an IIS reset.
Should be able to successfully crawl the content source now.
Tuesday, July 15, 2014
Best Practice: Migrating and converting SharePoint 2010 web applications from Classic-Mode to Claims-Based Authentication in SharePoint 2013
For migrating and converting SharePoint 2010 web applications from Classic-Mode to Claims-Based Authentication in SharePoint 2013, the following steps work best for me:
1. Create new classic-mode web application in SharePoint 2013, using PowerShell.
2. Restore and attach the content database from SharePoint 2010 to SharePoint 2013.
3. Deploy farm solutions as needed on the upgraded web application in SharePoint 2013.
4. Perform an IIS reset on Central Admin server and each WFE server in the SharePoint 2013 farm.
5. Ensure you can access the site collection in default Windows classic mode.
6. If you have a custom security trust config file, manually copy the file from a SharePoint 2010 WFE server to the Central Admin server and each WFE server in the SharePoint 2013 farm. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG.
7. If you perform step 6 above, you will also need to manually add the open and closing security policy tag to the web.config file on the Central Admin server and each WFE server in the SharePoint 2013 farm, directly under the system.web opening tag.
8. Convert the web application to Claims-Based Authentication.
9. Run the usermigration_Claim.ps1 script, provided by Karim.
usermigration_Claim.ps1
10. Perform an IIS reset on Central Admin server and each WFE server in the SharePoint 2013 farm.
11. Ensure users can successfully access sites in the converted web application.
1. Create new classic-mode web application in SharePoint 2013, using PowerShell.
2. Restore and attach the content database from SharePoint 2010 to SharePoint 2013.
3. Deploy farm solutions as needed on the upgraded web application in SharePoint 2013.
4. Perform an IIS reset on Central Admin server and each WFE server in the SharePoint 2013 farm.
5. Ensure you can access the site collection in default Windows classic mode.
6. If you have a custom security trust config file, manually copy the file from a SharePoint 2010 WFE server to the Central Admin server and each WFE server in the SharePoint 2013 farm. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG.
7. If you perform step 6 above, you will also need to manually add the open and closing security policy tag to the web.config file on the Central Admin server and each WFE server in the SharePoint 2013 farm, directly under the system.web opening tag.
8. Convert the web application to Claims-Based Authentication.
9. Run the usermigration_Claim.ps1 script, provided by Karim.
usermigration_Claim.ps1
10. Perform an IIS reset on Central Admin server and each WFE server in the SharePoint 2013 farm.
11. Ensure users can successfully access sites in the converted web application.
Wednesday, July 2, 2014
SharePoint 2013: Add user profile properties to People search results
By default, People search results in SharePoint 2013 only shows the Job Title and Department user properties. You can add additional user properties using a custom Display Template by following these steps.
1. On the Search Center site, go to Site Settings, Master pages and page layouts, Display Templates, and Search. Download a copy of the Item_Person.html file to your desktop, and open the file in your favorite editor. In the mso:managedpropertymapping section, add your user properties in the same format as the existing ones. For example, the Mobile Phone user property would be:
'MobilePhone':'MobilePhone'
Be sure to separate all newly added user properties with a comma.
2. In the variable declarations section, add your additional user properties in the same format as the existing ones. For example, Mobile Phone would be:
3. In the section below the variable declarations section, add each additional user property's DIV content in the same format as the existing ones. For example, Mobile Phone would be:
Be sure to add each user property in the appropriate order in this section. So, if you want Mobile Phone to be located after the Work Phone property in People search results, add the Mobile Phone DIV content directly after the Work Phone DIV content.
4. Save and rename the the file to to something specific to your organization, such as Item_Person_Contoso.html.
5. Upload the file to the same location where you initially copied the file (Search Center site, Site Settings, Master pages and page layouts, Display Templates, and Search). Be sure to check in and publish a major version of the file.
6. Edit your peopleresults.aspx page, and then edit the People Search Core Results web part. Expand Display Templates, select Use a single template to display items, and then select your custom Display Template. Save the web part. Check in the peopleresults.aspx page and publish a major version.
Test People search results and ensure the properties are there. All done.
A few notes:
If some of the user properties don't show in the search results, you may have to tweak them a little. In particular, I have noticed the following:
Email = WorkEmail
Mobile Phone = MobilePhone
Office = OfficeNumber
To get the email address to show as a link, add the anchor tag to the DIV content as shown in the example below:
1. On the Search Center site, go to Site Settings, Master pages and page layouts, Display Templates, and Search. Download a copy of the Item_Person.html file to your desktop, and open the file in your favorite editor. In the mso:managedpropertymapping section, add your user properties in the same format as the existing ones. For example, the Mobile Phone user property would be:
'MobilePhone':'MobilePhone'
Be sure to separate all newly added user properties with a comma.
2. In the variable declarations section, add your additional user properties in the same format as the existing ones. For example, Mobile Phone would be:
3. In the section below the variable declarations section, add each additional user property's DIV content in the same format as the existing ones. For example, Mobile Phone would be:
Be sure to add each user property in the appropriate order in this section. So, if you want Mobile Phone to be located after the Work Phone property in People search results, add the Mobile Phone DIV content directly after the Work Phone DIV content.
4. Save and rename the the file to to something specific to your organization, such as Item_Person_Contoso.html.
5. Upload the file to the same location where you initially copied the file (Search Center site, Site Settings, Master pages and page layouts, Display Templates, and Search). Be sure to check in and publish a major version of the file.
6. Edit your peopleresults.aspx page, and then edit the People Search Core Results web part. Expand Display Templates, select Use a single template to display items, and then select your custom Display Template. Save the web part. Check in the peopleresults.aspx page and publish a major version.
Test People search results and ensure the properties are there. All done.
A few notes:
If some of the user properties don't show in the search results, you may have to tweak them a little. In particular, I have noticed the following:
Email = WorkEmail
Mobile Phone = MobilePhone
Office = OfficeNumber
To get the email address to show as a link, add the anchor tag to the DIV content as shown in the example below:
Subscribe to:
Posts (Atom)