You are viewing limited content. For full access, please sign in.

Question

Question

Import Workflow gives error " A web service already exist with the name forms [0673-WF1)"

asked on May 3, 2016

I'm importing a large workflow from a client to a backup VM, when i try to import the workflow i get the error "A web service already exist with the name forms [0673-WF1)" at the end. 

After this i get a summary of the import, when i click finish i get the error.

So i already have a web service name "forms" which is correct, i can create a new web service but i cant change the web service name in the import and i cant change the web service name from the original workflow i exported the process out of.

How can i fix this ? I've had this issue before and just rebuilt the workflow, but htis workflow to large to do that.

0 0

Replies

replied on May 3, 2016

Do you have security set up on the Workflow Server? Sounds like the user importing does not have rights to create a new web service.

0 0
replied on June 18, 2018

I'm running into this issue as well and I believe all my security settings are correct. Any help would be appreciated.

2018-06-18_10-35-50.png
0 0
replied on May 3, 2016 Show version history

I'm logged in as Admin when i do the export and when i try to import, i think the problem is a naming issue as there is a web service on the VM that i am trying to import to already called "Forms".  i can create a new wen service, but cant delete the "Forms" one as it has processes linked to it. 

0 0
replied on May 3, 2016

This is not about the repository user, Workflow security uses Windows accounts, so it's not "admin".

When you import this workflow, are you prompted to rename the web service before you get this error?

0 0
replied on May 3, 2016

No i dont get a prompt to change the web service name.

I'm logged in as windows local administrator on the exported workflow server and as domain Administrator on the the VM server.

 

0 0
replied on January 3, 2020

Just to update this old thread, the issue was found to be related to mishandling the situation where the web service name in the workflow matches the name of an existing web service on the Workflow Server, but with a different casing.

In this scenario, since the Workflow Server has a web service name, "forms" and the workflow that's trying to be imported is using "Forms" then one workaround would be to edit the .wfi file, looking for

<Name>Forms</Name>

and replacing it with

<Name>forms</Name>

This would allow the workflow to be imported. Bug 216385 has been filed for this issue.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.