Err: 52 - Nom ou numéro de fichier incorrect - allsync 3.1.1

English support for the software AllSync
Post Reply
Eric Allard
Posts: 7
Joined: 26 Mar 2009, 22:49

Err: 52 - Nom ou numéro de fichier incorrect - allsync 3.1.1

Post by Eric Allard » 27 Jul 2009, 16:37

Hello

I'm using Allsync to synchronize directory every 5 minutes between a PC and a server. Sometimes, tthe scheduler stop and I got this error in the error.log file :

Code: Select all

Time: 25/07/2009 13:30:02
App: AllSync 3.1.1
Modul: modVorgang
Func: Init_ProfilLog_Close
Line: 250
Err: 52 - Nom ou numéro de fichier incorrect
Path: C:\Program Files\AllSync\AllSync.exe
OS: Windows XP Professional Service Pack 3 (Build 2600) Version: 5.1 Build: 2600 ID: 2
IE: 7.0.5730
Mem: 1 045,98 MB / 2 036,89 MB
CPU: (2) Pentium 586.6.5898 [Intel Pentium Pro, II, III or 4] Model 23, Stepping 10, 2792 MHz
Screen: 1024x768
Command: -S -a -ws (PROFILE: synchro surpervision HR1)
Debug0: d:\allsync\profile\synchro surpervision HR1.log
Debug1: d:\allsync\profile\ALS3398.tmp
Debug2:  (PROFILE: synchro surpervision HR1)
Stack: 262A3C767431204F3D777C3D2C (PROFILE: synchro surpervision HR1)
Apptitle: AllSync Scheduler 3.1.1 - Business Edition
Datapath: D:\Allsync
User: FRCH210
Admin: Faux
Profil: synchro surpervision HR1
StartMode:2
CopyMode:0
CopyTyp:0
Edition:3
Language:9
Errcount:1
Stop:0,0 (PROFILE: synchro surpervision HR1)
How could I know the name of the file that makes the scheduler crash ?

thank you
Eric

User avatar
Administrator
Site Admin
Posts: 3549
Joined: 04 Oct 2004, 18:38
Location: Thailand
Contact:

Re: Err: 52 - Nom ou numéro de fichier incorrect - allsync 3

Post by Administrator » 27 Jul 2009, 19:41

First please update to AllSync Version 3.3. Does this help to fix the problem?

Eric Allard
Posts: 7
Joined: 26 Mar 2009, 22:49

Post by Eric Allard » 27 Jul 2009, 21:27

Ok, i did the 3.3 update.
as the problem didn't occur each time, not even every day, i'll wait up to 1 or 2 week to be sure.
I let you know the result

Eric

Eric Allard
Posts: 7
Joined: 26 Mar 2009, 22:49

Post by Eric Allard » 06 Aug 2009, 15:06

Hello

I still got the same problem with the last version of Allsync

thanks for help

BR
Eric

User avatar
Administrator
Site Admin
Posts: 3549
Joined: 04 Oct 2004, 18:38
Location: Thailand
Contact:

Post by Administrator » 06 Aug 2009, 18:34

Please check your emails for an new update.

Eric Allard
Posts: 7
Joined: 26 Mar 2009, 22:49

Post by Eric Allard » 19 Aug 2009, 14:54

hello

Sorry, I'm coming bask from holidays and just saw your mail.
I tried to download the new version but it seems that the file is not available on the web site : I got a 404 error.
can you repost it again

thank you
Eric

Eric Allard
Posts: 7
Joined: 26 Mar 2009, 22:49

Post by Eric Allard » 03 Sep 2009, 20:30

Hello

I have installed the beta version, and, after a few days, I got the same error :

Time: 28/08/2009 14:00:01
App: AllSync 3.3.26 [BETA]
Modul: frmScheduler
Func: LogScheduler
Line: 540
Err: 52 - Nom ou numéro de fichier incorrect
Path: C:\Program Files\AllSync\AllSync.exe
OS: Windows XP Professional Service Pack 3 (Build 2600) Version: 5.1 Build: 2600 ID: 2
IE: 7.0.5730
RAM: 925,33 MB Free / 2 036,89 MB Total
Mem: 14,39 MB
CPU: Processeur Intel Pentium III Xeon
Screen: 768x768
Command: -S -a -ws
Debug0: FileError
Debug1: Checking the log file 'D:\Allsync\Log\scheduler.log' for old entries...
Debug2: D:\Allsync\Log\scheduler.log
Debug3: 1
Stack: 262A3C767431204F3D777C3D2C
Apptitle: AllSync Scheduler 3.3.26 [BETA] - Business Edition
Datapath: D:\Allsync
User: FRCH210
Admin: Faux
StartMode:2
CopyMode:0
CopyTyp:0
Edition:3
Language:9
Errcount:1
Stop:0,0

