Summary

Renaming a project using Microsoft Project Professional in a MS Project Server EPM environment requires the following procedure.

2. Steps to rename a project using MS Project Professional

To rename a project schedule, open the Microsoft Project Professional and make sure it is connected to MS Project Server.

1. Go to Filemenu and choose Open.

Microsoft Project Professional – File Open Dialog Box showing project from local cache

Tip: Notice in the screenshot that we renamed the EPM 2010 Rollout project in a previous step to EPM 2013 Rollout. But in the open dialog box it is still showing 2010 in the project name. That is due to local cache feature of MS Project Professional. Due to this reason, it is recommended that Project Managers publish their changes made in the project schedule using MS Project Professional before a project is renamed.

2. Click on the link ‘Retrieve the list of all projects from Project Server’

3. Locate your project from the list and right click over it then choose Rename

Microsoft Project Professional – List of Projects – Right Click a project and choose Rename

4. Enter new name of project (append V2 in name as an example) and hit enter key. A message box will bring this message

The rename job was successfully submitted to server

Based on the server load, it may time some time for this to complete. You will continue to see the old name till the operation is completed.

Microsoft Project Professional – Project Renamed Confirmation Message

5. Click OK to the message6. Close the open dialog box and open it again. You will notice the new project name in the list.

Tip:

Notice in the Open dialog box that you are using the Working store. Select the Publishstore and locate your project in the list. You will notice that the old project name will still show in the list. What happened here?

In MS Project Server, there are multiple databases (stores) draft, published etc. Save and Publish operations update different tables in the system. To resolve the issue, you need to open the working store version of project and publish it.

Microsoft Project Professional – Previous Project name shows up in Published Store

7. Make sure your have Working selected under Store in the dialog box8. Open the project (showing new project name) by double clicking on project name or by selecting it and clicking Open button at the bottom right

Microsoft Project Professional – Working Store showing new project name

Tip:If you get message regarding user submitted updates on the project, click No for now. You can approve those update later after the project is renamed. Update Center will show the new project name for the updates.

Microsoft Project Professional – Team Members submitted updates message

9. Go to File menu and choose Publish to publish the project data. That will update the new project name across all stores. (you can verify by going to file > open > ‘Retrieve the list of all projects from project server’ and then switching between working and published stores value and looking at the new project name)

Microsoft Project Professional – Publish Option

10. Go to File > Close to close the project11. Click Yes to any check-in message

More on this and other scenarios is coming in next parts of this series. So far we have completed the two parts. Review the third part to understand renaming the Project sites.

Related Softvative posts:

Create New Project from Existing in MS ProjectRename a Project in MS Project Server Part 1Rename a Project in MS Project Server Part 3Rename a Project in MS Project Server Part 4Rename a Project in MS Project Server Part 5

When working on projects in a PMO environment using Enterprise Project Management (EPM) system like Microsoft Project Server, you come across situations where you might have to rename objects. Those rename item request could be for project, resource, tasks or other objects in the system.

Summary

A project was created in Microsoft Project Server (MSPS) with a name. Later PMO / business teams wanted to change the name of the project.

1. Steps to Rename a Project using Project Web Access

Follow the steps below to rename a project using Project Web Access (PWA):

1. Go to PWA and click Project Center on left navigation

MS Project Web Access (PWA) – Project Center Link

2. Find the project from the list that you would like to rename and then select a cell other than the project name in the row or click the first empty cell on the left of the row [Hint: Don’t click on the project name as it will bring the project details page]

Project Web Access PWA – Select the Project to Rename

3. Click on PROJECTS ribbon tab on top, Click on OPEN dropdown under Project ribbon group and select ‘In Project Web App for Editing’

Project Web Access PWA – Open Project in PWA for Editing

4. On top area of left navigation, under project name, click on ‘Project Information’ or any PDP that has Name (that has project name) field in it.

5. Change the name of the project under NAME field
6. Click Save button in top left area of ribbon.
7. You will be presented with this message. Click OK to the following message:“The page and left navigation titles will not be updated with the new name of the project until the page has been reloaded.”

Project Web Access PWA – Warning after Project Renamed in PWA

You will see Save job message popping out from top right of screen.

Project Web Access PWA – Save Job Queued message

then

