Hey guys, I'm working to integrate UWS into an installed solution & have run into a really odd problem.

First of all, the Environment:

- Server 2008 R2, IIS installed, otherwise a fresh / clean installation.

- I have written a custom WIX installation that uses your bootstrapper to install UWS and register my web application on a separate port from IIS.

- I also create a shortcut to the address ( host:port/MyWebApp for example ).

What happens is that the FIRST TIME I launch the shortcut, I am presented with an error. Upon closing the browser (IE OR FireFox exhibit this behavior), and reopening the shortcut, everything works fine.

Any ideas?

Thanks in advance,
-Brian




Here are the error details:

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 7/16/2013 10:33:18 AM
Event time (UTC): 7/16/2013 2:33:18 PM
Event ID: d571ee0976f54d32bfdfd2bfb862cddd
Event sequence: 1
Event occurrence: 1
Event detail code: 0

Application information:
Application domain: /UWS/{0E801A51-1579-411B-82B7-5ABC0E49BA54}-1-130183907677242812
Trust level:
Application Virtual Path: /Vantage
Application Path: C:\Program Files (x86)\Telestream\Vantage Web Applications 5.0 Lite\
Machine name: BRIDEVVM

Process information:
Process ID: 3600
Process name: UWS.AppHost.Clr4.AnyCPU.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
Exception type: HttpException
Exception message: Server cannot access application directory 'C:\Program Files (x86)\Telestream\Vantage Web Applications 5.0 Lite\'. The directory does not exist or is not accessible because of security settings.
at System.Web.HttpRuntime.EnsureAccessToApplicationDirectory()
at System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags, PolicyLevel policyLevel, Exception appDomainCreationException)



Request information:
Request URL: http://bridevvm:5001/Vantage/Transcode/Default.aspx
Request path: /Vantage/Transcode/Default.aspx
User host address: fe80::5c66:6f5b:ca50:d131
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
Thread ID: 7
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at System.Web.HttpRuntime.EnsureAccessToApplicationDirectory()
at System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags, PolicyLevel policyLevel, Exception appDomainCreationException)


Custom event details:

Refreshing the browser via F5/Refresh does make it work (at least on the instance where I have recreated the problem).

I installed and ran Fiddler, though I'm not really sure what to look for... nothing seemed to pop out of me in terms of additional information.

I am using anonymous auth (we have implemented our own membership provider for authentication).

That was my thought too... so my QA team waited about 15 mins after installation to try it with the same results. :) (I have also replicated the behavior).

The same thing also happens if I open the UWS application and choose the various browse options. I had also wondered if it might relate to addressing the current host via DNS name instead of local IP or localhost, but none of that seems to make a difference either.

I'll go back and see if I can get you any other information from fiddler...

Thanks,
-Brian

Thanks! I'll give those a try and report my findings. I'm pretty sure that a manual registration of the app works fine (I had started with that upon doing some UWS testing / evaluation).