I keep getting this error that the remote name could not be resolved 'laserfische' when trying to start business processes. Looks like a typo to me, but I can't find where you enter any remote name in configuring business processes, I thought it just used whatever was configured in the workflow web services area. I found the typo there and corrected it and apparently that is not the correct area.
Question
Question
where is the business proccess remote name specified
Replies
Be sure to republish the workflows/business processes after you've made a change to the Workflow Web Services configuration.
I am having this same issue
When I checked the Workflow Web Services, it shows the IP address instead of the server name. The only place I see in the configuration manager that states the actual Server name is in the Monitored Repositories:
Here is the detailed log:
Error Code: 0
Error Message: Error launching Business Process:
Entry: \0 Records Management\Employee Records RM\0 Permanent\Employee Records\W\Wxx, Xxxxx (xxxxx)\Medical\Wxxx, Xxxxx (xxxxx)-Workers Compensation Form-01/18/2018
Error Type: Network Error
Error Message: The remote name could not be resolved: '862133-processi'
------------ Technical Details: ------------
LFSO:
LF.exe (10.2.0.839):
Call Stack: (Current)
LaunchBusinessProcess
CFolderListCtrl::OnStartBusinessProcess
Call History:
CGroupProvider::raw_GetAllGroupIdentifiers
CGroupProvider::raw_GetAllGroupIdentifiers
CGroupProvider::raw_GetAllGroupIdentifiers
CGroupProvider::raw_GetAllGroupIdentifiers
CGroupProvider::raw_GetAllGroupIdentifiers
CGroupProvider::raw_GetAllGroupIdentifiers
CGroupProvider::raw_GetAllGroupIdentifiers
CBusinessProcessManager::GetStartingInstructionsDocument
We have resolved this issue by editing the host file locally on their machine (C:\Windows\System32\drivers\etc\hosts file) and specifying the IP address and server name at the bottom of the file.
It was a case where the customer renamed the server long ago and I had to dig through the Workflow Administration utility where I found multiple references to the old server name, after fixing them it finally worked.
The hosts update would also be a workaround but if you can find it in the Administration console that is best, I can't remember which setting it was now.
The name of the web server is saved in the repository when the business process is published. If the WF server is moved, then the business processes need to be republished or the new server can be DNS-aliased to the old server or the client machines need to have their hosts files updated.