Archive a Look-up table old values

Environment: Project Server 2010/2013

Background: Customer has a large list of account code in the look-up table – some are current and some every old. Users were complaining that they needed to scan a long list of expired values before finding valid options.

Solution:

As there is no out of the box option available to archive the values of the lookup table, we suggest you create one level hierarchy with the name ‘Do not Use’ and indent the Account code values which is very old.

This results in retaining the old account code values for existing projects and means users don’t need to scan these old when looking to select a current value.

Let us know if you know any other better solution.

Hope this helps you.

 

 

Project Archive/Hide in Project Center

Environment: Project Server 2007, Project Server 2010, Project Server 2013

Solution:

There are two options to hide projects in the project center as per below:

Option 1: Set the project filter for the project center views based on enterprise custom field. For instance, custom field has following values – Archived, Live, On-hold.

Below are the steps to hide the projects in a project center view:

a. Logon to Project Web App. Click on Server Settings > Manage Views > Click on Project Center View in which you don’t want to see the ‘Archived’ Projects. Refer snapshot below:

b. Apply the filter using the Enterprise field in your environment. For example, we have used the ‘Project Status’ field as per below snapshot for the Project Center Summary view.

 

 Option 2: Daily Schedule Back up/Administrative Back up

a. Configure the daily schedule back up or perform the Administrative Back up as per TechNet link below –

Daily Schedule Back-up       http://technet.microsoft.com/en-us/library/jj590896(v=office.15).aspx

Administrative Back-up     http://technet.microsoft.com/en-us/library/dd207304(v=office.15).aspx

b. Make sure to validate the project availability in the archive database before you delete it. Steps as below –

Launch Project Web App > Server Settings > Administrative Restore

c. Once you have confirmed the project availability in the Archived DB then you are ready to delete the project so that it won’t appear in the Project Center. Following are the steps:

Project Web App > Server Settings > Delete Enterprise Objects > Select the project you want to delete > Make sure the option ‘Delete the associated Microsoft SharePoint Foundation sites is not ticked.  Refer snapshot below:

 Note: In case you need to restore the deleted project in future if required then you can associate the existing Project site after restoring the Project. If you tick this option while deleting your project then the Project site will be deleted permanently as Daily Schedule back up/Administrative back doesn’t archive a Project site.

How to Edit/Access your Schedule in Project Server

Environment: Project Server 2010/2013

Solution: Use 1 of the 2 below options

Option 1 – Using Project Web App
Logon with User PM/Admin Credentials to Project Web App > Projects > Click on the Project Name > Click on the Schedule PDP > Click on Task Tab > Click on Edit > In Microsoft Project

Note: If you are not able to see the schedule EPT for a project then you need to contact your admin to configure it for that Project Type.

Option 2 – MS Project connected to Project Server

Directly via MS Project. Open the MS Project via connecting to the Project Web App. (Assuming PM has configured the Project Web App URL in MS Project in local machine).

FYI, Steps as below:

