Search

Index

Global

search engine by freefind
 

No log file

COULDN'T OPEN LOGFILE
The error message shown to the right appears when DupSoft cannot access the log file. The message has nothing to do with the machine but is completely computer related.

 We distinguish between the two cases:
- first start
- subsequent start

FIRST START
Check that the path to BOS is
C:\BOS\ (It does not work to have BOS in a Program folder.)

Suggested remedies
1. Check that you have the rights to run the program. Or start the program as Administrator. i.e. Right-click the BOS icon and select "Run as administrator".

2. Check that you do not have any third party antivirus program (e.g. McAfee, Norton) that prevents access to the file. You can check the security log of the antivirus program if you have installed such a program.

3. Avoid special characters, c.f. below.

SUBSEQUENT START
1. It can be that you have used
unexpected characters in the file name if the message is displayed when you have created a new event.. Remedy: Create a new BOS event with basic Latin characters.

2. The message is displayed if you have a program running in the background that uses the logfile, Remedy: Restart PC

IN EMERGENCY
You can remove (delete) the logfile.txt file that you find in C:\BOS\DupSoft. if nothing else helps.

DupSoft (only)

index sitemap advanced
 

BOS (only)

index sitemap advanced
search engine by freefind
 

BT app (only)

index sitemap advanced
search engine by freefind
 

BT Admin (only)

index sitemap advanced
search engine by freefind
 

BSC (only)

index sitemap advanced
search engine by freefind