Archive for the ‘ProjectServer’ Category

Rename a Project in MS Project Server Part 2

Friday, January 30th, 2015

Rename a Project in Microsoft Project Server – Part 2

Version: 2.1

Applies to:
MS Project Server 2010
MS Project Server 2013
MS Project Online (Office 365)

This is the second part of the series to explain the details of different cases and how to best rename a project schedule in Microsoft Project Server EPM.

Table of Contents


Summary

1. Steps to rename a project using Project Web Access (PWA)
2. Steps to rename a project using MS Project Professional
3. Rename Project site
4. Scenarios: Renaming Project and different Statuses of Timesheets
5. Renamed Project Schedule and Business Intelligence Center Reports
Conclusion

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
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
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
Microsoft Project Professional – Project Renamed Confirmation Message


5. Click OK to the message
6. 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
Microsoft Project Professional – Previous Project name shows up in Published Store


7. Make sure your have Working selected under Store in the dialog box
8. 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
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
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
Microsoft Project Professional – Publish Option



10. Go to File > Close to close the project
11. 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.
Summary

1. Steps to rename a project using Project Web Access (PWA)
2. Steps to rename a project using MS Project Professional

3. Rename Project site
4. Scenarios: Renaming Project and different Statuses of Timesheets
5. Renamed Project Schedule and Business Intelligence Center Reports
Conclusion

Keywords:

  • Renaming a project in Project Server
  • Renaming a project in Microsoft Project Server
  • Rename a project using MS Project
  • Rename a project using MS Project Professional
  • Rename a Project in Project Server
  • best practice to rename a project in Project Server
  • best practice to change a project name in Project Server
  • How to change a project name in Project Server
  • How To guide for renaming a project in Project Server
  • Primer on renaming a project in Project Server
  • Step by step guide to rename a project in project server
  • Edit Project details to rename a project
  • Rename a project schedule in Project Server
  • Rename a project plan in Project Server
  • How to rename projects in Project Server
  • How to rename a mpp file in Project Server
  • Renaming Projects
  • Project rename process
  • Project rename job aid
Visit www.softvative.com for professional services.

Rename a Project in MS Project Server Part 1

Thursday, January 29th, 2015

Rename a Project in Microsoft Project Server – Part 1

Version: 2.3

Applies to:
MS Project Server 2010
MS Project Server 2013
MS Project Online (Office 365)

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.

MS Project Server has evolved as a mature EPM / PPM solution compared to its predecessor editions. In MS Project Server 2003 edition, we had to use other utilities to rename a project. Sometimes, special characters in project names used to cause so much trouble to the Cube build process.

These series of articles will explain the details of different cases and how to best rename a project schedule in Microsoft Project Server EPM.

Table of Contents

Summary

1. Steps to rename a project using Project Web Access (PWA)
2. Steps to rename a project using MS Project Professional
3. Rename Project site
4. Scenarios: Renaming Project and different Statuses of Timesheets
5. Renamed Project Schedule and Business Intelligence Center Reports
Conclusion

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
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
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
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.

Project Web Access PWA - Project Information PDP Page containing Name field
Project Web Access PWA – Project Information PDP Page containing Name field

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
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
Project Web Access PWA – Save Job Queued message

then

Project Web Access PWA - Save completed successfully message
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
Project Web Access PWA – Refresh the page to confirm the new project name on left nav
9. Click on SCHEDULE link on top left
10. Under Schedule Tools > Tasks tab of ribbon, click on PUBLISH.
Project Web Access PWA - Go to Schedule PDP page and Publish the Project
Project Web Access PWA – Go to Schedule PDP page and Publish the Project
11. Watch for message popping from the top right with status message:
   a. Processing
   b. Save job queued
   c. Publish completed successfully
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
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
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.
Summary
1. Steps to rename a project using Project Web Access (PWA)
2. Steps to rename a project using MS Project Professional
3. Rename Project site
4. Scenarios: Renaming Project and different Statuses of Timesheets
5. Renamed Project Schedule and Business Intelligence Center Reports
Conclusion


References:
1. Back to Basics: Renaming a Project correctly in Project Server 2013


