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

I used ASE to connect to database :-

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

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

Issue persist after tried  both DBParm options  :-

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

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

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

AppeonError log :-

AppeonServer log :-

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)]

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

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