Upgrade a SAP Web AS Java 7.0 to a new SPS stack (SPS10 to SPS14)

Hi
trying to upgrade SAP Web As Java 7 (SPS10) to SPS14.
During deployment I got the following error
java.rmi.RemoteException: Cannot deploy application sap.com/caf~eu~gp~ui~dt~comp~cons..
Reason: Clusterwide exception: Failed to deploy application sap.com/caf~eu~gp~ui~dt~comp~cons. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/caf~eu~gp~ui~dt~comp~cons. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Has anybody an idea what's wrong?
Regards
Karin

Hi everyone,
I had faced the similar problem from upgrading to caf-eu 4.0 to sp15,
The SDMlog file found as:
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/cafeugpuidtcompcons..
Reason: Clusterwide exception: Failed to deploy application sap.com/cafeugpuidtcompcons.
In the forum discussion as mentioned i have changed the default setting to false & the deployment resumed.
Thanks Kiran,
Regards,
Chetan Poojary.

Similar Messages

Upgrade from SAP Webas 6.40 to SAP Netweaver 2004s

Do we have to change the virtual host name used for high availability clustering environment to local host name before we conduct the upgrade from SAP WebAS 6.40 to SAP NetWeaver 2004's ?

Do we have to change the virtual host name used for high availability clustering environment to local host name before we conduct the upgrade from SAP WebAS 6.40 to SAP NetWeaver 2004's ?

No user is able to login to User Management Engine in SAP Web AS Java

Hi,
We are facing an error"User Authentication failed" in SAP Web AS Java(Stand-alone).
No user is able to login through User Management Engine but we were able to login as administrator into Visual admin.Tried SAP* (Emergency User Activation in config tool) also.SAP* is also able to login to Visual Admin But not into UME.Login in Visual Admin was successful when we tried with SAP* or administrator.
Feels like some UME configuration might have changed.Can anyone help me in this.
Thank You.
Regards,
Sudheer.

Hi
Has the SAP* emergency user been activated? While this user is active, all the other users are inactive. Check the following documentation for information on this:
http://help.sap.com/saphelp_nw70/helpdata/en/3a/4a0640d7b28f5ce10000000a155106/frameset.htm
Regards,
Désiré

No user is able to login through User Management Engine in SAP Web AS Java

Hi,
We are facing an error"User Authentication failed" in SAP Web AS Java(Stand-alone).
No user is able to login through User Management Engine but we were able to login as administrator into Visual admin.Tried SAP* (Emergency User Activation in config tool) also.SAP* is also able to login to Visual Admin But not into UME.Login in Visual Admin was successful when we tried with SAP* or administrator.
Feels like some UME configuration might have changed.Can anyone help me in this.
Thank You.
Regards,
Sudheer.

Hi Sudheer Koppireddy
login VA with SAP*
go to services -- key config login ticket and see in right hand side entry deleate all entry
and save it
then go to sm 59 and check HMI connection (http connection to R/3)
deleate it and recreate it
Thanks
Amit Shivhare
PS:Reward Point

User management in SAP web AS Java

My company currently has a user management concept in place for BASIS. These concepts follow the segregation of duties principle. So for example a system administrator can grant rights to end-users but he can't change content himself. This concept was put in place to comply with SOX.
Now my company would like the same principles to be implemented in SAP web AS Java. I have searched the forums, blogs and notes, but i can't seem to find some best practices regarding the matter.
As I have difficulties finding these I am wondering if it is perhaps not needed from a SOX point of view, as the web AS Java doesn't directly access content, does this make sense?
Regardless of the SOX point of view I still believe the problem exists because anyone can mess up your portal environment if the user management is not handled correctly. So does sap have some best practices regarding user management in the web AS Java?
Any feedback on these 2 questions would be great!

Hi,
when I hear these types of requirements I always think of IdM. Any IdM (not only from SAP) allows you to easily satisfy all SOX requirements. I understand that implementing IdM solution is not an easy task but you might get additional benefits from it like reduction of service desk calls and so on, not only compliance.
Cheers