Project Web Access PWA – Save completed successfully message

At this point you can close the project and it will show the new name in PWA. I prefer to publish it just so that other database tables are updated as well.

8. Refresh the page to confirm the project has been renamed

Project Web Access PWA – Refresh the page to confirm the new project name on left nav

12. Once the Publish operation is complete, click on PROJECT ribbon tab on top

13. Click Close button

Project Web Access PWA – Close the Project in PWA

14. You will be presented with the Check-in message. Click Yes

Project Web Access PWA – Check in project in PWA

Exceptions:

The TASKS page for team members will show the new project name. But the TIMESHEET page will show the old project name, if the timesheet was created prior to project rename. In that case delete / recall and create the timesheet again. It will then show the new project name.

More on this and other scenarios is coming in next parts of this series. So far we have completed the first part. Stay tuned for the second part.

Related Softvative posts:

Rename a Project in MS Project Server Part 4Rename a Project in MS Project Server Part 2Rename a Project in MS Project Server Part 5Rename a Project in MS Project Server Part 3How to Check in your own Project that is checked out to you in another session on MS Project Server

Microsoft Project can’t Connect with Microsoft Project Server EPM due to Version Mismatch

Version: 1.2, Modified: 12/29/2014

Microsoft Project Professional edition is the desktop client in Microsoft Project Server (MSPS). The version of the server and client software should be at a supported level in order of the two to work together. Service Pack or Cumulative Update (CU) patches if deployed without planning can cause issues in MS Project Server Enterprise Project Management (EPM) system.

There are different reasons as to why MS Project Professional can’t connect with MS Project Server EPM.

Below are some of the scenarios:

a. Not using the right edition of MS Project (Professional VS Standard)

b. Not using the right edition of MS Project Professional with the right edition of MS Project Server (2010 VS 2013)

c. Not using the correct URL of Project Web Access (PWA)

d. Not having enough permissions (a user with team member or lower rights trying to connect MS Project Professional to MS Project Server)

e. Not using the right version of MS Project Professional with the right version allowed by MS Project Server in PWA > Server Settings

The focus of this article is about the last scenario. I’ll also cover special case of this scenario.

e. Not using the right version of MS Project Professional with the right version allowed by MS Project Server in PWA > Server Settings

There are known issue if your MS Project Server (MSPS) is at latest patch version and your desktop MS Project Professional edition used it too old.

MS Project Server 2010 / 2013 / Project Online circumvent this problem by allowing the Project Server Admins / PMO Admins / PMO Analysts to set limit on the least version of MS Project Professional that can connect with the Project Server.

Which MS Project Professional product can connect with which MS Project Server product

The short summary is:

MS Project Professional 2010 can only connect with MS Project Server 2010

How to Control Which version of MS Project Professional Can connect with MS Project Server EPM

Microsoft Project Server 2010 / 2013 has the configuration setting that allows you to control which version of MS Project Professional within the same edition (2010 or 2013) can connect with the MS Project Server.

On that ‘Additional Server Settings’ page there is a setting to set the minimum version number of MS Project Professional that can connect with that instance of the MS Project Server EPM. Ms Project Professional versions prior to that number will not be able to connect with MS Project Server.

PWA Additional Server Settings > Project Professional Versions

You can see this pilot instance supports a minimum of 14.0.6123.5000 version of MS Project Professional. That version is dated back to June 2012. That is little too old.

As per ITIL best practices for Configuration Management and Problem Management and also as per Information Security’s Patch Management Life cycle, the application versions should be maintained at the best possible levels. Even from Information Risk Management prospective, sometimes supporting too old version means also keeping old vulnerabilities alive in your new system. There is lot more to talk about on these best practices related to this topic. But that is little out of scope at this time for the topic.

Special Case Scenario due to version mismatch

I’ve seen a special case where a Project Manager was not able to connect to MS Project Server with everything correct as per the scenarios discussed at the beginning of this article.

The PM was getting the error listed below when launching MS Project Professional using connection with MS Project Server.

The following job failed to complete.Job Type: LoadError ID: 12015 (0x2EEF)Error Description: An internal error occurred.Cloud not load Project. Please try after some time. If the problem persists, contact your system administrator.

MS Project can not connect with Project Server – Error ID 12015

