1. Nilotpal Bera
  2. PowerServer 2020 or older (Obsolete)
  3. Sunday, 7 March 2021 08:56 AM UTC

Hi,

Greetings!

In the PowerScript, while declaring and executing the embedded stored procedure, it is giving parse error during runtime stating that stored procedure not found.

Upon debugging Server APIs, found that it is using below query to look for a particular stored procedure by firing the below SQL query.

Now  this user_id function is returning the logged in user id whereas the procedure is under default dbo, hence the query could not find any stored procedure with the specific name.

Here obj.uid = 1 (dbo), but user id is any system generated number other than 1.

Please advise/ suggest.

PowerBuilder 2021 Build 1076

Sybase ASE 16, Web APIs connect via ODBC

PowerServer 2021 Beta

Thanks,

Nilotpal

 

Accepted Answer
David Xiong @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 10 March 2021 02:06 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # Permalink

Hi Nilotpal,

 

When the Stored Procedure is not owned by the currently logged-in user, it happens that the Stored Procedure cannot be found if no owner is specified when declaring Stored Procedure in PowerScript.

 

Please check your code and specify the owner when declaring Stored Procedure so that it can find this Stored Procedure by this Name, for example:

      DECLARE Emp_proc PROCEDURE FOR dbo.GetName;

      EXECUTE Emp_proc;

 

If the issue persists, please help provide a reproducible small case for further analysis. Thanks!

 

Regards,

David

Comment
  1. Nilotpal Bera
  2. Tuesday, 16 March 2021 08:56 AM UTC
Hi David,



Yes its working this way. Thanks for the advise.

But can you please confirm if it will be the same way in the final release, because we have so many embedded stored procedure declared and being executed from PowerBuilder script.



Thanks,

Nilotpal
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Tuesday, 16 March 2021 14:32 PM UTC
Yes, this is how it should work in the final release. If it doesn't work this way then it is a bug. As David mentioned, if you have this problem with the beta version please open a support ticket so we can fix this bug. Thanks!
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Sunday, 7 March 2021 15:23 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi Nilotpal,

Adding to what Chris said, what you are testing is a "preview" version so it's not even beta quality... it is barely alpha quality.  We have released it so customers can get an idea what PowerServer 2021 will be like.  So it is expected this version has many many many bugs.

At any rate, we want the final release to be good quality.  So please do as Chris said and open a support ticket with the problem you discovered so we can make sure it is resolved by the final release.

Thanks,
Armeen

Comment
  1. Nilotpal Bera
  2. Tuesday, 16 March 2021 08:54 AM UTC
Hi Ameen,



Thanks for the support and advise.



Best Regards
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Sunday, 7 March 2021 15:08 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Nilotpal

   For obvious possible errors like this vs general how-to questions, please open a Support Ticket and attach your findings / recreation details to the ticket.

Many thanks in advance.

Regards... Chris

Comment
  1. Nilotpal Bera
  2. Tuesday, 16 March 2021 08:53 AM UTC
Hi Chris, thanks as always!!!
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.