Ivyware Support Chartboard & P2Pmsgcore info@ivyware.com.au Melbourne, AU
Ivyware

Ivyware/Support

Support

Tell us what broke, and how to break it again

Support runs by email. A good report gets answered quickly; a vague one turns into a week of correspondence. Everything below is aimed at making the first reply useful.

Bug reports

When emailing a support request, please include:

  • The name of the download file in which the bug was encountered — the version number matters more than anything else here.
  • The Windows version it was identified on (Windows 10, 11 and so on).
  • A crisp description of the problem.
  • Steps to reproduce it, if at all possible.
  • The event associated with the bug, if you can capture it.
  • The Python advisor or scanner script involved, where one is. Attach the .pya or .pys file.

If the problem involves a script, turn on the diagnostics console first — Ribbon Bar → [Home] tab → [View] group → Console — reproduce the fault, and send the console output with the report. It is usually the fastest route to a diagnosis.

Two things to rule out first

  • Chartboard running elevated. It has no need for administrator privileges and disables Python scripting when it detects them. This is the usual cause of “my advisor script does nothing”.
  • A partial install. The Python 3.11 runtime ships with the installer; scripting is also disabled if it cannot be found.

Submit a question

If you have a question about Chartboard, email info@ivyware.com.au. An answer will be provided as quickly as possible. When submitting your question, please be as specific as possible and always include the exact error message, if there is one.

Questions about the libraries

For P2Pmsgcore and the integration libraries, the same address applies. Useful things to include:

  • Which archive and version you built from — for example P2PmsgODBC(VS2010)2_0_8.zip.
  • Your Visual Studio toolset, and whether you are building 32- or 64-bit.
  • The compiler or linker diagnostic verbatim, if the problem is a build failure.
  • For a runtime problem, the P2Pevent that was raised — every kernel object serialises into a message, so the event usually carries what is needed.

The architecture reference covers what each object family owns, which is often enough to place a fault before you write in.

A note on scope

Chartboard, the libraries and the reference applications are supplied free of charge. AKAserva, AKAssms and SQLmapi in particular represent work in progress and are subject to change without notice. Support is offered on a best-effort basis and is not a warranty of fitness for any particular purpose.

Nothing on this site is financial advice. Configured reference URLs inside the product are samples only and should not be taken as endorsements, nor their contents as valid.