Questions? Feedback?powered byOlark live chat software

Standard Support

Bug 1591

Sp Execution error 07 November, 2018

Abhishek sahu
24 August, 2018
Product: PowerBuilder Category: Database
Version: 2017 R3 Publishing: Public
Status: Verifying Priority: P3
Classification: Resolution:
Ken Guo 07 November, 2018
Hi Abhishek, 

I tested OLE Microsoft OLE DB, SNC SQL Native Client, ADO.Net and ODBC. I found that they have different requirements on ‘@’.
Generally speaking, when you create SP DataWindow, it will add ‘@’ by default. When you create a SP DataWindow with PB 10.5 and PB 2017, does it include ‘@’? If it is included by default, I suggest that you change your SP DataWindow to  include ‘@’ too. 

Regards,
Ken
Abhishek sahu 06 November, 2018
PB 2017R3 Errors.docx (404KB)

(In reply to Ken Guo from comment #13)
Hi Abhishek,

If possible kindly please provide us a test case(include PBL&SP) that can
reproduce this issue. Please understand that our development team can only
be able to work on to locate the problem after they reproduce it locally
with a test case. 

Regards,
Ken
Hi Ken, I am attaching the Doc for the steps and error.
Ken Guo 05 November, 2018
Hi Abhishek,

If possible kindly please provide us a test case(include PBL&SP) that can reproduce this issue. Please understand that our development team can only be able to work on to locate the problem after they reproduce it locally with a test case. 

Regards,
Ken
Abhishek sahu 05 November, 2018
PB 2017R3 Errors.docx (106KB)

(In reply to Ken Guo from comment #11)
Hi Abhishek,

PB 2017 doesn’t require adding @ with arguments. 
If you still have any questions, please provide more details preferably with
a sample case. 

Regards,
Ken
Hi ken, when I am trying to create anything in my 2017 environment most of the cases it gives errors i have attached in screenshot .Please have a look. Note: it works fine in PB 10.5.
Ken Guo 05 November, 2018
Hi Abhishek,

PB 2017 doesn’t require adding @ with arguments. 
If you still have any questions, please provide more details preferably with a sample case. 

Regards,
Ken
Abhishek sahu 02 November, 2018
(In reply to Ken Guo from comment #9)
Hi Abhishek,

Thanks for reporting the problem. 
I can’t reproduce your issue. Firstly, we suggest that you check the SP
declaration and see if it includes the SP argument names. If it does, please
delete them for a test and see if you still get the issue.
Please send us your SQLCA connection code, mainly SQLCA.DBMS and
SQLCA.DBParm.
In the meantime, please send us the SP information, including the SP syntax,
SP declaration and execution code. 

Of course, it would be much better if you could provide a complete
reproducible sample case.

Regards,
Ken
Hi, I tried using deleting the sp argument in declaration also i tried using @ in the argument. with @ SP execution is fine. so my question is do i need to change (arguments in sp declaration) everywhere else in the system. Is it compulsory in PB2017 to Add @with argument?
Ken Guo 11 October, 2018
Hi Abhishek,

Thanks for reporting the problem. 
I can’t reproduce your issue. Firstly, we suggest that you check the SP declaration and see if it includes the SP argument names. If it does, please delete them for a test and see if you still get the issue.
Please send us your SQLCA connection code, mainly SQLCA.DBMS and SQLCA.DBParm.
In the meantime, please send us the SP information, including the SP syntax, SP declaration and execution code. 

Of course, it would be much better if you could provide a complete reproducible sample case.

Regards,
Ken
Govinda Lopez 11 October, 2018
Hi Abhishek,

I will transfer your case to our engineering team. We will keep you posted on the results here.

Regards,
Govinda Lopez 11 October, 2018
From Abhishek:

Hi,
 
Actually this same thing working for me in PB 10.5 so i don't think its a coding Error.
 
 
Thanks,
Abhishek
Govinda Lopez 18 September, 2018
Hi Abhishek,

This might be a coding error. Please try doing a trace to your database and do let us know the results.


Regards,
Abhishek sahu 18 September, 2018
Sp execution.png (36KB)

Hi Govinda,

Thanks,
Yes it worked for me I have added  "PBNewSPInvocation='Yes'" and its working.
But for one of the Stored procedure i am getting the error i am attaching the error screenshot for the reference.
kindly help.
Abhishek sahu 18 September, 2018
(In reply to Govinda Lopez from comment #3)
Hi Abhishek,

Have you tried using the PBNewSPInvocation parameter? You may try placing it
in your DBMS DBParm like so:

SQLCA:DBParm="PBNewSPInvocation='Yes'"

You may find more information about this here:
https://www.appeon.com/system/files/product-manual/connection_reference_0.
pdf (Page 161).

Please do let us know if this worked for you.


Regards,
Govinda Lopez 04 September, 2018
Hi Abhishek,

Have you tried using the PBNewSPInvocation parameter? You may try placing it in your DBMS DBParm like so:

SQLCA:DBParm="PBNewSPInvocation='Yes'"

You may find more information about this here: https://www.appeon.com/system/files/product-manual/connection_reference_0.pdf (Page 161).

Please do let us know if this worked for you.


Regards,
Abhishek sahu 04 September, 2018
(In reply to Govinda Lopez from comment #1)
Hi Abhishek,

I will be working on analyzing/reproducing your case. We will keep you
posted on the results here.


Regards,
Hi Govinda, Is there any update on this. Thanks,
Govinda Lopez 24 August, 2018
Hi Abhishek,

I will be working on analyzing/reproducing your case. We will keep you posted on the results here.


Regards,
Abhishek sahu 24 August, 2018
*Phenomenon
application got hang and than close when it tries to execute the Stored procedure. data not saved 

*Reproduce Steps:


Remark:
OS:
Windows 8 
Platform:
64-bit 
Database Type:
Microsoft SQL Server 
Database Version:
2012