Windows Service working on Windows Server 2008r2 but not Windows Server 2012

Question

0.00/5 (No votes)

See more:

Hello Everybody
I've a small Windows Service that connect via a socket to another Service.
when i install it on Windows Server 2012 it sends a message over the socket, fine.
when i restart the service, it sends a message over the socket, fine.
when i reboot the server it does NOT send a message over the socket.

Everything works as it should on Windows Server 2008r2.

what has changed Service wise on Windows Server 2012?

Best Regards
Alex

Posted 17-May-13 0:37am

alekcarlsen

Updated 17-May-13 1:07am

v3

Add a Solution

Comments

[no name] 17-May-13 6:46am

There is not nearly enough information here to even begin.
"i install it on 2012", what is "2012"? I am not aware of any OS named "2012" available for you to install Windows services on.
"as it should on 2008r2", same thing.
The only thing I can imagine that 2012 and 2008R2 could refer to is SQL Server and you do not install Windows services in SQL Server.

alekcarlsen 17-May-13 7:04am

"you do not install Windows services in SQL Server." - then why would you imagine that i ment SQL Server? - let me answer your question with a question...
where do you install services - and which OS'es are named 2008r2 and 2012 where one could install a windows service?
i've edited my question to more correctly state which OS i'm talking about

here are some links
http://en.wikipedia.org/wiki/Windows_Server_2008_R2
http://en.wikipedia.org/wiki/Windows_Server_2012

[no name] 17-May-13 7:20am

Thank you for clarifying. Mostly because "2008r2" can also refer to SQL Server and is not specific to Windows Server at all. You were not specific in what you are trying to do.
And to answer your other question, there are no OS's named "2012" or "2008r2" that I am aware of. There is an operating system named Windows Server 2008 that you could install windows services on but you could not do this in SQL Server 2008.

alekcarlsen 17-May-13 7:31am

it's implicit that im talking about "Windows server 2008r2" when i'm talking about a windows service, that i wrote, that i installed on the OS. and NOT SQL server. Because as you said "you do not install Windows services in SQL Server."
Now.. do you actually have an answer to my question?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2013-05-17T04:04:00

Solution 1

It sounds like your service depends on a couple of other services (drivers) running before it can send it's packet.

I would modify your service registration to have dependancies on "TCP/IP Protocol Driver" and "Windows Firewall". It'll force your service to wait until those two services are running before it starts.

Posted 17-May-13 4:04am

Dave Kreskowiak

Comments

alekcarlsen 17-May-13 13:51pm

it has a reconnect method, that handles this. - still not working when rebooting windows 2012 server - but same thing works in 2008 - im curious as to what has changed.

Dave Kreskowiak 17-May-13 15:41pm

Well, it sounds like your reconenct code isn't detecting that it needs to do this, or it gives up too soon and/or retries too fast. This also depends on exactly how you implemented this reconnect code.

alekcarlsen 17-May-13 16:10pm

Well the thing, as stated numerous times.
The exact same code works fine in the same scenario on windows server 2008r2

Dave Kreskowiak 17-May-13 16:20pm

Without seeing the code, and there's going to be too much of it to post here, it's pretty much impossible to tell you what's going on.

There's nothing that changed that should have affected a service starting up and sending a TCP/IP packet. Most of what has changed has to do with security and services trying to put up a UI.

alekcarlsen 17-May-13 16:23pm

Ill post my code tomorrow.
But i cant figure out why the same code acts differently in 2 different scenarios on the same server - service restart.. The code connects and sends fine
But a full server reboot and it doesnt.

Dave Kreskowiak 17-May-13 17:23pm

I already told you what to do...