Keywords:

  • Renaming a project in Project Server
  • Renaming a project in Microsoft Project Server
  • Rename a Project in Project Server
  • best practice to rename a project in Project Server
  • best practice to change a project name in Project Server
  • How to change a project name in Project Server
  • How To guide for renaming a project in Project Server
  • Primer on renaming a project in Project Server
  • Step by step guide to rename a project in project server
  • Edit Project details to rename a project
  • Rename a project schedule in Project Server
  • Rename a project plan in Project Server
  • How to rename projects in Project Server
  • How to rename a mpp file in Project Server
  • Renaming Projects
  • Project rename process
  • Project rename job aid
Visit www.softvative.com for professional services.

MS Project cant Connect with MSPS MSProjectServer

Friday, December 26th, 2014

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
  • MS Project Professional 2013 can connect with MS Project Server 2013 & MS Project Online
  • MS Project Standard can’t connect with MS Project Server.
Softvative Infographics - Microsoft Project Professional and MS Project Server Editions Compatibility
Softvative Infographics – Microsoft Project Professional and MS Project Server Editions Compatibility

Review the Infographic slides:

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.

The settings are located in Project Web Access (PWA) > Server Settings > Additional Server Settings.

Microsoft Project Web Access (PWA) > Server Settings > Additional Server Settings link
Microsoft Project Web Access (PWA) > Server Settings > Additional Server Settings link

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
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: Load
Error 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 Error - The following job failed to complete Error ID 12015
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.

MS Project can not connect with Project Server - Error ID 12015 - More Info
MS Project can not connect with Project Server – Error ID 12015 – More Info

Click OK to the first error message brings the second error:

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.

MS Project Professional was able to connect with the Project Server.

References:

  1. Project Server 2013: Controlling the version of connecting clients–and PWA edits?
  2. How do I know???? Project Professional Versions and Consistency

Keywords:

  • MS Project can’t connect with Project Server
  • MS Project can’t connect with Project Online
  • MS Project can’t connect with PWA
  • Microsoft Project can’t connect with Project Server
  • MS Project can’t connect with Microsoft Project Server
  • Microsoft Project Professional can’t connect with Project Server
  • Microsoft Project Professional supported versions for Project Server
  • Microsoft Project Professional version inconsistencies with Project Server
  • Can not use MS Project with Project Server
  • Can not use MS Project with PWA
Visit www.softvative.com for professional services.

Softvative Microsoft Office365 Applications Brainstorming Plan

Sunday, November 16th, 2014

Office 365 Applications Brainstorming Plan

Version: 1.1

Microsoft Office 365 has lots of applications based on the plan you choose. To make it easy to plan and understand, Softvative created a brainstorming plan. the initial version if focused on external user interactions with corporate users.

Soon that plan will be offered as a full version download for registered users. The full version will be a MS Visio based version covering Visio plan, clickable links to important articles, comments on key areas and expanded plan with more details.

Review the current version of the Office 365 brainstorming plan that includes key Microsoft Online apps including:

  • Office 365
  • SharePoint Online
  • Project Online
  • Yammer
  • OneDrive for Business
  • Skype for Business (Lync)
  • Exchange Online
  • CRM Online
  • Power BI

SharePoint Document Conversion Services

Wednesday, October 29th, 2014

SharePoint Document Conversion Services

Version: 1.0

Applies to:

  • SharePoint 2010
  • SharePoint 2013
  • SharePoint Office 365

Overview of Document Conversion Services

SharePoint has Document Conversion Service that allows to convert files like Microsoft Word .docx into SharePoint webpages.

Office Web Apps (web version of Office) that works in SharePoint and allows users to view Office files even if they don’t have MS Office installed on their PC. In the absence of Office Web Apps (OWA), SharePoint Document Conversion Service will be handy to view the MS Office files.

Document Conversion services are not enabled by default. There are two services for Document Conversion.

1. Document Conversion Launcher Service
2. Document Conversion Load Balancer Service

Configuring Document Conversion Services

To enable the document conversion, you have to first configure its Load Balancer Service and then the Launcher service.

a. Configure Document Conversion Load Balancer service on SharePoint Application Server (Central Admin > Services on Server: ApplicationServer)

b. Configure Document Conversion Launcher Service on SharePoint Application Server (Central Admin > Services on Server: ApplicationServer)

c. Configure the Document Conversions (Central Admin > General Application Settings > Configure Document Conversions)

