snorman Posted June 23, 2015 Report Share Posted June 23, 2015 Everything was working fine for me with the older version of Sync. My group recently changed to a new linked folder to share among us. It has worked for several other people, but it is not working for me. Each time I try to link to the new link, I get the error message "Request denied." This has been ongoing since Friday. Caveat, I replaced my motherboard, CPU, and RAM on Friday. I'm running Windows 7, and I did not reinstall the operating system. Installing updated drivers brought everything up just fine. I had some issues with the time not showing up correctly, but I fixed all of that. The 2.0 client was working fine after the new hardware, but issues started up when I was given a new link on Friday evening. I've reinstalled the BitTorrent Sync software a couple times so far. I'm currently running version 2.0.126 (33) and I'm still getting the error. I've purged all of the files from my user directory and the program files directory. I've also purged everything BitTorrent related from my registry. Re-installing doesn't fix the issue. Running the client under Administrator also doesn't resolve it. I don't have antivirus running and the Windows firewall is disabled. I've tried connecting through a VPN and still getting the same error. I have a macbook pro running BitTorrent Sync, and I'm able to get sync working on there with the folder. For Windows 7, the problem still exists. I have not tried syncing with any other folders, I only use this tool to sync folders associated with a group I'm in. Thanks for your help. Quote Link to comment Share on other sites More sharing options...
Helen Posted June 24, 2015 Report Share Posted June 24, 2015 snorman. I see possible causes:1) the person in whose Sync the link was originated set the limits on number of days and times Sync can be used. Is it exactly "request denied'? Can you take a screenshot? 2) there are too many peers already connected to the share. What Sync version other people using, do you know? At least is it 2.0 or 1.4? Quote Link to comment Share on other sites More sharing options...
snorman Posted June 24, 2015 Author Report Share Posted June 24, 2015 http://imgur.com/jVCQLaE There's a screenshot of the client. I reached out to the person that created the folder and link, and they said that the new client had to approve everyone for some reason, but he disabled all that he could find. Everyone else is using at least 2.0. We were all told to upgrade once the new version of the folder was released. Checking the client on my server, there's about 30ish of over 70 peers online right now. My client on my windows 7 machine still came up with the request denied error. Everyone else in our group hasn't had the same issue I am having, so I am thinking it is probably related to my recent hardware upgrade. Quote Link to comment Share on other sites More sharing options...
Helen Posted June 25, 2015 Report Share Posted June 25, 2015 is there a chance that the sender of the link previously actually denied your request? In this case, when you use this link again, your peer will be automatically denied. Try - go to My devices, unlink current identity, create a new one. Ask the sender to share the link once again, and try this link again. Before doing it, enable debug logs on your Sync and if request will be again denied, send the logs to us. Quote Link to comment Share on other sites More sharing options...
snorman Posted June 26, 2015 Author Report Share Posted June 26, 2015 Thanks for the tip for enabling debug logs. I enabled that and then I dived into the C:\Users\Username\AppData\Roaming\BitTorrent Sync\sync.log file to see what was happening when I added the link to the folder. [2015-06-26 12:12:12] CRYPTO: Certificate::Verify: Failed to open NCrypt storage provider, error - 0x80090020 I found this item. Each time the Sync client would attempt to verify ACL, it would fail to open the local system's NCrypt storage provider and give an error. I searched about NCrypt and Windows 7, reviewed a couple articles on Window's Crypto API, and determined that one of my services wasn't running. I checked and found that the Extensible Authentication Protocol service was not running and neither was its dependency, the CNG Key Isolation service. I got those both running, deleted the folder, added the link again, and now it's working. Thanks for your help! Quote Link to comment Share on other sites More sharing options...
Helen Posted June 29, 2015 Report Share Posted June 29, 2015 snorman, you did it all by yourself, thank you for sharing the solution with others. marking it as solved. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.