TCPListener works in Win app but not in service app

[=?Utf-8?B?Sm9uIEphY29icw==?=]

(Note: the TCP Client is on another machine, and attempts communication every
minute.)

Both apps use the same assembly
The service app starts thusly, creating the tcp object and starting the
timer in the OnStart event. The timer calls OpenServer (one time):

Public Class TCPService
Private tcp As SimpleTCP
Private Timer1 As Timer

Protected Overrides Sub OnStart(ByVal args() As String)
tcp = New SimpleTCP
Timer1 = New Timer(50)
AddHandler Timer1.Elapsed, New
System.Timers.E lapsedEventHand ler(AddressOf Timer1_Tick)
Timer1.Start()
End Sub

Protected Overrides Sub OnStop()
Timer1.Enabled = False
End Sub

Private Sub Timer1_Tick(ByV al sender As System.Object, ByVal e As
System.Timers.E lapsedEventArgs )
Timer1.Enabled = False
tcp.OpenServer( Nothing)
End Sub
End Class

The win app is the same, really just a tester for the logic in the service,
except it creates the tcp object in form load and calls OpenServer in a
button click.
In the OpenServer method:

Server = New TcpListener(cfg .Port)
....
Try
Server.Start()
metrics.Log(Log NameServer, SourceNameServe r, "Server.Sta rt")
Running = True
While Running
If Server.Pending Then
metrics.Log(Log NameServer, SourceNameServe r,
"Server.Pending ")
Dim TalkThread As Thread = New Thread(TalkDela gate)
TalkThread.Star t()
End If

If Not (Respond Is Nothing) Then
Respond.Invoke( )
End If
End While

metrics.Log(Log NameServer, SourceNameServe r, "End While")

Catch ex As Exception
Dim S As String = ex.Message
metrics.Log(Log NameServer, SourceNameServe r, S)
End Try
I have confirmed that in OpenServer, both apps use the exact same values and
follow the exact same program flow. In the win app, it just plain works. In
the
service app (I do NOT have them running at the same time), Server.Pending is
always false, no matter how much data is waiting to be picked up. Running is
always true.

I considered that maybe I need the new constructor for TCPListener, so I used:
Server = New TcpListener(IPA ddress.Any, cfg.Port)
instead, but that made no difference.

Why would the server version simply fail to detect that data is pending?

Thanks,

Jon

[Michel Posseth [MCP]]

use a system threading timer and it wil work
hth

Michel
"Jon Jacobs" <Jo*******@disc ussions.microso ft.comschreef in bericht
news:4B******** *************** ***********@mic rosoft.com...

(Note: the TCP Client is on another machine, and attempts communication
every
minute.)

Both apps use the same assembly
The service app starts thusly, creating the tcp object and starting the
timer in the OnStart event. The timer calls OpenServer (one time):

Public Class TCPService
Private tcp As SimpleTCP
Private Timer1 As Timer

Protected Overrides Sub OnStart(ByVal args() As String)
tcp = New SimpleTCP
Timer1 = New Timer(50)
AddHandler Timer1.Elapsed, New
System.Timers.E lapsedEventHand ler(AddressOf Timer1_Tick)
Timer1.Start()
End Sub

Protected Overrides Sub OnStop()
Timer1.Enabled = False
End Sub

Private Sub Timer1_Tick(ByV al sender As System.Object, ByVal e As
System.Timers.E lapsedEventArgs )
Timer1.Enabled = False
tcp.OpenServer( Nothing)
End Sub
End Class

The win app is the same, really just a tester for the logic in the
service,
except it creates the tcp object in form load and calls OpenServer in a
button click.
In the OpenServer method:

Server = New TcpListener(cfg .Port)
...
Try
Server.Start()
metrics.Log(Log NameServer, SourceNameServe r, "Server.Sta rt")
Running = True
While Running
If Server.Pending Then
metrics.Log(Log NameServer, SourceNameServe r,
"Server.Pending ")
Dim TalkThread As Thread = New Thread(TalkDela gate)
TalkThread.Star t()
End If

If Not (Respond Is Nothing) Then
Respond.Invoke( )
End If
End While

metrics.Log(Log NameServer, SourceNameServe r, "End While")

Catch ex As Exception
Dim S As String = ex.Message
metrics.Log(Log NameServer, SourceNameServe r, S)
End Try
I have confirmed that in OpenServer, both apps use the exact same values
and
follow the exact same program flow. In the win app, it just plain works.
In
the
service app (I do NOT have them running at the same time), Server.Pending
is
always false, no matter how much data is waiting to be picked up. Running
is
always true.

I considered that maybe I need the new constructor for TCPListener, so I
used:
Server = New TcpListener(IPA ddress.Any, cfg.Port)
instead, but that made no difference.

Why would the server version simply fail to detect that data is pending?

Thanks,

Jon

[=?Utf-8?B?Sm9uIEphY29icw==?=]

use a system threading timer and it wil work
Thanks but...
Sorry I didn't show this peice of code:
Imports System.Timers

The timer DOES fire.

The problem is that it DOES get to this code:
If Server.Pending Then

but Server.Pending is always FALSE no matter how much data is pending.

I've traced the code execution very carefully. The timer is not the issue.

Any idea why the listener is not listening right?

Thanks,
Jon

[Michael D. Ober]

Make sure your service logs in with an account that has network access. The
default "LocalSyste m" account does not have network access.

Mike.

"Jon Jacobs" <Jo*******@disc ussions.microso ft.comwrote in message
news:BA******** *************** ***********@mic rosoft.com...

>use a system threading timer and it wil work

Thanks but...
Sorry I didn't show this peice of code:
Imports System.Timers

The timer DOES fire.

The problem is that it DOES get to this code:
If Server.Pending Then

but Server.Pending is always FALSE no matter how much data is pending.

I've traced the code execution very carefully. The timer is not the issue.

Any idea why the listener is not listening right?

Thanks,
Jon

[=?Utf-8?B?Sm9uIEphY29icw==?=]

Make sure your service logs in with an account that has network access. The

default "LocalSyste m" account does not have network access.

Thank you, Mike.

I tried it logging in with my user account, which for sure does have the
network access, the same account by which the win app version worked fine.
The service version does not work even then.

Jon