Error Message

No related messages in the Application event log

A corrupt job log, a job log with excessive size or path for job log is missing.

To test for this solution:

1.End the Beserver.exe process in Task Manager.
 

2.Open a command prompt, and change directory to the Backup Exec installation folder (e.g. c:\Program Files\Symantec\Backup Exec)

3.Run: beserver -console  If the text stops at: JobLogWriter::setLogFileName cannot get logfile Directory, continue to step 4.

4.Check the contents of the Backup Exec job log folder (by default, c:\Program Files\Symantec\Backup Exec\Data). Job log files are named BEX_computername_#####.xml.

5.Remove any extraordinarily large files.

6.Restart the Backup Exec Server service.

If issue still persist, Verify Job log path in rejistry - which is by default (C:\Program Files\Symantec\Backup Exec\Data)

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
 

1.Go to Start - Run - Regedit

2.Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Misc \Job Log Path

 Edit the Job Log Path registry value and enter 'C:\Program Files\Symantec\Backup Exec\Data'.

Note:  'C:\Program Files\Symantec\Backup Exec\Data' is the default path for Backup Exec installations. In some cases the path may be different if Backup Exec is installed in another path or drive.

3.Restart the Backup Exec Services