Issues in Configuring Document Conversion Services

Some times you get into issue during initial configuration of Document Conversion service or even later during operations where these services fail to start.

Error Starting Document Conversion Services

You go to SharePoint Central Administration site > System Settings > Manage Servers in this Farm > Click on an application server name (not SharePoint Web Front End). That will bring you to the Services on Server: ServerName page. In one of my scenario, I tried to start the Document Conversion Load Balancer service and got Error Starting status. I tried different ways but couldn’t start the service.

SharePoint Document Conversion Launcher Service - Error Starting status
SharePoint Document Conversion Launcher Service – Error Starting status

I went into Event Viewer logs first on the SharePoint application server and found following errors.

Event Viewer Error 1

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          10/28/2014 3:12:46 PM
Event ID:      7034
Task Category: Topology
Level:         Critical
Keywords:      
User:          softvativeSPFarmServiceAccount
Computer:      SharePointAppSrv.softvative.com
Description:
An attempt to start/stop instance  of service Document Conversions Load Balancer Service on server 

SharePointAppSrv did not succeed.  Re-run the action via UI or command line on the specified server. 

Additional information is below.

Operation is not valid due to the current state of the object.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-SharePoint Foundation” Guid=”{6FB7E0CD-52E7-47DD-

997A-241563931FC2}” />
    <EventID>7034</EventID>
    <Version>14</Version>
    <Level>1</Level>
    <Task>13</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-10-28T20:12:46.879677800Z” />
    <EventRecordID>858925</EventRecordID>
    <Correlation ActivityID=”{4A13B121-2470-406B-ADCB-2A97903E8D0D}” />
    <Execution ProcessID=”19412″ ThreadID=”788″ />
    <Channel>Application</Channel>
    <Computer>SharePointAppSrv.softvative.com</Computer>
    <Security UserID=”S-1-5-21-1627688274-1190192956-3999157559-1223″ />
  </System>
  <EventData>
    <Data Name=”string0″>
    </Data>
    <Data Name=”string1″>Document Conversions Load Balancer Service</Data>
    <Data Name=”string2″>SharePointAppSrv</Data>
    <Data Name=”string3″>Operation is not valid due to the current state of the object.</Data>
  </EventData>
</Event>

SharePoint Document Conversion Error - Event ID 7034
SharePoint Document Conversion Error – Event ID 7034

Event Viewer Error 2

Log Name:      Application
Source:        Microsoft-SharePoint Products-Document Management Server
Date:          10/28/2014 3:12:11 PM
Event ID:      7953
Task Category: Document Conversions
Level:         Critical
Keywords:      
User:          softvativeSPFarmServiceAccount
Computer:      SharePointAppSrv.softvative.com
Description:
The Office HTML Load Balancing Service experienced a problem.

Error:  Not launching Document Conversions Laod Balancer because registry key acknowledging service 

running on app server (‘AcknowledgedRunningOnAppServer’) is not set.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-Document Management Server” Guid=”{F78D66EC-09A9-

42A2-AC7A-5EE2062DE7E4}” />
    <EventID>7953</EventID>
    <Version>14</Version>
    <Level>1</Level>
    <Task>8</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-10-28T20:12:11.098100000Z” />
    <EventRecordID>858923</EventRecordID>
    <Correlation />
    <Execution ProcessID=”10552″ ThreadID=”16556″ />
    <Channel>Application</Channel>
    <Computer>SharePointAppSrv.softvative.com</Computer>
    <Security UserID=”S-1-5-21-1627688274-1190192956-3999157559-1223″ />
  </System>
  <EventData>
    <Data Name=”string0″>Not launching Document Conversions Laod Balancer because registry key 

acknowledging service running on app server (‘AcknowledgedRunningOnAppServer’) is not set.</Data>
  </EventData>
</Event>

SharePoint Document Conversion Error - Event ID 7953
SharePoint Document Conversion Error – Event ID 7953

Event Viewer Error 3

Log Name:      Application
Source:        Microsoft-SharePoint Products-Document Management Server
Date:          10/28/2014 3:12:11 PM
Event ID:      7960
Task Category: Document Conversions
Level:         Critical
Keywords:      
User:          softvativeSPFarmServiceAccount
Computer:      SharePointAppSrv.softvative.com
Description:
The Office HTML Load Balancing Service could not be started.

