Remote SQL Server weird semaphore timeout period error

I'm using SQL Server Express 2012 in a home server using no-ip service.
I tried to setup home server to allow remote so I can access home server in my office.
after following a walkthrough, I can register my server to Registered Servers, and tried a query "select * from users", it's worked and I can see the data return.
Test connection is also ok, telnet ok, ping ok, website try open and query ok.
but when I chose "Object Explorer", the management studio took a little time and return this error
TITLE: Connect to Server
Cannot connect to grandholy.no-ip.info.
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.) (Microsoft SQL Server, Error: 121)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=121&LinkId=20476
The semaphore timeout period has expired
BUTTONS:
OK
Could anyone tell me what I can do to explore object without the error?

Hi grandholy,
If you are using Windows Server 2003, Windows 2000 Server, or Windows NT 4.0 at home, you can refer to the following document:
http://support.microsoft.com/kb/892100/en-us
Allen Li
TechNet Community Support

Similar Messages

Error [hyt00] [microsoft][odbc sql server driver] query timeout expired

I have the below network setup:-
1. Its a simple network at my father's office at a small town called Ichalkaranji (District - Kolhapur, Maharashtra).
2. We are using private network range 192.168.1.xxx with two Windows Server 2003 Enterprise Edition with SP2 licensed copies and 15 local Windows 7 clients who are only using Server A.
3. The network is having a TP-Link Braodband Router Connected to internet with the IP 192.168.1.1.
4. Both there Windows Server 2003 Enterprise Edition with SP2 are running separate SQL Server 2005 Express with Advanced Services, you can treat them as Server A (Problematic Server with IP of 192.168.1.2)
and Server B (this is not having any issue with IP of 192.168.1.3).
5. Server A is also being used by 6 Remote users from our Kolkata office using DDNS facility through the NO IP client software which installed separately on both the servers. Kolkata remote users
do not use OR access the Server B.
6. Server B is being used by only 2 Remote users from our Erode office (Under Salem District, Tamilnadu) using DDNS facility through the NO IP client software which installed separately on both
the servers. Erode remote users do not use OR access the Server A.
7. The front end application which running separately on both the servers have been developed in VB by a local vendor at Ichalkaranji (District - Kolhapur, Maharashtra).
8. Both Servers are having the same database structure in terms of design and tables format. Only difference is that both the servers are being used separately.
9. This error OR problem is only related to Server A, where on the clients we get the message "error [hyt00] [microsoft][odbc sql server driver] query timeout expired" every now and then.
10. We have to frequently reboot the server whenever we get this message on the client machines. May be after rebooting every thing works perfectly for 2 hours / 5 Hours / may be one full day but
the the error will come back for sure.
11. Current Database back up size on Server A is around 35 GB and take around 1 hour 15 minutes daily to take the back up.
12. Current Database back up size on Server B is around 3 GB and take around 5 to 10 minutes daily to take the back up.
13. One thing I have noticed is that when ever we reboot Server A, for some time sqlsrvr.exe file will show memory usage of 200 to 300 MBs but it will start using slowly, what i understand is that
this is the way SQL Server works.
14. Both the Servers are also running Quick heal Antivirus Server Edition separate licensed copies also.
15. Server B is also running Tally ERP 9 Licenses copy which is being used locally by 15 users of Ichalkaranji (District - Kolhapur, Maharashtra) same users
Can any one help to resolve this issue. Any help will be highly appreciated.

The error message "query timeout expired" occurs, because by default many APIs, including ODBC only waits for 30 seconds for SQL Server to send any output. If no data has been seen for this period of time, they tell SQL Server to cancel execution
and return this error to the caller.
This timeout could be seen as a token that the query is taking too long time to execute and this needs to be fixed. But it can also be a pain in the rear parts, if you are content with a report taking five minutes, because you only run it once a day.
The simplest way to get rid of the error is to set the timeout to zero, which means "wait forever". This is something your vendor would have to do. This may, however, not resolve the problem, as the users may just find that the application is hanging.
To wit, there are two reasons why the query takes more than 30 seconds to complete. One is that there is simply that much work to do. This can be reduced by adding indexes or by doing other tuning, if the execution time is not acceptable. The other possibility
is blocking. That is, there is a process blocking this query from completing. This is much more likely to require attention.
It is not clear to me, whether the vendor has developed the database part as well. In this case, you should probably call the vendor's support desk to have them to sort this out.
Finally, I am little puzzled. You say that you are using Express Edition, but one of the databases is 35 GB in size. 35 GB is far above the limit for Express Edition.
Erland Sommarskog, SQL Server MVP, [email protected]

