Showing results for 
Show  only  | Search instead for 
Did you mean: 

Device not being created in FNO On prem 2018 R1

Device not being created in FNO On prem 2018 R1


Whilst creating a device in FNO on premise 2018 R1 it has been observed that an error is produced whilst selecting an account. In the flexnet.log the error is:
2018-10-01 05:23:56,955 [default task-6] ERROR (interceptors) [ADMN] SecurityInterceptor: Failed to execute Action:
com.opensymphony.xwork2.XWorkException: null
	at com.opensymphony.xwork2.util.DomHelper.parse( ~[struts2-core-2.5.13.jar:2.5.13]
	at com.opensymphony.xwork2.validator.DefaultValidatorFileParser.parseActionValidatorConfigs( ~[struts2-core-2.5.13.jar:2.5.13]
	at com.opensymphony.xwork2.validator.AnnotationActionValidatorManager.loadFile( ~[struts2-core-2.5.13.jar:2.5.13]
Caused by:
	at ~[?:1.8.0_102]
	at ~[?:1.8.0_102]


This issue is caused by restricting FNO so that it cannot connect to the internet. This may be due to a proxy or a firewall.


To resolve the issue you would need to allow the following URL's in the firewall or proxy :

* and most importantly
Labels (1)
Tags (1)
Was this article helpful? Yes No
No ratings
Version history
Revision #:
1 of 1
Last update:
‎Nov 23, 2018 01:11 PM
Updated by: