Hi,
Running UWS host processes under identities other than Network Service and Local System is not supported. We suspect that after UWS monitoring service starts UWS app host process, it can't communicate with the said host process due to user's insufficient access rights. Such host process is considered hung by UWS monitoring, and it will try to restart it again. The host process will too quit if it didn't get a ping from the monitoring service in about two minutes. So this broken link between monitoring service and host processes causes endless quit & multiple restart problem.
The best way to deal with this issue is to follow best practices and do no elevate entire host process'es access rights, but have an out-of-process ServicedComponent running in whatever user context you wish, and called by your app. This is applicable to any web app, under IIS or UWS, or any other web server: they are run under locked-down user account for security reasons and simply lifting these restrictions for the entire process is a bad practice.
Best regards,
UltiDev Team.
Please donate at
http://www.ultidev.com/products/Donate.aspx to help us improve our products.