Skip to content

Windows Application Log Messages

CheckTokenMembership() failed for group 'name', error=errno (errortext)

When file security is enabled and you specify group names for the Databridge Administrators the service uses this system call to determine if the current user is a member of this group. This is an indication that you are not using the SYSTEM ACCOUNT or the account specified as UserID in the Windows Registry, and that the attempt to verify the group membership of the current account in the Databridge Administrator group failed. We recommend that you always run the service using the default account, which is the SYSTEM ACCOUNT.

CreateDirectory() failed for "path", error=errno (errortext)

This message indicates that the service was unable to create the directory specified by path. This needs to be rectified before the service can run effectively. The most likely cause for this is that you entered a bad file name when running the updatepath utility at install time. You need to use regedit to correct this.

End cmd command for data source name, process_id= pid, exit_code= nnnn (exit_code_text)

This message is written to the Application Log when a client run launched by the service terminates.

cmd is the client command, which can be clone, configure, generate, process or redefine. Other client commands such as manage and verifysource are not logged. The process ID is used to find the matching entry when the client run is launched. nnnn (text) is the client exit code and the associated explanatory text that is written to the client log file at the end of the run.

Error in processing binary configuration file "dbcontrol.cfg"

This message is written to the Application Log when the service fails to start because it cannot read the configuration file. Looking at the application event log is a good place to start when the service will not start.

Failed to create configuration file "name"

The first time you run the service it creates its global working directory and the subdirectories config, logs and locks. It then creates the binary configuration file dbcontrol.cfg in the config subdirectory. This message indicates that an error occurred while writing this file.

Failed to open configuration file "name"

This message indicates that the service was unable to open the configuration file and that the subsequent attempt to create or verify the existence of the working directory failed.

INSTALLDIR parameter is an empty string in the Windows registry

The service uses the INSTALLDIR string in the Windows registry key for the key for the Databridge client. This string is created by the installer. This message indicates that the string has been wiped out. It is recommended with this situation to reinstall the Databridge Client.

Launch name command for data source name process_id=dddd, started by who [sched_type]

This message is written to the application log when a client run is launched by the service.

cmd is the client command, which can be clone, configure, generate, process or redefine. Other client commands such as manage and verifysource are not logged. The process ID is used to find the matching entry when the client run is launched. who [sched_type] indicates how the run was launched. Possible values include autogenerate, auto-redefine, console, config and scheduler. Runs started by the scheduler also the scheduling type, which can be daily, fixed_delay, err_retry or startup. startup is a result of having the run_at_startup parameter set to True for the data source. daily and fixed_delay indicate that the run was scheduled because the corresponding type of scheduling is enabled for the data source.

err_retry indicates that a process command was restarted because the service determined that retrying was appropriate. Most errors for which the service retries are controlled by the max_retries and sched_retry_secs parameters. Exit codes that are related to connectivity and inability to connect to the database do not use these parameters. Instead they retry forever using longer and longer intervals until they reach the maximum delay time (currently 5 minutes).

Launch of name command for data source name failed

This message is written to the application when the launch of a client run fails.

Set working directory failed

This message indicates that the service was unable to change the current directory to the working directory. The most likely cause for this is that you entered a bad file name when running the updatepath utility at install time. You need to use regedit to correct this.

SHCreateDirectoryEx() failed for "path", error=errno (errortext)

This message indicates that the service was unable to create the working directory specified by path. This needs to be rectified before the service can run. The most likely cause for this is that you entered a bad file name when running the updatepath utility at install time. You need to use regedit to correct this. Or you do not have write access to the directory in which you trying to create the working directory.

Started

When the service is successfully started it writes this message to the Application Log.

Unable to create DACL

When file security is enabled, the service creates a DACL that it uses to set the file security for all directories and files it creates. If it is unable to create it will revert to using default security, it writes this message to the Application Log as a reminder that something is not working correctly. The most likely cause of this error is that you are not running the service using the proper account. We recommend that you always run the service using the default account, which is the SYSTEM ACCOUNT

Unable to read reg_str parameter from Windows registry (result = nn)

This message indicates that the service was unable to retrieve the value of the string reg_str from the Windows registry key for the Databridge Client, where reg_str is one of the following names: FileSecurity, INSTALLDIR, UserID or WORKINGDIR. Use regedit to see if the Windows registry entry is corrupted. You probably should reinstall the Databridge Client software.

User 'name' not authorized to run Databridge client

When file security is enabled, the service writes this message to the Application Log if it determines that the current userid is not the SYSTEM account or a userid that has access to the Databridge working directory files. We recommend that you always run the service using the default account, which is the SYSTEM account.