The Venue url shows up as: https://usd-venue.usd.local:8000/Venues/c0ec25bc12c81692c1b57540b79b46e1
I'm sure that hostname is not what you expected. You can likely configure it better in Windows. Alternatively, you can set the AG_HOSTNAME environment variable to the right name, or to the IP address, before running the VenueServer. Tom On Aug 6, 2009, at 1:04 PM, Vine, Derek A wrote: Here is the log file. Let me know if there is anything else that is needed. --Derek From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Thomas Uram Sent: Thursday, August 06, 2009 11:03 AM To: Vine, Derek A Cc: AG-Tech Subject: Re: [AG-TECH] Venue Server help On Aug 6, 2009, at 10:33 AM, Vine, Derek A wrote: Greetings all. We have had a venue server running for a little over a year now and I was never able to add any other exits besides the default lobby. Whenever I add a new exit and try to access it from our node I get the following error: Error entering venue, getaddinfo failed. Is there some sort of security setting that I am missing? Can you send the relevant info from the VenueClient.log file? I suspect a problem with determining the hostname, which would result in an unreachable Venue address. The venue server is running on Windows server 2003 and is based off of the 3.2 beta 1 all-in-one installer. Also, what do I edit to change the location where venue FTP files are saved (ie. The data, services and application sessions). The default is in Application Data of the user and I need to move it to a different drive. The location of downloaded files can not be configured by the user, at this time. You should file an enhancement request to that end. It would be simple to add. Tom Thank you in advance. Derek Vine Communication Network Specialist DDN Site Coordinator The University of South Dakota Office - 605-677-5042 Cell - 605-677-8215 [email protected] <VenueClient.log>
