Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[starbar]

I am getting an error when loading some profiles

Illegal per-profile backup folder detected.
Using the root backup folder in this session for backup.

Can't understand why I am getting this error as haven't changed any settings since the last scans when everything seemed okay

[Roman]

This message appears if the backupfllder is not available or accessable after loading the profile. default backup folder is the folder named 'backup' within the cmpro folder. so it would be interesting to know if You changed the setting, the folser or where do you store cmrpo.

[starbar]

The backup folder has been changed to F:\Download\Backup\ and the cmpro folder is on the G Drive.

The only thing I have done recently is reinstall windows.

[Roman]

well maybe your f:\download\backup folder simply does not exist....

[starbar]

It is definitely there, I even tried selecting it from the list to see if that had any affect.

[Roman]

Well...you can pack your cmpro folder and send it to me so I can have a look...

[starbar]

Where do I send it to

[Roman]

I've sent you a private message

[Roman]

just to update the readers here....seems like it was more a weird Windows behaviour...

[starbar]

It seems to have been something to do with the folder options in windows and how the navigation pane is displayed.

When it is set to automatically expand it seems to cause problems.

[Roman]

sounds really weird...which Windows version are you using?

I've rechecked the code...looks pretty normal..

it builds up a per-profile backuppath by taking the default one plus datfile name....and checks if the folder exists or can be created...if this checks fails it shows the error...

...I can create a custom version for you which shows some debug information for this check....so maybe something fails during the path name creation... I will let you know when I got something for your to test...

[starbar]

Using Windows 7, like I said I had just reinstalled Windows after updating my motherboard and HD.

For some reason the folder options had changed from the default to automatically expand the navigation pane, it wasn't until I restored the default options that the error went away and haven't had a problem since, testing all the 1300+ tosec dats.

[Roman]

I tried that option but can't repeat the issue....but if it is ok for you know...well...lets put it on the weird but harmless list :-)

[starbar]

Yes is fine now, was just a problem at the time as I was doing a batch job and instead of just been able to let it get on with it overnight, I couldn't as it kept stopping.

It is definitely linked to the tree view in a folder view, because as soon as I expanded it manually it came back, but as soon as it is all collapsed and just showing the drives it works fine.

[Roman]

I really wonder how this can happen....since..well..hey..I'm simply checking files and folders with a Win32 api calls...wonder how such a window setting should influence that....
Maybe if I find some little more time I do some additional checks