Error:  Not launching Document Conversions Laod Balancer because registry key acknowledging service 

running on app server (‘AcknowledgedRunningOnAppServer’) is not set.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-Document Management Server” Guid=”{F78D66EC-09A9-

42A2-AC7A-5EE2062DE7E4}” />
    <EventID>7960</EventID>
    <Version>14</Version>
    <Level>1</Level>
    <Task>8</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-10-28T20:12:11.095099700Z” />
    <EventRecordID>858922</EventRecordID>
    <Correlation />
    <Execution ProcessID=”10552″ ThreadID=”16556″ />
    <Channel>Application</Channel>
    <Computer>SharePointAppSrv.softvative.com</Computer>
    <Security UserID=”S-1-5-21-1627688274-1190192956-3999157559-1223″ />
  </System>
  <EventData>
    <Data Name=”string0″>Not launching Document Conversions Laod Balancer because registry key 

acknowledging service running on app server (‘AcknowledgedRunningOnAppServer’) is not set.</Data>
  </EventData>
</Event>

SharePoint Document Conversion Error - Event ID 7960
SharePoint Document Conversion Error – Event ID 7960

Services in Console

In one of my scenario, I went into Windows Services console to review the Document Conversion services. Both the services were not running. Don’t try to start the services from Windows Service console.

SharePoint Document Conversion Services in Windows Services Console
SharePoint Document Conversion Services in Windows Services Console

Root Cause

It turns out there are registry keys that were needed to acknowledge that you configured the services to run on the application server.

Registry Location:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice ServerversionLauncherSettings
HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice ServerversionLoadBalancerSettings

Replace version based on SharePoint version:
SharePoint 2007 -> 12.0
SharePoint 2010 -> 14.0
SharePoint 2013 -> 15.0

You need to add the new key AcknowledgedRunningOnAppServer of type dword and set it to 1. That will let you start the Document Conversion services from Central Admin site.

SharePoint Document Conversion Launcher Settings - AcknowledgedRunningOnAppServer Key
SharePoint Document Conversion Launcher Settings – AcknowledgedRunningOnAppServer Key

SharePoint Document Conversion Load Balancer Settings - AcknowledgedRunningOnAppServer Key
SharePoint Document Conversion Load Balancer Settings – AcknowledgedRunningOnAppServer Key

My Registry Script

I created the AcknowledgedRunningOnAppServer registry entries as a registry file for easy import on new servers in future.

Download the Document Conversion Registry Fix files (.reg or .zip)

Download the .reg file or .zip file and extract the zip file contents to a folder. Locate the DocumentConversion_RegSettingKB2910363.reg file and double click on it. Click Yes to the message box.

Add the Document Conversion Registry Keys to SharePoint Application Server Registry
Add the Document Conversion Registry Keys to SharePoint Application Server Registry

Click OK to the successful message box.

Added Document Conversion Registry Keys to SharePoint Application Server Registry
Added Document Conversion Registry Keys to SharePoint Application Server Registry

After adding the registry entries, try to start the Document Conversion Load Balancer Service from the Central Admin site > Services on Server page. Click on Start under action column to start the Load Balancer service.

SharePoint Document Conversion Load Balancer Service Started
SharePoint Document Conversion Load Balancer Service Started

Now click on Start under action column for the Document Conversion Launcher Service. That will brig the Launcher Service Settings page. Select the same server from Load Balancer dropdown field and click OK.

SharePoint Document Conversion Launcher Service Settings
SharePoint Document Conversion Launcher Service Settings

You should now see the two Document Conversion services with the status of started.

SharePoint Document Conversion Services with Started Status
SharePoint Document Conversion Services with Started Status

Let take a peak at the Windows Service console for these services.

SharePoint Document Conversion Services -Started in Services Console
SharePoint Document Conversion Services -Started in Services Console

Configure Document Conversions

Once the Document Conversion services are running, its time to configure it. You go to Central Admin site > General Application Settings > Configure Document Conversions to configure the conversions.

SharePoint - Configure Document Conversions link
SharePoint – Configure Document Conversions link

On Configure Document Conversions page, you select the web application, enable document conversion, select a load balancer, schedule conversion and set converter settings. Click Apply. Once you are done with changes, then click OK.

