Skip to main content
Question

Application Error - The requested resource could not be found


Forum|alt.badge.img

Hi all,

We are attempting to host the IFS Assyst server locally using JBOSS EAP.
After completing the installation process, we started both the Windows service and the server.
However, when we try to access the server through localhost, we encounter an application error:

Error: "The requested resource could not be found, e.g., incorrect URL specified."

Installed applications and versions:

  • jboss-eap-7.4.0
  • assyst Web 11.5.2 Build 12554
  • JDK 8

Does anyone know the possible cause of this error and how to resolve it?

 

Thanks.

3 replies

Forum|alt.badge.img+1
  • Do Gooder (Customer)
  • 3 replies
  • January 16, 2025

We are experiencing the same issue. Did you validated the behavior is also occurring for assystweb? 

IFS Wiki (URL FORMATeven shows mixed case styles in its documentation which I always thought it was like that for read ability but realized endpoints are truly mixed-case which RFC 3986 Uniform Resource Identifier (URI) says mixing lower- and upper-case letters in APIs can potentially induce errors.

 

URL does NOT work > https://assyst.XXXX.com/assystNET/

URL does work > https://assyst.XXXX.com/assystnet/

URL does NOT work > https://assyst.XXXX.com/assystWEB/

URL does work > https://assyst.XXXX.com/assystweb


Forum|alt.badge.img+1
  • Do Gooder (Customer)
  • 3 replies
  • January 16, 2025

RFC endpoints are case sensitive. What happens if you change the URL? 

Does NOT work > localhost:8080/assystnet
Does this URL work? > localhost:8080/assystNET


Forum|alt.badge.img+1
  • Do Gooder (Customer)
  • 3 replies
  • January 22, 2025

 

Does Not work »  assystNET  (get application error)

Does work » assystnet

 

Ours is more regarding assystREST is stateless APIs. 

Does not work » assystrest

Does work » assystREST

IFS says, IFS Wiki (URL FORMAT), (Formatted Text markup in assyst) has always and was set up to use REST URLs in that format. 

URLs should automatically resolve to lower-case if entered in upper-case but with Assyst URLs that's not the case. Your issue could be within your “assyst server” configuration (deployment). Make sure in Web Site setup has been all entered in “lowercase” as mixing upper- and lower-case letters in your APIs can lead to misunderstandings and errors as you had indicated.        

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings