Skip to content
English
  • There are no suggestions because the search field is empty.

How do I troubleshoot common Daily Report errors?

Learn how to resolve the most common Daily Report 3 technical issues, including email client configuration problems, XML and INI file errors, network drive issues, Windows language settings, and email export failures. This article provides step-by-step troubleshooting instructions for restoring normal operation and sending reports successfully.

 

TROUBLESHOOTING

PROBLEMS SETTING THE DEFAULT E-MAIL CLIENT

Sometimes, Microsoft Outlook changes the settings of the default e-mail client. If you notice that you have problems sending e-mails directly to e.g. SkyFile:

1. Start Outlook
2. Open Tools → Options from the menu
3. Select Others
4. Ensure the Register Outlook as default e-mail client… is not set (second check box)
5. Click on OK and close the box.
6. Restart the computer
7. Follow the instructions in the chapter Sending the report file ashore for setting the default e-mail client

 

ERROR IN XML DOCUMENT

If you receive this error message, your fssettings.xml cannot be read anymore.

This file has to be deleted within the Daily Report installation folder. Once done, please restart the Daily Report 3 software and a new readable fssettings.xml will be created by the system.

You can find fssettings.xml file within your DailyReport folder:

This should generate a new file automatically.

If you don't know how to locate your Daily Report folder please see below:

or:

 

ERROR INI FILE DOES NOT CONTAIN ATTRIBUTE INSTALLED

This error occurs, if you install a Daily Report Update either without having a full installation or if you install the update to a directory in which no full installation of Daily Report is existing.

In order to correct this issue, please request a full installation from your ship manager or adjust the installation path to the already existing full installation of Daily Report.

 

AN ERROR OCCURRED: INVALID OP PATH DOES NOT MATCH THE FILENAME

This error occurs, if Daily Report is used in conjunction with a network drive, it can occasionally lose access to its files due to networking problems on the operating system side.

This can be easily fixed within the Daily Report 3 application, go to “File” choose “Reload forms/reports files” and hit “Yes” to the Regenerate forms/reports table, the program will restart after that.

 

AN ERROR OCCURED: 1 NOT A SUPPORTED CODE PAGE

This error might happen if the profile and user language are different. Although the profile is set to English, the process is still failing. The problem lies here: the service is running on a system level not on the profile itself.

Change the system settings of the Windows Machine to English. This can be done from Control Panel > Region > Administrative Tab > Copy Settings.

Preffered language (English) should be displayed at the top of this list.

Please carry out the above mentioned changes and than restart.

 

EXPORT ERROR - COULD NOT SEND EMAIL. CALLING EMAIL CLIENT FAILED.

The root cause of the problem in most of the cases lies here in the setting of Windows. Please be so kind and change the standard in the Windows registry into the email client you are using on board, as per below discription.

COMPUTER-WIDE SETTING

Please create a backup for safety reasons and than do the following.

What must the user set if DailyReport is not allowed to send emails using the default email client?

Description

Thunderbird (or any other email client) cannot be accessed from DailyReport via MAPI.

Solution

This is because there is no default email client defined on the computer or for any reason it is not recognized.

 

1. Check the Windows settings

  • Open Windows Key→Settings
  • Enter email in the search field
  • Open Select default email app
  • Select the email program from the displayed list of applications, e.g. Thunderbird
  • Sometimes it helps to change the settings once and then back

 

2. For Thunderbird

Thunderbird (and other mail clients) have an own button to let the application become the default email client. Open Settings and go to System integration. Check the button “When starting, check whether Thunderbird is registered as the default application” and click on “Check now…”

 

3. Check the registry

Open Start > Windows Administrative Tools > Registry Editor On the left (or enter it in the top row), select the key. Check whether the value MAPI (data type REG_SZ) is present on the right and is assigned the number 1. If not, correct or create this value manually:

Key Parameter Value
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Messaging Subsystem MAPI (Datentyp REG_SZ) 1
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows Messaging Subsystem MAPI (Datentyp REG_SZ) 1

 

Check Computer-wide setting

To get full control over defining the current email client for SMAPI, you need to look at the Windows registry:

Key Parameter Value
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail (Standard) (Datentyp REG_SZ) Mozilla Thunderbird

 

Below the Mail key, all available email programs are listed as subkeys. In our example these are Hotmail, Microsoft Outlook and Mozilla Thunderbird.
Now take a look at the right side. The value Microsoft Outlook is entered there under (Standard).

Check also

Key Parameter Value
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail    

 

Note: Windows automatically applies our change to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail to the Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail key.

 

User-related settings

The same key as under HKEY_LOCAL_MACHINE is sometimes also available under HKEY_CURRENT_USER:

Key Parameter Value
Computer\HKEY_CURRENT_USER\SOFTWARE\Clients\Mail (Standard) (Datentyp REG_SZ) Mozilla Thunderbird

 

If this key is not available, you can create it manually. If you enter the desired value here under Standard, this will overwrite the configuration in HKEY_LOCAL_MACHINE. So the user-related setting always wins.
If a change under HKEY_LOCAL_MACHINE is unsuccessful, then this is usually because another setting exists under HKEY_CURRENT_USER.