SAP Web AS Java version 2004s (7.0) installation problem

Hello,
I got the below error during the installation process of SAP Web AS Java. Any clue what is wrong?
ERROR 2007-07-05 07:00:30
CJS-30151 Java process server0 of instance PLV/DVEBMGS55 [ABAP:
ACTIVE, Java: (dispatcher: RUNNING, server0: UNKNOWN)] did not start
after 6:30 minutes. Giving up.
ERROR 2007-07-05 07:00:31
FCO-00011 The step startJava with step key
|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_StartJava|ind|ind|ind|ind|5|0|startJava
was executed with status ERROR
It seems
software components are installed but failed to start. I have about 10
steps left (most are configuration) before finish.
Thanks.

Please put consistent value between the max/min heap memory together with the value of young memory (NewSize) and tenured memory.
For example:
-Xmx768m
-Xms384m
-XX:NewSize=96m
-XX:MaxNewSize=192m
This will set the start of young memory 96m, and start of tenured memory (384-96)m
Max young memory is 192, and max for tenured is (768-192)m.
Never set something like below, it won't start.
-Xmx768m
-Xms769m
-XX:NewSize=96m
-XX:MaxNewSize=192m
or
-Xmx768m
-Xms384m
-XX:NewSize=385m
-XX:MaxNewSize=192m
etc, etc.

INSTALL SAP WEB AS JAVA SYSTEM

Dear All,
We installed SAP WEB as ABAP system and trying to install WEB as JAVA system for EP installation, pls give me the easy installtion steps. We are installing with
1) Windows 2003 Enterprise Edition.
2) J2sdk-1_4_2_09.
3) MS SQL 2000 server with SP3.
Thanks with regards
Vijaya kumara M.V

Dear James
Installation halted in JAVA ADD-ON installation stage 2/25 the installation log remains as follows
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
WARNING 2005-11-24 00:17:35
Execution of the command "F:\usr\sap\J2E\SCS01\exe/sapstartsrv.exe '-r' '-q' '-p' 'F:\usr\sap\J2E\SYS\profile\START_SCS01_cvsit' '-s' 'J2E' '-n' '01' '-U' 'cvsit\SAPServiceJ2E' '-P' 'XXXXXX' '-e' 'cvsit\j2eadm'" finished with return code -1. Output:
S
ERROR 2005-11-24 00:17:35
MOS-01011 'F:\usr\sap\J2E\SCS01\exe/sapstartsrv.exe' returned with '-1'.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
let me know the solution for the same to overcome the same.
Thanks with regards
Vijaya kumara

SAP Web AS Java Administration Guide

Hi,
Can anybody give me fundamental tutorial related to WebAS Java Administration.I am going to take training on Duet(SAPDUT) for this the fundas of WebAS Java Administration is must
so can anybody guide me
Thanks in advance

Hi,
You can refer the following pdf.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5c95f593-0701-0010-b3a1-8776da9bd85b
Thanks
R.Murali

SAP Web As Java Hangs after few days using it

Hi everybody,
I have some applications on an Enterprise Portal running in a Java Web As 6.40. Recently, the following problem has appeared: After a day or two of normal use, the portal starts to reject all the connections that are established to it (specifically, the internet explorer gives a time out error), although in Microsoft Management Console shows all processes in green. The problem solves restarting the instance, but the portal remains functional only few days.
Any hints on solving this?
Thanks for any help,

Hi Parga,
From your case, i believe that there has to be some problem with either application threads or heap memory, which are being freed up after restart.
Kindly let me know the Min Count and Max Count of Application threads, also the heap memory and your physical Memory(RAM).
Do you have any backend systems connected?
TFG - Venkatesh

The start page of SAP web AS Java is not starting

hi,
i recently installed SAP Solution Manager 4.0 (ABAP+Java) and i cannot access the system information using a browser. my instance number is 02, my server name in sun-test and the ip address is 192.167.1.219 using http://192.167.1.219:50200 or http://sun-test:50200 i cannot access the java stack.
what configuration could i have overlooked, are there any parameters that need to be specified after the installation?

