View Complete Post
We are developing a windows service application which queries the sql db every second. For now, we have enabled connection pooling and every time we open and close connection at every access. Since it is a windows service can I open connection at service
startup and close the connection shutdown
Please let me know the right approach in this scenario.
The exception message is: Could not connect to
http://126.96.36.199:43584/CProsp/CP_WCF/mex. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 188.8.131.52:43584.
What I am trying to do: a WCF service is self hosted in a Windows Forms application. The WCF client is in another Windows Forms application. Eventually, the client is supposed to run on a computer somewhere out there on the Internet and send messages to
the server which is running on my home computer. This is my first attempt at making a remote WCF call.
I have success when server and client either run on the same computer, or are running on different computers attached to my little in-home LAN. When I try to route the client's request via Internet (in preparation for having the client reside out there somewhere)
I get the exception reproduced in the first paragraph above after waiting for about 20 seconds.
OS is WinXP Pro with SP3. Using Visual Studio 2008, Visual Basic. 184.108.40.206 is the IP currently assigned to me by Comcast (I watch carefully to see when it changes; also, I altered it for purposes of asking this question).
I'm trying to migrate our applications working with SQL Server 2005 Express from Windows XP to Windows 7, and have following problem. Desktop applications connect to SQL Server fine, but windows service app returns following error when trying to connect:
[DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security error
I tried installing service under localsystem account and under desktop user account with no success.
My connection string looks like Provider=SQLOLEDB.1;Password=password;Persist Security Info=True;User ID=user;Initial Catalog=data;Data Source=servername
I've searched a bit about this error and one recommendation was to try to use SQL Native client, so I tried to change my connection string to
Provider=SQLNCLI;Pwd=password;UID=user;Database=data;Server=servername, this also works when running from desktop but when running from windows service I get another error
SQL Network Interfaces: The requested security package does not exist
This seems to be purely client problem because when I use wrong server name I still get the same errors.
I guess something changed with permissions of services in Windows 7
Any ideas what could be wrong and how to fix it?
Due to the distributed nature of a business process it makes sense for a workflow to be deployed as a distributed application. See how Windows Workflow and Web Services hold the key.
MSDN Magazine October 2006
Windows Communication Foundation supports several serialization mechanisms and provides a simple, interoperable foundation for future service-oriented applications. Here Aaron Skonnard explains it all.
MSDN Magazine August 2006
In some of my past columns on service orientation and contract-first development, I've mentioned the new suite of designers, formerly codenamed "Whitehorse," that are part of Visual StudioÃÂ® Team edition for Software Architects Team System.
MSDN Magazine August 2005
Windows services are applications that run outside of any particular user context in Windows NT, Windows 2000, or Windows XP. The creation of services used to require expert coding skills and generally required C or C++. Visual Studio .NET now makes it easy for you to create a Windows service, whether you're writing code in C++, C#, or Visual Basic. You can also write a Windows service in any other language that targets the common language runtime. This article walks you through the creation of a useful Windows service, then demonstrates how to install, test, and debug the service.
MSDN Magazine December 2001