DB Access Error - debug_print_backtrace() OUTPUT START

[zg2pro]

Hi everyone!

I have granted all privileges to my db user and yet I have an issue with the function: "Create a new Version" which always throws this error:
==============================================================================
DB Access Error - debug_print_backtrace() OUTPUT START
==============================================================================
#0 database->exec_query() called at [C:\wamp\www\testlink\lib\functions\testcase.class.php:1658]
#1 testcase->copy_tcversion() called at [C:\wamp\www\testlink\lib\functions\testcase.class.php:1552]
#2 testcase->create_new_version() called at [C:\wamp\www\testlink\lib\testcases\tcEdit.php:248]
==============================================================================

All other functions work fine but this one. I'm using testlink 1.9.6. I wonder whether I'm running into a config issue or a bug of this version of testlink, please advice. Thx!

[fman]

a) check mantis for similar issues
b) 1.9.8 is out there => update.

[aymen99]

Hello, i'm having the same error message
DB Access Error - debug_print_backtrace() OUTPUT START
ATTENTION: Enabling more debug info will produce path disclosure weakness (CWE-200)
did you figure out what's behind that?
Btw i'm a newbie to all the Qa tools stuff so it would be great if you use simple words.

i'm using Testlink 1.9.14 and i'm trying to integrate it with Jira 7.1.2
Thanks for considering my request.

Aymen

[LauraG]

Hi ! I have the same issue than Aymen. Did anybody find any solution ?

Thank you

[fman]

aymen99 has provided No steps to reproduce, then is impossible to do anything.

[LauraG]

I am having this issue when trying to assign requirements. The response from xml-rpc begins with <pre> and the message error told before.

Do you have any idea of what can be the problem ? Thank you

[fman]

@LauraG as you can see you do not have the same issue, you get same error message that is not the same.
And you do not have the issue when you try to assign requeriments, you have the issue when you try to do the task using XML-RPC, that is completely different.
Summarizing: all people in this thread missed important details, pretending solutions without full details, not a new approach.

As clearly stated on all (scarse) TestLink guidelines and documentation: if you have an issue use mantis, providing a very good use case (see any good guideline you can found in this forum and on internet before creating a far from clear and complete ticket on mantis).

In addition you can relax security on TestLink code to get more info on the error, but IMHO issue in your case is related to the response provided by api method.
Best advice AGAIN is use the PHP client to test before using other kind of client