MSA-eService: eService Portal Account Sign-up Workflow Fails to publish


After importing the customizations I experienced some problems with publishing a few of the workflows. In another post it was suggested that a work around was to recreate the workflow which for all of the others has worked nicely. With the eService Portal Account Sign-up Workflow however there are some fields I have not been able to recreate. The contact record id is encrypted and that was the piece that failed for me. The line reads Encrypt the Contact Record Id for the Email.
I am also unable in the actual step to send the e-mail [Send an e-mail with instructions on how to create an eService portal account] unable to setup the query string with the EncodedContactId(Encrypt the Contact Record Id for the Email). I assume this is because the previous step to encrypt the e-mail has not been created.
Has anyone else experienced this or can point me in the right direction?
Thanks in advance.


gherbstman wrote Dec 5, 2008 at 7:01 AM

My workflows imported just fine however, the Account sign-up does not function correctly. It is a problem with the custom workflow assemblies. The EncodedContactID fails and the e-mail is sent with the name of the function rather than the ID>

wrote Dec 5, 2008 at 7:02 AM

gunterdc wrote Jan 7, 2009 at 3:04 PM

When trying to install the msa-eService I got errors when importing customizations using the msa_eService.Install.exe. I imported the customizations (eservice-customizations.xml) using crm import customizations and published the customizations. Two workflows cannot be published : 'Case note added via eservice portal' and 'service portal account sign-up'. Is this due to the import ? Other workflows are changed as described in the video. Is there a way to verify the workflow or a way to create the workflow manualy ?

gunterdc wrote Jan 9, 2009 at 11:04 AM

I installed msa_eService out of the solution (source) instead off running the exe. I debugged where neccessary and succeeded installation. Altering and publishing the workflows went fine.

eServiceNazi wrote Mar 17, 2009 at 1:23 AM

I have similar problems to gherbstman.

I get one of two results, depending on how I create the link in the form. Either the link appears properly, but has a link value that is inappropriate:

https://productsupport.company.com/createuseraccount.aspx?id=3dZAcpar37hewu2ZLUHQMe1SPD4T3GwmxPQSN3OeYZ8vtP%2bHvi%2bfbRT4sxyD1ImA <https://productsupport.company.com/createuseraccount.aspx?id={EncodedContactId(Encrypt the Contact Record Id for the Email)}>

Or the link is created using only first half of the link (ie, only "https://productsupport.company.com/createuseraccount.aspx?id" appears in "blue" text as an html link), with the = and the encrypted hash appended immediately after it with no space, but not as part of the link. In this case, it works from email clients that view things in plaintext, but not html enabled mail clients.

I've tried importing the customization for this particular workflow directly from the source again, and the original workflow exhibits the same problem, i.e., it prints out the whole text for the link neat as you please:
But only the first part of it, up to the = (http://moss:4444/createuseraccount.aspx?id), is part of the link that gets created.

Anyone seen this/have a thought for a solution?


wrote Jul 7, 2009 at 5:57 PM

NZRegs wrote Jul 19, 2009 at 11:34 PM

i aslo could not publish workflows. adding the following entry back into my web.config file fixed this for me:
<authorizedType Assembly="mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Globalization" TypeName="CultureInfo" Authorized="True"/>

This is a known bug that occurs after you deploy crm hotfix rollup 2 to a server - http://support.microsoft.com/kb/959419

cheers, regan

fraterminor wrote Dec 11, 2010 at 6:30 PM

@eServiceNazi: Have you found a solution to the "linking-problem"? I am experiencing the same on my CRM 4.0

patrickmwangi wrote Mar 7, 2011 at 7:49 AM

The issue has put me at loggerheads with my boss.Has anyone found a solution?

NZRegs wrote Mar 7, 2011 at 9:30 AM

to generate the links properly, install the business productivity workflow tools accelerator and re-write the workflow using the html hyperlink creation custom workflow addin.
accelerator here: http://crmaccelerators.codeplex.com/releases/view/26691

@patrickmwangi: which problem, exactly, do you have? If its the one where the workflow wont publish then check my comments about the missing value in the web.config file

patrickmwangi wrote Mar 7, 2011 at 10:26 AM

My issue is similar to the one eServiceNazi wrote. The workflow published succesfully.However in the registration e-mail that the contact is sent ,there is a link with the encoded id.On clicking the link, the encoded ID is left out hence forcing the contact to copy the link and paste it to his browser which is a little bit too cumbersome as opposed to just clicking the link and getting the webpage to open

NZRegs wrote Mar 7, 2011 at 7:49 PM

as per my last message, downlaod and install the business productivity workflow tools accelerator and modify the workflow to use the "Generate Generic Hyperlink" function to construct your URL instead of the step that ships with the eService portal. The "Generate Generic Hyperlink" function allows you to create a hyperlink from a base url and up to 7 parameters and also lets you use different display text for the link.

the modification will only take a few minutes

patrickmwangi wrote Mar 8, 2011 at 1:20 PM

@NzRegs.This is an awesome tool i admit but theres one major bug that ought to be looked into carefully. Take for instance "Generate Generic Hyperlink" and using the eservice portal as our casepoint ,once you fix "EncodedContactId(Encrypt the Contact Record Id for the Email)" as the first parameter after giving a static url in the first textbox, the accelerator seems to work well upto the point you look at the url generated after opening the email.You will notice that all "2"'s with "52".Please look at this .Ill be greatfull,...Good work though.

wrote Feb 21, 2013 at 11:10 PM