title: Any reason this WebAPI call works in dev but will not work on Win2012? "Unable to locate a controller for ..." error
body: <p>I am stuck trying to find the reason this happens. I have a WebAPI service in my module. A specific call to a public entry point (the default path) works fine on my dev machine (Win7, IIS 7.5) but doesn't on the production server (Win2012, IIS8). The DNN installations are clones. Here is the call:</p>
  
  <pre><code>/DesktopModules/DNNEurope/LocalizationEditor/API?tabid=1&amp;moduleid=4
  </code></pre>
  
  <p>The Win2012 installation replies with "Unable to locate a controller for ..." and then naming the path and namespace this controller is in. Note the routing <em>should</em> work just fine as it works fine in dev.</p>
  
  <p>There is one <em>quirk</em> to note, here. I'm supplying the tabid and moduleid through the querystring, rather than through headers as is the practice when you're doing json exchanges. That is because this call is supposed to be consumed elsewhere. Again, keep in mind this works fine locally.</p>
  
  <p>The route definition is:</p>
  
  <pre><code>mapRouteManager.MapHttpRoute("DNNEurope/LocalizationEditor", "Default", "", New With {.Controller = "Localization", .Action = "ListObjects"}, New String() {"DNNEurope.Modules.LocalizationEditor.Services"})
  </code></pre>
  
  <p>and the method:</p>
  
  <pre><code>&lt;HttpGet()&gt;
  &lt;AllowAnonymous()&gt;
  Public Function ListObjects() As HttpResponseMessage
  </code></pre>
  
  <p>Any ideas?</p>