Solved: Error when saving model connection

Former Member · ‎03-02-2011

Hi,

When saving a model connection it checks out fine in the front end (connection successfull), but it's not saved/added to the list of model connections.

The java trace gives me the following error:

SQL error occurred on connection sm01.4cmc.local:CE1:SAPCE1DB: code=0, state="02000", message="IN or OUT param missing at position 1.";

SQL statement is "SELECT DISTINCT "REMOTE_USER","PASUSER" FROM "CPMS_USER_PASUSER" WHERE "CONTEXT" = ?".

it seems the problem is related to "CONTEXT" = ?"

Does anyone have any ideas?

Thanks,

Søren

Former Member · ‎03-02-2011

Hi Soren,

What version of SSM are you running?

Are you using JPIP or CPIP?

What user authorization are you using, UME or BOE?

In older versions of SSM there was a webservice user and that users PW info usually is the cause for model connections not saving.

This has changed with SSM 7.5 when using JPIP.

The latest 7.5 server config guide has this troublshooting step for model connections.

You may encounter a problem when you create a model connection and save it, but it does

not appear as a model connection in the Administrator.

The problem occurs if the msxml4.dll exists on the Windows server where Interactive

Publisher is installed, and msxml4.dll is unregistered.

To rectify this problem, open a Command window on the Windows server and type the

following:

regsvr32 msxml4.dll

You must be an administrator on the Windows server to do this.

In my case, I have BOE authentication. In the model connection the user for PAS System logon is a Windows server user where PAS is installed. This user is a administrator in Windows and the PW never expires.

This user is not a BOE user.

"In the Web Server User text box, type the authentication name of a user on the

Application Server system. On Windows, this user must be a member of the

administrators group. On Linux/UNIX, this user must have permission to run the

scripts and programs in the Application Server installation directory."

This is the user we have seen PW issues with that cause the model connection not to appear in the list.

Thanks,

Bill

Former Member · ‎03-02-2011

Hi,

The PAS System Logon: PIPADMIN

The pipadmin user has also been set up on the windows server.

I agree with the point that contexts shouldn't have an effect at this point. I was just wondering since it was part of

the sql statement with the error from the log.

The Java logs are from the NWA log viewer.

No - this is the first on this installation.

Thanks,

Stefan

Heres the log from the file and not the nwa logviewer:

#2.0 #2011 03 02 20:14:23:304#+0100#Error#com.sap.cpm.sm.pwx.web.SMServletBase#

###000C2978F88A01450000000700000BE8#7464650000000004#sap.com/xapps_cpmsm~strategymanagement#com.sap.cpm.sm.pwx.web.SMServletBase#pipadmin#19##1E2385D044EC11E09CB1000C2978F88A#47a20840450111e0bf18000c2978f88a#47a20840450111e0bf18000c2978f88a#0#Thread[HTTP Worker [@19980346],5,Dedicated_Application_Thread]#Plain##

Encounters error while performing named query

[EXCEPTION]

javax.ejb.EJBException: ASJ.ejb.005043 (Failed in component: sap.com/xapps_cpmsm_{strategymanagement, CPM-STM) Exception raised from invocation of public java.lang.String com.sap.cpm.sm.jta.NqJtaWrapperBean.execute(com.sap.cpm.sm.namedquery.NqStatement,java.lang.String) method on bean instance com.sap.cpm.sm.jta.NqJtaWrapperBean@1e2a830 for bean sap.com/xapps}cpm_smstrategymanagementannotation|sap.com_xappscpm_smstrategymanagementjta.jarannotation|NqJtaWrapperBean in application sap.com/xapps_cpmsm~strategymanagement.; nested exception is: com.sap.cpm.sm.common.exception.SMException: NamedQueryERROR: CB_CheckPASUser: executeQuery

com.sap.cpm.sm.common.exception.SMException: NamedQueryERROR: CB_CheckPASUser: executeQuery

at com.sap.cpm.sm.namedquery.NamedQuery.executeQuery(NamedQuery.java:519)

at com.sap.cpm.sm.namedquery.NamedQuery.execute(NamedQuery.java:93)

at com.sap.cpm.sm.jta.NqJtaWrapperBean.execute(NqJtaWrapperBean.java:56)

at sun.reflect.GeneratedMethodAccessor407.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

.

. at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315)

Caused by: com.sap.sql.exception.OpenSQLException: IN or OUT param missing at position 1.

OpenSQLExceptionCategories: []

at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLExceptionFactory.java:167)

at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQLExceptionFactory.java:72)

at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:936)

at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:862)

at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1495)

at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:314)

at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:238)

at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:345)

at com.sap.cpm.sm.namedquery.NamedQuery.executeQuery(NamedQuery.java:503)

... 70 more

Caused by: java.sql.SQLException: IN or OUT param missing at position 1.

at com.sap.dbtech.jdbc.CallableStatementSapDB.execute(CallableStatementSapDB.java:410)

at com.sap.dbtech.jdbc.CallableStatementSapDB.execute(CallableStatementSapDB.java:319)

at com.sap.dbtech.jdbc.CallableStatementSapDB.executeQuery(CallableStatementSapDB.java:763)

at com.sap.dbtech.jdbc.trace.PreparedStatement.executeQuery(PreparedStatement.java:161)

at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:310)

... 73 more

javax.ejb.EJBException: ASJ.ejb.005043 (Failed in component: sap.com/xapps_cpmsm_{strategymanagement, CPM-STM) Exception raised from invocation of public java.lang.String com.sap.cpm.sm.jta.NqJtaWrapperBean.execute(com.sap.cpm.sm.namedquery.NqStatement,java.lang.String) method on bean instance com.sap.cpm.sm.jta.NqJtaWrapperBean@1e2a830 for bean sap.com/xapps}cpm_smstrategymanagementannotation|sap.com_xappscpm_smstrategymanagementjta.jarannotation|NqJtaWrapperBean in application sap.com/xapps_cpmsm~strategymanagement.; nested exception is: com.sap.cpm.sm.common.exception.SMException: NamedQueryERROR: CB_CheckPASUser: executeQuery

at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:84)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)

.

. at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)

at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)

at $Proxy156.execute(Unknown Source)

at com.sap.cpm.sm.pwx.action.PwxNamedQuery.execute(PwxNamedQuery.java:62)

at com.sap.cpm.sm.pwx.web.Desktop.processRequest(Desktop.java:417)

at com.sap.cpm.sm.pwx.web.Desktop.doPost(Desktop.java:246)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

at com.sap.cpm.sm.pwx.web.SMServletBase.service(SMServletBase.java:27)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)

at com.sap.cpm.sm.jsp.web.AuthenticationFilter.doFilter(AuthenticationFilter.java:88)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

at com.sap.cpm.sm.jsp.web.QryFilter.doFilter(QryFilter.java:111)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:375)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:203)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:438)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:427)

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)