Hi,
this is the information that i'm getting in SMICM
Application Server State
TTP Application Server Handler
BAP Server operational        = TRUE
2EE Server configured         = TRUE
2EE HTTP port                 = 50200
2EE HTTPS port                = 50201
2EE Server operational        = TRUE
efault root access handler    = ABAP
RL Prefix Table loaded        = FALSE

SAP Web AS Java HTTP 404 - Not found

How can i resolve the following error?
Service cannot be reached
What has happened?
URL http://sun-test:8002/sap/monitoring/SystemInfo call was terminated because the corresponding service is not available.
Note
     The termination occurred in system SOL with error code 404 and for the reason Not found.
     The selected virtual host was 0 .
What can I do?
     Please select a valid URL.
     If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:sun-test_SOL_02-v:0-s:404-r:Notfound
HTTP 404 - Not found
Your SAP Internet Communication Framework Team

Hello Trevor,
I guess you are hosting two SAP instances on the same server.That is why you are using port 8002.Try using port 50200 for this purpose.
Normally the format is http://<hostname>.5<syso>00/sap/monitoring/SystemInfo.
make sure you have entry for sun-test in the host file as well.
Please reward points for useful info.
Regards.
Ruchit.

SAP Web AS Java 6.40 installation - FSL-06002 Error 19

hi,
we are trying to install SAP WAS 640
we downloaded the file SAPinst_SP_WAS640.exe from SAP's site.
At an early stage of the installation we get the error :
ERROR 2004-08-24 14:53:47
FSL-06002 Error 19 (The media is write protected.
) in execution of a 'GetTempFileName' function, line (205), with parameter (W:/).
what is the problem ?
why does the installation refer to w:/ ?
i did not choose the w:/ drive !
This error happens very early, right after i click the "i agree" button of the license screen.
Note - i don't know if this causes the problem, but Rational Clear Case is installed on my w:/ drive
thanks
Assaf

try to unmap the drives and install it. I have seen the installer trying to get write permissions on all the mapped drives

Web Intelligence Java Applet not working in new Chrome versions (42+)

Hi all,
It used to work until recently. Now I encounter the following error when using the Webi Java Applet in Chrome:
I read about Google quitting some specific Java support. Is anyone experiencing the same issue? What is a recommended workaround/solution except not updating Google Chrome or switching the browser?
Regards,
Peter
The BO platform version is 4.1, Java version is 7 update 67

Please check SAP Note 2156305.
You can re-enable NPAPI with the following URL: chrome://flags/#enable-npapi and then click on "Enable" for the NPAPI plugin.

Web AS Java 6.40 sp11

