Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors
As far as I remember you should be using '-ip' rather than '+ip' Also, did you try -ip 0.0.0.0 ? 2009/3/5 Andrew Armstrong and...@mammoth.com.au The server only has one IP, and that's the public one. I tried starting it without +ip as well, but the same error occurred. - Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of Nephyrin Zey Sent: Thursday, 5 March 2009 11:46 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Are you using any sort of NAT? Make sure you're bindg to the local IP and not the external IP. Any sort of improper -ip setting will cause all sorts of everything to fail to bind to ports. - Neph On 03/04/2009 04:23 PM, Robert C wrote: We've continued having this problem even when running only a single instance on a host. Another strange observation is that L4D servers run fine on the same hosts, but have a similar error displayed in the console: cminterface.cpp (940) : Assertion Failed: NULL != m_hConnection Chad Austin wrote: I think I had the same issue, and it went away after I left more room inbetween the ports for each gameserver, an I did not use anything in the 2702x range. I know its not a good solution, but its worth a try. Andrew Armstrong wrote: Hi, We are experiencing some problems trying to run a few Team Fortress 2 servers on a new Windows Server 2008 64bit machine. While the server attempts to start, the following error messages appear in the server console: -- WARNING: NNET_OpenSocket: bind: WSAEINVAL other log lines steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service CreateBoundSocket: ::bind returned Win32 error 10022 cminterface.cpp (598) : Assertion Failed: NULL != m_hConnection -- We also receive the following error at times: -- A dialog box appears with an OK button saying: Couldn't allocate any hltv IP port -- I know someone is going to suggest the tv_port variable, and so we tried setting that to a unique, free port. This removes the Couldn't allocate any hltv IP port error. We have had hltv support disabled though the entire time. However, the server still boots up with the WARNING: NN_NET.. Log lines as above, and the server remains insecure: 1.0.4.9/14 3755 insecure (secure mode enabled, disconnected from Steam 3) Please note we run the exact same server configuration on Windows 2003 32bit without any problems. Is this a known issue at Valve (a quick google indicates a few other people have the same problem), or is there a fix available? Thanks, Andrew ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds -- Sent from Olly's SEGA Game Gear ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors
Everytime I start our server it always says: steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service It never seems to affect anything, and numerous research attempts on google have left me with nothing to try. I can say though, that the server will run despite that error. :-) -Matt On Thu, Mar 5, 2009 at 3:37 AM, Olly oli...@gmail.com wrote: As far as I remember you should be using '-ip' rather than '+ip' Also, did you try -ip 0.0.0.0 ? 2009/3/5 Andrew Armstrong and...@mammoth.com.au The server only has one IP, and that's the public one. I tried starting it without +ip as well, but the same error occurred. - Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of Nephyrin Zey Sent: Thursday, 5 March 2009 11:46 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Are you using any sort of NAT? Make sure you're bindg to the local IP and not the external IP. Any sort of improper -ip setting will cause all sorts of everything to fail to bind to ports. - Neph On 03/04/2009 04:23 PM, Robert C wrote: We've continued having this problem even when running only a single instance on a host. Another strange observation is that L4D servers run fine on the same hosts, but have a similar error displayed in the console: cminterface.cpp (940) : Assertion Failed: NULL != m_hConnection Chad Austin wrote: I think I had the same issue, and it went away after I left more room inbetween the ports for each gameserver, an I did not use anything in the 2702x range. I know its not a good solution, but its worth a try. Andrew Armstrong wrote: Hi, We are experiencing some problems trying to run a few Team Fortress 2 servers on a new Windows Server 2008 64bit machine. While the server attempts to start, the following error messages appear in the server console: -- WARNING: NNET_OpenSocket: bind: WSAEINVAL other log lines steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service CreateBoundSocket: ::bind returned Win32 error 10022 cminterface.cpp (598) : Assertion Failed: NULL != m_hConnection -- We also receive the following error at times: -- A dialog box appears with an OK button saying: Couldn't allocate any hltv IP port -- I know someone is going to suggest the tv_port variable, and so we tried setting that to a unique, free port. This removes the Couldn't allocate any hltv IP port error. We have had hltv support disabled though the entire time. However, the server still boots up with the WARNING: NN_NET.. Log lines as above, and the server remains insecure: 1.0.4.9/14 3755 insecure (secure mode enabled, disconnected from Steam 3) Please note we run the exact same server configuration on Windows 2003 32bit without any problems. Is this a known issue at Valve (a quick google indicates a few other people have the same problem), or is there a fix available? Thanks, Andrew ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds -- Sent from Olly's SEGA Game Gear ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors
Is your server VAC secured though Matt? Type 'status' and see if it says its secure/insecure. - Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of CLAN RCR Sent: Thursday, 5 March 2009 9:19 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Everytime I start our server it always says: steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service It never seems to affect anything, and numerous research attempts on google have left me with nothing to try. I can say though, that the server will run despite that error. :-) -Matt On Thu, Mar 5, 2009 at 3:37 AM, Olly oli...@gmail.com wrote: As far as I remember you should be using '-ip' rather than '+ip' Also, did you try -ip 0.0.0.0 ? 2009/3/5 Andrew Armstrong and...@mammoth.com.au The server only has one IP, and that's the public one. I tried starting it without +ip as well, but the same error occurred. - Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of Nephyrin Zey Sent: Thursday, 5 March 2009 11:46 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Are you using any sort of NAT? Make sure you're bindg to the local IP and not the external IP. Any sort of improper -ip setting will cause all sorts of everything to fail to bind to ports. - Neph On 03/04/2009 04:23 PM, Robert C wrote: We've continued having this problem even when running only a single instance on a host. Another strange observation is that L4D servers run fine on the same hosts, but have a similar error displayed in the console: cminterface.cpp (940) : Assertion Failed: NULL != m_hConnection Chad Austin wrote: I think I had the same issue, and it went away after I left more room inbetween the ports for each gameserver, an I did not use anything in the 2702x range. I know its not a good solution, but its worth a try. Andrew Armstrong wrote: Hi, We are experiencing some problems trying to run a few Team Fortress 2 servers on a new Windows Server 2008 64bit machine. While the server attempts to start, the following error messages appear in the server console: -- WARNING: NNET_OpenSocket: bind: WSAEINVAL other log lines steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service CreateBoundSocket: ::bind returned Win32 error 10022 cminterface.cpp (598) : Assertion Failed: NULL != m_hConnection -- We also receive the following error at times: -- A dialog box appears with an OK button saying: Couldn't allocate any hltv IP port -- I know someone is going to suggest the tv_port variable, and so we tried setting that to a unique, free port. This removes the Couldn't allocate any hltv IP port error. We have had hltv support disabled though the entire time. However, the server still boots up with the WARNING: NN_NET.. Log lines as above, and the server remains insecure: 1.0.4.9/14 3755 insecure (secure mode enabled, disconnected from Steam 3) Please note we run the exact same server configuration on Windows 2003 32bit without any problems. Is this a known issue at Valve (a quick google indicates a few other people have the same problem), or is there a fix available? Thanks, Andrew ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds -- Sent from Olly's SEGA Game Gear ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http
Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors
Yep, it shows it as being secure. -Matt On Thu, Mar 5, 2009 at 4:29 AM, Andrew Armstrong and...@mammoth.com.auwrote: Is your server VAC secured though Matt? Type 'status' and see if it says its secure/insecure. - Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of CLAN RCR Sent: Thursday, 5 March 2009 9:19 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Everytime I start our server it always says: steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service It never seems to affect anything, and numerous research attempts on google have left me with nothing to try. I can say though, that the server will run despite that error. :-) -Matt On Thu, Mar 5, 2009 at 3:37 AM, Olly oli...@gmail.com wrote: As far as I remember you should be using '-ip' rather than '+ip' Also, did you try -ip 0.0.0.0 ? 2009/3/5 Andrew Armstrong and...@mammoth.com.au The server only has one IP, and that's the public one. I tried starting it without +ip as well, but the same error occurred. - Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of Nephyrin Zey Sent: Thursday, 5 March 2009 11:46 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Are you using any sort of NAT? Make sure you're bindg to the local IP and not the external IP. Any sort of improper -ip setting will cause all sorts of everything to fail to bind to ports. - Neph On 03/04/2009 04:23 PM, Robert C wrote: We've continued having this problem even when running only a single instance on a host. Another strange observation is that L4D servers run fine on the same hosts, but have a similar error displayed in the console: cminterface.cpp (940) : Assertion Failed: NULL != m_hConnection Chad Austin wrote: I think I had the same issue, and it went away after I left more room inbetween the ports for each gameserver, an I did not use anything in the 2702x range. I know its not a good solution, but its worth a try. Andrew Armstrong wrote: Hi, We are experiencing some problems trying to run a few Team Fortress 2 servers on a new Windows Server 2008 64bit machine. While the server attempts to start, the following error messages appear in the server console: -- WARNING: NNET_OpenSocket: bind: WSAEINVAL other log lines steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service CreateBoundSocket: ::bind returned Win32 error 10022 cminterface.cpp (598) : Assertion Failed: NULL != m_hConnection -- We also receive the following error at times: -- A dialog box appears with an OK button saying: Couldn't allocate any hltv IP port -- I know someone is going to suggest the tv_port variable, and so we tried setting that to a unique, free port. This removes the Couldn't allocate any hltv IP port error. We have had hltv support disabled though the entire time. However, the server still boots up with the WARNING: NN_NET.. Log lines as above, and the server remains insecure: 1.0.4.9/14 3755 insecure (secure mode enabled, disconnected from Steam 3) Please note we run the exact same server configuration on Windows 2003 32bit without any problems. Is this a known issue at Valve (a quick google indicates a few other people have the same problem), or is there a fix available? Thanks, Andrew ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors
Hi Matt, Olly, I tried both +ip (address) and -ip (address), they both had the same result. I tried +ip 0.0.0.0 and had the same result. Interestingly this morning the server boots up, and I see the Failed to start in-process Steam service message still, but a status report says: version : 1.0.4.9/14 3755 insecure (secure mode enabled, disconnected from Steam 3) So supposedly the server is secure - but its not, because I checked via the Steam server list (Also note the 'disconnected from Steam 3' bit). Compare that to another 32bit server that just says: version : 1.0.4.9/14 3755 secure (and is working fine). Does anyone else have any ideas? Cheers, Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of CLAN RCR Sent: Friday, 6 March 2009 5:48 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Yep, it shows it as being secure. -Matt On Thu, Mar 5, 2009 at 4:29 AM, Andrew Armstrong and...@mammoth.com.auwrote: Is your server VAC secured though Matt? Type 'status' and see if it says its secure/insecure. - Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of CLAN RCR Sent: Thursday, 5 March 2009 9:19 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Everytime I start our server it always says: steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service It never seems to affect anything, and numerous research attempts on google have left me with nothing to try. I can say though, that the server will run despite that error. :-) -Matt On Thu, Mar 5, 2009 at 3:37 AM, Olly oli...@gmail.com wrote: As far as I remember you should be using '-ip' rather than '+ip' Also, did you try -ip 0.0.0.0 ? 2009/3/5 Andrew Armstrong and...@mammoth.com.au The server only has one IP, and that's the public one. I tried starting it without +ip as well, but the same error occurred. - Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of Nephyrin Zey Sent: Thursday, 5 March 2009 11:46 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Are you using any sort of NAT? Make sure you're bindg to the local IP and not the external IP. Any sort of improper -ip setting will cause all sorts of everything to fail to bind to ports. - Neph On 03/04/2009 04:23 PM, Robert C wrote: We've continued having this problem even when running only a single instance on a host. Another strange observation is that L4D servers run fine on the same hosts, but have a similar error displayed in the console: cminterface.cpp (940) : Assertion Failed: NULL != m_hConnection Chad Austin wrote: I think I had the same issue, and it went away after I left more room inbetween the ports for each gameserver, an I did not use anything in the 2702x range. I know its not a good solution, but its worth a try. Andrew Armstrong wrote: Hi, We are experiencing some problems trying to run a few Team Fortress 2 servers on a new Windows Server 2008 64bit machine. While the server attempts to start, the following error messages appear in the server console: -- WARNING: NNET_OpenSocket: bind: WSAEINVAL other log lines steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service CreateBoundSocket: ::bind returned Win32 error 10022 cminterface.cpp (598) : Assertion Failed: NULL != m_hConnection -- We also receive the following error at times: -- A dialog box appears with an OK button saying: Couldn't allocate any hltv IP port -- I know someone is going to suggest the tv_port variable, and so we tried setting that to a unique, free port. This removes the Couldn't allocate any hltv IP port error. We have had hltv support disabled though the entire time. However, the server still boots up with the WARNING: NN_NET.. Log lines as above, and the server remains insecure: 1.0.4.9/14 3755 insecure (secure mode enabled, disconnected from Steam 3) Please note we run the exact same server configuration on Windows 2003 32bit without any problems. Is this a known issue at Valve (a quick google indicates a few other people have the same problem
Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors
h what could it be!? Thank you, Alec Sanger P: 248.941.3813 F: 313.286.8945 From: and...@mammoth.com.au To: hlds@list.valvesoftware.com Date: Fri, 6 Mar 2009 09:35:45 +1100 Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Hi Matt, Olly, I tried both +ip (address) and -ip (address), they both had the same result. I tried +ip 0.0.0.0 and had the same result. Interestingly this morning the server boots up, and I see the Failed to start in-process Steam service message still, but a status report says: version : 1.0.4.9/14 3755 insecure (secure mode enabled, disconnected from Steam 3) So supposedly the server is secure - but its not, because I checked via the Steam server list (Also note the 'disconnected from Steam 3' bit). Compare that to another 32bit server that just says: version : 1.0.4.9/14 3755 secure (and is working fine). Does anyone else have any ideas? Cheers, Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of CLAN RCR Sent: Friday, 6 March 2009 5:48 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Yep, it shows it as being secure. -Matt On Thu, Mar 5, 2009 at 4:29 AM, Andrew Armstrong and...@mammoth.com.auwrote: Is your server VAC secured though Matt? Type 'status' and see if it says its secure/insecure. - Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of CLAN RCR Sent: Thursday, 5 March 2009 9:19 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Everytime I start our server it always says: steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service It never seems to affect anything, and numerous research attempts on google have left me with nothing to try. I can say though, that the server will run despite that error. :-) -Matt On Thu, Mar 5, 2009 at 3:37 AM, Olly oli...@gmail.com wrote: As far as I remember you should be using '-ip' rather than '+ip' Also, did you try -ip 0.0.0.0 ? 2009/3/5 Andrew Armstrong and...@mammoth.com.au The server only has one IP, and that's the public one. I tried starting it without +ip as well, but the same error occurred. - Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of Nephyrin Zey Sent: Thursday, 5 March 2009 11:46 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Are you using any sort of NAT? Make sure you're bindg to the local IP and not the external IP. Any sort of improper -ip setting will cause all sorts of everything to fail to bind to ports. - Neph On 03/04/2009 04:23 PM, Robert C wrote: We've continued having this problem even when running only a single instance on a host. Another strange observation is that L4D servers run fine on the same hosts, but have a similar error displayed in the console: cminterface.cpp (940) : Assertion Failed: NULL != m_hConnection Chad Austin wrote: I think I had the same issue, and it went away after I left more room inbetween the ports for each gameserver, an I did not use anything in the 2702x range. I know its not a good solution, but its worth a try. Andrew Armstrong wrote: Hi, We are experiencing some problems trying to run a few Team Fortress 2 servers on a new Windows Server 2008 64bit machine. While the server attempts to start, the following error messages appear in the server console: -- WARNING: NNET_OpenSocket: bind: WSAEINVAL other log lines steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service CreateBoundSocket: ::bind returned Win32 error 10022 cminterface.cpp (598) : Assertion Failed: NULL != m_hConnection -- We also receive the following error at times: -- A dialog box appears with an OK button saying: Couldn't allocate any hltv IP port -- I know someone is going to suggest the tv_port variable, and so we tried setting that to a unique, free port. This removes the Couldn't allocate any hltv IP port error. We have had hltv support disabled though the entire
Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors
Okay, so ive been looking in to this issue further. Here are some thoughts: According to http://msdn.microsoft.com/en-us/library/ms740532(VS.85).aspx under Windows Vista/Win2K8, setsockopt() will fail with WSAEINVAL (instead of WSAENOPROTOOPT) when the option is not supported - which is the case with every version of Windows. 1) Valve (if you're reading this) is it possible that you gracefully ignore the WSAENOPROTOOPT for Windows, but don't do the same for WSAEINVAL when calling this function with unsupported flags? 2) KB article http://support.microsoft.com/kb/946886 suggests a similar error can occur when When there is a third-party legacy TDI filter driver installed on a computer that is running Windows Server 2008 or Windows Vista, the system receives error code WSAEADDRINUSE (10048) when the system tries to bind the socket for the first time. When the system tries to bind the socket for the second time, it receives error code WSAEINVAL (10022).. This does not appear to be the case with us (we do not have a third-party legacy TDI driver). So we can rule this out I think. 3) The KB article at http://support.microsoft.com/kb/819124 suggests the error code can be raised when: * An invalid argument (for example, an argument that specified an invalid level) was supplied to the setsockopt (Wsapiref_94aa.asp) function. - Which is possibly what is happening as per Point #1 * Sometimes, it also refers to the current state of the sockets, for example, calling accept (Wsapiref_13aq.asp) on a socket that is not listening. - If this was a problem, surely this would be occurring on Windows Server 2003 (and XP, etc) as well, but its not - so I think I can rule this out. This leads me to believe that the problem described in Point #1 is the most likely cause, otherwise I have no idea. Cheers, Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of Alec Sanger Sent: Friday, 6 March 2009 9:44 AM To: hlds@list.valvesoftware.com Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors h what could it be!? Thank you, Alec Sanger P: 248.941.3813 F: 313.286.8945 From: and...@mammoth.com.au To: hlds@list.valvesoftware.com Date: Fri, 6 Mar 2009 09:35:45 +1100 Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Hi Matt, Olly, I tried both +ip (address) and -ip (address), they both had the same result. I tried +ip 0.0.0.0 and had the same result. Interestingly this morning the server boots up, and I see the Failed to start in-process Steam service message still, but a status report says: version : 1.0.4.9/14 3755 insecure (secure mode enabled, disconnected from Steam 3) So supposedly the server is secure - but its not, because I checked via the Steam server list (Also note the 'disconnected from Steam 3' bit). Compare that to another 32bit server that just says: version : 1.0.4.9/14 3755 secure (and is working fine). Does anyone else have any ideas? Cheers, Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of CLAN RCR Sent: Friday, 6 March 2009 5:48 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Yep, it shows it as being secure. -Matt On Thu, Mar 5, 2009 at 4:29 AM, Andrew Armstrong and...@mammoth.com.auwrote: Is your server VAC secured though Matt? Type 'status' and see if it says its secure/insecure. - Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of CLAN RCR Sent: Thursday, 5 March 2009 9:19 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Everytime I start our server it always says: steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service It never seems to affect anything, and numerous research attempts on google have left me with nothing to try. I can say though, that the server will run despite that error. :-) -Matt On Thu, Mar 5, 2009 at 3:37 AM, Olly oli...@gmail.com wrote: As far as I remember you should be using '-ip' rather than '+ip' Also, did you try -ip 0.0.0.0 ? 2009/3/5 Andrew Armstrong and...@mammoth.com.au The server only has one IP, and that's the public one. I tried starting it without +ip as well, but the same error occurred. - Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of Nephyrin Zey Sent: Thursday, 5 March 2009 11:46 AM To: Half-Life dedicated Win32 server mailing list
[hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors
Hi, We are experiencing some problems trying to run a few Team Fortress 2 servers on a new Windows Server 2008 64bit machine. While the server attempts to start, the following error messages appear in the server console: -- WARNING: NNET_OpenSocket: bind: WSAEINVAL other log lines steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service CreateBoundSocket: ::bind returned Win32 error 10022 cminterface.cpp (598) : Assertion Failed: NULL != m_hConnection -- We also receive the following error at times: -- A dialog box appears with an OK button saying: Couldn't allocate any hltv IP port -- I know someone is going to suggest the tv_port variable, and so we tried setting that to a unique, free port. This removes the Couldn't allocate any hltv IP port error. We have had hltv support disabled though the entire time. However, the server still boots up with the WARNING: NN_NET.. Log lines as above, and the server remains insecure: 1.0.4.9/14 3755 insecure (secure mode enabled, disconnected from Steam 3) Please note we run the exact same server configuration on Windows 2003 32bit without any problems. Is this a known issue at Valve (a quick google indicates a few other people have the same problem), or is there a fix available? Thanks, Andrew ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors
I think I had the same issue, and it went away after I left more room inbetween the ports for each gameserver, an I did not use anything in the 2702x range. I know its not a good solution, but its worth a try. Andrew Armstrong wrote: Hi, We are experiencing some problems trying to run a few Team Fortress 2 servers on a new Windows Server 2008 64bit machine. While the server attempts to start, the following error messages appear in the server console: -- WARNING: NNET_OpenSocket: bind: WSAEINVAL other log lines steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service CreateBoundSocket: ::bind returned Win32 error 10022 cminterface.cpp (598) : Assertion Failed: NULL != m_hConnection -- We also receive the following error at times: -- A dialog box appears with an OK button saying: Couldn't allocate any hltv IP port -- I know someone is going to suggest the tv_port variable, and so we tried setting that to a unique, free port. This removes the Couldn't allocate any hltv IP port error. We have had hltv support disabled though the entire time. However, the server still boots up with the WARNING: NN_NET.. Log lines as above, and the server remains insecure: 1.0.4.9/14 3755 insecure (secure mode enabled, disconnected from Steam 3) Please note we run the exact same server configuration on Windows 2003 32bit without any problems. Is this a known issue at Valve (a quick google indicates a few other people have the same problem), or is there a fix available? Thanks, Andrew ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors
We've continued having this problem even when running only a single instance on a host. Another strange observation is that L4D servers run fine on the same hosts, but have a similar error displayed in the console: cminterface.cpp (940) : Assertion Failed: NULL != m_hConnection Chad Austin wrote: I think I had the same issue, and it went away after I left more room inbetween the ports for each gameserver, an I did not use anything in the 2702x range. I know its not a good solution, but its worth a try. Andrew Armstrong wrote: Hi, We are experiencing some problems trying to run a few Team Fortress 2 servers on a new Windows Server 2008 64bit machine. While the server attempts to start, the following error messages appear in the server console: -- WARNING: NNET_OpenSocket: bind: WSAEINVAL other log lines steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service CreateBoundSocket: ::bind returned Win32 error 10022 cminterface.cpp (598) : Assertion Failed: NULL != m_hConnection -- We also receive the following error at times: -- A dialog box appears with an OK button saying: Couldn't allocate any hltv IP port -- I know someone is going to suggest the tv_port variable, and so we tried setting that to a unique, free port. This removes the Couldn't allocate any hltv IP port error. We have had hltv support disabled though the entire time. However, the server still boots up with the WARNING: NN_NET.. Log lines as above, and the server remains insecure: 1.0.4.9/14 3755 insecure (secure mode enabled, disconnected from Steam 3) Please note we run the exact same server configuration on Windows 2003 32bit without any problems. Is this a known issue at Valve (a quick google indicates a few other people have the same problem), or is there a fix available? Thanks, Andrew ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors
Are you using any sort of NAT? Make sure you're bindg to the local IP and not the external IP. Any sort of improper -ip setting will cause all sorts of everything to fail to bind to ports. - Neph On 03/04/2009 04:23 PM, Robert C wrote: We've continued having this problem even when running only a single instance on a host. Another strange observation is that L4D servers run fine on the same hosts, but have a similar error displayed in the console: cminterface.cpp (940) : Assertion Failed: NULL != m_hConnection Chad Austin wrote: I think I had the same issue, and it went away after I left more room inbetween the ports for each gameserver, an I did not use anything in the 2702x range. I know its not a good solution, but its worth a try. Andrew Armstrong wrote: Hi, We are experiencing some problems trying to run a few Team Fortress 2 servers on a new Windows Server 2008 64bit machine. While the server attempts to start, the following error messages appear in the server console: -- WARNING: NNET_OpenSocket: bind: WSAEINVAL other log lines steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service CreateBoundSocket: ::bind returned Win32 error 10022 cminterface.cpp (598) : Assertion Failed: NULL != m_hConnection -- We also receive the following error at times: -- A dialog box appears with an OK button saying: Couldn't allocate any hltv IP port -- I know someone is going to suggest the tv_port variable, and so we tried setting that to a unique, free port. This removes the Couldn't allocate any hltv IP port error. We have had hltv support disabled though the entire time. However, the server still boots up with the WARNING: NN_NET.. Log lines as above, and the server remains insecure: 1.0.4.9/14 3755 insecure (secure mode enabled, disconnected from Steam 3) Please note we run the exact same server configuration on Windows 2003 32bit without any problems. Is this a known issue at Valve (a quick google indicates a few other people have the same problem), or is there a fix available? Thanks, Andrew ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors
The server only has one IP, and that's the public one. I tried starting it without +ip as well, but the same error occurred. - Andrew -Original Message- From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of Nephyrin Zey Sent: Thursday, 5 March 2009 11:46 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Windows Server 2008 64bit: Couldn't allocate any hltv IP port / bind errors Are you using any sort of NAT? Make sure you're bindg to the local IP and not the external IP. Any sort of improper -ip setting will cause all sorts of everything to fail to bind to ports. - Neph On 03/04/2009 04:23 PM, Robert C wrote: We've continued having this problem even when running only a single instance on a host. Another strange observation is that L4D servers run fine on the same hosts, but have a similar error displayed in the console: cminterface.cpp (940) : Assertion Failed: NULL != m_hConnection Chad Austin wrote: I think I had the same issue, and it went away after I left more room inbetween the ports for each gameserver, an I did not use anything in the 2702x range. I know its not a good solution, but its worth a try. Andrew Armstrong wrote: Hi, We are experiencing some problems trying to run a few Team Fortress 2 servers on a new Windows Server 2008 64bit machine. While the server attempts to start, the following error messages appear in the server console: -- WARNING: NNET_OpenSocket: bind: WSAEINVAL other log lines steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam Service CreateBoundSocket: ::bind returned Win32 error 10022 cminterface.cpp (598) : Assertion Failed: NULL != m_hConnection -- We also receive the following error at times: -- A dialog box appears with an OK button saying: Couldn't allocate any hltv IP port -- I know someone is going to suggest the tv_port variable, and so we tried setting that to a unique, free port. This removes the Couldn't allocate any hltv IP port error. We have had hltv support disabled though the entire time. However, the server still boots up with the WARNING: NN_NET.. Log lines as above, and the server remains insecure: 1.0.4.9/14 3755 insecure (secure mode enabled, disconnected from Steam 3) Please note we run the exact same server configuration on Windows 2003 32bit without any problems. Is this a known issue at Valve (a quick google indicates a few other people have the same problem), or is there a fix available? Thanks, Andrew ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
