Skip to main content
Content Starts Here Search Solutions

Solution Detail

 
Solution TitleI am getting the error "Flow Validation Error: User managed backing folder does not exist"
Solution Number00000737
Solution Details
Symptoms

When I try to activate my flow I get the error "Flow Validation Error: User managed backing folder does not exist"

Cause

This can be caused by a permissions issue. 

Switch has several processes which run with different permissions:

Switch Designer.
This process is the UI, it runs with normal permissions.

Switch Server.
This is the name to describe all background processes. These run with elevated permissions.

The problem with network locations mapped to a drive letter is that they are not shared between these two permission levels. This means that when you mounted the network shares to drive letter on the normal permission level (which is default) that:

Local Switch Designer will be able to see the shares. Therefore you will be able to use a folder from such a share in a browse dialog.

Switch Server will not be able to see the share. This means that if you would activate a flow containing such a folder it will error. This is because Switch Server verifies flows, Switch Designer does not.

When you are using a Remote Designer, then it gets all it's information from the Switch Server processes. Those are running elevated, which means they can't see the network shares mapped to drive letters on a normal permission level.

Solution

There are some possible solutions:

1 Use UNC paths instead of network locations mapped to drive letters.
This is what I recommend since it avoids the security issues.

2 Map the network shares to drive letters both on the normal permission level and the elevated permission level
If you already have it on the normal permission level, then you can add it on the elevated permission level like this:
- Right click Cmd in the start menu and choose "Run as administrator"
- Use the "Net use" command to mount the share. You can find more information here:
https://technet.microsoft.com/en-us/library/bb490717.aspx

3 Disable the security feature with the two permission levels.
Please be aware that this is lowering security, you can find more information here:
http://security.stackexchange.com/questions/94528/does-enabling-enablelinkedconnections-pose-a-security-risk

You can find out how to do this on the following page:
https://technet.microsoft.com/en-US/library/ee844140%28v=WS.10%29.aspx














 
Does this solution help you answer your question?