SharePoint - Configure Document Conversions Settings
SharePoint – Configure Document Conversions Settings

Under Converter Settings, click on one of the link for the installed converters to review and adjust settings.

SharePoint Document Converter - From Word Document to Web Page Converter Settings
SharePoint Document Converter – From Word Document to Web Page Converter Settings

I’ll demonstrate more including some the limitations on Document Conversion in next version of the this article. Hop over to this page later to review the updated version.

References

  1. Configure Document Conversions Load Balancer and Launcher Services
  2. Document conversion load balancer unavailable
  3. Configure the Document Conversions Load Balancer Service
  4. Manage document conversions
  5. Some document-conversion services in SharePoint Server are not secure when they run in a particular environment

Ten effective Sharepoint ProjectServer training resources

Wednesday, September 10th, 2014
Question:
What are really effective end user training resources?

Answer:
Role based training containing real world examples are the most effective and keep the users engaged. SharePoint 2010 User Adoption training videos from Microsoft were short, precise and extremely good for business users.

Video training are also effective. Having videos in LMS is bonus plus. I’ve effectively used the following training formats for my customers:

  1. Small 2-3 minutes structured personalized on-demand videos that you can host within SharePoint or on a streaming media server. Use Jing, Microsoft Expression Encoder, Camtasia Studio, Articulate or similar resources to record, edit, create, encode and publish contents
  2. Creating a SharePoint site collection just for training where users can practice 
  3. Use step by step word / PDF guide divided into chapters that users can download and print. Make training contents relevant to the training site collection is most valuable
  4. Using WebEx to deliver live or on-demand training and also use Webex LMS with user registration
  5. Using LMS format training
  6. Conducting pre-training and post-training surveys to measure the trainee’s skillset, performance and training effectiveness.
  7. Structuring training based on roles is best. That was users increase their knowledge level and will be motivated to move to next role training
  8. Create a FAQ Blog under the training site collection where cover weekly / monthly posts on new topics, most frequent problem and other hot pressing issues.
  9. Tie your ticket support system with the SharePoint knowledge base within the training site collection. Don’t just fix or resolve issues, but document and create knowledge base that will go with you for long
  10. Please contact my company Softvative Inc for your Sharepoint, Project Server EPM / PPM and PMO training needs.
Keywords:
  • SharePoint end user training resources
  • SharePoint role based training resources
  • SharePoint best training resources
  • SharePoint video training resources
  • SharePoint LMS training resources
  • SharePoint training guides
  • SharePoint document based training
  • SharePoint On-Premises training
  • SharePoint Office 365 training
  • Best Sharepoint training in Minnesota
  • Best Sharepoint training MN
  • Best Sharepoint training in Midwest
  • SharePoint training in Minnesota
  • Office 365 SharePoint training
  • SharePoint Online training
  • ProjectServer end user training resources
  • ProjectServer role based training resources
  • ProjectServer best training resources
  • ProjectServer video training resources
  • ProjectServer LMS training resources
  • ProjectServer training guides
  • ProjectServer document based training
  • ProjectServer EPM training
  • ProjectServer MSPS training
  • MSProjectServer training
  • ProjectServer video training
  • ProjectServer role based training
  • ProjectServer training in Minnesota
  • Best ProjectServer training in Minnesota
  • Best ProjectServer training in MN
  • Best ProjectServer training in Midwest

How to Check in your own Project that is checked out to you in another session on MS Project Server

Wednesday, August 6th, 2014

Version 1.5

Table of Contents

  • Issue and Cause
  • Resolution
  • How to view my project in read-only when it is already checked-out in another session or by someone else?
  • How can a MS Project Server Admin / PMO Can help PM / RM?
  • Risks in Force checking-In Projects

Issue and Cause

Sometimes when working with your projects in MS Project Server, Project Managers / Resource Manager (PM / RM) forget to check-in their project at the end. Few times due to latency issues the project is not checked-in when PMs / RMs close their project. That leaves the project in questions still checked-out on MS Project Server side.
Next time the PM / RM tries to open that project, they will not be able to do it. The system will prompt the PM that the project is checked out.

Resolution

