| Author | Message | ||
     David Donnelly |
Can someone please explain this message as I cannot access a dis to rebuild it. Thanks David | ||
| Stefan Fleischmann (Admin) |
You get this message from WinHex when you try to open a logical drive or physical disk with the disk editor? If so, this message originates from Windows (and just has been forwarded by WinHex). It might mean that an error occurred when Windows wanted to synchronize a concurrent access by another process to the same disk. | ||
| Paul Creamer |
but what can u do? I updated from win2k to xp.. and one partition of 3.... was not available after update.. this one partition ..was a logical partition.. now I cant even get to it... its as if its blank...or similar.. My email is pjc@pcreamer.com I dont want to reformat or even go that route until i know that the data is now lost? | ||
| james |
hello im useing windows xp and i had my computer lock on me and it came up with same error and now i cant seem to get into my hard drive not sure why was hoping on saveing some of the info on it but i can use fdisk on it which im thinging about useing even if it means i lose all the stuff i got on it but still a friend had this happen but there were still able to get into it and format it not sure why i cant get into mine all all just gives that error message if any one can help me please well i want to try to save some of my info i had on it if i can | ||
| Anonymous |
if it's a fat32 drive, try booting with a win98 floppy. seems win98 can read them just fine. | ||
| Anonymous |
hi..i got the same problem..can someone help me plz... | ||
| RipRap |
I get the same message trying to access my HD. I thought the HD had gone bad. So this is a software error? | ||
| Anonymous |
Has nothing to do with disk, at least in one of it's manifestations (i.e. when trying to connect to a network share with no log of error). So far I have been unable to find a solution. I know that SP2 doesn't fix it either. We have an all Windows XP/Windows Server 2003 network. I've read somewhere about it being an issue with the spanning tree protocol on the switches. I'll give that a try after testing a bit more. | ||
| Anonymous |
Update from my previous post. I have found some information regarding Intel Pro 1000 network cards. That's what we have on the server running Windows Server 2003. Anyone else expiriencing the problem have such type of cards? Would be good to know to disregard that one. Can't go about changing that card on the server unless there is a confirmation of the problem. Will continue googling and report back. Since this page comes up in the first of Google when searching for an answer and it allows quick and anonymous posts, please use it to report as many details as possible related to this. We'll crack this one down ;) | ||
| Anonymous |
From another page: "This message is how both 2000 and XP advise that they cannot renew a DHCP lease." So trying to fix the ip address see if this still happens... will report back. | ||
| Anonymous |
By the way, the problem comes and goes. Which makes it even more annoying and hard to troubleshoot. | ||
| Anonymous |
Hmmm, if it were the DHCP lease, I would expect that error to leave some trace in the logs of the client or server, but there is nothing in either one of them. Setting fixed IP I can't reproduce the problem, but I can't either on turning it back to automatic. Bummer. Ok. I will keep searching. If nothing comes up in the next few hours I will disable the Spanning Tree Protocol in the Switches (3Com 4226T with latest firmware as of this date, in case it's relevant). All network cards have also all the latest drivers. Several computers in the network sport this problem. | ||
| Anonymous |
Found this bit (http://forums.us.dell.com/supportforums/board/message?board.id=oplex_network&message.id=4763) mentioning the problem being with the Intel network cards, but it doesn't apply to me, I don't get any record on the event's log. Also, looking at the audit information of the DHCP server left on a log file, nothing there. I found though that on the server, under the C:\WINDOWS\system32\dhcp folder there is a file called j50.chk of type "Recovered File fragments" with a date and time close to when I first got the error today in one of the computers. Don't know at the moment if this is in any way related. In any case the "Recovered file fragments" association with .chk files is not something I had come accross before. Also, for sake of completeness, this is all a new setup with Dell servers and workstations, though there are a few non dell workstations that also show the problem. | ||
| Anonymous |
Ok, seems at least someone found a solution, though it doesn't apply directly here... still, it might help someone: http://www.mail-archive.com/samba@lists.samba.org/msg41996.html | ||
| Anonymous |
Looking at the logs in the switches I found that there was one error in the last 48 hours. It was pointing to the port where the last machine gave me the error. Was a collision/fragment error. Not that I know that it means anything or is directly related, but again to give as much information as possible. | ||
| Anonymous |
Aha! now I have some errors in the eventlog. Event ID 30013 from Source ipnathlp The DHCP allocator has disabled itself on IP address 10.0.0.53, since the IP address is outside the 192.168.0.0/255.255.255.0 scope from which addresses are being allocated to DHCP clients. To enable the DHCP allocator on this address, please change the scope to include the IP address, or change the IP address to fall within the scope. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp The link provided by Microsoft had no information. Let's search for more information now that we have this. www.eventid.net had not much to offer: http://www.eventid.net/display.asp?eventid=30013&eventno=1048&source=ipnathlp&phase=1 googling... By the way, if this is of interest, I have a GPO on the server that applies to all computers and disables their server service. Just in case is relevant. still nothing, but didn't pay attention to the other only two errors in the event log that preceeded the one I mentioned. both are the same and are like this: Error IPNATHLP Event ID 32003 The Netwok Address Translator (NAT) was unable to request an operation of the kernel-mode translation module. This may indicate misconfiguration, insufficient resources, or an internal error. The data is the error code. For more inform.... Data: 1f 00 00 00 Eventid.net wasn't of help here either. Don't have ICS (Internet Connection Sharing) on the server nor is the service enabled. still googling... | ||
| Anonymous |
woa, ok. Tired right now. Let's see if someone else chips in. In the mean time I'm going to disable the Computer Browser service in all the workstations. Does anyone know if this will have any adverse effect? I'll continue posting as I try more things in the coming days. Right now I'll wait until I see it happening again. | ||
| Anonymous |
back. Searching for "semaphore timeout period expired scope" brought me to this: http://miataru.computing.net/windows2000/wwwboard/forum/54262.html So I'm going to disable the spanning tree protocol right away and wait and see. Please, if you read this and have the same problem, post (doesn't require login in) with details, and of course if you find a solution, by all means share ;) | ||
| Stefan Fleischmann (Admin) |
If you like, you may post your final conclusion here. After that, please discontinue your postings because what you report is not related at all to our software. Thanks. | ||
| Anonymous |
I get the same error on a Windows 2000 SP4 box and I'm running a GPO that installs some MS patch and get the error on a Windows Script Host window | ||
| Dennis Young |
Did this turn out to be spanni tree for everyone so far? I'm not runnign spanning tree and see it ONLY when I perform a renew when I already have an ip address. If I release first then no errors. | ||
| Jeff Thomason Username: jiro383 Registered: N/A |
I am trying to access files on my Sandisk cruzer mini 1.0 GB travel drive. I am getting the Semaphore timeout period expired error message. Clueless as to how to solve it. Please help!!!!!! | ||
| Alfons Kramer Username: admin3 Registered: 4-2004 |
Your travel drive is defective. But defective drives can be read partially in most cases. There are three alternative disk access methods available in WinHex or XWF. Two of them let you specify the timeout interval. An increase of this value might result in a read success. 10 seconds is the default for the Windows disk driver. A decrease helps to skip defective areas. Another way to deal with defective areas is to make use of the "Clone Disk" function, which allows for partial reads. The success in such situations mainly depends on the level of experience - so try and learn. |