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?

Similar Messages

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

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.

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.

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

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

Failover Cluster Manager : Add node wizard Error " This operation returned because the timeout period expired" Windows Server 2012

Hi Everybody,
I have two node cluster and trying to add the third node (which is a Virtual Machine), all nodes are in different subnet and can communication with each other. While adding the third node it gives the error at the end of wizard " This operation
returned because the timeout period expired ". My domain controller is 2008 Enterprise Server and nodes are all running Windows Server 2012 Standard Edition. Any idea what is causing the issue.
thanks

Hi,
Before you add a server (node) to a failover cluster, we strongly recommend that you run the Validate a Configuration Wizard for the existing cluster nodes and the new node
or nodes. The Validate a Configuration Wizard helps you confirm the configuration in a variety of important ways. For example, it validates that the server to be added is connected correctly to the networks and storage and that it contains the same software
updates. Please post the error or warning report.
Please try to install the Recommended hotfixes and updates for Windows Server 2012-based failover clusters:
Recommended hotfixes and updates for Windows Server 2012-based failover clusters
http://support.microsoft.com/kb/2784261
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

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

Software deployments - timeout period expired

Is there an undocumented timeout period when deploying Application packages ? I've noticed that after about a month, deployment status on computers which haven't received a particular Application package return with "This operation returned because
the timeout period expired" We've re-scheduled installation deadlines every few subsequent days to catch as many online computers in our device collection as possible. I don't see any time-out period in the settings for the Application package
apart from the estimated installation time and max allowed run time (set at a couple of hours)
Thanks

So, then the clients are having issues getting content. You need to troubleshoot this process as it really has nothing to do with the deployment itself. And no, to my knowledge, you can't tweak this timeout. As mentioned, you really need to figure out
why the content isn't being downloaded in the first place and address that.
Jason | http://blog.configmgrftw.com

"Error: 0x800705B4. This operation returned because the timeout period expired"

Hello,
I deployed security updates Mid October 201, however some clients failed to install with the error "0x800705B4 this operation returned because the timeout period expired when installing updates".
Although, i saw an article but this did not address the issue. It was advised i temporarily disable any third party antivirus software and firewall.
Unfortunately, we use SEP antivirus and any attempt to disable it would yanck the clients off the network. Windows Firewall is also disabled on these clients.
Can anyone help urgently?

Hi,
What's the status in Software Center about the updates?
Have you checked SCCM updates logs on the clients?
http://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_SU_NAPLog
Please also check the boundary groups associated with DPs have been configured correctly.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Adobe 10 error #1460 - Timeout period expired

We have been having a problem with saving documents since the upgrade to Adobe 10. If the document is not saved fast enough,
we get the timeout period expired error #1460. Is there some way to adjust this timeperiod?

http://social.technet.microsoft.com/Forums/windowsserver/en-US/b5b439fe-1aa9-4823-a3ac-d0be643a5073/query-using-ad-module-timed-out?forum=winserverDS
has some more information on this, though I don't know if there were any improvements to the AD Module in the last year that might change this situation.
Long story short, the AD module is good for small scale, but beyond that, you might be better off using the System.DirectoryServices classes for better performance and finer control.

Windows 2008 R2 Failover Clustering Issue - The operation returned because the timeout period expired.

I am trying to get a new Windows 2008 R2 cluster to work on two VMware servers (VMware ESXi 5.0.3) and am experiencing some form of timeout issue during the creation of the cluster according to the logs.
All validation checks pass successfully, whether trying to create a single node or dual node cluster, but the same error message is seen when creating the cluster. I have tried various suggestions found but none of them have made a difference. In an effort
to further diagnose the issue I enabled the following diagnostic logs:
- FailoverClustering
- FailoverClustering-Manager
- FailoverClustering-Client
The only useful error I can find is in the FailoverClustering-Client log which reports an error 'Couldn't resolve tcp binding to cluster' for each physical node to be part of the cluster.
In order to further diagnose the cause of the issue, I am looking for any options for increasing logging when attempting to create the cluster. Is there a way to increase the logging to see what the actual timeout is occurring with?
Alex.

Sorry, I should have been more clear ...The servers I am attempting to create a cluster with are Virtual Servers running on a VMware ESXi (5.0.3). They have access to two shared disks (connected to each VM using a separate SCSI Controller from that for the
disk used to install the OS) with Virtual SCSI Bus Sharing set within VMware.
Each Virtual Server has two NICs configured (with static IPs) - one for internal (domain connectivity) and the other for heartbeat connectivity. The servers can ping each other via both interfaces, as expected, but only domain connectivity works via the
internal NIC.
I have tried creating a single node or dual node cluster and get the same error each time. When the cluster is attempting to be created I can see the new computer object is created in Active Directory (which is then deleted when the cluster creation fails)
and I have also tried pre-creating the computer object and specifically setting permissions on it.
When creating the cluster I have tried via the GUI and via PowerShell (both with and without the option to attach the shared storage) but always get the same type of timeout error message. I am hoping there are further debugging options that can be used
to provide a better output as to what the timeout is occurring with.

The semaphore timeout period has expired

Ok seriously what the heck does this mean? Its been happening within this last week! I am using Secure CRT...connectivity is fine between me and router no drops in pings for over 30 mintues.

I too see this problem. Did you solve it? If so what did you do?
Everything I've read says to modify or turn off Windows SNP Chimney stack and SynAttack protect. My server guys say they've done all of this but the problem still persists and now they are pointing at the firewall as the problem.

ZEN StonePlus-Semaphore timeout period expired+firmware issue

Similar Messages

Maybe you are looking for