A Project Web Access (PWA) user that can check-out a project, can also check-in the project. Below are the steps on how to check-in your project that says it is checked out to you.
1. Go to Project Web Access (PWA) home
2. Click on Project Center link on the left quick launch navigation
3. Click on ‘Check-in My Projects’ link on the top ribbon area under Navigate group. If you don’t see the ribbon, make sure you are in the Projects tab and not the Browse tab of the ribbon.
4. You will be in ‘Force Check-in Enterprise Objects’ page. Make sure you have ‘Enterprise Projects’ highlighted under the ‘Select the type of object you want to force check-in:’ dropdown. From the list below, locate your project and check the box in front of that row. That will activate the Check-in button.
5. Click on the Check-In button to force check in the selected project(s).
6. Click OK to the dialog box that asks ‘Are you sure you want to Force Check-in these items?
7. The Job State column will show Processing. Refresh the page and the project should not be there in that list.
8. The project will be check-in and PM / RM should be able to check out the project again using either Project Web Access (PWA) or Microsoft Project Professional (MSPP) from desktop.
9. Click on Project Center link on left and check out your project.

How to view my project in read-only when it is already checked-out in another session or by someone else?

At the time of project showing as checked out, if a PM / RM goes into MS Project Professional, they see that project says it is check out. PM will not be able to open the project in Read/Write mode to edit it.
PM / RM can open the same project in Read Only mode. In that case the top middle title area of MS Project Professional will display the project name with [Read-Only] at the end of it.
 
Hint: Make sure you don’t make changes in the read-only project. I’ve seen PMs spending hours and hours changing a read-only project and then come to a point of no return. You will be able to save changes on desktop but not to a project that is already checked out.
 

How can a MS Project Server Admin / PMO Can help PM / RM?

MS Project Server EPM Admin can force check-in any project for PMs/ RMS. PWA Admin can follow the same steps as above. He can also do the same steps from PWA > Server Settings > ‘Force Check-in Enterprise Objects’ under Database Administration section.
 
 
 
Project Server Admin / PMO can go to the Server Settings > Manage Queue Jobs > Under ‘Job Completion States’ add ‘Success’ state to the right and review the Project Check-in job type status.
 

Risks in Force checking-In Projects

During the last checked out session if the project was not saved, there are chances that you might lose recent changes after the force check-in.

Keywords

  • why project in pwa do not checkin
  • why project do not checkin
  • PWA checkin issues

Primer on Sharepoint Excel DataRefresh Settings

Sunday, June 1st, 2014

Primer on SharePoint Excel Data Refresh Settings

V 1.2

There are different places where you can configure the Excel data refresh settings for external data when using it with SharePoint.

a. Microsoft Excel file Data Connection Properties
b. Excel Web Viewer refresh option – viewing files in Excel Web Access
c. In Central Admin > Excel Services > Trusted File Locations
d. SharePoint Excel Web Part Properties

I created this Excel Data Refresh Options Chart that I’ve used on different projects. It shows external data refresh option in standalone MS Excel file, Excel file in a SharePoint library, in Excel Web Access and in Excel Web Access Web Part. It also shows different roles around Excel in an organization. Excel Workbook Author in some organization could be different than the SharePoint Site Admin that sets the web parts.

Softvative – MS Excel External Data Refresh Options Chart

a. MS Excel Data Connection Properties

1. Open your MS Excel file that has the data. Click on Data Ribbon tab and then click Connections.

MS Excel Data Connections Menu

2. Select one of the existing connections in your workbook and then click on Properties button.

MS Excel Data Connections Dialog Box

3. Under the Usage tab, under Refresh Control section there are refresh data settings:

  • Enable background refresh
  • Refresh every n minutes
  • Refresh data when opening the file
  • Remove data from the external data range before saving the workbook
MS Excel Data Connection – Refresh Control Settings

b. Excel Web Viewer refresh option – viewing files in Excel Web Access

You need to have SharePoint Enterprise edition for Excel Services. Hover mouse over an Excel file in a library, click on drop down arrow on right side to bring the menu and choose ‘View in Browser‘.

SharePoint Excel File in a Document Library – View in Browser

 When MS Excel file opens up in Excel Web Access, click on Data menu. SharePoint users will see these two options:

  • Refresh Selected Connection
  • Refresh All Connections
SharePoint – Excel Web Access – Data Refresh Options

c. In Central Admin > Excel Services > Trusted File Locations

