Skip to main content

After update Invalid File Handle

Thread solved

Hello,

after updating to version 40729 backups not working anymoore. The scheduled tasks stopped. I couldn't access the source (local hard drive) an target ( NAS - connection atemp with success). Also I couldn't open the option of these jobs. On allI'm getting the error message:

Invalid file handle : 0x00040025+0x0000FFF0+0x80070544

Also I couldn't access the recovery. There's only a white screen. 

Looks like a bug in the update. I want to create new backup jobs.

Does anyone have the same problem or could help me. 

Thank you. 

0 Users found this helpful

Not seeing this issue on my machine. I am running with only the minimum Backup functionality installed.

 

Just done a successful upgrade from 40338 to 40729 on my Win 11 Hyper-V VM with all Protection turned off / real-time & try and decide not installed.

Running a new backup to my Synology NAS is progressing fine without any sign of the issue reported in the initial post (invalid file handle) but this is a new task, not one ported from an earlier version / build.

Just updated install with option for Anti-ransomware but leaving Real time protection and Try/Decide off. Seems to be running fine. Next I'll add real time protection.

Just created a new job (local to NAS). Options, Sources and Target are working. But the job won't work too. There's only the message: Can't open open job. 

Jos from local drive in the cloud working. 

So I have no idea what I could try anymoore. 

Thought I was the only one with the error, I haven been getting the same error when trying to backup to a Ubuntu SMB share from a Windows 11. It works fine on the same share from MacBook.

Actron,

A simple suggestion is to try restarting your machine.  A initialization of the hardware sometimes fixes invalid exceptions.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

Hello!

I have updated the ticket raised by yourself.

You can expect a contact from our team as soon as possible so we can troubleshoot the issue.

Feel free to update the thread as soon as you have any news/solution from our support.

Best regards.

Enchantech wrote:

Actron,

A simple suggestion is to try restarting your machine.  A initialization of the hardware sometimes fixes invalid exceptions.

That was the first one what I tried to solve the problem. But a reboot doesn't have any effect.  In the meantime a opened a ticket. 

I could try a re-installation but I don't know about the effect for the existing jobs. 

In the meantime after contact with the contact there's a solution for the problem. 

If you change the login credentials for the NAS to "servername\username" the backup job is working again. 

Actron,

Yes, servername\username is the correct syntax for SMB share connections.  That is how share access permission are controlled.

Glad you have it sorted.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

Actron wrote:

In the meantime after contact with the contact there's a solution for the problem. 

If you change the login credentials for the NAS to "servername\username" the backup job is working again. 

Hello!

Thanks for sharing what helped you to workaround the issue.

Best regards. 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

Actron wrote:

In the meantime after contact with the contact there's a solution for the problem. 

If you change the login credentials for the NAS to "servername\username" the backup job is working again. 

Hello!

Thanks for sharing what helped you to workaround the issue.

Best regards.