Archive for the ‘HowTo’ Category

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

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

Softvative Video – Linksys 003 – Connecting WRT54G WiFi Router with E3000 Wirelessly

Sunday, October 9th, 2011
The video covers how to connect Linksys WRT54G WiFi router with Linksys E3000 Wirelessly.

Softvative Video – Linksys 002 – WRT54G Wifi Router Upgrade firmware to DDWRT

Sunday, October 9th, 2011
The video covers how to upgrade Linksys WRT54g router to DD-WRT open source firmware.

Using Sharepoint 2010 Document ID Feature for PMO Documents

Thursday, July 7th, 2011
SharePoint 2010 has introduced a new feature called Document ID. That feature allows SharePoint to assign unique IDs to documents. This helps in content management scenarios. A Project Management Office (PMO) using Project Server 2010, can leverage this feature for their PMO documents.
MS Project Server 2010 application can be configured in different ways. This document assumes that there are two web applications – one for Project Web Access and the other one for Project Workspaces (Project SharePoint Sites)
Project Web Access
http://projectserver/pwa
Project SharePoint Workspaces
http://projectsites/sites/ps
Turn on Document ID feature for both /PWA and Project Sites site collections.
When the Document ID Timer Jobs completes, IDs are assigned to each document. Go to View Properties page of a document to view the Document ID for it.
To view it, hover the mouse over a document in a document library then from dropdown chooses View Properties. Alternately, you can select a document and click View Properties on ribbon under Library Tools ; Documents.
SP Document ID Feature 01

SP Document ID Feature 01

 You can add the Document ID column in a SharePoint library view to see the IDs for each document.
Once the Document IDs are assigned in a site collection, a search web part ‘Find by Document ID’ becomes available for the site collection. That web part allows users to enter the Document ID for a document and get the document in a pop up.
Once the ‘Find by Document ID’ web part has been added to a page by your administrator, users will be able to locate documents using document ID. To find a document, enter the document id in the correct format in the field.
1.    The web part will show the document ID search field on the page with the Document ID format for the site collection
SP Document ID Feature 02

SP Document ID Feature 02

2.    Enter the Document ID of a document and click on Go button next to the field. That will bring the document in a popup
SP Document ID Feature 03

SP Document ID Feature 03

3.    Click on Open to review the document
1.    The same Find by Document ID web part can also be used from the search center. Go to search center site (for example: http://projectsites/sites/projectsites/search) Enter the document id of a document in ‘Find by document ID’ field and click Go button next to it.
SP Document ID Feature 04

SP Document ID Feature 04

 2.     Optionally, users can enter the document id in the search box and click on search icon to do a general search on document id. User can search using the initial characters in the ID up to a specific library to get search results for a specific library. Like 289 refers to a specific project workspace