Follow these steps to review / configure the Excel Services Refresh Settings. 

1. Go to SharePoint Central Admin Website 
2. Click on ‘Application Management‘ on left navigation
3. Click on ‘Manage Service Applications‘ link and then click on your Excel Service Application name
4. Click Trusted File Location

SharePoint – Excel Services Application

5. Hover mouse over one of your trusted file location and from drop down menu choose Edit.

SharePoint – Excel Web Services – Trusted File Locations

6. Scroll down and review / update values as appropriate under External Data section > External Data Cache Lifetime section for automatic and manual refresh. Default setting for both is 300 seconds (5 minutes)

  • Automatic refresh (periodic / on-open)
  • Manual Refresh

SharePoint – Excel Services – External Data Cache Lifetime

d. SharePoint Excel Web Part Properties

1. Create a new page or using existing page. Edit the page by clicking on Page ribbon tab > Edit Page. (or Site Settings > Edit Page)

SharePoint – Edit Page

2. Click on ‘Add a Web Part‘ link
3. Click on ‘Business Data‘ under Categories and then click on ‘Excel Web Access‘ under Web Parts section. Click Add button on the right side of the screen.

SharePoint – Add Web Part – Categories > Excel Web Access

4. Excel Web Access – Select a Workbook web part will come up on your page. Click on link that says ‘Click here to open the tool pane

SharePoint – Excel Web Access – Select a Workbook

5. Excel Web Access Web Part Properties section comes up on the right side of the page. Select an Excel file under Workbook field.

SharePoint – Excel Web Access Web Part Properties – top

SharePoint – Excel Web Access Web Part Properties – bottom

The default refresh connection settings on that web part are:

Section Option Default
Toolbar Menu Command Refresh Selected Connection, Refresh All Connections Checked
Interactivity Periodically Refresh if Enabled in Workbook Unchecked

You can leave the default setting for “Refresh Selected Connection, Refresh All Connections” to have that refresh option for your end users. Alternatively you can uncheck that option to remove refresh connection option for your users.

6. Optionally expand the Advanced property section of the web part and uncheck following options:
Allow Close
Allow Hide
Allow Editing in Personal View

SharePoint – Web Part Advanced Properties

7. Click Apply at the bottom right of the web part properties.
8. Review the Excel Web Access file and go to Data menu and see Refresh options.
9. Edit the web part properties again and uncheck the option “Refresh Selected Connection, Refresh All Connections“. Click Apply to save changes. Now review the Data menu and you will notice the refresh options are now removed.

SharePoint – Excel Web Access – Data menu

10. Excel Web Part property ‘Type of Toolbar‘ is by default set to full. That displays toolbar options based on settings. You can set that option to Summary, Navigation or none. These settings also hide or show refresh options in the Excel Web Access tool bar.

References:

External Data Cache Lifetime reference:
http://technet.microsoft.com/en-us/library/ff191194(v=office.14).aspx

Excel 2007 with Excel Services Reference
http://office.microsoft.com/en-us/sharepoint-server-help/refresh-external-data-in-excel-services-HA010105474.aspx

Excel Web Access Web Part custom properties (Sharepoint 2010)
http://office.microsoft.com/en-us/sharepoint-server-help/excel-web-access-web-part-custom-properties-HA010377893.aspx

Getting Started with Excel Services and Excel Web Access
http://office.microsoft.com/en-us/sharepoint-server-help/getting-started-with-excel-services-and-excel-web-access-HA010377881.aspx

Excel Services 2010 Data Refresh Flowchart: What is going on behind the scenes
http://blogs.technet.com/b/tothesharepoint/archive/2011/07/29/troubleshooting-excel-services-data-refresh.aspx

Excel Services data refresh flowchart
http://technet.microsoft.com/en-us/library/hh369968.aspx

Overview of connecting to (importing) data
http://office.microsoft.com/en-us/excel-help/overview-of-connecting-to-importing-data-HP010342748.aspx

Excel 2010 – Connection Properties
http://office.microsoft.com/client/helppreview14.aspx?AssetId=HA010342299&lcid=1033&NS=EXCEL&Version=14&tl=2&queryid=&respos=1&HelpID=22115