Hi All, any help you can give would be greatly appreciated, or indeed point me to the right place if this is not the correct forum, Thanks!
I was installing sp11 from sp0 on an XI 6.40 system, following the sp11 install pdf documentation. I patched the kernel, imported the SAP BASIS 6.40 sp, changed relevant configuration (including updating the jdk from 1.4.2_05 to 1.4.2_07) but when I got to the section on SAP Web AS Java 6.40 support package I ran into an issue. I downloaded the relevent patches and unpacked with SAPCAR, ran SAPInst from the unpacked folders and all was working until it reached the phase "Deploy File System" directly following the phase "SDM Installation/Upgrade". I got an error dialog (Retry/View Log/Stop/Reset) and the log showed the following error:
ERROR 2005-04-04 14:34:51
MUT-02041 SDM call of j2eeenginestartstop mode=manual ends with returncode 16
I also get this error if I run the above call on the command line, together with a java stack, which also appears in the logs:
WARNING 2005-04-04 14:34:51
Execution of the command "C:\j2sdk1.4.2/bin/java.exe '-Xmx256M' '-Djava.ext.dirs=C:\usr\sap/XI1/DVEBMGS00/SDM/program/lib;C:\j2sdk1.4.2/jre/lib/ext' '-jar' 'C:\usr\sap/XI1/DVEBMGS00/SDM/program/bin/SDM.jar' 'j2eeenginestartstop' 'mode=manual' 'sdmhome=C:\usr\sap/XI1/DVEBMGS00/SDM/program' 'logfile=C:\Program Files\sapinst_instdir\PATCH\MSS/callSdmViaSapinst.log'" finished with return code 16. Output:
Starting SDM - Software Deployment Manager...
tc/SL/SDM/SDM/sap.com/SAP AG/6.4011.00.0000.20050207154237.0000
Initializing Network Manager (50017)
Checking if another SDM is running on port 50018
Caught Exception: java.lang.NullPointerException
java.lang.NullPointerException
     at com.sap.sl.util.cvers.impl.TableDescriptionFactory.getTableDescription(TableDescriptionFactory.java:73)
     at com.sap.sl.util.cvers.impl.CVersManager.loadTable(CVersManager.java:47)
     at com.sap.sl.util.cvers.impl.CVersManager.loadDBStructure(CVersManager.java:62)
     at com.sap.sl.util.cvers.impl.CVersManager.openDBSource(CVersManager.java:87)
     at com.sap.sl.util.cvers.impl.CVersManager.<init>(CVersManager.java:114)
     at com.sap.sl.util.cvers.impl.CVersFactory.createCVersManager(CVersFactory.java:46)
     at com.sap.sdm.app.cvers.wrapper.CVersFactory.createCVersManager(CVersFactory.java:69)
     at com.sap.sdm.app.cvers.deplobs.impl.CVersProxyImpl.updateCVers(CVersProxyImpl.java:133)
     at com.sap.sdm.persistency.RepositoryPersistor.persistRepository(RepositoryPersistor.java:54)
     at com.sap.sdm.control.command.decorator.RepositoryPersistor.execute(RepositoryPersistor.java:39)
     at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:53)
     at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)
     at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)
     at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)
     at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)
     at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)
     at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)
     at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)
     at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:54)
     at com.sap.sdm.control.command.decorator.SyntaxChecker.execute(SyntaxChecker.java:37)
     at com.sap.sdm.control.command.Command.exec(Command.java:42)
     at SDM.main(SDM.java:21)
Severe (internal) error. Return code: 16
I can't find anything in the sap notes about this, or in the other documentation, and am really stuck. I have tried checking if there is another sdm server running and there is not (if I start one I get a different error saying that there is already an SDM server running)
If I really can't work out what to do I will have to go back to the last system backup I did because at the moment the J2EE engine won't even start and I can't get the SAPInst to go forward or backward to where I was before I ran it (e.g under j2ee/os_libs I have a folder "moved_by_sapinst" which remains even when I do a "reset" after the error and the Jlaunch exe has been moved there, and I think this may be why my j2ee server is not starting??)
Many thanks for any help you can give,
Cheers,
Chris

Hi all,
Does anyone else have any suggections as to what I might try? I am still having this issue and have tried everything I can think of, I will keep trying but am running out of ideas.. The fact that the stack trace mentions CVERS table leads me to believe that the Web AS Java sp11 install is maybe looking for a component in my system that is not there, the only 4 things listed in my CVERS table are:
PI_BASIS 2004_1_640 0008 X
SAP_ABA   640        0011 S
SAP_BASIS 640        0011 S
SAP_BW    350        0011 W
Could I be missing something vital or is this a red herring?!
Thanks for any help you can provide,
Chris

Error in installing SAP Web AS ABAP (Unicode Version)

