0
Fixed

Disable 'Current' node in Sitemap

Richard Courtenay 5 years ago • updated by anonymous 3 years ago 3

I am experiencing the following error if I click the 'Select Management Agent' link in the breadcrumb while editing an existing Operation in an operation list.

Server Error in '/' Application.
--------------------------------------------------------------------------------

The resource cannot be found. 
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly. 

Requested URL: /Operation/CreateRunProfileOperationSelectManagementAgent


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272 

Reproduction steps are:
1 Navigate to the Operations Page
2 Open an existing Operation List with at least one configured Operation
3 If required, stop the Operation List
4 Select an operation of type 'Run Profile' (Runs a FIM MA) and choose 'Edit Operation'
5 On the 'Select Management Agent' page do not change the Management Agent. Hit 'Update'.
6 On the second 'Select Maangement Agent' page (where run profile information can be supplied), at the breadcrumb near the top of the page click 'Select Management Agent'. See attached screnshot

Expected Outcome: A page loads

Actual Outcome: 404 Error

Not: I havent tested this when creating a new management agent operation from scratch. Since a similar/identical page loads, the error may or may not occur there also.


screenshot-1.jpg

Tony, could you please confirm that this is an issue. If so please move it to EB project fix version v3.1.1.

Thanks.

Thanks Richard,

What you're seeing is that the page you're on - 'Select Management Agent' - is the result of a POST, so the current url is correct, but missing all POST DATA.

The FIM EB Site map has been architected so that all 'parent nodes' are GETS, so clicking any of the parents will always be fine, but the current node hasn't been validated like that.

Fix in this case is to disable clicking the current node in the site map - which'll be in 3.1.1 - thanks for bringing it up.

Will be fixed once using latest Framework.