VIP Swap and 'The semaphore timeout period has expired' errors

We use the VIP swap technique of rolling out new versions of our apps. These apps use an Azure SQL Database. Starting sometime early this year we started seeing SQL Database errors during the VIP swap. The problem is very consistent, if we have database
activity during the VIP Swap it is very likely to generate one or more of these errors. As you can see below in our custom formatted version of the error the actual SQL Error number is 121 and the text is 'The semaphore timeout period has expired':
SQLError Number:121, Message:A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)
We do utilize the Enterprise library for transient error handling and I have seen these errors from time to time and random points, but the fact that this is very consistent with a VIP swap bothers me. Since both deployments exist before and after the VIP swap
why would there be any interruption in SQL Database connectivity? Our apps consist of a Web App, a few Web Services, and a few Worker Roles. I have seen this error from all of them at different times during VIP swaps.
Any ideas?

Hi Curious,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Best Regards,
Iric
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Weird Semaphore timeout error

Running SQL Server 2008 v10.0.2766 on a Windows 2003 R2 X64. The SQL Server instances (2 per side)are part of an active-active cluster. We are seeing the following series of errors generated from our agent jobs:
From the job's Agent History:
TCP Provider: The semaphore timeout period has expired. [SQLSTATE 08S01] (Error 121) Communication link failure [SQLSTATE 08S01] (Error 121). The step failed.
From the SQL Agent log:
[298] SQLServer Error: 121, Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
[298] SQLServer Error: 121, TCP Provider: The semaphore timeout period has expired. [SQLSTATE 08S01] (LogToTableWrite)
Any ideas what is going on and what these errors mean?
Thanks -
Mike

Hi ShoelessMike,
Based on my research, the error message ("The semaphore timeout period has expired") probably comes from Network/Socket layer and is not directly related to SQL. All
your network activity would fail at that time.
And error 121 usually means a network NIC problem.
To fix this issue, could you please check the following article if it applies to you.
http://support.microsoft.com/kb/325487
And also see the following thread....
http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/d99b4d8e-feeb-43cb-80af-3d4826340a2c
If you have any more questions, please feel free to let me know.
Thanks,
Yoyo Yu

SCCM 2012 R2 configure WSUS got error remote SQL Server 2012

Hi All,
I got question ask on when i want to configure the WSUS component it failed as per screenshot and my SCCM cant work with it.
SCCM Server : Windows Server 2012 R2 (WSUS featured installed)
SCCM Version: System Center Config Manager R2
Remote SQL Server : Windows Server 2012 R2
SQL Version: SQL Server 2012 SP1 -11.0.3153
WSUS Error:
SCCM Error:
Hope you all can provide me a good solution on it I had no clue on this.
Regards,
Sam

Sam,
Recommend you
Remove SUP
Remove WSUS role
Delete the SUSDB on the remote SQL server
Reboot the server
Reinstall WSUS feature
Reinstall SUP
Take a look at my blog on installing a SUP on 2012 from the section 'Install WSUS on the remote SUP server'
http://sccmentor.wordpress.com/2014/09/11/installing-a-remote-sup-in-sccm-2012-r2-on-windows-server-2012-r2/
Make sure you run the Post Install tasks as well.
Cheers
Paul | sccmentor.wordpress.com

Error 0x80070079: The semaphore timeout period has expired

