Description of the Project 2010 hotfix package (Project-x-none.msp): April 24, 2012

https://support.microsoft.com/kb/2598274

Description of the Project Server 2010 cumulative update package (Project server-package): April 24, 2012

https://support.microsoft.com/kb/2598152

Description of the SharePoint Server 2010 cumulative update package (SharePoint server-package): April 24, 2012

https://support.microsoft.com/kb/2598151

You can also retrieve Product support lifecycle information for any Microsoft product at https://support.microsoft.com/lifecycle

Outgoing: Users in the specified domain can authenticate in the local domain, but users in the local domain cannot authenticate in the specified domain. This trust is not transitive. Only users from the directly trusted domain may authenticate in the trusting domain.

In a one way trust scenario if the PSVR is configured using the domain A service account, Active Directory sync will not work as Domain A service account does not have access to read the Domain B resource information. However, You can use domain B account as service account and reconfigure the service application and application pool accounts in Project Server farm. I would suggest to reconfigure the farm using all the service accounts from Domain B to avoid any other access related issues.

Few of the recommendations around successful AD Sync

• Avoid having Inactive users in AD group. This may cause AdminNTAccountNotFound error,
• Avoid empty AD groups
• Avoid nested groups with circular dependencies.
• Avoid duplicate accounts. This may cause 'ResourceNameAlreadyInUse' error.

And you are good to go.

An extract from the link https://technet.microsoft.com/en-us/library/gg982985.aspx

Note:

Project Server 2010 does not support synchronizing your Enterprise Resource Pool or security groups with Active Directory users across different domains in which only a one-way trust relationship exists between domains. It is possible for Active Directory user to synchronize with SharePoint Server 2010 in a cross-forest deployment in which a one-way trust relationship exists between domains (see Resolve accounts across multiple forests (SharePoint Server 2010). However, Project Server 2010 does not support this scenario.

 

List of all 2007 Office system SP3, 2007 Office servers SP3, and Windows SharePoint Services 3.0 SP3 packages

2596533 Project 2007

2596542 Project Server 2007

SP3 does not include October 2011 CU. You will have to install both SP3 and October 2011 CU to be up to date.

More details about the SP3 for WSS and SharePoint Server 2007

Service Pack 3

+ System

  - Provider

   [ Name]  Microsoft-SharePoint Products-Project Server
   [ Guid]  {B2178104-1B5B-4C20-8C8F-960678CED9E5} 
   EventID 6971 
   Version 14 
   Level 2 
   Task 20 
   Opcode 0 
   Keywords 0x4000000000000000 
  - TimeCreated

   [ SystemTime]  2011-11-07T07:30:51.139721000Z 
   EventRecordID 96009 
  - Correlation

   [ ActivityID]  {A8047DDA-9EB8-4659-94EC-D379C1843849} 
  - Execution

   [ ProcessID]  3728
   [ ThreadID]  9140 
   Channel Application 
   Computer projectserver.com 
  - Security

   [ UserID]  S-1-5-21-1987276620-123495779-302720296-236687
- EventData

  string0 PWA 
  string1 Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SPWebApplication Name=SharePoint - 80 was updated by projectserver\epm, in the STSADM (6368) process, on machine projectserver. View the tracing log for more information about the conflict. at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure) at Microsoft.SharePoint.Administration.SPConfigurationDatabase.Microsoft.SharePoint.Administration.ISPPersistedStoreProvider.PutObject(SPPersistedObject persistedObject, Boolean ensure) at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate() at Microsoft.SharePoint.Administration.SPWebApplication.Update() at Microsoft.SharePoint.Administration.SPAutoSerializingObject.UpdateParent() at Microsoft.SharePoint.Administration.SPPrefixCollection.UpdateParent() at Microsoft.SharePoint.Administration.SPPrefixCollection.Add(String strPrefix, SPPrefixType type) at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.AddExplicitInclusionPrefix(SPWebApplication& webApp, String prefix) at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateWSSSite(ProjectProvisionSettings provset, SPWebApplication parentWebApp, String adminName, String adminEmail, String secondaryAdminLogin, String secondaryAdminName, String secondaryAdminEmail, SPSiteStatus& siteStatus)

Well, this was caused due to the SharePoint Cache. Resolution steps provided at the KB to clear the SharePoint Cache https://support.microsoft.com/kb/939308 should help to fix this issue. The article is for 2007 but it goes well with 2010 as well. Now there could be different object in the error. Here you could see that the object name was SPWebApplication Name=SharePoint - 80. There is a possibility that the object you might have in the error is different than this one. So just check before you jump on to the next step to fix the issue.

Before running the macro let's ensure that the item is not associated with any of the Resources or Tasks before deleting the same.

First create a list of projects in “Projects.txt” – each project name on a new line.

• Save this file on the C:\
• Open the Project Pro
• Go to the Visual Basic Editor
• Copy and paste the below Macro in any of the Module.

Function RemoveCalendars()

' Macro RemoveCalendars

' Macro Recorded by Maulik Raval.

On Error Resume Next

i = 0

fspec = "c:\Projects.txt"

Set fso = CreateObject("Scripting.FileSystemObject")

Set ots = fso.OpenTextFile("c:\Projects.txt", 1)

Do Until ots.AtEndOfStream

k(i) = ots.readline

i = i + 1

Loop

Set prjApp = CreateObject("Msproject.Application")

For j = 0 To i - 1

If prjApp.FileOpen("<>\" & k(j), False) = True Then

OrganizerDeleteItem Type:=5, FileName:=k(j), Name:="CalendarName"

prjApp.FileSave

bool = prjApp.FileCloseEx(pjSave, , True)

End If

Next j

Set prjProject = Nothing

Set prjNewProject = Nothing

Set prjApp = Nothing

End Function

• Run this macro.

Here Type 5 Indicates Calendar.

Below are the other Types and what it indicates.

Type:=0 = View
Type:=8 = Forms
Type:=5 = Calendar
Type:=4 = Reports
Type:=1 = Tables
Type:=6 = Toolbars
Type:=10 = Groups
Type:=3 = Modules
Type:=2 = Filters
Type:=7 = Maps
Type:=9 = Fields

Enjoy!!!!

https://servername/pwa
The SharePoint item being crawled returned an error when attempting to download the item.

To resolve this we will need to change the registry key value for the "UserAgent".

The original value is set to
Mozilla/4.0 (compatible; MSIE 4.01; Windows NT; MS Search 6.0 Robot)

We need to change this to the one below
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.3; .NET4.0C; MS-RTC LM 8; Tablet PC 2.0)

And here are the steps.

Ensure that you have taken the full back up of the Registry before making any changes.
Open the Registry Editor
Now locate and replace the user agent key’s value in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Global\Gathering Manager\UserAgent
with this value: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.3; .NET4.0C; MS-RTC LM 8; Tablet PC 2.0)

Restart the server after making the changes.

Run the full crawl again.

You will notice that searchable items number will increase from the previous number.