Jump to content
Division-M Community


  • Content Count

  • Joined

  • Last visited

  • Days Won


CBers last won the day on January 13

CBers had the most liked content!

About CBers

  • Rank
    Advanced Member
  • Birthday 04/08/1962

Profile Information

  • Gender
  • Location
    : Kent, UK.

Recent Profile Visitors

9,189 profile views
  1. I have raised a Support Ticket with Anthony, as I am having issues when playing content with EMBY that needs transcoding with DB v3.4. When transcoding occurs, temporary files are written to a folder in the pool, but playback fails and I get the following message in the EMBY server log: "System.UnauthorizedAccessException: System.UnauthorizedAccessException: Access to the path 'X:\Videos\transcoding-temp\B12932.m3u8' is denied." It appears that with the latest version, although writes appear to occur successfully, reads seem to be a problem. If I delete the 'transcoding-temp' folder from 'X:\Videos' and let EMBY re-create it and then play something, loads of files are created in the folder as expected, but I get the "access denied" message in the EMBY server logs. When the playback ends, EMBY tidies the folder, so it cannot be permissions. I have regressed from v3.4 to v3.1 and transcoding and playback works fine, using the same folder in the pool. I believe a friend of mine has seen a similar occurrence with v3.4 but with a different service. I just thought I'd put this out there in case others see similar issues.
  2. CBers

    Windows XP

    Have you considered upgrading from Windows XP to Windows 10? According to this page, DriveBender supports Windows XP, but you could raise a Support Ticket just to confirm. FYI, v3.4.0.0 has just been released.
  3. I would upgrade, as there are many more features and bug fixes. I would suggest that you raise a Support Ticket first though, just to check that there wouldn't be any issues upgrading from V2.3 to v3.4. I don't think there would be, but better to be forewarned.
  4. Version has been released. No release Notes as yet, but it can be downloaded from here: https://files.division-m.com/DriveBender v3400.exe
  5. UPDATE: I gave Anthony full access to my server to try and resolve the issue, which he has now done after finding what the bug was. Hopefully a newer version of DB will roll out in the next few days/week. Watch this space !!
  6. Calm down merwinsson, there nothing stopping you going back to v3.1 😀 Use this link for v3.1: https://files.division-m.com/DriveBender v3100.exe Make sure you uninstall v3.3, reboot, (**) install v3.1, reboot and go from there. (**) You may need/want to Hard Reset the DriveBender firewall rules before re-installing v3.1: https://support.division-m.com/hc/en-us/articles/360000568955-Hard-resetting-Pool-Firewall-rules If you Hard Reset the rules, you'll have to set them all up again. Never be in a rush to upgrade to the latest release of software, let others (like me and w3wilkes) use it first and report back any issues, as we tend to have develop servers for this reason. The DriveBender developers can only test so much, before a release. Thanks.
  7. That's one of the things we're investigating.
  8. I have a separate Support Ticket open for v3.3, for which I am supplying Anthony with various debug logs. This has been the case for 2 weeks now, so no, there is no real update. I am running v3.2 on one server and v3.3 on a separate server and even though those messages are appearing, nothing within either pool is affected. Your issue is just the message, rather than a real issue though, correct ?
  9. Hi Joker169. First off, I would raise a Support Ticket and supply the .sil files from around the time the issue occurred, possibly all of them since DriveBender started. Did you recently upgrade from v3.2 to v3.? You could try installing v3.2.
  10. I had that as well, which was when I uninstalled DB, rebooted, installed DB v3.3 and rebooted etc. It's because it's the same version.
  11. Hi Anthony. I did the normal process, uninstalled DB, rebooted, installed DB v3.3, rebooted and all was back online etc. I went into the settings for FolderWall and it was enabled. I turned it off and it said a reboot was required, so I rebooted again. When it was back up, I checked the FolderWall settings and it was enabled again. I haven't done anything else since.
  12. Still getting the same error on start and the FolderWall is enabled on start as well. I downloaded v3.3 again from another PC, so it should be the latest. I have opened a new (another) ticket to upload my .SIL files.
  13. Sounds plausible. I'll give it a whirl 😃
  14. Hi Anthony. Just updated my test server to v3.3 and I got the same message on restart. I then noticed that the FolderWall was enabled, so I have disabled it for now, as I don't use FolderWall. Following the reboot after disabling FolderWall, I still got the same message and FolderWall was enabled again. It's not causing me any issues, so just reporting my findings. Thanks.
  • Create New...