#ProjectServer 2010 Quick Launch configuration page issue after upgrade from #PS2007 #PS2010 #MSProject #SP2010November 28, 2011 at 2:27 pm | Posted in Administration, Fixes, Issue | Leave a comment
Tags: Project 2007, Project 2010, Project Server 2007, Project Server 2010, PS2007, PS2010
I recently investigated an issue where the Quick Launch configuration page in PWA > Server Settings didn’t display the links / sections correctly in Project Server 2010. The sections would not expand so therefore you could not change any settings for these links. The issue appears to exist only when upgrading from Project Server 2007 when the 2007 PWA site has custom links on the quick launch.
Below you can see how the Quick Launch configuration page looked in the 2007 environment:
Notice the custom SSRS link below Server Settings.
And how this page looks after upgrading to Project Server 2010:
After upgrading it is not possible to expand all sections / headings apart from the section that is at the top. In the screen shot above you can see that the Projects section is expanded, in the screen shot below you can see that after moving My Work to the top, this is now expanded but the Projects section is now collapsed.
The only fix for this that I know of is to remove the custom link from the MSP_SiteMap table in the Published database. Direct access to the Published database is not recommended or officially supported by Microsoft. If you do come across this issue I would recommend that you open a support case with Microsoft but if you want to proceed at your own risk please see the steps below. I would carry this out on a replica Test environment first before applying to any Production environment, also make sure you have full database backups.
You might need to get the SQL DBA to carry out the SQL tasks due to SQL Server access. Launch SQL Server Management Studio and run the following query against the Published database to get the SM_UID value for your custom link:
where SM_CUSTOM_TITLE = ‘SSRS’ — update the title for your custom link title
As you can see, for my custom link which was called SSRS in my PS 2007 environment the SM_UID value is B1EA03CC-7584-4F6B-9DBD-0655B6970471. Once you have the SM_UID value for your custom link you can delete the custom link using the MSP_SITEMAP_DeleteMenuItem Stored Procedure on the Published database:
Right click on the MSP_SITEMAP_DeleteMenuItem stored procedure and click “Execute Stored Procedure” as shown below:
Enter the SM_UID value surrounded by singe quotes in the Value column, so in this example I entered ‘B1EA03CC-7584-4F6B-9DBD-0655B6970471’
Click OK to execute the stored procedure and you should see the following appear:
You will need to repeat this for all custom links.
Now refresh the Quick Launch configuration page and you will see that all menu sections / headings are now expanded correctly:
You can now re add any custom links that were present in the PS 2007 environment into the PS 2010 environment:
As mentioned above, if you do find yourself with this issue I would recommended opening a support case with Microsoft but if you wish to proceed at your own risk please do so on a replica test environment before carrying this out on a Production environment.
#ProjectServer 2010 Manage Site Services group level permission issue #PS2010 #MSProject #EPM #SP2010November 22, 2011 at 1:35 pm | Posted in Administration, Fixes, Issue | Leave a comment
Tags: Project 2010, Project Server 2010, PS2010
Removed Manage Site Services permission from the Administrators security group? If you have done this and no other Project Server Security Groups have this permission enabled you will see the following error when trying to enable this permission:
The group could not be saved due to the following reason(s):
- You do not have the required permission to modify this group’s ‘Manage Site Services’ permission.
This issue is related to a post Brian Smith created regarding the same permission but at the Project Web App Permissions global level: http://blogs.technet.com/b/projectadministration/archive/2011/05/18/project-server-2010-removed-the-manager-site-services-permission-and-can-t-get-it-back.aspx
The fix is different to the one documented for the global permission in the link above but again this is an update to the Published database directly via T-SQL which is not recommended.
The fix can be found below, please run this against the Published database. I would recommend testing this on a test PWA instance first and taking full database backups beforehand.
declare @Count int
select @Count = COUNT(*) from MSP_WEB_SECURITY_SP_CAT_PERMISSIONS where WSEC_REL_UID = ’13FD872B-1DB8-4651-86B3-8F484C9B825D’ and WSEC_FEA_ACT_UID = ’55FE20B7-73D6-421A-A0A8-41B8A482AE8B’
if(@Count = 0)
PRINT ‘Relationship does not exist Manage Site Services permission row will be created now to associate Administrators group with permission’
insert into MSP_WEB_SECURITY_SP_CAT_PERMISSIONS(WSEC_REL_UID, WSEC_FEA_ACT_UID, WSEC_ALLOW, WSEC_DENY, WSEC_ACCESS)
PRINT ‘Relationship already exists Manage Site Services permission already associated with Administrators group’
Please note, you may need to update the apostrophes if you copy and paste this SQL query.
This SQL above will check if the relationship exists, if not it will then insert the row in the table to associate the Manage Site Services permission with the Administrators group.
Many thanks to my colleague Frank Merla for sharing this fix.
Tags: Project 2007, Project 2010, Project Server 2007, Project Server 2010, PS2007, PS2010, SharePoint 2007, SharePoint 2010, SP2007, SP2010
This is quick a quick post to summarise the main key areas that can be used when investigating any Project Server issues, I have included SharePoint as most would also apply to SharePoint.
Firstly I will just list the key tools / logs that can be used then go on talk about each one in more detail if needed.
- Project Server Queue
- SharePoint ULS logs / Monitoring
- IIS logs
- Windows Event logs
- Web.Config (custom errors off)
- SQL Server logs
- SQL Server Profiler
Project Server Queue
It is good practice to monitor the Project Server queue daily to make sure that jobs are processing and to catch any errors as soon as possible, as you can see below there are no jobs failed or processing currently in my test environment
If you find that a user complains about a issue that occurred the previous day, change the Job history back a day and refresh the status to see if anything failed in the queue.
If you come across any failed jobs click the message in the Error field “Click to view the error details”
A new window will pop up giving you more details on the error:
In this case I entered the incorrect SMTP server so that I could generate an error for the purpose of this post! If you scroll down the error message but don’t find anything helpful, at the end you will see a JobUID to search the SharePoint ULS logs for more details.
Copy the JobUID then take a look at the SharePoint ULS logs, which leads us on the the next area.
SharePoint Unified Logging Service (ULS) / Monitoring
I wont go into details as there is a very good MSDN article found here for 2010: http://msdn.microsoft.com/en-us/library/gg193966.aspx. The ULS log viewer is recommended, for more details:http://blogs.msdn.com/b/opal/archive/2009/12/22/uls-viewer-for-sharepoint-2010-troubleshooting.aspx
Project Server 2007 / SharePoint 2007 also uses the SharePoint ULS logs, the default locations is of the log files on the SharePoint server(s) is C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS.
Following on from the Project Server queue error, you would open up the log file that is likely to contain more details (check the Project Server manage queue page for the time that the job failed) then search for the JobUID given in the error. In this example the JobUID is 8fe02d26-8892-4144-9d27-b07f21cb3f54
Examine the logs and hopefully you should be able to workout why this failed or once you have what looks to be a meaningful error copy and paste this into your favourite Internet search engine and you might find a fix!
Also worth noting is the System Centre Operations Manager (SCOM) management pack for monitoring SharePoint / Project Server 2010: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=4419 and for Project Server 2007: http://www.microsoft.com/download/en/details.aspx?id=24107
Knowledge articles for SCOM and Project Server 2010: http://technet.microsoft.com/en-us/library/ff678247.aspx
IIS might be usefully when diagnosing page load issues. The logs can be found in the following locations by default:
IIS 6.0 – %windir%\System32\LogFiles
IIS 7.0 / 7.5 – %SystemDrive%\inetpub\logs\LogFiles
Updating the web.config file(s) is useful to see actual pages errors rather than seeing the custom friendly error if an error occurs. There are plenty of articles on the Internet about turning of SharePoint custom errors in the web.config files.
SQL Server logs
The SQL server logs can be useful when investigating issues depending on what the issue is, looking at the SQL logs you would quickly be able to identify any failed database login attempts, database locks, if a database file is full etc.
SQL Server Profiler
The SQL server profiler is a very useful tool for investigating Project Server issues, for example is you have a Project that continuously errors on save or publish you can run a SQL trace while you submit another save or publish job then look though the output and hopefully see where the issue occurs. It would help you get to the bottom of the issue, whether it is a resource issue, task or assignment issue etc. Worth noting here is, please do not make any direct database updates, make changes via Project Professional / PWA / custom code via the PSI.
For more details on the SQL Server Profiler see the following MSDN article: http://msdn.microsoft.com/en-us/library/ms187929.aspx
If you find yourself with an issue that you can’t get to the bottom of I would recommend starting a new post on the Project Server forum found here: http://social.technet.microsoft.com/Forums/en-US/category/projectserver2010
Tags: Project Server 2010, PS2010, SharePoint 2010, SP2010
This issue comes up quite frequently, users who have Office installed on Windows Server 2008 / 2008 R2 try to save a file to SharePoint and see the error “Path does not exist” as shown below:
At first it might not make sense that the path does not exist when the user can browse to that path in Internet Explorer. The reason for this is that Office applications such as Excel or Word will use the Explorer view when browsing these sites, the Explorer view relies on the WebDAV Protocol not just the HTTP protocol. Users will also see the following error when clicking the Open with Explorer on the ribbon from the same machine:
“Your client does not support opening this list with Windows Explorer”
To enable WebDAV, you will need the Web Client service running. On the server you will need to enable the Desktop Experience feature:
Add the desktop experience feature then restart the server, this will add Web Client service. Once the server has restarted, set the Web Client service start up type to Automatic then start the service. Browsing the SharePoint document libraries should now work as will the Open with Explorer functionality on the ribbon.
If you experience this issue on a client machine (Windows 7 / Vista) check that the Web Client service is running.