We are deploying wsp solutions to our DEV environment and when the server attempts to restart the application pools after the wsp has been deployed it's able to start all but one app pool. The one application pool doesn't stop and an error gets thrown in the ULS logs:
09/06/2013 13:54:14.43 OWSTIMER.EXE (0x08CC) 0x09E0 SharePoint Foundation Topology 0000 Unexpected Unable to invoke metabase method Stop: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException (0x8007041D): The service did
not respond to the start or control request in a timely fashion. (Exception from HRESULT: 0x8007041D) --- End of inner exception stack trace --- at System.DirectoryServices.DirectoryEntry.Invoke(String methodName,
Object[] args) at Microsoft.SharePoint.Administration.SPMetabaseObject.InvokeMethod(String method) 245a26da-ab89-409a-9db6-b6719fb782e2
09/06/2013 13:54:14.43 OWSTIMER.EXE (0x08CC) 0x09E0 SharePoint Foundation Topology 8zqb High Solution Deployment : Error stopping application pool myapplicationpool. Starting stopped app pools. Exception Information : The application pool "myapplicationpool" cannot be stopped. Stop the application
pool using Internet Information Services Manager and then try the operation again. 245a26da-ab89-409a-9db6-b6719fb782e2
However, when I got and look at IIS the app pool shows as being stopped and users get a 503 error when trying to access the site the app pool is associated with.
I don't see anything in the Event Viewer on the web front end that this app pool resides on and nothing else shows up as a potential culprit. The error log above makes me think it could be a security issue, but all the other web application pools use the same account and don't have this problem.
Any ideas where to look next?