Clicking more Info button reveals more details. You can see the version that is passed on to the PWA is not the right one.

Cloud not retrieve Enterprise global template.There seems to be a problem with the database, please contact your server administrator.

Issue Cause

I verified that the MS Project Professional version was new relatively i.e. 14.0.7015.1000. That was higher than the minimum supported version configured in PWA.

Looking at the File > Help in MS Project Professional and reviewing the version screen in a large print out, I was able to find an anomaly. See the above screen shot again. It shows that MS Project Standard and MS Project Professional both as activated versions!

It turned out to be the Desktop Engineering person deployed MS Project Standard version first by mistake (& without any service packs or updates). Later he installed MS Project Professional over the same version as upgrade rather than removing the standard version. Now when the PM was trying to connect to MS Project Server using Ms Project Professional, somehow the desktop was passing the lower version 14.0.4751.1000 (see one of the screen shot above) and thus PWA was rejecting the connection.

Resolution

Uninstall any version of Microsoft Project from the desktop, reboot and then install the correct version of MS Project Professional with the the latest service pack and CU level as supported by the organization.

Revo Uninstaller – Free version is one nice 3rd party application (Pro Version) to remove the stubborn applications. That helped in getting rid of the old version completely and then installing the MS Project Professional version again.

The correct version once installed and activated should only show MS Project Professional under File > Help.

Scenario:

I had an external Yammer Network with few groups underneath it. I had a SharePoint Online (Office 365) site collections with sub-sites. I created three pages under the main site and leveraged three different option (one on each page) to integrate the Yammer Feed with the SharePoint Online site.

Issue Details

Everything was working until an unknown bump caused the feed to break. I started getting the following Yammer Login message no matter even if I click on login icon and go through the Yammer login page to login using ADFS login.

Users should have access to the SharePoint site pages and the Yammer Network / Group feed that is embedded

SharePoint page URL format can make or break Yammer Feed on the page

1. Adding Sites URL to Internet Explorer Trusted Sites for the Yammer Feed to work in SharePoint Online:

I found a Microsoft article that talks about adding Yammer feed to a SharePoint page. See the section ‘Having trouble with the app’ in that article. I then worked with the AD / security team to make the change in the GPO to add the Yammer, SharePoint and MicrosoftOnline links to the IE trusted zone.

We added these links to the Active Directory Group Policy for computers.

Using Group Policy Management Console (thanks to RSAT for Win7), I was able to view the changes. Once you have the RSAT installed and configured, you can use the server tools from your desktop. Open ‘Group Policy Management’ from Start > Administrative Tools or type gpmc.msc in Start > run and enter.

In the Group Policy find the GPO that applies the Internet Explorer trusted site settings to computers.

Active Directory – Group Policy Management Console

Expand the Organization Unit (OU) from left that contains the computers and click on the Group Policy. Click on Settings tab and then expand all settings by clicking Show All. Look for Internet Explorer related settings.

3. Users should have access to the SharePoint site pages and the Yammer Network / Group feed that is embedded
User visiting a SharePoint page with the Yammer network / group feed embedded on the page, should have access to Yammer network / group. Else user will get content can’t be displayed message in the app part (web part) area on that page.

This content cannot be displayed in a frameTo help protect the security of information you enter into this website, the publisher of this content does not allow it to be displayed in a frame.What you can try:Open this content in a new window

Yammer Feed can not be displayed in the Frame Error on a SharePoint Online (Office 365) page

If you click on the link ‘Open this content in a new window‘, you will see the yammer page for that network displaying ‘Join Network’ link. that indicates that the user doesn’t have permissions or is not part of the Yammer network that was embedded on that SharePoint Page.

Yammer – Join Yammer Network Page – SharePoint Integration

Users that will be part of the network should be able to see the feed on the SharePoint online Page.

4. SharePoint page URL format can make or break Yammer Feed on the page

I’ve noticed another issue where the URL address format of the SharePoint page can make or break the Yammer feed integrated on a SharePoint page.

For a same site, notice the difference in URL:

Yammer Feed Worked:

Yammer Feed Failed:

In case of the second link, Yammer feed displays the same message ‘This content cannot be displayed in a frame’ as listed above in one of the screenshot. Investigating this issue further.

Download Updates:

Mitigating Factors

