cancel
Showing results for 
Search instead for 
Did you mean: 

NWDI Configuration Wizard Execution Error

0 Kudos

Hello NWDI Experts- Need help on this , please.

We have DualStack install NW2004s SP13. I am trying to configure DI. I have deployed the following DI SCA's successfully.

DICBS13_0-10003500.SCA

DIDTR13_0-10003501.SCA

DICMS13_0-10003499.SCA

SAPBUILDT13_0-10003479.SCA

And now my http://server:port/devinf shows up with all components DTR,CMS and CBS. So, the installation part is complete.

But Now , when I try to execute the Configuration Wizard for DI All-in-One Post Install Configuration from NWA , I get the following error. It takes only 2 seconds to execute , And shows as "0 steps executed successfully". And I see the following error in "Show Report" screen. Please Help...

java.lang.NumberFormatException: For input string: "" java.lang.NumberFormatException:forInputString:48 java.lang.Long:parseLong:415 java.lang.Long:parseLong:452 com.sap.tc.lm.ctc.protocol.ReportingRenderer:getStartEndTime:232 com.sap.tc.lm.ctc.protocol.ReportingRenderer:getReportingAsHTML:74 com.sap.tc.lm.ctc.summary.renderer.Protocol:displayReporting:129 com.sap.tc.lm.ctc.summary.renderer.Protocol:doGet:108 javax.servlet.http.HttpServlet:service:740 javax.servlet.http.HttpServlet:service:853 com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl:runServlet:401 com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl:handleRequest:266 com.sap.engine.services.httpserver.server.RequestAnalizer:startServlet:387 com.sap.engine.services.httpserver.server.RequestAnalizer:startServlet:365 com.sap.engine.services.httpserver.server.RequestAnalizer:invokeWebContainer:944 com.sap.engine.services.httpserver.server.RequestAnalizer:handle:266 com.sap.engine.services.httpserver.server.Client:handle:95 com.sap.engine.services.httpserver.server.Processor:request:175 com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener:process:33 com.sap.engine.core.cluster.impl6.session.MessageRunner:run:41 com.sap.engine.core.thread.impl3.ActionObject:run:37 java.security.AccessController:doPrivileged:-2 com.sap.engine.core.thread.impl3.SingleThread:execute:100 com.sap.engine.core.thread.impl3.SingleThread:run:170 500 Internal Server Error

SAP J2EE Engine/7.00

Application error occurred during request processing.

Details: com.sap.engine.services.servlets_jsp.server.exceptions.WebIllegalStateException: The stream has already been taken by method [getOutputStream()].

Exception id: [0017087C8A88006500000B9C00004F23000443746FDAD5AA]

Regards

Venu

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Thanks Again, Srini . How about central SLD ? This system where we trying run Template Configuration for NWDI is on a Central SLD environment. Any ideas...

Regards

Venu

Former Member
0 Kudos

Hi,

Before proceeding with template installer for NWDI, you have to just ensure that the communication user NWDI_CMSADM is available on the central SLD server with appropriate security roles.

For further details refer Note 877804 - NWDI communication user in Central SLD server

Hope this helps !

Regards

Srinivasan T

Answers (3)

Answers (3)

0 Kudos

Thank you again , Srini. Will go through it and see if ait works , otherwise we are planning on get it installed on a brand new server with Java AS and NWDI Usage types.

Rewarded full points to you.

Regards

Venu

0 Kudos

Thanks Srini. I have changed the idlestart parmater already. Looking at the arhitecture of NWDI , It appears that configuring NWDI is not going to be possible for our system , since it has dual stack and it is a Central SLD environment. Can anyone confirm this ?

Regards

Venu

Former Member
0 Kudos

Hi,

NWDI installation is possible in the dual stack.

Check these forum links,

Regards

Srinivasan T

Former Member
0 Kudos

Hi,

To configure DI usage type, you have to set the CBS service property 'idleStart' to 'false' through the Visual Administrator -> server (node) -> service -> Component Build Service -> property sheet. After changing the parameter, restart the service and restart the J2EE engine.

Regards

Srinivasan T