1. Chen Mey Lee
  2. PowerServer 2020 or older (Obsolete)
  3. Wednesday, 20 January 2021 06:08 AM UTC

Hi,

Below issue happened sometime in PowerServer Web  but work fine in PB ,  confirm this input argument always supply with value. It also happened in datawaindow (bind with stored procedure) which 1st input argument us not supplied.

Miguel Leeuwe Accepted Answer Pending Moderation
  1. Wednesday, 20 January 2021 07:08 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi,

I'm not an expert here, but maybe the problem could have something to do with the following:
( I got these ideas from https://docs.appeon.com/ps2019/features_help_for_appeon_web/ch11.html )

- Looking at the error message I assume your using Sybase ASE.

- Maybe you don't have any problems from Powerbuilder, because you are setting staticbind=0 in the dbparms. I think that setting staticbind is not supported on Powerserver.

- Maybe your problem can be solved by using the delimitIdentifier parameter, combined with "Enclose table and column names in double quotes" option to yes or no and

- also try to NOT use the owner name "dbo" and see if leaving it out 

- disablebind parameter?

Hope you can solve it or someone else knows what's going on.

regards

Comment
  1. Chen Mey Lee
  2. Wednesday, 20 January 2021 07:40 AM UTC
Thanks :)
  1. Helpful
There are no comments made yet.
Zhao James Accepted Answer Pending Moderation
  1. Thursday, 21 January 2021 05:11 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Chen,

You said that ‘Below issue happened sometime in PowerServer Web but work fine in PB’. It seems a parameter value related issue, please provide the information below to us for more study, thanks.

1 Is it the ODBC driver or native driver used in AEM data source?
2 Can you always reproduce the issue with a certain case?
3 Please provide a simple PB case (include SQL to create stored procedure , tables , data, etc.)to reproduce the issue.
4 Please refer to the below article to provide the PowerServer log and PowerServer error log to us too, thanks.
http://support.appeon.com/index.php?/Knowledgebase/Article/View/50/0/what-you-can-provide-to-us-for-further-debugging-when-you-run-into-the-appeon-server-related-issues


Regards,
ZhaoKai

Comment
There are no comments made yet.
Chen Mey Lee Accepted Answer Pending Moderation
  1. Thursday, 21 January 2021 05:52 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

Hi ZhoKai,
1. ODBC driver
2. Uncertain case, if put messagebox to display the input parameter value before call stored procedure or datawindow.retreive() then it worked fine.
3. Stored Procedure :-
CREATE PROCEDURE g_VerifyRestrictedIds
@id varchar(15)
,@ErrorMessage varchar(255) = NULL OUTPUT
AS
Declare
@login varchar(15)
Select @login = NULL

Select @login = id
from RestrictedIds
where id = @id

If @login != NULL
Begin
Select @ErrorMessage = 'You can not use ' + @id + ' Login ID to log on.'
return 20000
End

RETURN 0
go
Grant Execute ON dbo.g_VerifyRestrictedIds TO public
go
sp_procxmode 'g_VerifyRestrictedIds', 'unchained'
go

Table:-
CREATE TABLE dbo.RestrictedIds
(
id varchar(15) NOT NULL
)
LOCK ALLPAGES
go
CREATE UNIQUE CLUSTERED INDEX RestrictedIds_i
ON dbo.RestrictedIds( id)
go

4. Logs file cannot attached due to format issue.
In AppeonErorr log, got another similar issue happpened :-
2021-01-21 00:32:37.884 : [Application name=dbweb,conn cache=dbweb_DEVP_adca8li_KL_SP,SQLOrProcedure=g_PlanSlct]Procedure g_PlanSlct expects parameter @comp_nr, which was not supplied.

in AppeonServer log,
884:3 [21-01-21 00:32:37] [Sessions (GetSession)] sessionName=1913406593
884:3 [21-01-21 00:32:37] [DWRetrieveCommand (outputDataObjectHeader)] dataObjectName=dddw_plan, lastModifyTime=NULL
884:3 [21-01-21 00:32:37] [DWRetrieveCommand (executeOneDataObject- pos 10)] DataObject=dddw_plan, actualParamIndex=0, paramList=[DataParameterInfo[name=, dataType=STRING, Direction=Input, IsNull=False, value=886], DataParameterInfo[name=, dataType=STRING, Direction=Input, IsNull=False, value=CB]]
884:3 [21-01-21 00:32:37] [DWRetrieveCommand (execute - get SPWrapper)] spWrapper=SPWrapper[
884:3 [21-01-21 00:32:37] ResultSetNo=0,
884:3 [21-01-21 00:32:37] SQL=g_PlanSlct]
884:3 [21-01-21 00:32:37] [Sessions (getSessionNoUpdateTime)] sessionName1=1913406593
884:3 [21-01-21 00:32:37] [EonASENETCommand (add parameter)] index = 0; type = AnsiString; value = 886
884:3 [21-01-21 00:32:37] [EonASENETCommand (add parameter)] index = 0; type = AnsiString; value = CB
884:3 [21-01-21 00:32:37] [DWRetrieveCommand (execute- general info)] packageCount=1,objectIdList=[0], zipFlag=[0]
900:3 [21-01-21 00:32:37] [DWRetrieveCommand (execute- After execute)] returnValue=ReturnObject [ Code=34, Message=Procedure g_PlanSlct expects parameter @comp_nr, which was not supplied.
900:3 [21-01-21 00:32:37] , Exception=, ReturnValue= ]
900:3 [21-01-21 00:32:37] [JRouterImpl (execute - Before validateTransactionAfterExecute)] ReturnObject [ Code=34, Message=Procedure g_PlanSlct expects parameter @comp_nr, which was not supplied.
900:3 [21-01-21 00:32:37] , Exception=, ReturnValue= ]
900:3 [21-01-21 00:32:37] [Sessions (GetSession)] sessionName=1913406593
900:3 [21-01-21 00:32:37] [JRouterImpl (Call-After execute)] After execute command.execute()
900:3 [21-01-21 00:32:37] [AXDispatcher (doPost)]

 

