Author | Topic: WAA Error "socketListen Failed" | |
---|---|---|
Michael | WAA Error "socketListen Failed" on Sat, 09 May 2009 23:11:57 -0400 When I run WAA I get the "socketListen failed" error. What causes this, and how can I resolve it? | |
Thomas Braun | Re: WAA Error "socketListen Failed" on Mon, 11 May 2009 13:43:35 +0200 Michael wrote: > When I run WAA I get the "socketListen failed" error. What causes this, and > how can I resolve it? Most likely there is already some service running that uses the same port as your WAA instance. Try netstat -a on the command line or better use tcpview from sysinternals to find out which program causes this. thomas | |
Michael | Re: WAA Error "socketListen Failed" on Tue, 12 May 2009 11:22:46 -0400 Ok, that was it. I changed WAA to use port 1025 instead. But now I have another problem. When I try to run the program using /WAA1GATE.EXE, IIS gives me a 404 (File Not Found) error. Why is that? The file is in the \INETPUB\WWWROOT folder along with the CFG file, and the server and WAA1GATE config files set the port to 1025. I am using IIS. This was working before, but not sure why not. I also set the Windows Firewall to allow port 1025, but without success. "Thomas Braun" <spam@software-braun.de> wrote in message news:el7cr8gs52u7$.zj0e0oaumf6x.dlg@40tude.net... > Michael wrote: > >> When I run WAA I get the "socketListen failed" error. What causes this, >> and >> how can I resolve it? > > Most likely there is already some service running that uses the same port > as your WAA instance. > > Try netstat -a on the command line or better use tcpview from sysinternals > to find out which program causes this. > > thomas | |
Thomas Braun | Re: WAA Error "socketListen Failed" on Wed, 13 May 2009 09:19:05 +0200 Michael wrote: > But now I have another problem. When I try to run the program using > /WAA1GATE.EXE, IIS gives me a 404 (File Not Found) error. > > Why is that? The file is in the \INETPUB\WWWROOT folder along with the CFG > file, and the server and WAA1GATE config files set the port to 1025. > > I am using IIS. Sorry - I haven't used IIS for ages, only Apache - so I'm no big help in that area. Maybe others might jump in to help. Thomas | |
Andreas Herdt | Re: WAA Error "socketListen Failed" on Fri, 26 Jun 2009 12:20:55 +0200 Hallo Thomas, Your receive this error message, because the IIS is not able to find waa1gate.exe. Usually CGI gateways and ISAPI packages are to be deployed in dedicated folders. Please refer to the IIS documentation for details. In case of the waa gateway waa1gate.exe the waa1gate.cfg file should be deployed at the same directory where the exe resides. In case you like to use the waa1gate.isa/waa1gate.dll ISAPI package, the configuration file is to be deployed in c:\windows\system32\inetsrv\. With my best regards, Andreas Herdt Alaska Software -------------------------------------------------------------------- Technical Support: support@alaska-software.com News Server: news.alaska-software.com Homepage: http://www.alaska-software.com WebKnowledgeBase: http://www.alaska-software.com/kbase.shtm Fax European Office: +49 (0) 61 96 - 77 99 99 23 Fax US Office: +1 (646) 218 1281 -------------------------------------------------------------------- Michael schrieb: > Ok, that was it. I changed WAA to use port 1025 instead. > > But now I have another problem. When I try to run the program using > /WAA1GATE.EXE, IIS gives me a 404 (File Not Found) error. > > Why is that? The file is in the \INETPUB\WWWROOT folder along with the CFG > file, and the server and WAA1GATE config files set the port to 1025. > > I am using IIS. > > This was working before, but not sure why not. I also set the Windows > Firewall to allow port 1025, but without success. > > > "Thomas Braun" <spam@software-braun.de> wrote in message > news:el7cr8gs52u7$.zj0e0oaumf6x.dlg@40tude.net... >> Michael wrote: >> >>> When I run WAA I get the "socketListen failed" error. What causes this, >>> and >>> how can I resolve it? >> Most likely there is already some service running that uses the same port >> as your WAA instance. >> >> Try netstat -a on the command line or better use tcpview from sysinternals >> to find out which program causes this. >> >> thomas > > |