Repair web.config After Opening a Published Project

There are sometimes circumstances (ahem, ServiceDesk) which require that we open a published Workflow file.  By deleting or otherwise adjusting the “project.deployed” file name that sits in the published project directory, we are able to “unlock” that project for editing in the Workflow designer.

2015-06-12_15-06-19

However, once that project is again published, errors arise that source back to the web.config file.

2015-06-12_15-10-27

This is because the web.config content is being improperly built upon publish.  The duplicate “add name” entry for the StartDialog.aspx path is causing the form not to load.

In order to repair this, locate the web.config file in the Projects directory (either by browsing to the directory on the designer server, or by clicking the top-level object in the project tree in the workflow project, shown below).

2015-06-12_15-13-16

In the web.config file, delete the following line:

2015-06-12_15-14-45

and save the file.  Remember that this is the web.config file in the Projects directory, not the Deployed directory.

Republish the project and try again.  The form should now load properly (assuming no other errors exist).

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s