Project Server 2010 PWA Site corrupted? default.aspx Corrupted, contains jibberish?

Hey Everyone,
Running Project Server 2010 Server w/ SQL Server 2008 R2 back end
Sometime after 5:30 pm Friday , our main PWA site url which is
http://servername/PWA now contains the below mess of characters and text... seems the default.aspx file located in
\\servername/PWA share got corrupted, messed with? ANY ideas how to fix this? or how why this happened. really need a fix...... Thanks
Jack Galante Sr Systems Engineer

Jack,
Are you the Project Server Administrator?Does this happen for all users or just one? If just one, please see if the users system is the issue.
If it is all users, then Do you know if anybody else with approproate permissions added any custom code?
I am not really sure of the issue here. Here are a few things you could try:
1) Reboot all the servers
2) Restart the Project Server related services like Events Service and Queue Service
3) Navigate to Central Admin, and see if you restart the Project Application Service.
If none of the above work, then I would recommend contacting Microsoft Support before making any further changes.
Prasanna Adavi,PMP,MCTS,MCITP,MCT http://thinkepm.blogspot.com

Similar Messages

Need to send a email alert to Projectmanger when publishing a project in project server 2010 PWA site

Hi All
When creating and publishing a project in PWA(server 2010) need to send a mail alert to the concerned project manager.
How can i achieve this..
I have configured the outgoing mail sending in sharepoint and its working fine now.
Please help me..
Thanks Advance
SharePoint Module Lead Assyst International Private Ltd Cochin India

Nothing is built in Project Server to do this for you automatically.
They way I have done this in the past is to create a SQL job using SSIS. It runs every hour and when it sees a project schedule that has a recent PUBLISHED date then this is a trigger to send an email to project manager.
Cheers!
Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
Website http://www.WhartonComputer.com
Blog http://MyProjectExpert.com contains my field notes and SQL queries

Project Server 2010: PWA Removing Default Project Site Security Groups When Creating a New Project

I looked for this specific issue with Project Server 2010/PWA/SharePoint and could not find an exact answer... hopefully someone can help.
We are currently using Project Server 2010 and have a number of project site templates that are used dependent upon the enterprise project type selected. Each of these project site templates have unique permissions which should create the default security
groups on the project site upon publishing/syncing:
<Project Name> Members
<Project Name> Owners
<Project Name> Visitors
<Project Name> Project Managers (Project Web App Synchronized)
<Project Name> Team Members (Project Web App Synchronized)
Web Administrators (Project Web App Synchronized)
Whether a user creates a project through PWA or Project Pro 2010 and imports the project into PWA, we get a weird result in the Site Permissions of the newly created project site. PWA will remove all default security groups from the project site template
and add a whole list of users in the Site Permissions list without groups.
Once the project is published and the project site is created, we can then go back and add those default security groups back in the project Site Permissions and even add a couple of custom groups without them being removed on all subsequent project syncs
or publishing.
How do we get PWA to not overwrite the project site templates' security groups and place each user in the proper default security groups? At the same time, how is PWA adding a number of users into the Project Site Permissions?
Thanks in advance.

Paul,
Thanks for that information. Right now we are using the Test environment to turn the Auto-sync feature back on. I suspect that the reason this is happening is due to PWA groups/categories/security templates. There may be more than one PWA group that is "overwriting"
the default project site groups upon initial creation of the project. We will look further into the security settings to tighten up the policies.

Project Server 2010 PWA Provisioning Error - System.UnauthorizedAccessException: Access is denied.

