Workflow Soluiton

I'm in the process of shifting a Workflow server from using its actual name to a cname (alias).  I used the LocalMachineInfoEditor to modify the "Server Details" and "Workflow Server Setup" settings to use the new cname.

Everything is working fine including all our workflows except for a few odd page elements which remain fully pathed to the original server name.  Elements include ExpandCollapseReportGrid.js, resizable-tables.js & documents-expand-down.gif.  These show on the page as broken elements and they show up in the browser developer tools as errors.

I know one solution is to run the Workflow installer again with the new cname but I'd really like to understand where this previous server name is stored.  I've checked registry, the Process Manager db and numerous files in the install folder to no avail.

Can anyone advise?

Unless all of your components were using a project property, the components will have that configuration specificially.  Unfortunately, that is one of the headaches of what you are doing, and since there is no real validation until you run the Workflow, you are kind of stuck with the long and tedious form of troubleshooting Workflows.

Sorry.

Hi Lark,

I've spoken to support about this not too long ago, and if I remember correctly the only way to fix this is to repair your workflow environment with the new name.

It's a fairly straightforward and a quick process as not much is changing in your environment for the name to be changed. I would suggest you snapshot/backup your environment beforehand however just in case. 

Let us know how you get on, thanks!

Thanks Sam - I came to the same conclusion and finally got a change through to try this out today.  No luck though - same problem after a repair using the new cname.  Nothing else broke though (other than a little css tweaking - easily fixed) so yes it was fairly straight forward.

Its weird  - everything seems to work fine except for links and image references within the Standard Report Viewer web part.  Its almost as if whatever delivers these web parts is doing some sort of reverse lookup when the request is from a remote source.

For example;

Remote browser to [alias.mydomain] - links in web part refer to [servername.anotherdomain]

Local browser to [alias.mydomain] - links in web part refer to [alias.mydomain]

Local browser to [localhost] - links in web part refer to [localhost]

Local nslookup on servers IP yields [servername.anotherdomain]

I do have two domains here and yes there is another IIS server doing a domain re-write on the way through which complicates things.  As far as I know, everything else is working in this setup though - other Process Manager components and various workflow forms we use.

Hi Lark,

I think the next best course of action would be to create a ticket for this through Support. They'll be able to look into these specific components in more detail and see why this is occurring.

Thanks