ERROR_INVALID_PASSWORD: Network password not correct. [WNetAddConnection2]

[Flx]

Hi,
I've a problem while synching in a network.
There are 12 computers, all synching to a NAS.
The job is launched by a batch run from task scheduler.
The batch autenthicates to the NAS,
it checks if a particular file on the NAS exist
and, if it finds the file, it runs a FreeFileSync batch job to synch the PC folder to the relative NAS folder.

Every now and then, usually every 4/5 days at least 2 or 3 computers gave the problem
Cannot connect to \\192.168.xxx.xxx\folder
ERROR_INVALID_PASSWORD: Network password not correct. [WNetAddConnection2]

I do nothing, I just let it be and wait for the next day,
the problem last 1, maximum 2 days and then it works as expected,
till the next time.

If I run the job directly from the interface I never got the problem.

I could let it be this way,
but the time I need the data, and they're not the last version,
it wouldn't be this great.

I've seen the this is a problem known since years
and it is surely given to some crazy thing inside the function.
Has anyone solved the thing in some way ?
Or, at the code level, it is not possible to use another function ?

Thanks

[therube]

Sounds similar to, Batch synchronization fail with ERROR_INVALID_PASSWORD.

[Flx]

Hi therube,
yes, it is the same problem.
I already run it as they say.
The task run by the scheduler is a batch,
the batch before autenthicates to the NAS (netuse)
and then launch the FreeFileSync batch job.
Also, before to launch the FreeFileSync job it check if a particular file on the NAS exists,
so the connection is checked before to run it.

[Flx]

I'm really sorry I didn't get any reply to this problem (I mean from developers).
This is a problem that I have since some time and, looking in the forum, is known from years.
I did some test and, definitely, this is a software problem, not fault of developer coding but fault of the component used.
The problem is seen while running the batch with task scheduler copying data from PC to NAS.
I've been able to avoid the problem by disabling HDD power saving in the NAS.
So, the problem arise, using task scheduler, when disks on the NAS are powered down,
the library used, in those conditions, is not able to wait enough for the NAS to wake up.
So either there is a way to increase the timeout in the component or it is necessary to change it.
The actual timeout used is just on they grayline, in a week I got the problem 2 or 3 times so most of the times it works, just it is not what you expect from a backup task.
Hope it helps
Thanks

[therube]

(I'm not really familiar with Windows Task Scheduler...)

Instead of running the .ffs_batch, what if you ran a .bat file instead.

And that .bat file:
- first wakes up your NAS
- sleeps for 5 seconds (or whatever might be needed for your drives to fully awaken)
- & then runs your .ffs_batch.

[Zenju]

I've been able to avoid the problem by disabling HDD power saving in the NAS.
So, the problem arise, using task scheduler, when disks on the NAS are powered down,

It is peculiar that the error code would be ERROR_INVALID_PASSWORD rather than e.g. ERROR_BUSY.