The Blog

This is an old one, but some co-workers ran into this again recently on a project.

When you have a SharePoint workflow that assigns tasks (either Designer or Visual Studio workflow), when you change the Assigned To column on the task list to allow Multiple Selections, your workflow will hang and become unresponsive when a user edits the task. You’ll receive a message about the task being locked (“This task is currently locked by a running workflow and cannot be edited”). OnTaskChanged events will no longer fire and your workflow will be stuck and unrecoverable.

There is no hotfix or workaround for this, so you simply cannot have the assigned to column support multiple users or groups. Just use a single group instead.

Following are some other resources discussing this:

I’ve just released a beta of xPollinate, my Windows Live Writer Cross Post Plugin.

You can download the installer at the CodePlex site, and I’ll shortly post it on the Live Writer plugin gallery.

As an example, I’ve used it to cross-post this entry to my old Blogger account, as well as via Ping.FM to my Twitter feed (status method) and as a full blog post to my Tumblog.

UPDATE 3/31/09: Plugin is now available on the Live Writer Gallery here.

I’ve seen several examples of creating document converters in SharePoint that convert documents to PDF format, using tools like Aspose and other print-based solutions.

I recently did a proof of concept for a customer that used a different product, Outside In PDF Export from Oracle. This is an interpretive converter that can take a slew of file formats (including MS Office) and automatically convert them into a PDF file. If you aren’t familiar with PDF conversion, there are two basic kinds:

  • Print based conversion – This is the Acrobat Distiller approach. Uses a printer driver that accepts the PostScript output from an application (such as Microsoft Word), and converts it to PDF. This approach results in the most accurate conversions, but is hardest to automate because it involves opening the native application and automating its “Print” functionality.
  • Interpretive conversion – This is an approach that reads the contents of a native file format and translates the contents into PDF format. This results in potentially less accurate conversions, but is much easier to automate.

Outside In, and in particular the PDF Export SDK, is an EXE and set of DLLs that contains logic to covert over 400 different file types to PDF. In combination with Transformation Server (a web services wrapper to PDF Export), you can create SharePoint Document Converters that will convert your documents to PDF format.

How I Did It

For the proof of concept, I followed these steps to get it working

  • Download PDF Export, Transformation Server, and SrvAny.exe.
  • Install and Configure the Transformation Server and Web Service
  • Develop and Install the Document Converter

Download of PDF Export 8.3.0 and Transformation Server 8.2.0

You can download both products here:

http://www.oracle.com/technology/products/content-management/oit/oit_dl_otn.html

You’ll have to register with an Oracle account to get it, but it is a freely available trial version, and does not appear to have any trial expiration limitations.

You will also need SrvAny.exe to run Transformation Server as a Windows Service. I found this site that had a download:

http://www.tacktech.com/display.cfm?ttid=197

Install and Configure the Transformation Server and Web Service

Extract the contents of the Transformation Server zip you downloaded to a folder on your server that will do the document conversions (e.g. “C:PDFConverter”). There will be a bunch of dlls, some wsdl files (we’ll use those later), some EXE’s (which are run as a service), and some XML config files.

Transformation Server doesn’t really know anything about PDF generation, it is just a web service wrapper, so we’ll need to place the PDF Export library into our folder so it can use it. Extract the contents of PDF Export 8.3.0 to a separate folder on your machine. Grab every DLL in the root folder, as well as exporter.exe, px.cfg, and cmmap000.bin and copy those files into “C:PDFConverter”.

Open the file called server_startup.xml in “C:PDFConverter”. This configures the service to listen on a specific port and hostname/ip address. I went ahead and changed the port, but you can leave it as is if you wish, just make note of the port for later:

Go ahead and double-click tsmanager.exe to make sure it is working. It should open a console window and show you what host/port it is listening on.

tsmanager console

Press Ctrl + C to quit.

Now we need to run this program as a service, so that it is always available, even when nobody is logged on to the server. Place instsrv.exe and srvany.exe in your C:PDFConverter folder. Run the following command prompt:

Open regedit, and browse to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTransformation Server.

Create a new key called Parameters, and add a new string value inside this key called Application, with a value of C:PDFConvertertsmanager.exe.

ts registry entries

Go to the services console and start the Transformation Server service. Optionally, you can also go to the Properties for this service account, and change the Identity that this service runs under.

Develop the Document Converter

Create a new .NET C# console application project and solution from within Visual Studio 2008, called PDFConverter.

Right-click the project in Solution Explorer and choose Add Service Reference…

Since the wsdl files for Transformation Server are not compliant with WCF services, choose the Advanced… button on the Add Service Reference dialog, and then choose the Add Web Reference… button to add a .NET 2.0 style web service reference. In the Add Web Reference dialog, enter the path to the wsdl file: C:PDFConvertertransform_net_2005.wsdl. Hit Go.

Once your web reference has resolved, enter TransformationServer in the Web reference name box and click the Add Reference button.

Open your Properties/Settings.settings file. There will be one setting in the file for the web service URL. Change this to the right hostname/port in your server_settings.xml for Transformation Server. Make sure to include a trailing “/transform” on the end, e.g.:

http://www.lifeonplanetgroove.com/transform

A document converter is just a console EXE that is called by SharePoint with command line arguments, so we’ll setup our console app to handle the arguments. In Program.cs, before static void Main, add the following code (taken from the WSS SDK here):