Excel 2010 – Refresh connected (imported) data
http://office.microsoft.com/client/helppreview14.aspx?AssetId=HP010342826&lcid=1033&NS=EXCEL&Version=14&tl=2&queryid=&respos=1&HelpID=199707

Configure Excel Services data refresh by using the unattended service account (SharePoint Server 2010)
http://technet.microsoft.com/en-us/library/hh525344(v=office.14).aspx

Configure Excel Services data refresh by using external data connections (SharePoint Server 2010)
http://technet.microsoft.com/en-us/library/hh525341(v=office.14).aspx

Keyword:

  • SharePoint  BI
  • Excel Web Access BI
  • Excel Web Services BI
  • SharePoint Business Intelligence
  • Softvative SharePoint BI Data Refresh Chart
  • Data Refresh Chart
  • Excel Data Refresh Options
  • Excel Data Refresh Settings
  • Excel Automatic Data Refresh Options
  • Excel Manual Data Refresh Options

MS14-022 Critical Vulnerabilities in SharePoint ProjectServer

Tuesday, May 13th, 2014
Recently Microsoft Security Bulletin MS14-022  has been released as Critical. It covers following products:
  • Sharepoint Server 2007, 2010, 2013
  • WSS 3.0
  • Sharepoint Foundation 2010 / 2013
  • Office Web Apps Server 2010 / 2013
  • Sharepoint Designer 2010 / 2013
Risk: High
Discovered: 05/13/2014
The security update addresses the vulnerabilities by correcting how SharePoint Server and Web Applications sanitize specially crafted page content.
Vulnerabilities in Microsoft SharePoint Server Could Allow Remote Code Execution (2952166)
MS Knowledge Base Article
MS14-022: Vulnerabilities in Microsoft SharePoint Server could allow remote code execution: May 13, 2014
Vulnerabilities Summary:
#
Vulnerability
CVE
Mitigating Factors
1
To exploit any of these related vulnerabilities, an attacker must be able to authenticate on the target SharePoint site. Note that this is not a mitigating factor if the SharePoint site is configured to allow anonymous users to access the site. By default, anonymous access is not enabled.
2
CVE-2014-1754
Microsoft has not identified any mitigating factors for this vulnerability.
3
To exploit this vulnerability, an attacker must be able to authenticate on the target SharePoint site. Note that this is not a mitigating factor if the SharePoint site is configured to allow anonymous users to access the site. By default, anonymous access is not enabled.
Security Resources
It is good to review the SANS Internet Storm Center for the criticality of these updates
https://isc.sans.edu/
SANS Internet Storm Center – May 2014 Patch Tuesday
Search on the Security Focus site
Recommendation
Run all software with less-privileged user with minimal access rights.

Add new Server in Farm with SharePoint, MSPS, OWS and LPs

Tuesday, May 13th, 2014
How to add a new server to the SharePoint Farm when the farm is running:
a. SharePoint 2010
b. MS Project Server 2010
c. Office Web App Server 2010
d. Language Packs

I ran through these steps.

1. Attach Setup files to new server [CD, Virtual Cd image, or setup files]
2. Start SharePoint setup and begin the SharePoint Pre-Req install
3. It failed listing update KB976462 as causing install error
4. Re-Ran the pre-req and it worked
5. Run the SharePoint 2010 setup
6. Change drive letter for Setup Data folder to D: drive. Leave the folder location with D drive as same. Also leave the SharePoint installation directory to C: drive default location
7. At the end of setup uncheck the option to Run Configuration Wizard and click close button.
8. Install Project Server 2010 setup (follow steps 6 & 7 during its setup and don’t run config wizard)
9. Install Office Web App 2010 setup (follow steps 6 & 7 during its setup and don’t run config wizard)
10. Install Language Packs for English, Chinese, Arabic or others. Install language packs for SharePoint 2010 Server version. (follow steps 6 & 7 during each setup and don’t run config wizard)
11. Install Service Pack 2 for SharePoint 2010 Server, Project Server 2010, Office Web Apps 2010, Language Packs SP 2 for each language listed in step 10 above. (follow steps 6 & 7 during its setup and don’t run config wizard)
12. Current Farm patch version was 14.0.7105.5000
13. Download Aug 2013 CU update that matches the version number for this patch.
14. Run SharePoint Config Wizard to join the server to the farm
15. Configure and verify the new server.