Different controllers with the same name in two different scopes cause a routing conflict

I have two areas:

ControlPanel

and Patients

.

Both have a controller called ProblemController, similar only in name. The desired results would be routes that give / controlpanel / problems => MyApp.Areas.ControlPanel.Controllers.ProblemsController and / patient / problems => MyApp.Areas.Patients.Controllers.ProblemsController.

Each has routes configured as follows:

public override void RegisterArea(AreaRegistrationContext context)
        {
            context.MapRoute(
                "**Area Name Here**_default",
                "**Area Name Here**/{controller}/{action}/{id}",
                new { action = "Index", id = UrlParameter.Optional }
            );
        }

      

        
        
        
      

    

where ***** Region name here ***** is either the control group or the patient.

When I go to / patients / problems / create (for example), I get 404, where the routing error says A public action method 'create' was not found on controller 'MyApp.Areas.ControlPanel.Controllers.ProblemsController'

.

I'm not sure what I am doing wrong.