An attacker who successfully exploited this vulnerability could run arbitrary code in the context of the current user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

The vulnerability cannot be exploited automatically through email. For an attack to be successful a user must open an attachment that is sent in an email message.

In a web-based attack scenario, an attacker could host a website that contains a file that is used to attempt to exploit the vulnerability. In addition, compromised websites and websites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted website. Instead, an attacker would have to convince them to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes them to the attacker’s site, and then convince them to open the specially crafted file in an affected version of Microsoft Office software.

SharePoint Document Management Best Practices

Version: 2.0, Last Updated: 12/03/2014

SharePoint like any document management system, has best practices that needs to be followed to get maximum value out of the system. A planned roll out of document management features helps the organization and users. A planned roll out should have some sort of discipline (Plan, Do, Check, Act) around it. In an unplanned roll out you will come across discipline (Do, check, plan, act) that cause more pain.

What are the “benefits of planned SharePoint roll out” :

1. With planning, staff knows what is coming and when

2. You select the features that best fit into the organization in the beginning. It might be difficult to change user behavior of how they work in the systems later if you started with rudimentary features and process

3. Users might use a SharePoint library just like a network shared drive to dump files. Versus organizing a library with columns, content types or term store features might go long way

4. Same department contents structured using right features might save lot of time and hence the cost (full time employees are not free, everyone has a cost associated)

5. Structured information will help the team leads / Management make quick and intelligent decisions in short time

Now, what are some of the “common best practices around SharePoint Document Management”?

There are no hard and fast rules. Every situation and roll out might require different combination of features. Below I’ve listed some of the ‘”common best practices for Sharepoint”. This list by no mean is complete and there might be additional best practices needed around different department contents. Use this list as a reference and come up with your plan.

1. Use short Site, Library and List names

Don’t use long names in Sites, Libraries and lists in Sharepoint. Avoid having space in names. Like instead of ‘Billing Department’ use BD or Billing. Another example for site name se short name like AEC instead of An Excellent Company. Create sites, libraries and list with short names. Once created go the Title configuration areas to change to long title and add text in the description field. Creating those items with shot names conserves the URL address space.

2. 255 Characters URL Limit and Windows file / folder path Limits

There is a limit of characters in the URL address as part of web standard. It is 255 characters. Using long site, library, folders, files path can lead to situation where that limit might be reached. In Sharepoint that could cause some hard stop. Few examples could be users not able to edit files even with right permissions, previous versions of file not working etc.

b. You receive a “The specified file or folder name is too long” error message when you create a new folder or a new document in a document library in SharePoint Portal Server or in Windows SharePoint Services http://support.microsoft.com/kb/894630

c. A webpage that has a long URL may not print to a network printer in Internet Explorer 9

3.Avoid Using Special Characters in File, Folders , Library and Site names

Special characters cause special problems. To make a file / folder on the top of the list, use Sharepoint views, filters and sorts option. If you really need to make something on top of the list manually, use period (.) or underscore (_) in the beginning of the name. But it is better to use simple names.

Reference:

Information about the characters that you cannot use in site names, folder names, and file names in SharePoint

4.Avoid Using Spaces in Names and avoid having space in beginning

If you need to use two words in names, avoid space in the middle. That one space takes three character (i.e. %20) in the URL address. For example use BestDocument instead of Best Document. You can use underscore (_) in the middle of two words without adding spaces. In same example that will look like Best_Document.

5.Don’t add version number of file at the end of name

It is a common scenario users do on network shared drives. Don’t use the same practice in a content management system like Sharepoint. Instead turn on the versioning feature at the library or list level and use it to your advantage. Let the Sharepoint do its job of maintaining versions. Add those versioning columns in the view for users. On the side note, when you turn on the versioning feature don’t turn on unlimited versions, set a limit on the last number of versions to keep. For example 5 or 10 [Sharepoint site Admin can setup versioning for libraries and lists.].

6.Use Metadata instead of Folders

Metadata is much better way of working with contents compared to organizing contents in folders. Using Columns, Content Types, Metadata Term store feature of Sharepoint are recommend ways.

Reference:

a.SharePoint 2013 Best Practices: Using Folders [same concepts can apply to other Sharepoint editions]

7.Don’t use long folder names

