We have a customer where Nintex Workflow 2013 is installed on two environments, a quality environment and a production environment. In the quality environment we can work with Nintex without an issue. On production however WorkflowDesigner.aspx is not loading correctly.
This is what the issue looks like (it is also impossible to use most ribbon controls, except Workflow Settings and Help).
At first I thought the issue would be that the custom master page does not work correctly with the WorkflowDesigner, but after enabling the Seattle or Oslo master page the issue remains.
So I went to check the versions. It seems that both are on version 18.104.22.168 (quality on a development license and production on a registered enterprise license) . On production I did see a strange 2010 banner, but I am not sure if it is related:
These errors pop-up upon loading the page when debugging using developer tools and trying to use commands in the ribbon:
oConfigXml = CreateXmlDoc("<NWActionConfigurations><ActionConfigs></ActionConfigs></NWActionConfigurations>");
var configs = oConfigXml.selectSingleNode("/NWActionConfigurations/ActionConfigs");
Does anyone know what might be the matter or what we can do next, apart from reinstalling Nintex on our production environment?
iisreset was done, we did not redeploy NintexWorkflow2013.wsp.
We tried using different browsers (Firefox, IE, Chrome).
If there is no other option we will have to start redeploying and installing, but as this is a production environment we would like to avoid this.
Thanks for your input, but no luck with fixing the issue so far...
When going into global settings for Nintex in the central admin we receive this error... Does this ring a bell?
This is my first time seeing this error. What's your farm topology? Are the WSP deployed correctly without throwing any errors?
Most likely if nothing special on your environment, i afraid you need re-deploy the WSP.
Thanks for the feedback so far. We have an equal topology in quality where everything works flawless. The deployment was done by someone else and at the time no issues were detected, but I am not sure how well they tested either...
If no other solution comes up we will redeploy.
Today we did the following actions to resolve our issue.
Now everything seems to work correctly.
Thank you all for your advise!