Hi,
When migrating from a Prod Environment to a Test Environment using the Project Server 2010 5 Database backup and restore process (actually 6 DB's with the Project Sites DB), upon encountering a failure during provisioning the PWA Instance, we get the errors listed
at the base of this posting in our Event Logs.
To clarify what we have done already, we have:
1. Backed up the 6 databases from the Source Environment.
2. Removed the existing PWA_Content and PWS_Content (Project Sites) databases from the Target Environment Farm.
3. Restored the 6 databases in the Target Environment.
4. Given the SP Farm Service Account 'db_owner' rights to each of the 6 restored databases.
5. Added the PWA_Content and PWS_Content databases (exact same names) to the Target Environment.
6. Locked down (offline/stopped), all of the SharePoint Content databases in the Farm except for the PWA_Content database.
7. Run the PWA Provisioning process from the 'Project Server' SharePoint Service in Central Admin.
It is during the PWA provisioning that we encounter these errors.
As the Target Environment is for Test/Dev purposes, the SP Farm Service Account is setup to support all of the SharePoint Farm Services, is in the Local Admin Group of each of the Servers (App, WFE and DB), and is actually in the sysadmin
role on the DB Server.
Any suggestions on what is causing this denied access situation would be most appreciated.
Cheers,
Wayne
Event Log Entries:
============================================
Log Name:      Application
Source:        Microsoft-SharePoint Products-Project Server
Date:          1/22/2014 2:47:34 PM
Event ID:      6971
Task Category: Provisioning
Level:         Error
Keywords:
User:          ACCOUNTS\svc_psfarm
Computer:      SERVER.accounts.domain.com
Description:
Failed to provision site PWA with error: Microsoft.Office.Project.Server.Administration.ProvisionException: Membership synchronization failed. ---> System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
   at Microsoft.SharePoint.Library.SPRequest.AddRoleDef(String bstrUrl, String bstrName, String bstrDescription, Boolean bHidden, Int32 lRoleOrder, UInt64 iPermMask, Byte iType, Int32 lRoleDefID)
   at Microsoft.SharePoint.SPRoleDefinitionCollection.AddCore(SPRoleDefinition role)
etc....
Failed to create the Report Center web (Exception: PSI Entry Point:
Project User: DOMAIN\svc_psfarm Correlation Id: c0a30b18-46e4-4447-b469-f8fd3bb1490a
PWA Site URL: http://pstest2010/PWA
SSP Name: Project Server
PSError: NoError (0))
Failed to grant 'DOMAIN\svc_psfarm' access to web application 'SPWebApplication Name=Portal'.
Error: System.Security.SecurityException: Access denied. Only machine administrators are allowed to create administration service job definitions of type: Microsoft.SharePoint.Administration.SPUpdateWorkerProcessGroup, Microsoft.SharePoint, Version=14.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c.
   at Microsoft.SharePoint.Administration.SPAdministrationServiceJobDefinition..ctor(String name, SPService service, SPServer server, SPJobLockType lockType)
   at Microsoft.SharePoint.Administration.SPUpdateWorkerProcessGroup..ctor(SPTimerService timerService, String[] loginsToAdd, String[] loginsToRemove)
   at Microsoft.SharePoint.Administration.SPWebApplication.GrantAccessToProcessIdentity(String username, SPPolicyRoleType policyRole)
   at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.GrantAccessToWebApp(List`1 webApps, String userName) The Zone of the assembly that failed was: MyComputer

Is the Test and Production in the same domain. If they are not, then the SIDs associated with the SQL accounts may look the same but they are not. At times, I have had to recreated accounts when in different domains.
I would also use PowerShell cmdlets and see if it finds any issues, such as Test-SPContentDatase.. Validate the SharePoint content databases, because if not setup properly the Provisioning will fail.
Also check these properties.
$web=get-spweb http://prodproj01/pwa
$Web.AllProperties[“PWAURL”] ### see what the value is.. you may have to blank it out, specially if it is pointing to a different URL
Here is how to fix.
$Web.AllProperties[“PWAURL”]=””
$web.Update()
Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
Website http://www.WhartonComputer.com
Blog http://MyProjectExpert.com contains my field notes and SQL queries

Project Server 2010 PWA - attempting to move folders from root to document library subfolder does not work

Hello all,
We have an issue whereby attempting to move documents from the top level folder to a subfolder in a PWA site appears to work initially, but within a few minutes the documents are moved back to the top level folder with no error message.
Uploading a document has the same effect.
Permissions are granted at all levels in the document folder.
Only some users seem to be affected.
Only some project sites are affected.
As an admin user I can successfully upload and move documents without issue.
Any thoughts on what might cause this ? I've actually never seen this before (and I have worked on a lot of SharePoint/Project Server deployments) so interested to know if anyone out there has a bright idea on how this might get fixed ?
Many Thanks

Hi,
I understand you encountered the issue when save document from Office client application to SharePoint 2010 site.
Is there any Proxy settings in networking side? Please bring up IE > Internet options > Connections > Lan settings. If so, please uncheck options in Proxy server and test the issue again.
If you have deploy GPO to add SharePoint site into Trusted sites, please check if there is any other GP associated with trusted sites that might affect the issue. You could also remove it from Trusted sites via IE options and test the issue again.
In addition, please provide more error message to help narrow down the issue, you could locate error information in Event log at least.
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

Project Server 2010 (PWA Timesheet) Error

Hello,
I am an administrator for Project Server and had a resource submit a timesheet in error. The timesheet was approved at the time and recalled by the resource at the same time. When the resource had tried to recall, they received back an error. I delegated
as the resource and tried to recall it as the user but it gets stuck with the green loading picture and never moves past that. It seems the status update was accepted when it got approved and now the timesheet is "stuck". From the user's standpoint,
it shows only as "Submitted" in their Timesheet status, but somehow it does not let me delete the timesheet. The error received is saying Invalid object, timesheet failed/blocking correlation. Anyone have any idea how to resolve this? Can't seem
to fix this error.
This is the error i get in return:
Timesheet:
GeneralInvalidObject (20009). Details: id='20009' name='GeneralInvalidObject' uid='fc00fed3-1cb1-48b2-83b6-800b03b33f1d' parameter='nextApproverUID'.
Queue:
GeneralQueueJobFailed (26000) - TimesheetReview.ReviewTimesheetMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='fbebdb81-29b5-416b-818d-a085a4f1d808' JobUID='e9104f34-f416-4b89-9d3e-8574a868e065' ComputerName='WEGSFES29090'
GroupType='TimesheetReview' MessageType='ReviewTimesheetMessage' MessageId='1' Stage=''. For more details, check the ULS logs on machine
WEGSFES29090 for entries with JobUID e9104f34-f416-4b89-9d3e-8574a868e065.
Thanks!

Is the Test and Production in the same domain. If they are not, then the SIDs associated with the SQL accounts may look the same but they are not. At times, I have had to recreated accounts when in different domains.
I would also use PowerShell cmdlets and see if it finds any issues, such as Test-SPContentDatase.. Validate the SharePoint content databases, because if not setup properly the Provisioning will fail.
Also check these properties.
$web=get-spweb http://prodproj01/pwa
$Web.AllProperties[“PWAURL”] ### see what the value is.. you may have to blank it out, specially if it is pointing to a different URL
Here is how to fix.
$Web.AllProperties[“PWAURL”]=””
$web.Update()
Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
Website http://www.WhartonComputer.com
Blog http://MyProjectExpert.com contains my field notes and SQL queries

Project Server 2010 PWA Printing Issue

we are having issues when printing from the Project Web App schedule web part where if they went over a certain number of rows (around 42 – spooky!) the printed page was blank (although the pop-up with just the grid displayed for printing
looked just fine). This was after seeing this warning – which is expected – when you are printing a grid of more than 30 rows: Print Warning - There are more than 30 records in the current grid.
In my testing internally I saw the same, I clicked OK on the warning, the new page opened with everything looking good and I could choose my printer – but the print was blank (I did try a large plan and in this case the final 40 or so tasks printed…)
However, if I turned off the compatibility setting under Tools, Compatibility View Settings, so that these were not applied to Intranet sites then the project page does not open and it says it requires IE 7 or above for it to open.
Regards,
Ankit Manchanda

Ankit,
Make sure that you have updated printer drivers, also try using different printer model
Hrishi Deshpande Senior Consultant

Issue in Custom Filter in PWA of Ms Project Server 2010

Hi,
i am facing an issue on setting a cutom filter in the Project Center view of PWA. I am setting a custom filter and it works fine.
Projects are filtered as per the filter. However, on selecting the filter for editing, I get a message viz. "Failure. There was an error processing the request".
I am looking for pointers and guidance to resolve this issue. Any helpin this regard will be appreciated.

Hi,
Evenif you already checked this out, it is likely to be a security issue. This functionality is managed by permissions in PWA server settings and not in the Central Admin.
Check this article :
http://msprojectnow.com/Blog/tabid/142/entryid/556/Enabling-Task-Sheet-functionality-to-Add-Yourself-to-a-Task-in-Project-Server-2010-PWA.aspx
Check if you're not belonging to multiple categories that might have the given permission disabled.
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

Any good training videos for project server 2010

Hi All,
I am working on SharePoint for several years and we had installed project server & created PWA site. But project server looks lot different from SharePoint. is there any good training video's for project server 2010?
Thanks for any help
Rithu

Rithu,
This would be a good place to start: http://technet.microsoft.com/en-us/library/ff628958(v=office.14).aspx
There are also several videos on Youtube as well. I am not sure if there is a 'structured' course available for Project Server 2010
Cheers,
Prasanna Adavi, Project MVP
Blog:
Podcast:
Twitter:
LinkedIn:

Reports permission in Project server 2010

Hi,
I have reports created in SSRS, i need to bring those reports to Project Server PWA. How to do that? i need the steps.
Reports like Number of active resources working in Project, Number of projects in that PWA instance.
My requirement is, i have a structure like Executives - Program Managers1- 1.Project Manager 2. Project Manager.
Program Manager2 - 1. Project Manager 2. Project Manager.
Each program manger has to see only their projects(the project which comes under him) in PWA not the other Program Manager's project and Project Manager has to see only his project not the other project manager's project in the same program.
I have Executive who should see all the projects in the organization.
Can someone assist me how to execute in Project Server 2010 PWA?
K.Gokulraj

Hello,
Sounds like you might need to use the project server security to filter the data in the reports, take a look at this example:
http://msdn.microsoft.com/en-us/library/office/ee862408(v=office.12).aspx
To get the reports in side PWA there are several options. As you are querying this I guess SSRS in not SharePoint Integrated mode? If in SSRS Native mode you can just add page viewer web parts on the pages in the PWA site then reference the report server
report URL.
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Project Professional 2010 Not Publishing to Project Server 2010

I am having trouble publishing a project from Project Professional 2010 to the Project Server 2010 (PWA). What I am trying to publish is a master project which is contains many enterprise projects as subprojects. When I press publish, it prompts me
to save and if I click yes then it goes through and saves all the subporjects and then just stops there and doesn't publish the changes to the master project. If I press publish and click no to the save prompt then it gives me the status "sychronizing
data to server" for around 15 seconds and then just does nothing after the sychonization finishes.
It usually should be giving a "publishing job done 0%" or "publishing job completed" when it publishes, but it gives nothing like that. I also check the project through the PWA and it has not updated yet, but when I open it for editing in the client it has
everything updated and up to date, meaning that the save is working properly and just not the publishing.
All my subprojects are able to publish correctly, it's just this master project that is not working.
Does anyone know why this is happening? Is the publishing process timing out for some reason? Or is it something else?
Please help.
EDIT: The progress notification at the bottom of Project Professional just stops at "save completed sucessfully" whenever I try to publish

To check the queue, navigate to Server Settings > Manage Queue and view the jobs that are present. If there is an error when publishing you should see it in the queue.
Alex Burton
www.epmsource.com |
Twitter
Project Server TechCenter |
Project Developer Center |
Project Server Help | Project Product Page

Error when navigating to the PWA root site for Project Server 2010

I received a nice Happy New Year from my Project Server 2010 today. I tried to navigate to the root site and received the following error.
Error
The base type 'Microsoft.Office.Project.PWA.PJBaseWebPartPage' is not allowed for this page. The type is
not registered as safe.
Troubleshoot
issues with Microsoft SharePoint Foundation.
Correlation ID: b1898d3e-5d41-4ed4-9466-1d7775714293
Date and Time: 1/3/2012 10:54:53 AM
I did some searching and found that it could be one of 2 things
1.
App Pool security
2.
Custom Master page.
All the sub-sites seem to work fine, so I went with option 2. I changed the Master page of the root site back to v4.master and everything works fine again.
So far the only solution I found to allow for using a Custom master page is to modify the web.config as suggested here:
http://jimecox.wordpress.com/2011/05/03/project-server-2010-changing-master-page/
My custom master was working fine for the past 6 months, so I’m not sure why I need to make this new update.
Anyone else run into this recently with another fix? The changes seem to be opening the security on the Project web app a bit or am I wrong?
Thank you in Advance!

Looks like I fixed this by changing the Master page back to the OOTB version v4.master here:
https://<pwa url>/_Layouts/ChangeSiteMasterPage.aspx
Then I navigated to the PWA root site.
https://<pwa url>/default.aspx
Finally changed the master page back to my custom one. Error gone!

Project Server 2010 / Sharepoint 2010 Permissions not syncing to Project Site

Project Permissions not syncing to Project Site
Project Manager Group
New project is created and published project server sends permissions to Sharepoint which puts users into the following groups:
<dir><dir></dir></dir><dir><dir>
Web Administrator (Microsoft Project Server)
Project Managers (Microsoft Project Server)
Team members (Microsoft Project Server)
Readers (Microsoft Project Server)
At this time the creator/owner, owner’s management, portfolio managers, and executives should all have Project Manager rights on the sharepoint site, and Admins will have Web Admin permissions.
Issue #1: Only the Web Admin permissions and creator/owner permissions are being added to the Sharepoint permission groups
Workaround #1: Going into the project site permissions and adding the
Project Managers (Microsoft Project Server) group manually and the sync will keep the permissions
Workaround #2: Going into the Server Settings, Manager Groups then removing or add all users to the No Permission Group, which forces an sync to all workspaces. Con: This workaround can only be down at night when users are not active since it will
block the queue for at least an hour.
Project Owner Transfer
Previously created project has owner change, once saved and published project server sends permissions to update user’s permission to
Project Managers (Microsoft Project Server) on Sharepoint project site.
Issue #2: When Project owner is changed and project is published the owner is not getting permissions to the Sharepoint project site. However, if owner is also added to the team using the Build Team Feature the sync will give the owner Project
Manager permissions on the Project Site.
Workaround #1: Going into Server Settings, Project Sites, select project and Synchronize. Once this is done, the owner will have Project Manager Permissions without being added to the team.
Users who have been added to this project in Project Server 2010, but not assigned to tasks. Users who have assignments in this project in Project Server 2010 and are contributors to the project workspace site,
meaning that they can create and edit documents, issues, and risks. Users who have published this project or who have
Save Project permission in Project Web App and are contributors to the project workspace site, meaning that they can create and edit documents, issues, and risks. Users who have
Manage SharePoint Foundation permission in Project Web App and are contributors to the project workspace site, meaning that they can create and edit documents, issues, and risks.</dir></dir>

By default when you create project build team add users in the task and publish the project plan then All the User which are available in the project plan including Project owner will go to below mentioned group in project site:
1. creator/owner, owner’s management, portfolio managers, and executives should all have Project Manager will get access to Project Managers (Microsoft Project Server)
2. User who are having team member access to PWA will get Team members (Microsoft Project Server) access if they are assigned to the project task.
3. User who are having team member access to PWA will get Readers (Microsoft Project Server) access if they are not assigned to the project task.
4. Only PWA Administrator will get the access to Web Administrator (Microsoft Project Server)
Sharepoint permission you have to use when you want to give permission manually to users on project site
In the Project Site provisioning setting under Server setting if you have Check to automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions change in Project
Server.
Then all the user get access as per describe above and if you will give access manually to any of the user either in project server group or in Sharepoint group once you will publish the project next time all the manually given permission will go away.
IF you want to give permission to user manually to sharepoint group or project server group then uncheck automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions
change in Project Server.
You check PWA site setting --> Site permission then member of Sharepoint group user who will have access to sharepoint group in PWA site setting site permission will have access to all the project site sharepoint group as Project site inherit permission
from PWA root site.
Both the issue which you have described is behavior of project site.
For issue 2 when first time project owner create and publish the project and projectsite is getting created then porject owner name gets access in the porject manager (project server group) nect time if you will change the owner and publish the project
until he will not present in the project plan will not get the permission.
If you want to give sharepoint permission to users then uncheck automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions change in Project Server and give
the permission manually.
Project site in 2010 has some issue and not full filling customer need some time ,Ms has came up with 2013 which is having tight integration with project sites .
Project workspace security groups are equal to the SharePoint Server 2010 security groups.
Web Administrator equals Full Control
Project Managers equals Design
Team members equals Contribute
Readers equals Read
Users who have Manage
SharePoint Foundation permission in Project Web App and are contributors to the project workspace site, meaning that they can
create and edit documents, issues, and risks will get access to Web Administrator (Microsoft Project Server)
http://technet.microsoft.com/en-us/library/cc197668(v=office.14).aspx
kirtesh

Project Server 2010 - Assigned tasks not visible in PWA

Hi,
When I enter an issue on a project site, the assigned issue is not visible in the PWA under Issues & Risks.
Based on this link (http://social.technet.microsoft.com/Forums/en-US/f5abd024-3c9a-47f8-a7cb-7743fafebf2b/project-server-2010-cannot-see-assigned-issues-and-risks) I have tried to solve it however without success.
In the queue jobs I have the following error details:
General
Reporting Wss list sync failed:
ReportingWssSyncListFailed (24018) - 1100. Details: id='24018' name='ReportingWssSyncListFailed' uid='6c8a0779-3c9f-4d25-a81c-04d69d6fce1d' SPListType='2136b7a0-03b9-4547-8b2d-c66497accd08' Error='1100'.
ReportingWssSyncListFailed (24018) - 1101. Details: id='24018' name='ReportingWssSyncListFailed' uid='1573855e-b176-44cc-bf92-8959d167f8fe' SPListType='2136b7a0-03b9-4547-8b2d-c66497accd08' Error='1101'.....................................
Reporting message processor failed:
ReportingWSSSyncMessageFailed (24016) - RDS failed while trying to sync one or more SP lists. The RDS queue message will be retried.. Details: id='24016' name='ReportingWSSSyncMessageFailed' uid='839ed0b8-6b8c-4bd5-bfbe-540349c1f27a' QueueMessageBody='ProjectUID='2136b7a0-03b9-4547-8b2d-c66497accd08'.
ForceFullSync='False'. SynchronizationType='All'' Error='RDS failed while trying to sync one or more SP lists. The RDS queue message will be retried.'.
ReportingWSSSyncMessageFailed (24016) - RDS failed while trying to sync one or more SP lists. The RDS queue message will be retried.. Details: id='24016' name='ReportingWSSSyncMessageFailed' uid='b0e773af-5cc3-4965-85b3-a4d8050e86f5' QueueMessageBody='ProjectUID='2136b7a0-03b9-4547-8b2d-c66497accd08'.
ForceFullSync='False'. SynchronizationType='All'' Error='RDS failed while trying to sync one or more SP lists. The RDS queue message will be retried.'............................................
Queue:
GeneralQueueJobFailed (26000) - ReportingWSSSync.WSSSyncMessageEx. Details: id='26000' name='GeneralQueueJobFailed' uid='07edaa28-647c-4dee-974e-06f47e4b4e40' JobUID='899bd048-2c19-4176-bd6c-1b45b8379a40' ComputerName='NLHGOL7FPR' GroupType='ReportingWSSSync'
MessageType='WSSSyncMessageEx' MessageId='1' Stage=''. For more details, check the ULS logs on machine NLHGOL7FPR for entries with JobUID 899bd048-2c19-4176-bd6c-1b45b8379a40.
As I understand this error could be due to a mismatch between the fields that are 'standard' in the project server and fields that are op the project site.
If the reporting database could not sync, will consequently also the issues not be visible on the PWA??
Any suggestions how to solve this?
Regards,
Dirk

Hello,
Yes, if the Issues & Risks are not being synchronised to the Reporting database then this will impact the issues & risks appearing on the PWA homepage reminders web part. See this post on how the data gets to the Reminders web part in Project
Server 2010:
http://pwmather.wordpress.com/2012/07/13/projectserver-active-issues-and-risks-on-pwa-reminders-web-part-ps2010-sp2010-sharepoint/
The error you are seeing is probably caused by the default Issue or Risks columns being edited or removed from the Issues or Risks lists. It might be worth taking a look at this post:
http://pwmather.wordpress.com/2011/06/20/project-server-2010-project-site-default-fields/
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Bulk Project Site option isn't working in project server 2010 migrated from PS 2007.

Hi,
I am doing a test migration from epm 2007 to epm 2013.
So first, i need to migrate the project server 2007 to project server 2010. i have 2 separate environments for EPM 2007 and EPM 2010).
there is no problem in migration process and i successfully migrate entire PWA 2007 to 2010, except Workspaces (Project sites).
Bulk project site option is not helping. I have tried 4-5 times with different PWA 2007 databases (PWA1, PWA2...) but this option did not work. and errors in queue are WSSWebDoesNotExist(16405) and GeneralQueueJobFailed(26000).
Then next time while migrating all over again i kept the same port and same PWA name then bulk project site option worked.
Question is, Do i need to keep the same PWA name and same port for the new upgraded PWA??, one more issue regarding this is that if don't keep the same PWA name and i open the project site and click on the "Project web app" back link, it
redirects me to old PWA site which doesn't exist and give me page not found error (Obviously).
Below, you can see the both scenarios.
my previous PWA 2007 site, say - http://epm2007:2222/PWA
When - migrated PWA 2010 site, say - http://epm2010:3000/NewPWA (Bulk project site update just doesn't work)
When - migrated PWA 2010 site, say - http://epm2010:2222/PWA (Bulk project site update worked)
Whats the solution of this problem. is there any utility or query to link all project sites correctly?
Will i face the same problem while migrating PS 2010 to PS 2013??
Thank you.
sandeep

Hi,
I would say it is easier to keep the same PWA name between 2007 and 2010 (no need to have the same port).
If you want to move to a new PWA URL maybe you can use stsadm backup/restore as detailed in this article?
http://technet.microsoft.com/en-gb/library/ee662500(v=office.14).aspx
Hope this helps
Paul

Project Server 2010 PWA Site corrupted? default.aspx Corrupted, contains jibberish?

Similar Messages

Maybe you are looking for