I have SAP Web AS Java in my machine already, but in order to install XI, I need to install also ABAP unicode. During the installation, I got the following error. I can't interpret it what it is or what I have done wrong. Can anybody give me a hand?
Here is the error message:
ERROR 2005-12-16 01:51:17
MOS-01082 File system node E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE with type NODE does not exist.
ERROR 2005-12-16 01:51:17
MOS-01105 Processing of one or more file system node operations of table   Content of table: t_SAPComponent_Filesystem_Action_SHARED with condition WHERE WapsSystemName='J2E' AND WapsInstanceName='DVEBMGS00' AND WapsInstanceHost='vm-w3k-pck' AND OpMode NOT IN('CHECKFREESPACE', 'CHECKIF') Row[0]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/prfclog" FollowLinks="TRUE" NodeName="C:\usr\sap/prfclog" NodeType="DIRECTORY" OpMode="CREATE"   Row[1]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E" NodeType="DIRECTORY" OpMode="CREATE"   Row[2]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00" NodeType="DIRECTORY" OpMode="CREATE"   Row[3]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/data" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/data" NodeType="DIRECTORY" OpMode="CREATE"   Row[4]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/data/cache" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/data/cache" NodeType="DIRECTORY" OpMode="CREATE"   Row[5]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/exe" NodeType="DIRECTORY" OpMode="CREATE"   Row[6]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/log" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/log" NodeType="DIRECTORY" OpMode="CREATE"   Row[7]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/sec" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/sec" NodeType="DIRECTORY" OpMode="CREATE"   Row[8]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/work" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/work" NodeType="DIRECTORY" OpMode="CREATE"   Row[9]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS" NodeType="DIRECTORY" OpMode="CREATE"   Row[10]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe" NodeType="DIRECTORY" OpMode="CREATE"   Row[11]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe/opt" NodeType="DIRECTORY" OpMode="CREATE"   Row[12]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe/dbg" NodeType="DIRECTORY" OpMode="CREATE"   Row[13]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe/run" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe/run" NodeType="DIRECTORY" OpMode="CREATE"   Row[14]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/gen" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/gen" NodeType="DIRECTORY" OpMode="CREATE"   Row[15]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/gen/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/gen/dbg" NodeType="DIRECTORY" OpMode="CREATE"   Row[16]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/gen/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/gen/opt" NodeType="DIRECTORY" OpMode="CREATE"   Row[17]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/global" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/global" NodeType="DIRECTORY" OpMode="CREATE"   Row[18]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/profile" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/profile" NodeType="DIRECTORY" OpMode="CREATE"   Row[19]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/src" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/src" NodeType="DIRECTORY" OpMode="CREATE"   Row[20]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap/tmp" NodeType="DIRECTORY" OpMode="CREATE"   Row[21]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans" FollowLinks="TRUE" NodeName="C:\usr\sap\trans" NodeType="DIRECTORY" OpMode="CREATE"   Row[22]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/tmp" NodeType="DIRECTORY" OpMode="CREATE"   Row[23]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS" NodeType="DIRECTORY" OpMode="CREATE"   Row[24]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/in" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/in" NodeType="DIRECTORY" OpMode="CREATE"   Row[25]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/out" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/out" NodeType="DIRECTORY" OpMode="CREATE"   Row[26]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/log" NodeType="DIRECTORY" OpMode="CREATE"   Row[27]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/bin" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/bin" NodeType="DIRECTORY" OpMode="CREATE"   Row[28]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/buffer" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/buffer" NodeType="DIRECTORY" OpMode="CREATE"   Row[29]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/cofiles" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/cofiles" NodeType="DIRECTORY" OpMode="CREATE"   Row[30]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/data" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/data" NodeType="DIRECTORY" OpMode="CREATE"   Row[31]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/etc" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/etc" NodeType="DIRECTORY" OpMode="CREATE"   Row[32]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/log" NodeType="DIRECTORY" OpMode="CREATE"   Row[33]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/sapnames" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/sapnames" NodeType="DIRECTORY" OpMode="CREATE"   Row[34]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="WAPS_COPY_E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE_C:\usr\sap\J2E\SYS\exe\run\..\UNINSTSAP.EXE" NodeName="E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE" NodeTarget="C:\usr\sap\J2E\SYS\exe\run\..\UNINSTSAP.EXE" OpMode="COPY" failed.

