So this instance of the problem is resolved, but the reason for the problem is not. It would still be interesting to look at the logs to understand what went wrong. If you're able to collect them, it'd be a good bug to submit to bugzilla.
Tom On 7/19/07 1:33 PM, Jeremy Mann wrote: > Thomas, interestingly enough, the problem with XP not showing VIC and > RAT was fixed when I restart our VenueServer. For whatever reason that > fixed it. > > On 7/18/07, Thomas D. Uram <[email protected]> wrote: >> It might be interesting to also look at the VideoProducerService.log and >> the AudioService.log. >> >> The code that opens the firewall is isolated so errors that occur there >> do not affect the launching of vic/rat. I'm curious to know what the >> problem is. If we find out quickly, we can try to reproduce it in >> AG3.1beta, and fix it for the final. >> >> Tom >> >> >> On 7/18/07 4:32 PM, Jeremy Mann wrote: >> > On 7/18/07, Ed Brannin <[email protected]> wrote: >> >> >> >> Looks like it's trying to make a firewall exception for something, >> >> but your >> >> client doesn't have Windows' permission to modify (that part of) the >> >> registry. Is he running as a limited user, or an administrator? >> >> >> >> The line in question is trying to set this Registry key: >> > >> > That's what I thought too, so I told him to log out and log in as >> > Administrator. He reports that he has the same problem, VIC and RAT do >> > not appear. >> > >> > -- >> > Jeremy Mann >> > >> > >> > >