Whenever I try to copy large files over a wireless network (Laptop > Desktop) I get the following error:-
Error 0x80070079: The semaphore timeout period has expired
I've done a search on Google and have found that a number of other users are having the same problem, but no-one seems to have a fix for it.
Can anyone help?
(I'm running Vista Ultimate on both my Laptop & Desktop)

Lionel Chen - MSFT wrote:
Hello Ady,
Thanks for your post!
This issue may be a little complex and require some steps to troubleshoot:
1.    Update the driver of wireless network adapters in both of your computers.
2.    Temporarily disable all the firewalls and anti-virus applications, then check the issue again.
3.    To exclude the factors from other services and applications, do a clean boot to check the issue and perform Step 4.
(KB929135) How to troubleshoot a problem by performing a clean boot in Windows Vista
http://support.microsoft.com/default.aspx?scid=kb;EN-US;929135
4.    With clean boot, try to apply the hotfixes contained in the following KB articles:
(KB932045) Error message when you use a network connection to copy a large file from one Windows Vista-based computer to another Windows Vista-based computer: "The connection has been lost"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;932045
(KB932063) Several problems occur on a Windows Vista-based computer when you work in a wireless network environment
http://support.microsoft.com/default.aspx?scid=kb;EN-US;932063
If problem still persists after steps above, this issue is very possibly due to network devices or configurations, please let me know:
1.    Whether this problem occurs in wired network?
2.    If strengthening the network signals, the problem can be changed?
3.    What size of files will lead to this error.
4.    Does this error terminate the copy process?
5.    Models of the wireless network adapter and wireless router.
More details about his issue are preferred. Thanks!
Have a nice weekend!
Regards,
Lionel Chen
Microsoft Online Community Support
Well this did'nt work for me.
Any other solution?
Using XP Prof. Service Pack 3 beta.

Error 0x80070079: The semaphore timeout period has elapsed.

Trying to Copy videos from Windows 8.1 Enterprise Dell Inspiron PC to Seagate Slim drive. I keep getting following error:
An unexpected error is keeping you from copying the file.If you continue to receive this error, you can use error code to search for help with this problem.
Error 0x80070079: The semaphore timeout period has elapsed.
Size 138 MB
Availability: Available Offline
Please suggest

Hi,
In addition, please also take a look into the below thread:
Error 0x80070079: The semaphore timeout period has
expired
Please take a look at the reasons mentioned by Robinson Zhang, and then check if issue could be solved in safe mode.
Best regards
Michael Shao
TechNet Community Support

The operation failed because of a protection agent failure. (ID 998 Details: The semaphore timeout period has expired (0x80070079))

Recently we got this error, while backup to tape, and no idea what is it.
What cause of this error?
The operation failed because of a protection agent failure. (ID 998 Details: The semaphore timeout period has expired (0x80070079)
DPM 2010 with latest roll-up (KB2250444) | DELL Server R710 (Windows 2008 R2 SP1) RAM: 24GB PF: 36-60GB | DELL TL2000 (2 Drives) | And still struggling and monitoring... :(

Hi,
Try this workaround, increase the TcpMaxDataRetransmissions to 10 or more.
How to modify the TCP/IP maximum retransmission timeout
http://support.microsoft.com/kb/170359
Diagnostic steps when "Semaphore timeout" is hit during network transfer:
1. Check if the protected server (sender) or DPM (receiver) was under stress or inaccessible during the time of failure – from event logs from both the machines. Retry should work if the packet loss was because of either of the servers being inaccessible
or under stress for a period.
2. Check if the network between the PS and the DPM is flaky – retransmit count from ‘netstat –s’ or perfmon counters can give an idea.
3. Else contact network support engineer to diagnose the packet loss issue – netmon captures from both machines, packet route and network layout/devices will be required to start the investigation.
4. Take some performance monitor logs on both DPM and Proteted server side.
Some good and basic perfmon counters to take to see if the servers are under stress are below.
Logical Disk/Physical Disk
\%idle
• 100% idle to 50% idle = Healthy
• 49% idle to 20% idle = Warning or Monitor
• 19% idle to 0% idle = Critical or Out of Spec
\%Avg. Disk Sec Read or Write
• .001ms to .015ms = Healthy
• .015ms to .025 = Warning or Monitor
• .026ms or greater = Critical or Out of Spec
Current Disk Queue Length (for all instances)
80 requests for more than 6 minutes.
• Indicates possibly excessive disk queue length.
Memory
\Pool Non Paged Bytes*
• Less that 60% of pool consumed=Healthy
• 61% - 80% of pool consumed = Warning or Monitor.
• Greater than 80% pool consumed = Critical or Out of Spec.
\Pool Paged Bytes*
• Less that 60% of pool consumed=Healthy
• 61% - 80% of pool consumed = Warning or Monitor.
• Greater than 80% pool consumed = Critical or Out of Spec.
\Available Megabytes
• 50% of free memory available or more =Healthy
• 25% of free memory available = Monitor.
• 10% of free memory available = Warning
• Less than 100MB or 5% of free memory available = Critical or Out of Spec.
Processor
\%Processor Time (all instances)
• Less than 60% consumed = Healthy
• 51% - 90% consumed = Monitor or Caution
91% - 100% consumed = Critical
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
posting is provided "AS IS" with no warranties, and confers no rights.

Trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.

I am trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
It verifies the connection and then throws the error:
The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
WSUS Server : Windows Server 2012 R2
Remote SQL Server: 2012 SP1 CU7 hosted on Windows Server 2012 R2
Please let me know if anyone has experienced this issue.

We were trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
It verifies the connection and then throws the error:
The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
Same error even after rebooting the server multiple times.
WSUS Server : Windows Server Standard2012 R2
Remote SQL Server: Windows Server 2012 SP1 CU7 hosted on Windows Server 2012 R2
Event ID 7000:
The Windows Internal Database service failed to start due to the following error:
The service did not start due to a logon failure.
Event ID 7041
The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.
Service: MSSQL$MICROSOFT##WID
Domain and account: NT SERVICE\MSSQL$MICROSOFT##WID
This service account does not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user
right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated
with this node might be removing the right.
I found following article:
"MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID" error when you install WID in Windows Server 2012
http://support.microsoft.com/kb/2832204/en-us
To work around the issue, use one of the following methods:
Assign the Log on as a service user right to NT SERVICE\ALL SERVICES in the GPO that defines the user right.
Exclude the computer from the GPO that defines the user right.
We moved the SCCM server to OU where no policies were getting applied and then applied the new GPO to that OU. Restarted the server and we were able to install WSUS role.
Regards
PR

ZEN StonePlus-Semaphore timeout period expired+firmware issue

Hello, im new here, i apolgize if the topic with same problem already exist. (i found similar, but from 2007.)
I have a problem with my Zen Stone Plus 2GB. The firmware is broken i think. It wont turn up, pc wont recognize it in any way.
I tried this :
http://forums.creative.com/t5/MP3-Pl...67B37F890FAA05
Hey I keep replying to myself. But this time it's good news, I've fixed the problem!
Here are the steps I performed:
. Put the player in recovery mode with these instructions (I was only able to do this once so follow the instructions carefully):
Here are the instructions:
a. Download and install the Mass Storage Drivers from the website.
b. Press and hold the Play button while connecting your player to the PC. If you have a one-piece player then remove the battery first.
c. Keep pressing Play until the New Hardware Wizard starts - this will only happen the first time you put your player into Recovery Mode.
d. Complete the New Hardware Wizard.
To check that you are in Recovery Mode open Device Manager (right-click My Computer and choose Properties, then the Hardware tab and Device Manager) and look for a Player Recovery Device entry.
When in Recovery Mode you can reload the firmware.
2. DO NOT INSTALL THE RIGHT FIRMWARE FOR ZEN STONE PLUS, instead upload the firmware for the MuVo player: http://files.creative.com/manualdn/D...W_LF__2_03.exe
3. After the firmware has been updated go into recovery mode again but this time upload the correct firmware for Zen Stone Plus: http://is.europe.creative.com/suppor...ame=Windows+XP
VOILA! The player has risen from death and can continue to be enjoyed!
And this says the same :
http://www.mycreativefansite.com/200...ue-on-zen.html
NOW what I have done :
. Installed drivers for creative players from their site [done]
2. Inserted the player to the PC [done]
3. Installed the "MP3 Player Recovery Device Drivers" (mentioned in above link) [done]
4. My player is now in "recovery mode" it was recognized as "Player recovery device" [done]
5. I tried to install the firmware for MUVO players (again see the link above) but it came up with the "Operating system reported error: The semaphore timeout period has expired" [fail]
6. I tried to install the latest Zen Stone Plus firmware from creative site but again - "Operating system reported error: The semaphore timeout period has expired" [fail]
http://img97.imageshack.us/img97/430/aerhbae.th.jpg - picture here !
I tried MUVO V200.
That error should came up within the installation of ZEN firmware, not the MUVO firmware. But my problem is : The MUVO firmware does the same error as the ZEN firmware.
I also tried different firmware, for MUVO T200. It wont even turn on the update - "Your player is not connected, please connect your player" it says.
Reseted milion times and the battery is charged by the way.
ps : sorry for my english
Thanks for your help !

Anyone?

Classic ASP web app trying to acces remote SQL Server.

Hi
I have a classic asp web application which accessing a remote SQL Server 200. I am trying to connect using the following connection string in Global.asa file. For some reason not connecting to the remote SQL Server 200. The string is as follows.
Session("dsn") = "provider=SQLOLEDB;app=AppName;server=SERVERNAME;uid=;password=;database=DBName;Trusted_Connection=No"
Session("datadsn") = "data provider=SQLOLEDB;app=AppName;server=SERVERNAME;uid=;password=;database=DBName;Trusted_Connection=No"
Session("server") = "SERVERNAME"
Let me know if I am missing something or doing something wrong?
Varun

SQL Server Error Log has no error
But I found couple of errors in Application EventViewer
The VB Application identified by the event source logged this Application Globalization: Thread ID: 5312 ,Logged: -2147168246 New transaction cannot enlist in the specified transaction coordinator. Error Source: Microsoft OLE DB Provider for SQL Server->ValidateUser
A caller has attempted to propagate a transaction to a remote system, but MSDTC network DTC access is currently disabled on machine 'MyMachineName'. Please review the MS DTC configuration settings.
Varun

Sqliosim semaphore timeout period expired...

I want to know about the semaphore timeout error caused while read/write io of sqliosim.
I have mapped lun to windows through FC connection and started io using sqliosim, i am getting semaphore timeout error.
I have found many microsoft links which talks about this error but not explained exactly the reason of this error
May i know the reasons of this error?
Sample testcase to get this error?
Is this related to disk device registry timeout?
how i can regenerate this error using sqliosim?

Hi vikram jadhav1,
The error "0x80070079: The semaphore timeout period has expired" is returned from the Windows API "winerror.h". It occurs when a synchronization object of type semaphore times out.
A semaphore object is a synchronization object that maintains a count between zero and a specified maximum value. The count is decremented each time a thread completes a wait for the semaphore object and incremented each time a thread releases the semaphore.
When the count reaches zero, no more threads can successfully wait for the semaphore object state to become signaled. The state of a semaphore is set to signaled when its count is greater than zero, and nonsignaled when its count is zero. It acts as a gate
that limits the number of threads sharing the resource to a specified maximum number.
So, in case the semaphore object is nonsignaled(its count is zero) and there are threads waiting for the object, the error occurs when the waiting reaches the timeout.
The error can occur in many scenarios. E.g. TCP/IP, Disk Driver, VSS etc.
It this case, it seems to be a driver issue. However, it is really hard to say what it is the exact cause without the detailed error message.
To understand the exact root cause, I would suggest you to open premier case to Microsoft. The premier team can help to debug the sqliosim to get the cause.
Short answers to your other questions:
--Sample testcase to get this error?
No
--Is this related to disk device registry timeout?
It may be. Debug is required to confirm it.
--how i can regenerate this error using sqliosim?
Without get the root cause, it is hard to reproduce it.
Thanks,
Jinchun Chen

Semaphore timeout period has expired

when trying to prompt the windows server 2012 to be additional domain controller or join server to Domain i got this message
"Semaphore Timeout period has expired " , i changed the Network card with no result.

Hi,
Please confirm your network MTU size is the default value 1500, you can use the following command line to get the current MTU size.
netsh int ipv4 show int
to get your NIC mtu valut.
Please try to disabled the RSS and large send offload on the server and rejoined the member server to the domain.
More related information:
PSA: Incorrect MTU size causes connectivity issues with Windows Server 2012 and Windows Server 2012 R2
http://blogs.technet.com/b/askpfeplat/archive/2014/12/01/psa-incorrect-mtu-size-causes-connectivity-issues-with-windows-server-2012-and-windows-server-2012-r2.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Windows 8: 0x80070079 The semaphore timeout period has expired

I am getting the following error when I try to move files/folders onto my external hardrive.
0x80070079 The semaphore timeout period has expired.
How can I resolve this issue? Thank you.

Hi,
We need some steps to troubleshoot:
Were the files you attempted to move located on the local hard drive?
Please change another port for External hard drive to connect to your computer for test.
Please disconnect the network and try again for test.
Temporarily disable the firewall and anti-virus to check the result.
If it doesn't resolve the issue, perform an safe mode to check the result:
Start your computer in safe mode
http://windows.microsoft.com/en-in/windows-8/windows-startup-settings-safe-mode
Karen Hu
TechNet Community Support

Accessing remote SQL server

Hello, all.
This is the first time I've ever needed to access a remote SQL server, and I'm getting an attribute validation error for the cfquery tag.
The CFQUERY tag currently opens as:
<cfquery name="[queryName]" debug="1" username="#User#" password="#Pass#" dbserver="[SQL Server IP]" dbname="[databaseName]">
What are the attributes that I need in order to remotely access the database?
Thanks,
^_^

You need to setup a datasource in the CF admin pointing to the remote
server, using dbServer will not work.
Mack

Remote SQL Server weird semaphore timeout period error

Similar Messages

Maybe you are looking for