Home/ Questions/Q 8917061
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T05:23:57+00:00

namespace StorageRoleMVC4.Controllers { public class SearchController : ApiController { public Dictionary<string, string> Get([FromUri] string

  • 0
namespace StorageRoleMVC4.Controllers
{
    public class SearchController : ApiController
    {
        public Dictionary<string, string> Get([FromUri] string searchString, [FromUri] string searchObject)
        {
            var searchHelper = new SearchStorageHelper();
            var objectList = searchHelper.Retrieve(searchString, searchObject);

            return objectList;
        }
    }
}

Is there anything about this controller that makes it unreachable once it’s deployed (to an Azure web role)? I just get a 404 error when I try to reach it. It works great on the local emulator.

The last 2 times I’ve deployed my project, all the controllers in my web service have returned 404 errors for several hours, until the project seems to fix itself. I’m not sure why, but it might be related.

UPDATE
There is a WARNING in the event log on the web role VM after I publish:
The application ‘/’ belonging to site ‘1273337584’ has an invalid AppPoolId ‘ea7a2e15-9390-49e1-a16b-67ff1cdb7dcb’ set. Therefore, the application will be ignored.

This is the id of my site, but the AppPoolId is not correct. Changing the app pool turns the 404 into a 502.

Also, after publishing, the World Wide Web Publishing Service is turned off. When I turn it on and do an IIS reset, after the reset it’s turned off again.

When I reboot the web role VM, most of the controllers work again, and the World Wide Web Publishing Service is turned on. But still, this SearchController doesn’t work. Or any other new controllers I’ve created since this problem started happening.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Well, after a ridiculous amount of unsuccessful troubleshooting, I just rolled back to an earlier version of the code and found that it didn’t read the web service when I deployed it. So I started over with that version and re-built the delta.

    This involved removing a few web.config entries and removing some libraries, creating a few classes and referencing them in the global.asax (I think that’s where it was) in order to override te Authorize attribute…

    If anyone has a better answer, I will switch the answer to what you post.

    • 0