More Details :

https://technet.microsoft.com/en-us/library/project-online-service-description.aspx

Windows Antivirus Exclusion Recommendations (Servers, Clients, and Role-Specific)

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

for our sweet products, we have these detailed info to exclude files and processes.

SharePoint

Certain folders may have to be excluded from antivirus scanning when you use file-level antivirus software in SharePoint

https://support.microsoft.com/kb/952167/en-us

IIS

IIS Server

Exclude the IIS compression directory from the antivirus software's scan list.

The default compression directory in IIS 6.0 is %systemroot%\IIS Temporary Compressed Files. This directory may have been changed to another location. In IIS 7.0, the default location of the compressed file cache is %SystemDrive%\inetpub\temp\IIS Temporary Compressed Files.

To verify the compression directory:

1. Click Start, point to Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

2. In IIS Manager, right-click the Web Sites folder, and then click Properties.

3. Click the Service tab.

Under HTTP Compression, make sure that Compress static files is selected, and then locate the path to the temporary directory.

Process Exclusions

• %systemroot%\system32\inetsrv\w3wp.exe

• %systemroot%\SysWOW64\inetsrv\w3wp.exe

SQL

SQFiles and Directory Exclusions

• SQL Server data files

  • *.mdf

  • *.ldf

  • *.ndf

• SQL Server backup files

  • *.bak

  • *.trn

• Full-Text catalog files

  • Default instance: Program Files\Microsoft SQL Server\MSSQL\FTDATA

  • Named instance: Program Files\Microsoft SQL Server\MSSQL$instancename\FTDATA

• Trace files

  • *.trc - these files can be generated either when you configure profiler tracing manually or when you enable C2 auditing for the server.

• SQL audit files (for SQL Server 2008 or later versions)

  • *.sqlaudit

• SQL query files

  • *.sql

• The directory that holds Analysis Services data – default is C:\Program Files\Microsoft SQL Server\MSSQL.X\OLAP\Data.  You can view and change the data directory by using Analysis Manager. To do this, follow these steps:

1. In Analysis Manager, right-click the server, and then click Properties.

2. In the Properties dialog box, click the General tab. The directory appears under Data folder.

• The directory that holds Analysis Services temporary files that are used during Analysis Services processing – default is C:\Program Files\Microsoft SQL Server\MSSQL.X\OLAP\Data. You can view and change the directory that holds temporary files in Analysis Manager. To do this, follow these steps:

1. In Analysis Manager, right-click the server, and then click Properties.

2. In the Properties dialog box, click the General tab.

3. On the General tab, notice the directory under Temporary file folder.

Note : Optionally, you can add a second temporary directory for Analysis Services 2000 by using the TempDirectory2 registry entry. If you use this registry entry, consider excluding from virus scanning the directory to which this registry entry points

• Analysis Services backup files – default is C:\Program Files\Microsoft SQL Server\MSSQL.X\OLAP\Backup

• The directory that holds Analysis Services log files – default is C:\Program Files\Microsoft SQL Server\MSSQL.X\OLAP\Log

• Directories for any Analysis Services 2005 and later-version partitions that are not stored in the default data directory

• Note When you create the partitions, these locations are defined in the Storage location section of the Processing and Storage Locations page of the Partition Wizard.

• Filestream data files (SQL 2008 and later versions)

• Remote Blob Storage files (SQL 2008 and later versions)

• The directory that holds Reporting Services temporary files and Logs (RSTempFiles and LogFiles)

Process Exclusions

SQL Server 2012

• %ProgramFiles%\Microsoft SQL Server\MSSQL11.<Instance Name>\MSSQL\Binn\SQLServr.exe

• %ProgramFiles%\Microsoft SQL Server\MSRS11.<Instance Name>\Reporting Services\ReportServer\Bin\ReportingServicesService.exe

• %ProgramFiles%\Microsoft SQL Server\MSAS11.<Instance Name>\OLAP\Bin\MSMDSrv.exe

 https://blogs.technet.com/b/projectsupport/archive/2013/09/12/project-server-2010-service-pack2-and-august-2013-cumulative-update-installation-issues.aspx

After a 90-day period, SP2 will be offered as an automatic update through Microsoft Update. Customers using the Office Click-to-Run technology will have SP2 streamed to from August.

Download Links
for Service Pack 2

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

https://blogs.msdn.com/b/russmax/archive/2013/04/01/why-sharepoint-2013-cumulative-update-takes-5-hours-to-install.aspx

The  solutions to this issue are:

In Project 2010, use the Project Permissions feature. Or, project managers can add users manually to the project. To do this, they can use the Build-team feature where they can filter on RBS equals the project owner's and then add the returned set of users to the project.
Or
1.If you go to Manage Users and edit one of the resources and you change a property such as e-mail or initials and save and look at the users who have access to the site you will see that the user has now access to the site.
2 But if you go to Server Settings - Project Sites and select the site for the project and click the Synchronize button the edited resource will be removed from the site permissions.

One Citrix VM built on WinXP SP3 with IE8 could not open via the internet explorer in the PWA, Project Files with the Project Client. Opening
Files from the Project Client was working.

 The Problem was caused by Citrix XenConverter (this is converting the workload from a Server or Desktop virtual machine to the XenServer.)

 This is a Known Limitations in Citrix:

Open Files – XenConvert cannot copy a file in use by another application on Windows XP. To ensure that a conversion includes a file, close that application before converting.

https://support.citrix.com/servlet/KbServlet/download/28774-102-666402/XenConvertGuide.pdf

After the XenConverter was disabled everything was working fine

ms-word:nft|u|https://o15psvr:8080/Shared Documents/Forms/template.dotx|s|https://o15psvr:8080/Shared Documents

 Excel Files :  "ms-excel:ofv|u|https://sharePointDocumentlibraryURL"

This problem is related to the new Microsoft SharePoint Foundation Support this installs a new version that office 2010 is not aware of.

Here are the steps to fix the problem:

You have to change your installation of Project2013 and run the Repair of the Office 2010. The issue is linked to the New Microsoft SharePoint Foundation support which Project 2013 is installing.

To do so run the change Project
Professional from the control Panel

 
Disable the “Microsoft
SharePoint Foundation Support “ option and continue.

After the changes take effect run the Office 2010 Repair and the issue should be solved.

Why?

Please see the Microsoft Support Lifecycle pages for full details. Here’s a quick summary – once a Service Pack is released, support for the previous baseline ends 12 months after release (or at
the end of the product lifecycle, whichever comes first) for Office products. Since we are now a year past the release of SP3, we have reached the end-of-life for the SP2 baseline.

Builds with check-in to drop RTM baseline:

QFE Build: 12.0.6672.5000 (February CU build – CP2)

COD Build: 12.0.6670.5004

What this means:

Any patches from the builds noted above, or later, will no
longer apply over the SP2 baseline. SP3 must be installed in order to apply
future updates.

First customer releases which will contain this change:

February PU, February CU 2013

FAQ:

Q: What about products that didn’t have an SP3 release?

A: For any products which fall into that category, the last
released baseline is still the most current baseline, so will continue to be
supported.