"Failed to retrieve a designer token" after launching Workflow 5. However, it works for reportin (no such error). It is pretty sure that the workflow 5 license is not expired.
-
Hi Steven,
A few questions to help narrow down the potential cause:
- What version did you install?
- Are you logging into Designer using the same user account that you used when running the Post Installer?
- What type of security are you using for logins?
Thanks, Stefan
0 -
@Stefan Schweigert? , I just now got this error as well. I was just using GW5 yesterday and it was working fine but now I got this error. I then upgraded to 5.12 to see if that was the issue at all and it still gives me this error.
We are using OAuth.
Thanks,
Nelson
0 -
Hi Nelson,
I have a few questions to help narrow down the issue you are seeing:
- Can you re-run the Post Installer software for Workflow and ensure that the Portal settings are still valid?
- What are your security settings configured as in IIS for your site?
- What version of Portal are you authenticating with?
- Did you make any changes to your infrastructure or setting for Workflow during the upgrade?
Thanks, Stefan
0 -
- Re-ran the post install multiple times. Even uninstalled and reinstalled the application as well. Even reverted back to previous versions.
- Anonymous was enabled and that was it
- 10.7.1
- No changes. In Place upgrade and left all settings the same.
0 -
I am now seeing this error when going to the designer:
We could not connect to Geocortex Workflow. Please ensure it is configured correctly.
I also don't see ASP.NET feature in my IIS for this application. ASP.net is installed and enabled for others (Web/Printing/Report) and visible in the features view but not for the Workflow.
0 -
I'm getting the same error for users besides myself. I can access it, but other users are getting this error.
0 -
Here is the error response we are getting:
{
"error": {
"id": "GW001.403",
"message": "GW001.403: Access Denied",
"status": 403
}
}
0 -
Never mind, I found out what the issue was. The workflow application created in Portal was not shared. I created a group for users who create and modify workflows, and shared the workflow application in portal to this group.
0 -
@Steven Chen? @Nelson Dobbs? Hi guys! We have a GXWF 5.18 release in partner availability (GA next week) that adds improved logging here. Please let me know if you are still seeing this issue and we can look further.
0 -
We are experiencing this issue with release 5.12 (had to install this to mirror PROD before upgrading to the latest release). We've set up a DEV server where all apps are sitting on one machine, and installed the web adaptor extensions as per https://communities.geocortex.com/s/article/Install-the-Geocortex-Web-Adaptor-Extensions, including adding the service account we use for running the Geocortex App pool to the local group, restarting the server etc.
When running up Workflow designer in a browser the sign-in process works fine until Portal routes us back to the designer login page. We then see the "Failed to retrieve a designer token" error, checking the browser dev tools we see this:
The browser console shows: Designer access check failed Error: Failed to retrieve a designer token.
The Network tab shows a POST request to ../geocortex/Workflow/service/auth/token/designer that failed with error code 400.
The request payload contains what looks like a valid Portal token and there is nothing else about the request that provides a clue as to what the actual problem may be. The domain account we use to run the application pool has sufficient privileges on the VM and we're not seeing this behaviour on the PROD VM.
Has anybody found a cause (and ideally a solution) for this?
Thanks for any information you can share!
0 -
@Jan Roggisch? Hi Jan, there are a few potential causes for that 400 error, we added logging to the Windows Event Log in GXWF 5.18 to help identify the specific cause in your deployment. I'd suggest upgrading your dev environment to that version (or the latest 5.19) and have a look at the Event Viewer on the server to see what errors show up there. I'd also suggest sending us an email at support@geocortex.com so that we can work with you directly to troubleshoot.
0 -
Hi Gareth, thank you for the quick response!
I'll try the 5.19 release and email support if that doesn't help fix the issue.
0 -
Was this issue ever resolved?
I'm running Geocortex Workflow 5.24.
I could successfully test the app registration in the post-installation, but when launching the workflow designer, I get this error message;
We could not connect to Geocortex Workflow. Please ensure it is configured correctly.
Any idea what could be the cause of this?
Thanks,
Jan
0 -
@Jan Creupelandt? this "could not connect to Geocortex Workflow" error means there is an underlying technical problem preventing us from connecting to the GXWF server.
I have seen this caused by a broken .NET runtime on the GXWF server. Try repairing the .NET runtime from the Add/Remove programs panel on the server.
If that does not fix the issue, please submit a case by emailing support@geocortex.com and we'll troubleshoot it with you.
0
Please sign in to leave a comment.
Comments
14 comments