MS Project 2010 - Access Denied Error 70

If your users are getting error similar to the following:

... try doing this:

1. Exit MS Project
2. Clear/remove all temp files from c:\windows\temp
3. Go to the properties for c:\windows\temp. Uncheck the "Read-Only" checkbox and click apply.
4. Clear/remove all temp files from C:\Users\USERNAME\AppData\Local\Temp
5. Go to the properties for C:\Users\USERNAME\AppData\Local\Temp. Uncheck the "Read-Only" checkbox and click apply.
6. Open MS Project
7. Clear Cache
8. Archive again

Project Server 2010 - Orphan baseline tasks

PROBLEM:
In the past year or so, I have been seeing the following errors in the job queue


ReportingProjectChangeMessageFailed (24006) - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmTask". The statement has been terminated..

GeneralQueueJobFailed (26000) - ReportingProjectPublish.ReportProjectPublishMessageEx



SOLUTION:

The temp workaround is to run the following SQL scripts:

select PROJ_NAME, MTB.PROJ_UID,TASK_UID,TB_BASE_NUM from MSP_TASK_BASELINES MTB

inner join MSP_PROJECTS MP on MTB.proj_uid=MP.proj_uid

where TASK_UID not in (select TASK_UID from MSP_TASKS)

order by PROJ_Name

delete from MSP_TASK_BASELINES where TASK_UID not in (select TASK_UID from MSP_TASKS) 

The permanent solution is to apply the hotfix from Microsoft... http://support.microsoft.com/kb/2598351

Project Web App Cannot connect to Project Server

PROBLEM

System.ServiceModel.FaultException`1[[Microsoft.Office.Project.Server.Interfaces.DefaultServerFault, Microsoft.Office.Project.Server.Communications, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]]: The databases are out of the range of compatibility, upgrade your databases.   Server stack trace:    

 at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)   

 at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)   

 at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)   

 at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown

 at [0]:    

 at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)   

 at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)   

 at Microsoft.Office.Project.Server.Interfaces.IAuthentication.GetUserByName(String username)   

 at Microsoft.Office.Project.Server.AuthenticationHelper.AuthenticateUserByName(String userName, Guid siteId)   

 at Microsoft.Office.Project.PWA.PJContext.AuthenticateUserForPWA(Boolean needToValidateUser, String username, Guid siteId)

PROBLEM

If you get the above, you can try the following:

1. Start and restart the Project Services

2. Run the SP Configuration Wizard on the Project Server

Userful Powershell / STSAdm Commands

During my SP2010 upgrade process, on of the challenges I have is constently running PowerShell scripts and piping the results to a file so that I can parse and create new scripts against the results.  I have been doing it using the old way... like using "> test.txt".  Than I found ou that you can use the CovertTo and Export options with better and consistent results.  Below are a few examples:


TEST-SPContentDatabase -name MyContentDB -webapplication http://intranet -serverinstance MyDBServer  | ConvertTo-Html | Out-file intranet.html


TEST-SPContentDatabase -name MyContentDB -webapplication http://intranet -serverinstance MyDBServer  | ConvertTo-CSV -Delimiter "~" | Out-file intranet.csv


TEST-SPContentDatabase -name MyContentDB -webapplication http://intranet -serverinstance MyDBServer  | Export-CLIXML intranet.xml

Other PowerShell Commands useful around Upgrade

Get-Command -noun SP* - similar to stsadm -help

Test-SpContentDatabase – discussed in this post
Upgrade-SPContentDatabase – to resume failed upgrades
Upgrade-SPEnterpriseSearchServiceApplication – Upgrade Search
Upgrade-SPSingleSignOnDatabase – Upgrade SSO
Mount-SPContentDatabase – Used to attach a database or multiple parallel databases to the farm. Essentially is nearly the same as the STSADM –o addcontentdatabase.   If you‘re doing parallel content database attach for example, this PowerShell method is recommended. You‘d simply run each ofthese in different command/management windows.
Upgrade-SPProjectWebInstance – Upgrade Project Server databases. Obviously this only applies with Project Server deployments, but I know there are definitely many out there.
Upgrade-SPEnterpriseSearchServiceApplication – Upgrade the Search Service Application Instance. This commandlet it designed to upgrade the content sources and configuration of search and to upgrade it into the new service application.
Set-SPSite  -- Can use this command to setup site collection admins

STSADM Commands useful around preparing for Upgrade

stsadm -o ExportIPFSAdminObjects

stsadm -o MergeContentDB

stsadm -o EnumAllWebs

stsadm -o DatabaseRepair [-deletecorruption]

stsadm -o DeleteSite [-force] [-gradualdelete]

stsadm -o DeleteWeb [-force]

stsadm -o ForceDeleteList

stsadm -o VariationsFixupTool

stsadm –o Upgrade (Used for build to build upgrades, including service packs.)