Jump to content
Division-M Community

JonnyManiac

Members
  • Content Count

    13
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by JonnyManiac

  1. I did yes. Hit the issue of the DriveBender DLL not being able to be overwritten during that but just copied the file mentioned in the error dialog manually and clicked OK to continue. All then installed fine. Oddly rolling back to v3.2a that didn’t happen!
  2. I’ve also seen similar post upgrade to 3.4 and rolled back to 3.2 as 3.1 has a memory leak that was causing major issues for me. At first sight it looks like all it is ok. The pool comes up and you can open files. The moment however you try to save an open Office file it fails to save leaving just the .tmp version it uses whilst you edit the file. The pool drive then becomes inaccessible even though DriveBender itself via the management console thinks all is ok! Only fix is the forcefully kill the DriveBender service exe in Task Manager or reboot my WHS2011 server as it basically kills it. Saving the file locally on the laptop I access the server from and then copying the file back to the server (same path) successfully overwrites the file. All other drives remain accessible unless you try to access the DriveBender volume at which point Explorer essentially crashes. The DriveBender console doesn't show any open files related to the (in this case) Excel spreadsheet but does appear to keep other open file handles 'active' and listed. Support ticket raised.
  3. I'm getting these error messages in v3.4 as well. They didn't occur in v3.2. Support ticket logged.
  4. Unfortunately I have to take the above back. At first sight it looks like all is ok. The pool comes up and you can open files. The moment however you try to save an Office file (which writes a tmp file version of the document/spreadsheet initially and then renames the file) it fails to save. The pool drive then becomes inaccessible even though DriveBender itself via the management console thinks all is ok! Only fix is the forcefully kill the DriveBender service exe in Task Manager or reboot my WHS2011 server as it basically kills it. Will have to rollback once I’ve captured logs and logged a support ticket.
  5. Upgraded and all looks good. Do however have the issue of the new DriveBender DLL not copying over the existing version that I’ve had for the last several releases. This is really as a manual copy of the file from the lib directory referenced in the error message works just fine!
  6. I also have the same issue and have a call open. In my case it looks to have occurred after a large change of data occurred. In this particular instance after a clean up of WHS backup data.
  7. Excellent stuff! Thank you! Had an issue with upgrading from v2.7 and DriveBender.dll as I did upgrading to 2.7. Luckily I still had the support emails from before that told me where to get the new DLL from post install which worked fine otherwise!!
  8. To fix the DLL issue if it has not been updated: - Stop any services that might be using the DriveBender volume such as backup software etc. - Using the Services management console in Windows Stop the ‘Drive Bender Service’. You might be promoted to Stop other dependent services which will be listed, click Yes and let them cleanly stop. - Once the service(s) is/are stopped you can update the DLL. Note of caution there are 2 versions of the DLL and Anthony had to determine what version I should use. There’s one in the lib\v5 and one in the lib\v6 directories which I assume relate to your OS version. With WHS2011 mine was the v5 one but this may not be correct for your OS. If you’re not sure - DON’T CHANGE IT! - Once you have updated the DLL (noting the above) you can reboot the server. All should then come up at boot and be using the replaced DLL.
  9. I've a call open at the moment so once I know anything I'll post it here. Although I'm sure if it's anything serious Anthony will post anyway. So far he has stated that this version of the DLL should work with DB 2.7 without any issues.
  10. Yep, was already running v2.6 before the upgrade. Given the DLL version in use is 2.5 I suspect that upgrade also didn't update the DLL. The version in the C:\Program Files\Division-M\Drive Bender\lib\v5 folder is the 2.7.0.0 version. It should be possible to copy it to the program folder proper without the service running but I don't know if it needs registering or is simply a resource file. I've logged a support call so I'll update this post when I hear back from them.
  11. Thanks, will do once I get a few mins again!
  12. I do indeed have the latest version of 2.7 as I only downloaded it yesterday. While I could uninstall and reinstall, as it essentially works at the moment thought I'd ask if there was a quick way to resolve.
  13. Just upgraded to v2.7.0 on WHS2011 and during install received an error regarding DriveBender.dll: Unable to copy the core library file: C:\Program Files\Division-M\Drive Bender\lib\v5\DriveBender.dll to C:\Program Files\Division-M\Drive Bender\DriveBender.dll The install completed and the drive pool has come up successfully so no problems there. However if I check the DLL version in the main program folder it's still v2.5.0.0. Would a reinstall help or does this need the service stopping, new DLL manually copying and then registering please?
×
×
  • Create New...