TCP communication with a LabVIEW executable running as windowsXP!

[Rashid-Malik]

Here is a problem I am facing and would really appreciate some solution/guidance;

I have a Server (written in LabVIEW) that accepts TCP connection and responds to them. But when I turn it into executable (works fine as an executable as well) and then launch that executable as a windowsXP service using Service Runner (http://servicerunner.codeplex.com/) I can not establish a connection with it from another pc.

Any advvice/help?

Thanks a lot and a very pleasant day to you!

[Rashid-Malik]

Following error is returned;

"Error 63 occurred at TCP Open Connection in SVI-SLDSClient-OpenConnectiontoServer.vi->GUI-SLDSServer-Top.vi

Possible reason(s):

LabVIEW:  Serial port receive buffer overflow.
=========================
LabVIEW:  The network connection was refused by the server."

[nathand]

Do you have a firewall?  If so, I would try disabling it temporarily; if that fixes the problem, you'll need to figure out how to add an exception for your service.

One other question, though: which is returning the error, the client or your server?  If your server, why is it trying to open a TCP connection instead of opening a listener?

[Rashid-Malik]

---

@nathand wrote:

Do you have a firewall?  If so, I would try disabling it temporarily;

---

If can communicate with the client running on one pc and server running on another (as LabVIEW VIs or executables) so firewall is already allowing the packets to pass through. Moreover, the server pc has no firewall! But could it be that we need separate set of firewall configuration for the server executable when running as a windows service.

---

nathand wrote:

One other question, though: which is returning the error, the client or your server? 

---

The client, the client returned that error!

And lots of thanks for the reply!

I managed to run the server executable as a windows scheduled task and it would run on the pc even when no one was logged onto the pc (one of the requirement) and I have conveyed that as an alternate solution to my boss. Lets see if he accepts it or not!

[nathand]

Sounds like the server didn't actually start properly as a service; do you have a debug log indicating that it started properly?  I'd confirm that there's no error when it opens the TCP listener.  Also sounds like you have proposed a reasonable work-around, so I hope that works out for you.

[Rashid-Malik]

---

@nathand wrote:

Sounds like the server didn't actually start properly as a service; do you have a debug log indicating that it started properly?  I'd confirm that there's no error when it opens the TCP listener.

---

Is this debug log provided by windows or do you code it in your LabVIEW applications?

[nathand]

You'd need to code something yourself.  You could also check the Windows event log, but I'd be surprised if it indicates anything helpful.

[Rashid-Malik]

Good idea, friend! I'll do the event log check tomorrow at work!

Thanks a looooooooooooooot for your time!