Add the following code inside static void Main:

Now that the command line arguments can be parsed, it is time to use the web service and do the document conversion. The Transformation Server download contained some code samples for C#, and I was able to basically use as-is, only modifying the input and output file paths. After the argument handling code in static void Main, add the following code:

Most of this code is cut-and-paste from the sample, and we are just swapping the input file path (source.spec.str) and output file path (sink.spec.str) with the arguments from the command line.

Installing the Converter

To install the converter, you need to create a feature file, install the feature, and place the converter EXE in the proper directory.

Create a feature.xml file and add the following:

Create an Elements.xml file, and add the following code. You can create as many document converter nodes as you need for each file type you want to convert (just make sure each has a unique guid).

Place both these files in a folder called PDFConverter in your …/12/TEMPLATE/Features folder, and use stsadm to activate the feature on a particular web application.

After activating the feature, go to Central Administration, Applications tab, and click the Document Conversions link. Ensure that your web application has document conversions turned on. You should see your document converters in the list at the bottom of the screen:

Document Conversion Settings

Since you are using a Web Service, a proxy class needs to be generated dynamically, and so you’ll need to give your SharePoint Document Conversion User Account rights to create this in C:WindowsTemp (or whatever your system temp directory is). Grant List Folder Contents and Read permissions to the Document Conversion account (usually a local machine account that starts with “HVU_”) on your Temp folder.

The Document Conversion service stores temporary documents in the following folder: C:Program FilesMicrosoft Office Servers12.0BINHtmlTrLauncher. By default, this folder only grants the Document Conversion User account access. Since the Transformation Server windows service is running under its own account, you need to give this account access to the folder. Grant the account that your Transformation Server windows service is running under Read and Write access to this folder.

The last step involves copying over your compiled console EXE and exe.config file into the following SharePoint folder (the actual path may vary depending on your setup, but you should be able to find the TransformApps folder):

C:Program FilesMicrosoft Office Servers12.0TransformApps

Results

Navigate to your SharePoint site. Upload a document into your document library (make sure it is a file extension that you’ve configured in your Elements.xml file). Open the drop down menu and choose Convert Document. Your document converter should appear in the list. Run the conversion. After around a minute if you refresh your document library and all went well, you should see your PDF file in the library.

Generated PDF in document library

Here is a picture of a generated Visio document in PDF format, not too bad:

exported visio file

I am just finishing up the touches on my first Windows Live Writer plugin, which I’m calling xPollinate. I’ve wanted to cross post to multiple blogs as well as Ping.FM from Windows Live Writer, and originally I found this plugin by Daniel Cazzulino that was not perfect, but got the job done.

I used this plugin as a basis and then added a bunch of bells and whistles that I wanted. Following are some feature enhancements that I’ve added:

  • Cross post to multiple blogs at the same time
  • Choose blogs to post to at cross post time
  • Set plugin defaults through the options dialog, and override at posting time.
  • Ability to turn comments and trackbacks (pings) on/off at the cross posted blog
  • Add header or footer html to each cross posted entry
  • Cross post to Ping.FM
    • Supports triggers and services
    • Post using blog, microblog, or status methods, simultaneously or individually

Here are some screen shots:

The Blogs Tab:

xPollinate Blogs Tab

This enables you to select multiple blogs to cross post to. You can optionally post a summary, and include header and footer text.

The Ping.FM tab:

xpollinate-options-ping-large-triggers

This enables you to post your blog entry via Ping.FM to your configured services. You can post a full or summarized version to your Ping.FM blogs, and can post a notification to your Ping.FM status and microblog services. The format of the notification is customizable.

Left to Do

I’ll be releasing this as a free plugin to the community, and will release the source as well. The final few things I have left to do are:

  • Clean up the installer
  • Get a public API key from Ping.FM
  • Submit to the Live Writer plugin gallery

When I was a kid, I remember my doctor really taking care of me. There were just things that doctors did that were expected of them, such as:

  • If a wound was dirty, the doctor would clean it
  • If medicine needed to be prescribed, and the doctor’s office had some, they would administer the first dose in the office
  • If a sibling looked to be suffering from the same ailment, they wouldn’t have to be setup with a separate formal visit
  • Multiple prescriptions might have been given at the same visit (e.g. “try this first, if it doesn’t work then try this”), saving multiple office visits

After taking my son in to be looked at for Pink Eye, I was amazed at how much things have changed.

We didn’t clean his eyes before the visit, to make sure that the doctor saw the discharge. She looked at his eyes which were all goopy, and didn’t even clean them out when she was done.

I guess they didn’t have any eye drops on hand to offer the first dose onsite, but even if they had, they wouldn’t have done it anyway.

His sister’s eyes were also starting to get goopy, and it was a good bet at the time that she got what her brother had. Of course, the doctor couldn’t offer any suggestions for her, she needed a separate visit because “she was not in the system yet”. Along those lines, she told us that his sister couldn’t use his drops because she was under a year old, and they typically use an ointment instead of drops. I guess I just wondered why she couldn’t have prescribed both meds for him, and let us use the ointment on her, since she was clearly progressing along the same lines as her brother.

I don’t know what the reasons are, maybe it’s fear of lawsuits, maybe it’s financially motivated to increase office visits, maybe it’s just a shift in expectations that’s occurred as a result of limited time and budgets. In any case, it ain’t what it used to be.