OK, I just gave this a try. Note this is pretty much exactly the same
process as described in the MS KB article I linked to in my earlier
post. Installing the service seems to work, and it can be started, but
when I try to connect to my server, I get the error you see here in this
screenshot: http://imgur.com/EgNbL. If I run red5.bat manually (not as
a system service), I can connect just fine. My host is running Windows
Server 2003 R2, 64-bit, SP2.
Seth
On 08/01/2012 01:14 PM, Seth Galitzer wrote:
Alvaro,
I did see your email earlier today. I just haven't had a chance to try
it out yet. Thanks for sharing!
Seth
On 08/01/2012 03:12 PM, greenes wrote:
Hi Seth,
Is a tutorial to build OpenMeetings as a Windows service
here:
https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials
+related+to+OpenMeeting
...is called:
OpenMeetings as Windows service.pdf
It works with OM 2.0!
Alvaro
..................
El lun, 30-07-2012 a las 13:45 -0500, Seth Galitzer escribió:
Greetings,
First of all, kudos to OM devs for getting 2.0 out the door. I'm really
liking the improvements so far and look forward to how things progress.
I can't wait to replace my production Connect server with OM.
I've been testing 1.9 on Windows Server 2003, using the NT Wrapper to
install red5 as a service. 2.0 doesn't seem to like this setup, or
perhaps I need to adjust the wrapper config. I can start the red5
service manually, but I'd like to run it as a system service. Any
advice on how to do this with 2.0?
Thanks.
Seth
--
Seth Galitzer
Systems Coordinator
Computing and Information Sciences
Kansas State University
http://www.cis.ksu.edu/~sgsax
sg...@ksu.edu
785-532-7790