1. Launch the MS Project 2010/2013 then Click the File tab to open the backstage view > Click Info > Manage Accounts.
2. In the Project Server Accounts dialog box, click Add.
3. In the Account Properties dialog box, type a name for account in the Account Name box.
4. In the Project Server URL box, type the complete UAT server name (for example, https://ProjectServer/PWA).
5. To make this your default Project Server account, select the Set as default account check box.
6. To log on to the enterprise schedule via MS Project, close and restart MS Project.

Note: User should have edit rights to make changes in the schedule.

Hope this helps you. Thanks.

Error: The content type text/html

Environment: Project Server 2013, SQL Server 2012

Background: When access the SSRS report in Business Intelligence, it gives the below error message

The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+msbin1). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: ‘<!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN” “http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd”> <html xmlns=”http://www.w3.org/1999/xhtml”> <head> <title>IIS 8.0 Detailed Error – 500.19 – Internal Server Error</title> <style type=”text/css”> <!–body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;} code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;} .config_source code{font-size:.8em;color:#000000;} pre{margin:0;font-size:1.4em;word-wrap:break-word;} ul,ol{margin:10px 0 10px 5px;} ul.first,ol.first{margin-top:5px;} fieldset{padding:0 15px 10px 15px;word-break:break-all;} .summary-container
fieldset{padding-bottom:5px;margin-top:4px;} legend.no-expand-all{padding:2px
15px 4px 10px;margin:0 0 0 -12px;} legend{color:#333333;;margin:4px 0 8px
-12px;_margin-top:0px; font-weight:bold;font-size:1em;}
a:link,a:visited{color:#007EFF;font-weight:bold;}
a:hover{text-decoration:none;} h1{font-size:2.4em;margin:0;color:#FFF;}
h2{font-size:1.7em;margin:0’.

Report deployment throws below error:

An unexpected error occurred while connecting to the report server. Verify that
the Reporting Services Service Application mapped to this web application is
available OR the report server is available and configured for SharePoint
Integrated mode. à
The content type text/html; charset=utf-8 of the response message does not
match the content type of the binding (application/soap+msbin1). If using a
custom encoder, be sure that the IsContentTypeSupported method is implemented
properly. The first 1024 bytes of the response were: ‘<!DOCTYPE html PUBLIC “-//W3C//DTD
XHTML 1.0 Strict//EN” “http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd”>

<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>IIS 8.0 Detailed Error – 500.19 – Internal Server
Error</title>
<style type=”text/css”>
<!-– body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;}
code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;}
.config_source code{font-size:.8em;color:#000000;}
pre{margin:0;font-size:1.4em;word-wrap:break-word;}
ul,ol{margin:10px 0 10px 5px;} ul.first,ol.first{margin-top:5px;}fieldset{padding:0 15px 10px 15px;word-break:break-all;} .summary-container fieldset{padding-bottom:5px;margin-top:4px;}
legend.no-expand-all{padding:2px 15px 4px 10px;margin:0 0 0 -12px;}
legend{color:#333333;;margin:4px 0 8px -12px;_margin-top:0px; font-weight:bold;font-size:1em;}
a:link,a:visited{color:#007EFF;font-weight:bold;} a:hover{text-decoration:none;}
h1{font-size:2.4em;margin:0;color:#FFF;} h2{font-size:1.7em;margin:0’. à The content type text/html; charset=utf-8 of the response message does not match the content type of the binding
(application/soap+msbin1). If using a custom encoder, be sure that the
IsContentTypeSupported method is implemented properly. The first 1024 bytes of
the response were: ‘<!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>IIS 8.0 Detailed Error – 500.19 – Internal Server
Error</title>
<style type=”text/css”>
<!– body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;}
code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;}
.config_source code{font-size:.8em;color:#000000;}
pre{margin:0;font-size:1.4em;word-wrap:break-word;} ul,ol{margin:10px 0 10px 5px;} ul.first,ol.first{margin-top:5px;} fieldset{padding:0 15px 10px 15px;word-break:break-all;} .summary-container fieldset{padding-bottom:5px;margin-top:4px;} legend.no-expand-all{padding:2px 15px 4px 10px;margin:0 0 0 -12px;} legend{color:#333333;;margin:4px 0 8px -12px;_margin-top:0px; font-weight:bold;font-size:1em;} a:link,a:visited{color:#007EFF;font-weight:bold;} a:hover{text-decoration:none;} h1{font-size:2.4em;margin:0;color:#FFF;} h2{font-size:1.7em;margin:0’.
The remote server returned an error: (500) Internal Server Error.

ULS Log Error Details:

System.Net.WebException: The remote server returned an error: (500) Internal Server Error.    At System.Net.HttpWebRequest.GetResponse()     at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

 

Cause: This issue occurs when Reporting files is not under 15 hive as per below path –

\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\WebServices\Reporting which is mapped to SSRS Service?

Please note If you have used the ISO for SQL Server 2012 with SP1 that was released on November 8th does not install SP1.

http://support.microsoft.com/kb/2783963?wa=wsignin1.0

If you downloaded the ISO prior to November 27, it means you have a BAD ISO VERSION.

Solution:

To fix the issue you need to install the SQL Server 2012 SP1 onto the SharePoint Server. Once it is installed you will notice Reporting files is available in the below path and this will fix the issue. J

\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\WebServices\

Hope this helps you.

 

 

 

 

 

How to Lock down the Content Database?

Environment: Project Server 2013

Why do you want to Lock down the Content Database?

As part of creating the Project Web App, Project server 2013 doesn’t ask you which Content databases need to be used. Instead, it picks up whatever content database is available so you need to temporarily lock down the Original SharePoint content database and  create a separate SharePoint content database for Project Server 2013 application as part of good practice. Once you have locked down the original content database then create a separate SharePoint WSS_Content database for Project Server 2013 application, afterword’s you are ready to create a Project Web Application Site which uses that content database.

Steps:

To lock down the content database, complete the following steps:

1. Log in to the Application server as the Farm administrator service account

2. Open the SharePoint Central Administration. Click the Manage Content Database under Application Management section.

3. Make below changes in the Database Capacity Settings section of the Manage Content Database setting dialog but before any changes make note of the Number of Sites so you can revert to original

• Number of Sites before a warning is generated field to 1
• Maximum number of sites that can be created in this Data field to 2

Note: Maximum number of sites should match the current number of existing created sites pointing to the content DB.

4. After step 3 you can verify your changes in the Content Database dialog.

Hope this helps!