remembered credentials for NAS

[admin]

Does the problem still persist?

Yes, I tried the current Beta 1 version, still a problem unfortunately.

Steps:

1. Set default location to a local drive (probably not required).
   
2. Create a new job with a network drive, enter credentials when prompted for (current Windows user should not have access by default).
   
3. Do one backup, should work the first time.
   
4. Close HBS, restart services.
   
5. Open HBS again, try to "Restore". If it still works, repeat from step 4.
   

This works a few times but eventually credentials will be lost.

Are you sure you're using Beta 1? I've tried many times and haven't been able to reproduce the issue. Please make sure that no other software is accessing the NetConnect.db during testing, and send us the log file if the issue occurs.

[al3x]

Yes, I tried the current Beta 1 version, still a problem unfortunately.

Steps:

1. Set default location to a local drive (probably not required).
   
2. Create a new job with a network drive, enter credentials when prompted for (current Windows user should not have access by default).
   
3. Do one backup, should work the first time.
   
4. Close HBS, restart services.
   
5. Open HBS again, try to "Restore". If it still works, repeat from step 4.
   

This works a few times but eventually credentials will be lost.

Are you sure you're using Beta 1? I've tried many times and haven't been able to reproduce the issue. Please make sure that no other software is accessing the NetConnect.db during testing, and send us the log file if the issue occurs.

Yes, I'm using the latest beta. I just retried and I think it only happens for the first time now with the latest beta.

Here's a video of it showing the bug:
https://youtu.be/i1cc3bCwi5s




Log folder is attached. Hope that helps 

[admin]

Are you sure you're using Beta 1? I've tried many times and haven't been able to reproduce the issue. Please make sure that no other software is accessing the NetConnect.db during testing, and send us the log file if the issue occurs.

Yes, I'm using the latest beta. I just retried and I think it only happens for the first time now with the latest beta.

Here's a video of it showing the bug:
https://youtu.be/i1cc3bCwi5s




Log folder is attached. Hope that helps 

Very strange issue, we will fix it as soon as possible.