Comment
  1. Miguel Leeuwe
  2. Thursday, 21 January 2021 19:08 PM UTC
Correct me if I'm wrong, but I think you cannot use a stored procedure like "g_VerifyRestrictedIds" for a retrieve in a datawindow. The stored procedure has to end with a SELECT statement to work in a datawindow.
  1. Helpful
There are no comments made yet.
Chen Mey Lee Accepted Answer Pending Moderation
  1. Thursday, 21 January 2021 07:47 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 4

Below is similar issue , 1st input parameter comp_nr is passed as 006 :-

AppeonError log :-

AppeonServer log :-

Comment
There are no comments made yet.
Chen Mey Lee Accepted Answer Pending Moderation
  1. Thursday, 21 January 2021 08:48 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 5

Below is the 1st issue capture in log files :-

AppeonError log :-

AppeonServer log:

PB logic calling the stored procedure in non-visual object nvo_trx_info.uf_connect() function

 

Comment
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Thursday, 21 January 2021 09:40 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 6

Aha, you are using ODBC

I'm not sure if this parameter is supported on Powerserver and if it will fix your problem, but it's worth trying:

SQLCA.DBParm="PBNewSPInvocation='Yes'"

I'm not sure if you might get a problem when you also use StripParmNames, see:

https://www.appeon.com/developers/get-help/knowledgebase/stripparmnamesyes-not-working-when-pbnewspinvocationyes-used-dbparm.html

Hope it works out,

regards

Comment
There are no comments made yet.
Chen Mey Lee Accepted Answer Pending Moderation
  1. Thursday, 21 January 2021 10:48 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 7

Issue persist after tried  both DBParm options  :-

Comment
  1. Miguel Leeuwe
  2. Thursday, 21 January 2021 14:22 PM UTC
If you WANT to use the native driver, which I would recommend over ODBC, maybe you should use DBMS=ASE and not SYC, said by someone named Chris on this website:

https://answers.sap.com/questions/12374693/connect-powerbuilder-app-to-sybase-ase-usig-oleado.html

"

BTW: if your using PB 12.5.x to connect to ASE, you should be setting your Transaction Object as follows:

SQLCA.DBMS = "ASE"

"
  1. Helpful
  1. Miguel Leeuwe
  2. Thursday, 21 January 2021 21:45 PM UTC
In one of the links that I attached, it's being explained that you should NOT use both parameters as it probably cancels one of them. Anyway, you are NOT running this using ODBC, so those parameters are not relevant anymore.

regards.
  1. Helpful
There are no comments made yet.
Chen Mey Lee Accepted Answer Pending Moderation
  1. Thursday, 21 January 2021 11:06 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 8

Parameter is pass-in but error message said is not supplied :-

Comment
  1. Miguel Leeuwe
  2. Thursday, 21 January 2021 11:30 AM UTC
What calls my attention is that there's 10 named parameters in "paramList" (DataParameterInfor) and there's 11 EonASENETCommands which "add parameter).

Should there not be 11 named parameters instead of 10?

regards
  1. Helpful
  1. Miguel Leeuwe
  2. Thursday, 21 January 2021 11:32 AM UTC
(or maybe the 11th value is not visible on your image).
  1. Helpful
  1. Chen Mey Lee
  2. Thursday, 21 January 2021 15:31 PM UTC
11 parameters (last 2 parameters display in 1 line)
  1. Helpful
There are no comments made yet.
Chen Mey Lee Accepted Answer Pending Moderation
  1. Thursday, 21 January 2021 11:08 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 9

Comment
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Thursday, 21 January 2021 14:26 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 10

Please see my new comments for you last response:

(You are probably not using ODBC but native driver. dbms = SYC.
You should probably change SYC to ASE if on version 12.5 or higher of ASE.)

Comment
There are no comments made yet.
Chen Mey Lee Accepted Answer Pending Moderation
  1. Thursday, 21 January 2021 15:26 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 11

 

I used ASE to connect to database :-

Comment
  1. Kai Zhao @Appeon
  2. Monday, 25 January 2021 02:21 AM UTC
Hi,



Please open a support ticket in the support portal and please provide a test case, Many thanks in advance.

https://www.appeon.com/standardsupport/



Regards,

ZhaoKai

  1. Helpful
  1. Chen Mey Lee
  2. Monday, 25 January 2021 02:42 AM UTC
Bug 5934 open , thks
  1. Helpful
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Thursday, 21 January 2021 21:47 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 12

I suggest you report this as a possible bug on:

https://www.appeon.com/standardsupport/search

They might be able to give you more help.

regards

Comment
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.