I’ve seen examples where people used kind of whole history of the folder as part of folder name. For example “A Long Company Name, Contract Number, Customer Number, Customer Location” as part of folder name. Compare it to having a folder with just the short company name ABC Company and using rest of the information as part of the metadata properties at file level to classify contents is much better and faster approach. You will run into long URL issues if you will have hierarchical chain of folders with longs names and long file names inside those folders.

Just like people don’t use long names. They use first and last name or maybe middle name. But people don’t add their grandfather, great grandfather and whole ancestral names as part of their name. Another example, book writers don’t add the full summary of the book on the title. It is usually in next few pages.

8. Think Before you Act

Always think and plan before you would like to do any important thing in SharePoint. Try to get your information organized from the beginning. Unplanned start can cause you lots of rework later that might take twice or thrice the efforts and costs. It is like plan and pay early and save a lot later versus do it without planning and keep paying forever.

9. Use Site, Library, List Templates

SharePoint comes with lots of templates for sites, libraries and lists. You can create a customized site, library or list using out of the box features and then save it as template. Those template can then be used later by other department and team. Thus saving lots of time and efforts later.

10.Know you SharePoint Document Management features

SharePoint offers lots of features for document management that help in different scenarios. Content Types, Content Organizer Rule, Documents Sets, Document ID, workflows and others are some of the advanced features that can bring value to your contents. Know what you have at your disposal, before users start using your libraries.

11. Learn about Content Management Features of SharePointSharePoint has lots of Enterprise Content Management (ECM) features that you may not be aware of it or you may not aware of other ways to leverage those features for your contents.

Learn about these features and jargon in SharePoint that will help your in the Document Management.

Common Issues with Visio Graphics Services

1. The server failed to process the request

A user tries to view Visio in browser (or view the Workflow Visualization page) from SharePoint and gets the error message:

The server failed to process the request

SharePoint Visio Graphics Service Error – The server failed to process the request

At this point a user tries to click on ‘Open in Visio’ link on top left of the workflow Visualization section to open the file in MS Visio on their desktop. The Visio file opens up in MS Visio.

In one scenario I was able to open the Workflow Visualization file in MS Visio on my desktop only in read only mode. I was getting a warning message:

Visio Standard does not support savings files of this type. When saving the file, you will be prompted to save as a different file type.

The reason of this warning is clear from the warning message. I had standard version of MS Visio on my PC. The Workflow Visualization file had .visio web drawing file extension (.VDW). The users with Ultimate, Premium and other higher version would be able to open and edit the web drawing format Visio files.

Secure Store Service application ID that is configured for Visio Graphics Services doesn’t have correct Permissions

Visio Graphics Services on SharePoint Server are not running

Some other failing services causing issue

Resolution:

In one of my scenario, everything was right except the fact that Secure Store Service was having some issues. That lead to issues for Visio Graphics Services. An IISReset /noforce on SharePoint Servers helped in resolving this issue.

Visio drawing started working in Workflow Visualization and also in Visio Web Part.

ULS Log Errors:

System.TypeInitializationException: The type initializer for ‘Microsoft.Office.Excel.Server.CalculationServer.ExcelServerApp’ threw an exception. —> System.IO.FileLoadException: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401) at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException,TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock) at Microsoft.Office.Server.Diagnostics.ULS.SendWatsonOnExceptionTag(UInt32 tagID, ULSCatBase categoryID, String output, BooleanfRethrowException, TryBlock tryBlock, CatchBlock catchBlock, FinallyBlock finallyBlock) at Microsoft.Office.Excel.Server.CalculationServer.ExcelServerApp..ctor() at Mic…There was an error in communicating with Excel Calculation Serviceshttp://SPAppServer013:32843/0753ec6cff654ce09f369241f98d06a7/ExcelService*.asmx exception: An error has occurred. [Session: User: domainSPFarmAdmSvcAct].ServerSession.ProcessServerSessionException: An exception thrown during ExecuteWebMethod failed to convert to ECSException for server:http://SPAppServer013:32843/0753ec6cff654ce09f369241f98d06a7/ExcelService*.asmx, method: GetHealthScore, ex:Microsoft.Office.Excel.Server.CalculationServer.Proxy.ServerSessionException: An error has occurred. —>System.ServiceModel.FaultException: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the se…..