Still have the same error message.
When I look at the log, it fails at some step that tried to copy UNINSAP.EXE to my local drive. It is looking at directory IM01_NT_I386/SAPINST/NT/I386/UNISAP.EXE. This is a path in the "Installation Master" DVD. However, during the intsallation, the installation wizard asked me to insert the RDBMS DVD. I don't know exactly what it means. Anyway, following is a stack trace. See the last line:
MOS-01105 Processing of one or more file system node operations of table
Content of table: t_SAPComponent_Filesystem_Action_SHARED with condition WHERE WapsSystemName='ABP' AND WapsInstanceName='DVEBMGS00' AND WapsInstanceHost='vm-w3k-pck' AND OpMode NOT IN('CHECKFREESPACE', 'CHECKIF')
Row[0]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/prfclog" FollowLinks="TRUE" NodeName="C:\usr\sap/prfclog" NodeType="DIRECTORY" OpMode="CREATE"
Row[1]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP" NodeType="DIRECTORY" OpMode="CREATE"
Row[2]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00" NodeType="DIRECTORY" OpMode="CREATE"
Row[3]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/data" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/data" NodeType="DIRECTORY" OpMode="CREATE"
Row[4]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/data/cache" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/data/cache" NodeType="DIRECTORY" OpMode="CREATE"
Row[5]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/exe" NodeType="DIRECTORY" OpMode="CREATE"
Row[6]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/log" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/log" NodeType="DIRECTORY" OpMode="CREATE"
Row[7]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/sec" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/sec" NodeType="DIRECTORY" OpMode="CREATE"
Row[8]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/work" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/work" NodeType="DIRECTORY" OpMode="CREATE"
Row[9]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS" NodeType="DIRECTORY" OpMode="CREATE"
Row[10]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe" NodeType="DIRECTORY" OpMode="CREATE"
Row[11]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe/opt" NodeType="DIRECTORY" OpMode="CREATE"
Row[12]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe/dbg" NodeType="DIRECTORY" OpMode="CREATE"
Row[13]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe/run" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe/run" NodeType="DIRECTORY" OpMode="CREATE"
Row[14]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/gen" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/gen" NodeType="DIRECTORY" OpMode="CREATE"
Row[15]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/gen/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/gen/dbg" NodeType="DIRECTORY" OpMode="CREATE"
Row[16]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/gen/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/gen/opt" NodeType="DIRECTORY" OpMode="CREATE"
Row[17]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/global" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/global" NodeType="DIRECTORY" OpMode="CREATE"
Row[18]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/profile" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/profile" NodeType="DIRECTORY" OpMode="CREATE"
Row[19]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/src" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/src" NodeType="DIRECTORY" OpMode="CREATE"
Row[20]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap/tmp" NodeType="DIRECTORY" OpMode="CREATE"
Row[21]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans" FollowLinks="TRUE" NodeName="C:\usr\sap\trans" NodeType="DIRECTORY" OpMode="CREATE"
Row[22]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/tmp" NodeType="DIRECTORY" OpMode="CREATE"
Row[23]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS" NodeType="DIRECTORY" OpMode="CREATE"
Row[24]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/in" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/in" NodeType="DIRECTORY" OpMode="CREATE"
Row[25]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/out" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/out" NodeType="DIRECTORY" OpMode="CREATE"
Row[26]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/log" NodeType="DIRECTORY" OpMode="CREATE"
Row[27]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/bin" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/bin" NodeType="DIRECTORY" OpMode="CREATE"
Row[28]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/buffer" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/buffer" NodeType="DIRECTORY" OpMode="CREATE"
Row[29]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/cofiles" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/cofiles" NodeType="DIRECTORY" OpMode="CREATE"
Row[30]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/data" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/data" NodeType="DIRECTORY" OpMode="CREATE"
Row[31]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/etc" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/etc" NodeType="DIRECTORY" OpMode="CREATE"
Row[32]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/log" NodeType="DIRECTORY" OpMode="CREATE"
Row[33]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/sapnames" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/sapnames" NodeType="DIRECTORY" OpMode="CREATE"
Row[34]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="WAPS_COPY_E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE_C:\usr\sap\ABP\SYS\exe\run\..\UNINSTSAP.EXE" NodeName="E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE" NodeTarget="C:\usr\sap\ABP\SYS\exe\run\..\UNINSTSAP.EXE" OpMode="COPY"
failed.

Upgrade a SAP Web AS Java 7.0 to a new SPS stack (SPS10 to SPS14)

Similar Messages

Maybe you are looking for