[Element Not Found Utorrent Network Drive
Luther Lazaro
I have setup a Windows Server 2008R2 with DNS and AD. When I define a shared folder on the Server and connect to it via \domain.lan\folder I can see the content but if I try to change something in the folder I get the error "element not found". This behaviour is always the same. It doesn't matter if I try connecting directly from the server or through a windows 7 client. BUT: IF I ACCESS THE FOLDER VIA IP ADDRESS OF THE SERVER e.g. \192.168.0.22\folder all works fine. So my guess there is a big problem with the Windows DNS Server. Pinging domain.lan results in the correct IP Address so it is resolved correctly. I don't know where the problem can be.
Long version - My issue was not with my Mac, but with the remote shares. They had 750 permissions, which seemed reasonable since I only wanted the owner and appropriate groups to get access to the folders. But the afpd (Apple File Protocol Daemon) process wasn't in the group! So it was unable to access the files. When other clients, such as my Windows machine accessed the share, they accessed it via Samba (smbd), which was running as root. Thus my Windows machine ran fine, and my Mac client seemed "buggy".
Aloha. I had this same issue with a shared volume on OS X Server 5.1 under OS X 10.11.4 beta. Regardless of the fact that these were beta releases, I have had this issue before. Here's how I managed to solve the problem of the "original item" not being found:
It worked fine for me after that. Note that I do not have the Connect dialog (Command-K in Finder) ever remember my password in the Keychain since I often want to log in as different users. This also helps me troubleshoot once in a while. Also, before doing the above 4 steps, I had gone into the server and removed the shared folder from the File Sharing area and then re-added it, thinking that this would solve the problem; it did not. So therefore, I think the four steps I took (above) were the fix in my situation.
I had this problem for an smb share. After checking /etc/smb.conf on the server, I hadn't added the user trying to connect from the client machine to the valid users line for that share. Once I added the user to valid users, the error resolved and I could successfully connect.
Had this same issue on a Synology NAS not being able to access specific folders. I realized that I had used one set of credentials on some shared folders, and another set of credentials on other shared folders. Once I figured that out all I had to do was:
I have a Drobo 5N, and it's network name is "Drobo5N" - I get this error occasionally, and I have noticed that when I get the error, and I look in the Finder, my Drobo is named "drobo5n" (all lower-case). I have not found a way to fix this without rebooting my computer... but, I'd love to find one. (I do not have to do anything to my Drobo - just reboot my Mac.)
I am thinking the IP change may be causing this problem to crop up and for some reason the mounts are tied up and won't unmount. At that point Finder doesn't know how to remount because the old mounts will not unmount properly.
In my case, similar to some of the others, it was a permissions problem on the Windows 10 machine that hosted the share I was trying to access. I needed to add permissions to the files (not just the share permissions, but the actual file permissions). Specifically, I needed to either add the "Everyone" group as having access, or (because I didn't really want "everyone" to have access) the specific users I wanted to be able to access the share.
For the specific users, it did work to give access with the Windows Live accounts on a Windows 10 Home machine (in case anyone is thinking, as I initially was, that maybe you need local users and/or a Pro version of Win10).
I experienced this issue shortly after upgrading to macOS Sierra and thought that perhaps permissions or something were messed up in the process. After reading through the other replies here and trying to both force restart Finder, check folder permissions, play with the network share from my router, I finally decided to re-enter the credentials (which were saved in my keychain) for the user I had been logging in as, routinely. This fixed the issue for me.
After upgrading machines (new one running Sierra) I was setting up my standard favorites and dragging my NAS share (hosted on a Linux box) and always ended up with a "?" in the favorites. After trying everything in this thread, nothing worked.
After many days of trial-error, research and agonizing, I concluded that my Catalina Mac-mini (as server) with Timemachine External-HD was invisible to my Mojave Macbook. The macbook could see the files on the External-HD from Finder, etc. but Timemachine did not even see the remote External-HD. So, I put my smaller, older WD MyPassport on my macbook as its local Timemachine.
In my case, I had set up various permissions according to my needs (users, groups, read only, read/write, etc.) but I also had on permission set to "Everyone":"No Access". I presume that this particular permission overrides any other one. As soon as I changed that one to "Everyone":"Read Only" everything worked like a charm.
This is what fixed the issue for me:Make sure the domain "local" is included in the DNS/Search Domains settings for your network connection. That's all I had to do, in my case. See this thread for details:
The share was created for all users and when I create a new user the mapped drive is there and working. Problem occurred when the file server was restarted and the user could not access the share. I tried deleting the share from the user. I tried accessing the share directly. Tried creating a new one. Element not found.
I stumbled across your question while researching a related problem of my own.You may wish to check out the following link: explains that when you use the "run as admin" option, you are actually running under an account that is different from the account on which the drive was originally mapped.
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
To be honest I cannot think of anything else to try and despite extensive searching have not found anything else to attempt. The fact I can access the NAS from my wife's PC and via the command prompt leads me to conclude that the NAS and the networking on my PC are both working correctly so logically it is problem with Explorer but I have no idea what, there was nothing installed about the time the problem occurred so I have no idea of the problem or its cause.
I just upgraded my computer from Windows 7 Ultimate to Win 10 Pro. After the process all my network drives have been disconnected and no longer appear under Network along with the other computers connected to the network. I have checked my Network sharing and discovery settings, and I can see the Win10 computer from other computers on the network, just not the other way around.
Try opening them anyway; the disconnectedness is checked at login time, a time at which network connections may or may not be fully established. If you get a prompt for credentials, enter them; it's possible saved passwords got lost in the upgrade.
Open the desktop Control Panel (it's on the Win+X menu). If you're in Category view, choose View network status and tasks. If you're in one of the icon views, choose Network and Sharing Center. Then, on the left, click Change advanced sharing settings.
Expand Private or Guest or Public depending on what you've called your current network connection. (Private, hopefully.) Make sure Turn on network discovery and Turn on file and printer sharing are enabled, then press Save changes.
I just had the same problem with Network Drives not appearing in the Network listing of File Explorer. I fixed the problem with the steps described in the following article: -to-do-if-windows-cannot-map-network-drive.
We have found that laptops don't always connect to mapped drives and to ensure the proper firing of an application that is drive dependent, we wrote a visual basic program to "shake awake" the mapped drive before continuing with starting the of the actual desired program.
Hello, for the last few months I have been having an issue with utorrent. I keep getting the error message 'Error: Element not found'. I check the logger and it says 'readfile error' on the file I choose not to download. Because of this message I 'force re-check' the torrent file. When I do so the file always comes back around 99% finished. Why am I all of a sudden missing parts the files that I know were already completed. For example a movie I may have downloaded and already have watched but was still seeding now is incomplete somehow. This seems to mainly happen on torrents that have a few files and I choose not to download the whole lot of them. This is really starting to add up and hurt my ratios as my upload speed is only about 50 Kb/s.
I checked the FAQs and bt.compact_allocation is already set to False, so I believe that means it's off (forgive my ignorance on that if it is obvious). I only turned up 1 result when searched for 'Error Element not found' and it may something similar to my situation although that thread went unsolved.
I am on WindowsXP and use Sygate Firewall and Nod32 Anti virus. My version of utorrent is 1.7.5, and has been before this issue had started. I am suspicious of Sygate Firewall or the Nod32 doing file checks or something, but I haven't figured out any settings that have fixed the problem. And I have had both of them and utorrent running cohesively in the past. The search results for 'Sygate firewall' and 'Nod32' are fairly large and weaving through all them posts may be a little tedious.
BTW, Call me a Noob, but why does the file, at one point I have already used, watched, or opened without an issue, all of a sudden because missing elements to it when utorrent reads it? Why does say Winrar, VCL, or opening an .exe per say, not have the same effect? Again call me Noob if you want, I am curious. And this only seems to happen to torrents I do not fully download, meaning I elect to only download some parts and do not download others. If I download a torrent completely I do not seem to run into this issue.
795a8134c1