After creating several custom retail MPOS regsiters, then creating a custom c# API wrapper (that exposes older DLL functionality) my AOS is toast....I get 503 server error. I tried deleting the entire model via powershell, full model build / compile and then restart IIS via LCS, restart batch via LCS, restart IIS via windows svcs, restart AOSBatch via windows services....
but you cant see IIS at all, the event viewer craps out and wont show anything related to IIS6 there so debugging is a problem. On top of that if your app pool keeps stopping you cant know of this either. In LCS there are options for system monitoring but they are lacking app pool in the collectors setup..so when you run the LCS diagnostic tool it has some helpful stuff, but nothing related to the fact that my app pool wont start, AOS returns 503 errors. so not helpful in the end. LCS stop and start whole environment also. I am debating just deallocate and new instance at this point but if this was a customer DEV VM with real stuff I cant imagine...also did I mention that other sites such as cloud pos and ecom still work fine, however aos only returns 503 server error no matter what.
how can I tell what is causing issues as the only events are that App Pool was stopped, however I cant see iis logs or restart app pool without restarting IIS correct? and only via powershell?
*This post is locked for comments
I have the same question (0)
