I have a strange issue. Have a windows service running on Windows Server 2008 that receives files over TCP and saves to disk. Initially service was running as Local System account. It worked ok for 7 days and stopped receiving. From the sender side connection succeeds but send fails. The service blocks forever on receive and connection times out.
I changed the user account to "Network Service" and it started working again for 7 days and stopped. I then changed it to run as administrator. It ran for 4 days and stopped again. Now whatever I try it does not work. Rebuilt the code re-installed the service but same issue.
Does anybody ever face such an issue? is it a virus or something? Is windows blocking it? any suggestions will be greatly appreciated.
Note: If I run it as a windows form application it just works fine. Also disabled the firewall but it did not help. While debugging the code I never see any issues. Because it works as a forms app and also worked perfectly as a service for 15-20 days now.
I figured out the problem. When the issue started happening I ran the Filemon utility and figured that the service was failing to access a temp file created using GetTempFileName().
This seems to be a known issue with Windows server 2008R2 and happens randomly.
Here is a solution/Hotfix from Microsoft: http://support.microsoft.com/kb/982613
Related
I'm having a very strange problem with an application in windows 10. It consists of several .exe in the same computer communicating between them with sockets using system.net.sockets library.
The problem I have is that after installing Windows 10 in a new computer, install all windows updates and then installing that application, connection to sockets doesn't work correctly and the application fails. The strangest thing is that if you leave the computer alone for 1-2 days the applications starts working just fine. The same has happened after installing version 1803 update, it stops working and then works one or two days later.
Any idea of what can it be? Has anyone seen something similar?
It really seems to be related to the 1803 update you mentioned.
Symptoms:
Running an application from a network share will fail when creating a socket;
Copying the very same application to a local drive/path will work just fine, without any further modification.
We are also struggling with this while connecting to an Oracle database (both ODBC and ODP.NET) and it seems the issue has recently been acknowledged:
https://support.oracle.com/knowledge/Oracle%20Database%20Products/2399465_1.html
It also seems this is a recurrent Windows bug:
Win Socket Creation fails with Error code 10022 if non super user
https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/3076a9cd-57a0-418d-8de1-07adc3b486bb/socket-fails-with-error-10022-when-application-is-run-from-certain-network-shares-on-vista-and?forum=wsk
Sorry, no effective solution at the time (other than copying the app binaries to a local folder). I'll update this answer once we get a better solution.
OK, looking a little further I found here in SO that this might be related to a SMBv1 network share, which describes the environment we had here (the network share was disabled because of another bug we faced - thanks MSFT).
Re-enabling SMBv2 / SMBv3 on the server solved the issue.
Related post:
After Windows 10 update 1803 my program can't open a socket when running from network share
I downloaded the latest version of Appium from the GitHub. I have installed it on two Windows PCs,
On first one it works fine.
But on the second one, just by clicking "Start server v1.7.2" a window appear showing "The server is stopped".
What is wrong with the configuration?
I found the solution for above error.
It was due to firewall modified by an antivirus, it disables all open ports on this PC.
There can be around three solutions:
Format the PC will help us to get open ports, but it is not a recommended solution.
Uninstalling Antivirus can open blocked ports, by recovering firewall to its original state.
If the 2nd solution does not help then Uninstalling Antivirus and create a new User Account on PC, helps me to run Server successfully.
I have a simple C# Windows Forms application I'm trying to create. on Form1_Load I query my database with a simple request to fill a DataGridView.
If I debug the application, the query executes immediately without issue.
If I "Start without debugging," the connection to the database times out every time with SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
This is affecting multiple different projects which used to work flawlessly before today, so I'm pretty certain it's an issue with Visual Studio and not my code. Here's hoping someone knows what could be causing this.
After a fresh install of VS2008 on a new machine, I'm still experiencing the issue. I was able to run the project without debugging, and the first time connecting to the database worked fine, but now it always fails as described above. Possibly some kind of weird connection pool issue in VS?
Check your antivirus software.
My antivirus was flagging every new application I tried to run without debugging, but I had alerts for my antivirus turned off so I had no idea.
I turned on alerts and suddenly when I ran my app I got a notice from my antivirus. I just allowed it permanently and now everything runs smoothly.
Can't run Pritunl client anymore. It just keeps showing the same error on my Mac.
Error: Unable to communicate with helper service, try restarting
OS X: El Capitan 10.11.6
Tried restarting and re-installing the app.
The app used to work, not sure when it stopped working as I update most updates which come up in app store.
Has anyone experienced this before? Any suggestions on the solution are appreciated.
After some researching I couldn't find anything useful to resolve the issue but I was sure there was a process which was conflicting with functionality of this client. I decided to Quit applications through Activity Monitor one by one. I quitted two or three known to me applications before stumbling upon a service which didn't take up much memory or CPU resources, called helpd. After quitting that application Pritunl Client started without any issues.
What worked for me:
echo "127.0.0.1 localhost" >> /etc/hosts
and then restart
(I had cleaned /etc/hosts previously and it became a problem)
We've successfully set-up WDS (Windows Deployment Services) and had it all working (it's serving an unattended Windows 7 x64 installation, the user only has to F12 then wait for the install to finish) but it no longer works the way it did before.
We're trying to F12 the exact same machine where it used to work. The WDS part of the installation is still automatic (unattended) but ImageUnattend.xml does not seem to run on the client at all now, it gets stuck at the language selection (everything after that is manual as well which is supposed to be automatic).
Inspecting C:\windows\panther on the client machine shows that WDS pops up with an error: WDS CallBack_WdsClient_CopyPrivatesDone: Failed to process client unattend variables.
Changing "%MACHINENAME%" to "*" in the ImageUnattend.xml file makes it all automatic again, however it then renames the computer incorrectly.
The variable %MACHINENAME% worked before, so why does it not work now? Has anyone else met this issue before?
Using a different user (domain administrator) in the ImageUnattend.xml file does not seem to change anything.
After countless of attempts with at least 15 new ImageUnattend.xml files, I decided to restart the server and use the original files I knew worked before.
This fixed it.