Skip to main content
Version: 2.5.0

Troubleshooting Checklists

Checklist for contacting b+s Support in case of an unexpected system behavior​

  • Description of the impact
  • Detailed scenario description
  • Error messages / print screens
  • Version information of all involved components
  • Configuration files of all involved components
  • Example of an occurrence:
    • Cisco CCE agent ID
    • Device extension
    • Timestamp
  • Log files of all involved components that cover the occurrence

Checklist for contacting b+s Support in case of a component crash​

In addition to the above-mentioned bullet points, please collect the followings:

  • Memory dump files (*.dmp or *.mdmp) of the crashed component
  • All binaries (executables, dynamic linked libraries etc.) and symbol files (*.pdb) of the crashed component
always provide logs

For unexpected system behavior as well as for component crashes, always provide logs for the b+s Connects for Siebel components. Ensure that the correct trace masks are set for troubleshooting.