1. The Semaphore Timeout Period Has Expired Veeam
2. Western Digital
3. Windows 10 Semaphore Timeout

I'm getting this error..

When you receive semaphore timeout messages, the messages are usually the result of one of the following 1. A heavy load on the server is causing processes to be delayed from releasing semaphores. A process has crashed while holding a semaphore, causing other processes to block when trying to acquire the semaphore.

1. The semaphore timeout period has expired (Exception from HRESULT: 0X80070079) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRIntern at (Int32errorcode IntRtrerrorInfo). I checked the the Crashdump and it referred to Pinnacle11 (video editing application), and cooincidentally, the problem only started after I had been editing a couple of video files.
2. Jun 10, 2019  This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.

The Semaphore Timeout Period Has Expired Veeam

The semaphore timeout period has expired.

On this line..

ThePorts.ActivePort1.Open();

..but I only get it from time to time. When it happens, it happens over and over again. Then the problem goes away, for hours or days, then it comes back.

The serial port is a USB with a BlueTooth connected.

The 1747-L532 has a backplane current of 500 mA at 5 Volts DC and of 175 mA at 24 Volts DC.

I think this guy was having a very similar problem, but not in C#

As best I can estimate, I have read his entire problem, and the resulting comments, and the answer, but I really can't figure out which one fixed his problem, or if C# is significantly different from what he was experiencing.

Thanks for any help for the clueless. This is the actual code where it's happening.

3 Answers

This error could also appear if you are having network latency or internet or local network problems. Bridged connections that have a failing counterpart may be the culprit as well.

Okay, I am now connecting without the semaphore timeout problem.

If anyone reading ever encounters the same thing, I hope that this procedure works for you; but no promises; hey, it's windows.

In my case this was Windows 7

I got a little hint from This page on eHow; not sure if that might help anyone or not.

So anyway, this was the simple twenty three step procedure that worked for me

Western Digital

• Click on start button

• Choose Control Panel

• From Control Panel, choose Device Manger

• From Device Manager, choose Universal Serial Bus Controllers

• From Universal Serial Bus Controllers, click the little sideways triangle

• I cannot predict what you'll see on your computer, but on mine I get a long drop-down list

• Begin the investigation to figure out which one of these members of this list is the culprit..

  • On each member of the drop-down list, right-click on the name

  • A list will open, choose Properties

  • Guesswork time: using the various tabs near the top of the resulting window which opens, make a guess if this is the USB adapter driver which is choking your stuff with semaphore timeouts

• Once you have made the proper guess, then close the USB Root Hub Properties window (but leave the Device Manager window open).

• Physically disonnect anything and everything from that USB hub.

• Unplug it.

• Return your mouse pointer to that USB Root Hub in the list which you identified earlier.

• Right click again

• Choose Uninstall

• Let Windows do its thing

• Wait a little while

• Power Down the whole computer if you have the time; some say this is required. I think I got away without it.

• Plug the USB hub back into a USB connector on the PC

• If the list in the device manager blinks and does a few flash-bulbs, it's okay.

• Plug the BlueTooth connector back into the USB hub

• Let windows do its thing some more

• Within two minutes, I had a working COM port again, no semaphore timeouts.

Hope it works for anyone else who may be having a similar problem.

Windows 10 Semaphore Timeout

I had this problem as well on two different Windows computers when communicating with a Arduino Leonardo. The reliable solution was:

• Find the COM port in device manager and open the device properties.
• Open the 'Port Settings' tab, and click the advanced button.
• There, uncheck the box 'Use FIFO buffers (required 16550 compatible UART), and press OK.

Unfortunately, I don't know what this feature does, or how it affects this issue. After several PC restarts and a dozen device connection cycles, this is the only thing that reliably fixed the issue.

Not the answer you're looking for? Browse other questions tagged c#serial-portusbsemaphoreusbserial or ask your own question.

We are getting this message - more often on Mondays, but we got it today (Wed) on a system when trying to access a network resource.
We have 5 computers, 1 of which sits idle and acts as a 'server.' Some client computers get turned off at night, others do not. All are running both ZoneAlarm and NAV. We are using a DSL modem, Netgear switch and Linksys router.
About 3 weeks ago, we found that we were getting the above message when trying to access shared folders on the server. Not all computers misbehave - the problem occurs on different ones on different mornings. When a system does have the problem, it can still access other shared resources (on other client computers) with no problem. It can also ping the 'server' with no problem. The clients which fail are both XP and W2K systems. The ONLY way we have found to get these connections restored is to reboot the server system. Rebooting the problem clients does nothing.
I've read that this may have something to do with 'renewing IP addresses'.
Any suggestions (in plain English)?
Thanks a ton in advance,
John