thanks for help
BR
ERic

User avatar
Administrator
Site Admin
Posts: 3549
Joined: 04 Oct 2004, 18:38
Location: Thailand
Contact:

Post by Administrator » 03 Sep 2009, 20:53

I try to explain what AllSync do:

1. Open the scheduler log
2. write a text line to the log file
3. close the scheduler log <-- here your error occured

Curiously error! Is the drive letter D: a network drive?

Eric Allard
Posts: 7
Joined: 26 Mar 2009, 22:49

Post by Eric Allard » 03 Sep 2009, 21:40

no, D: is a local drive

allsynch is scheduled every 5 minutes and the last log in the scheduler is at 13:55, nothing was writed at 14:00 when the problem occurs. here is the end of scheduler.log :

Code: Select all

28/08/2009 13:55:01 - Checking the log file 'D:\Allsync\Log\scheduler.log' for old entries...
28/08/2009 13:55:01 - ==================================================
28/08/2009 13:55:01 - Task 'sync HR1' started
28/08/2009 13:55:02 - ==================================================
28/08/2009 13:55:02 - PROFILE: synchro surpervision HR1
28/08/2009 13:55:02 - COPY MODE: 1:1 copy
28/08/2009 13:55:02 - --------------------------------------------------
28/08/2009 13:55:02 - SOURCE: \\ch2fi01e\odx$\Supervisions_HR\HR1\aide_process\
28/08/2009 13:55:02 - DESTINATION: D:\data\aide_process\
28/08/2009 13:55:02 - Calculating data for progress indicator...
28/08/2009 13:55:02 - Processing source -->> destination
28/08/2009 13:55:02 - --------------------------------------------------
28/08/2009 13:55:02 - SOURCE: \\ch2fi01e\odx$\Supervisions_HR\HR1\rcp\
28/08/2009 13:55:02 - DESTINATION: D:\data\rcp\
28/08/2009 13:55:02 - Calculating data for progress indicator...
28/08/2009 13:55:02 - Processing source -->> destination
28/08/2009 13:55:02 - --------------------------------------------------
28/08/2009 13:55:03 - SOURCE: \\ch2fi01e\odx$\Supervisions_HR\HR1\ahp\
28/08/2009 13:55:03 - DESTINATION: D:\data\ahp\
28/08/2009 13:55:03 - Calculating data for progress indicator...
28/08/2009 13:55:03 - Processing source -->> destination
28/08/2009 13:55:05 - --------------------------------------------------
28/08/2009 13:55:05 - SOURCE: \\ch2fi01e\odx$\Supervisions_HR\Message_ecran_veille\
28/08/2009 13:55:05 - DESTINATION: D:\data\Message_ecran_veille\
28/08/2009 13:55:05 - Calculating data for progress indicator...
28/08/2009 13:55:05 - Processing source -->> destination
28/08/2009 13:55:05 - --------------------------------------------------
28/08/2009 13:55:05 - PROFILE STATISTICS:
28/08/2009 13:55:05 - Elapsed time : 0:00:03
28/08/2009 13:55:05 - No changes have been made.
28/08/2009 13:55:05 - --------------------------------------------------
28/08/2009 13:55:06 - Copy operation completed.
28/08/2009 13:55:06 - --------------------------------------------------
28/08/2009 13:55:06 - LICENSE INFO: 1 of 6 license(s) have been used since starting AllSync.
I don't think that another software lock this file, there is only a backup task but it's during the night.
what do you think if I try to put the allsync directory in C: ?

BR
Eric

User avatar
Administrator
Site Admin
Posts: 3549
Joined: 04 Oct 2004, 18:38
Location: Thailand
Contact:

Post by Administrator » 04 Sep 2009, 00:54

the next run of your task was at 14:00. Before an task starts the log of the scheduler gets verified for old entries. the bugreport occur while trying to log the text "Checking the log file 'D:\Allsync\Log\scheduler.log' for old entries...". no other software has locked the log file because the scheduler could open and write to that log file but can't close the log file. That's curious...

You can try to change the allsync data path to drive C:. Maybe this helps.

There is no error at the AllSync software that we can fix. Maybe an aggressive virus scanner software blocked the file sometimes.

Post Reply