WebDeploymentException [sap.com/tc~wd~dispwda] when trying to access NWA

[eduard_korat]

Hi,

Today I installed the NW Java AS with CE 7.1.1 trial version from the SDN (after deinstalling an old version with a BRMS problem). When trying to access the netweaver admin page (http://<computer name>:<port>/nwa) I get an error "com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error in starting application [sap.com/tc_wddispwda].". The start page http://<computer name>:<port>/index.html works fine. Actually any navigation from the start page results in the error above.

Thanks!

Eduard

[Vlado · Accepted solution]

Hi Eduard,

Please check the server trace file for more details on that.

/usr/sap/<SID>/<instance>/j2ee/cluster/server<N>/log/defaultTrace.trc.

HTH!

\-- Vladimir

[eduard_korat · Accepted solution]

Hi Vladimir,

Here the first section of the log trace. First a couple of warnings and then a fatal sql error wrt to UME. Does this give you an idea? Thanks!

<!LOGHEADER[START]/>

<!HELP[Manual modification of the header may cause parsing problem!]/>

<!LOGGINGVERSION[1.5.7.1006]/>

<!NAME[./log/defaultTrace_00.trc]/>

<!PATTERN[defaultTrace_00.trc]/>

<!FORMATTER[com.sap.tc.logging.ListFormatter]/>

<!ENCODING[UTF8]/>

<!FILESET[0, 20, 10485760]/>

<!PREVIOUSFILE[defaultTrace_00.19.trc]/>

<!NEXTFILE[defaultTrace_00.1.trc]/>

<!LOGHEADER[END]/>

#2.0 #2008 11 17 15:23:41:828#0-800#Warning#com.sap.engine.core.service630.container.ReferenceResolver#

#BC-JAS-COR#kernel.sda#0019B93BFBD900000000000500000070###com.sap.engine.core.service630.container.ReferenceResolver########Thread[main,5,main]#Plain##

Interface ejblocking without declared provider.#

#2.0 #2008 11 17 15:23:41:828#0-800#Warning#com.sap.engine.core.service630.container.ReferenceResolver#

#BC-JAS-COR#kernel.sda#0019B93BFBD900000000000600000070###com.sap.engine.core.service630.container.ReferenceResolver########Thread[main,5,main]#Plain##

Interface dsr_ejbcontext_api without declared provider.#

#2.0 #2008 11 17 15:23:41:828#0-800#Warning#com.sap.engine.core.service630.container.ReferenceResolver#

#BC-JAS-COR#kernel.sda#0019B93BFBD900000000000700000070###com.sap.engine.core.service630.container.ReferenceResolver########Thread[main,5,main]#Plain##

Interface ejbormapping without declared provider.#

#2.0 #2008 11 17 15:23:41:828#0-800#Warning#com.sap.engine.core.service630.container.ReferenceResolver#

#BC-JAS-COR#kernel.sda#0019B93BFBD900000000000800000070###com.sap.engine.core.service630.container.ReferenceResolver########Thread[main,5,main]#Plain##

Interface visual_administration without declared provider.#

#2.0 #2008 11 17 15:25:05:769#0-800#Warning#com.sap.engine.services.deploy#

com.sap.ASJ-dpl.ds-000463#BC-JAS-DPL#deploy#0019B93BFBD900030000000000000070#6304950000000120##com.sap.engine.services.deploy#####c832acc4b4fe11dda1c20019b93bfbd9##0#Service Runner [tc_jecachemgmt~srv]#Plain##

Warnings:

The Cache Configuration Upload container reports that doesn't support parallel operations, which slows down the deploy, update and remove operations with applications.

Solution: Please contact the container holder to fix these warnings.#

#2.0 #2008 11 17 15:25:50:955#0-800#Error#com.sap.engine.library.monitor.mapping.ccms.RuntimeParameters#

#BC-JAS-ADM-MON#monitortree#0019B93BFBD900080000000000000070#6304950000000388##com.sap.engine.library.monitor.mapping.ccms.RuntimeParameters####C832ACC4B4FE11DDA1C20019B93BFBD9#c832acc4b4fe11dda1c20019b93bfbd9#c832acc4b4fe11dda1c20019b93bfbd9#0#Service Runner [monitor]#Plain##

Can't create CCMS connector directory (

PALD00441777A
saploc
CCMS
CE1_00
j2ee6304950). Check file system permissions.#

#2.0 #2008 11 17 15:27:33:974#0-800#Warning#com.sap.engine.services.deploy#

com.sap.ASJ-dpl.ds-000463#BC-JAS-DPL#deploy#0019B93BFBD900090000000500000070#6304950000000779##com.sap.engine.services.deploy####C832ACC4B4FE11DDA1C20019B93BFBD9#c832acc4b4fe11dda1c20019b93bfbd9#c832acc4b4fe11dda1c20019b93bfbd9#0#Service Runner [bi_mmrdeployer]#Plain##

Warnings:

The metamodelrepository container reports that doesn't support parallel operations, which slows down the deploy, update and remove operations with applications.

Solution: Please contact the container holder to fix these warnings.#

#2.0 #2008 11 17 15:27:35:836#0-800#Warning#com.sap.engine.services.deploy#

com.sap.ASJ-dpl.ds-000463#BC-JAS-DPL#deploy#0019B93BFBD9000F0000000000000070#6304950000000767##com.sap.engine.services.deploy####C832ACC4B4FE11DDA1C20019B93BFBD9#c832acc4b4fe11dda1c20019b93bfbd9#c832acc4b4fe11dda1c20019b93bfbd9#0#Service Runner [com.sap.glx.repository.svc]#Plain##

Warnings:

The Galaxy_Content_Archive container reports that doesn't support parallel operations, which slows down the deploy, update and remove operations with applications.

Solution: Please contact the container holder to fix these warnings.#

#2.0 #2008 11 17 15:27:37:449#0-800#Error#com.sap.sql.jdbc.direct.DirectPreparedStatement#

com.sap.sql_0025###0019B93BFBD900050000000F00000070#6304950000000164##com.sap.sql.jdbc.direct.DirectPreparedStatement####C832ACC4B4FE11DDA1C20019B93BFBD9#c832acc4b4fe11dda1c20019b93bfbd9#c832acc4b4fe11dda1c20019b93bfbd9#0#Thread[_keystore_managed_system_thread_,5,SystemThreadGroup]#Java##

FATAL SQL error occurred on connection PALD00441777A.dhcp.pal.sap.corp:CE1:SAPCE1DB: code=-708, state="08000", message="[-708] Shutdown";

SQL statement is "SELECT "PID" FROM "UME_STRINGS_PERM" WHERE "PID" = ? AND "PIDH" = ? AND "NAMESP" = ? AND "NAMESPH" = ? AND "ATTR" = ? AND "ATTRH" = ?".#5#-708#08000#[-708] Shutdown#PALD00441777A.dhcp.pal.sap.corp:CE1:SAPCE1DB#SELECT "PID" FROM "UME_STRINGS_PERM" WHERE "PID" = ? AND "PIDH" = ? AND "NAMESP" = ? AND "NAMESPH" = ? AND "ATTR" = ? AND "ATTRH" = ?#

....

[Vlado · Accepted solution]

You should search for the stacktrace / nested exceptions of the above mentioned exception:

"com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error in starting application \[sap.com/tc_wddispwda\]"

This does not seem related...

[eduard_korat · Accepted solution]

Hi Pavlov,

thanks for your quick response! I restarted the server and now it is okay. I guess there can be a problem connecting to the DB server if one starts the AS too early.

Thanks again for your help!

Eduard