6. Refresh the page after few seconds and make sure the service is in stopped status

7. Once the Service show stopped status, click on Start under action column to start the service

8. Refresh the page for few seconds to make sure the Excel Calculation Service shows Started under status column

9. Go back to the page under step 2 above and follow steps for next server

10. Test one Excel file on the Sharepoint site by opening it in browser

Instead of restarting the servers or performing doing IISReset, stopping and starting the Excel service helped resolve the issue. Due to farm serving other critical apps out of SharePoint, server reboot and IISReset were not an option.

SharePoint Excel Services Unable to Save Workbook

Scenario:

A user opens an Excel file for editing using ‘Edit in Browser’ option.

SharePoint Excel Web Services – Edit In Browser an Excel File

Error:

After sometime in the edit mode, the user gets the message

Unable to Save WorkbookWe will try again automatically, but you should try to save your workbook to another location or click Open in Excel.

There will be an error dialog box that says:Your changes could not be saved. It is recommended that you select Open in Excel or try to save your changes to a different location immediately. If your changes can still not be saved after a few more minutes, your session will be ended to prevent any more loss of data.

Remedy:

During the issue the users impacted can use the Save As option in Excel Web Viewer to save the file locally if they want to edit the file and upload it later after issue is fixed.

Excel Web Services – Save As option

The user will loose the changes they will do during this issue if they will not save a copy and then edit the saved copy.

If you continue making changes in Excel file within Excel Web Viewer, you will get a prompt with following message. At this point you have lost the changes you would have made during this session.

Either due to communication issues or a server problem, you need to be rejoined to your editing session. You may have lost changes that you made recently.

Excel Web Viewer – Session Lost and Lost recent changes Message

At this point go to your document library location where your Excel file is located and review the Modified date. You will notice that the modified date will not reflect that it was modified. Same will be true for version number if versioning was enabled for that library.

Excel Web Services issue – File changes not Saved

At this point the user will feel angry, frustrated or a lost soul based no their work. Don’t loose hope. There is some green light. Its coming in next section.

Resolution:

The above issue with Excel Web View not able to save could happen due to number of reasons. In this case when I started reviewing the SharePoint Farm for the application servers running Excel Services, I found that whenever there was error in Excel web viewer for this issue, around the same time there was an error log for Symantec Protection for SharePoint Servers. Now you know why I listed the Symantec error in the Errors section.

I went to SharePoint Central Admin website and looked at the Symantec settings. I noticed the service was showing as stopped on one application server.

Next I looked into the Windows Services console and found the service ‘Symantec Protection 6.0 for SharePoint Servers’ in STOPPING status. In that state you can not start, stop or restart that service.

Windows Services Console – Symantec Protection Service in STOPPING State

I terminated the Symantec Protection SPSS process using Windows Task Manager on the server. Then I started that service successfully. Later I went to SharePoint Central Admin website > Symantec Protection section and looked at that server and it was showing as Started.

SharePoint Central Admin – Symantec Protection Service in Started state on an App Server

Next I opened the Excel file from SharePoint location in Excel Web services in edit mode. I was able to edit the file and Excel Web Services saved the changes back to the file. I then reviewed the Modified date and it was showing the file was modified at recent time with my name under Modified Bu field.

Today Microsoft released a patch for vulnerability in Microsoft SharePoint Foundation Could Allow Elevation of Privilege under Microsoft Security Bulletin MS14-073.

What:An attacker who successfully exploited the vulnerability could execute arbitrary script in the security context of the logged-on user. The script could then, for example, take actions on the affected SharePoint site on behalf of the logged-on user with the same permissions as the logged-on user.

How:An attacker could modify certain lists within SharePoint to exploit this vulnerability, and then convince users to browse to the modified list.

Risk:Systems running an affected version of SharePoint Server that also support the mobile browser view are primarily at risk.

Mitigation:In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit these vulnerabilities and then convince a user to view the website. The attacker could also take advantage of compromised websites and websites that accept or host user-provided content or advertisements. These websites could contain specially crafted content that could exploit these vulnerabilities. An attacker would have to convince users to take action, typically by getting them to click a link in an email message or in an Instant Messenger message that takes users to the attacker’s website, or by getting them to open an attachment sent through email.