on 05-07-2007 2:31 PM
I am unable to reset PREPARE...it terminates with the message "Unable
to reset PREPARE".
I see that SAPup is unable to find the transdirectory!
The file being processed here is \usr\sap\put\bin\DEFAULT.TPP and it is
unable to locate the file. I too checked that this file is not available in any directory.
Could this be the problem ?
One more mistake we committed was that after the homogeneous system copy, we had not recreated the transport management system (which was inconsistent). Although we have now updated the STMS, could it be that this is still not updated in some registries or dlls ?
Of course, these are just my assumptions.
Can anyone help in troubleshooting this problem ?
<b>EXECUR.LOG</b>
ERROR IN PREP_RES, program "tp" returned error code 208, see log file F:\usr\sap\put\tmp\PREP_RES.ECO for details.
ERROR IN PREP_RES, program "tp" returned error code 208, see log file F:\usr\sap\put\tmp\PREP_RES.ECO for details.
-
<b>PREP_RES.ECO</b>
SAPup> Starting subprocess tp with id 5652 at 20070507125617
EXECUTING F:\usr\sap\SOL\SYS\exe\run\tp pf=F:\usr\sap\put\bin\DEFAULT.TPP execdbscript SOL -x UVERSRES.TQL
This is F:\usr\sap\SOL\SYS\exe\run\tp version 320.56.80 (release 620)
E-F:\usr\sap\put\bin\DEFAULT.TPP could not be opened.
EXIT
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
error in transportprofil (param missing, unknown,...)
Error in F:\usr\sap\put\bin\DEFAULT.TPP: transdir not set.
Process with ID 5108 terminated with status 208
SAPup> Starting subprocess tp with id 5652 at 20070507125622
EXECUTING F:\usr\sap\SOL\SYS\exe\run\tp pf=F:\usr\sap\put\bin\DEFAULT.TPP execdbscript SOL -x RESETAVERS.TQL
This is F:\usr\sap\SOL\SYS\exe\run\tp version 320.56.80 (release 620)
E-F:\usr\sap\put\bin\DEFAULT.TPP could not be opened.
EXIT
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
error in transportprofil (param missing, unknown,...)
Error in F:\usr\sap\put\bin\DEFAULT.TPP: transdir not set.
Process with ID 5352 terminated with status 208
-
<b>dev_SAPup</b>
SAPup aborted in phase EXTRACTKRN_PRE with exception at Mon May 07 11:09:10 2007
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
-
Application exception occurred:
Exception : c0000005 (Access Violation)
App : SAPup.exe (pid=4936)
When : 5/7/2007 11:9:10.876
Threads : 1
-
Computer Name : RANSOLMAN4
User Name : soladm
-
Number of Processors: 8
Processor Type: x86 Family 15 Model 2 Stepping 2
Windows Version : 5.2 Current Build: 3790
-
State Dump for Thread Id 112c
eax=01325bea ebx=00af6240 ecx=0f307221 edx=00000001 esi=00000051 edi=01325bea
eip=7c34175b esp=0131f758 ebp=01325c04 iopl=0 nv up ei pl nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010202
function : mbscpy
7c34174a 57 push edi
7c34174b 8b7c2408 mov edi,[esp+0x8] ss:0263d8ab=????????
7c34174f 8b4c240c mov ecx,[esp+0xc] ss:0263d8ab=????????
7c341753 f7c103000000 test ecx,0x3
7c341759 741a jz mbscpy+0x2b (7c341775)
FAULT-> 7c34175b 8a11 mov dl,[ecx] ds:0f307221=??
7c34175d 83c101 add ecx,0x1
7c341760 84d2 test dl,dl
7c341762 0f84b5f9ffff je 7c34111d
7c341768 8817 mov [edi],dl ds:01325bea=50
7c34176a 83c701 add edi,0x1
7c34176d f7c103000000 test ecx,0x3
7c341773 75e6 jnz strlen+0x86 (7c34185b)
7c341775 bafffefe7e mov edx,0x7efefeff
7c34177a 8b01 mov eax,[ecx] ds:0f307221=????????
7c34177c 03d0 add edx,eax
7c34177e 83f0ff xor eax,0xff
--> Stack Back Trace <--
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
01325c04 0049c2dd 00af6240 01325c24 00000000 00000000 MSVCR71!mbscpy
0132c000 00000000 00af6300 00000018 00af6ae0 018ada90 SAPup!<nosymbols>
-
SAPup aborted in phase EXTRACTKRN_PRE with exception at Mon May 07 11:09:51 2007
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
-
Application exception occurred:
Exception : c0000005 (Access Violation)
App : SAPup.exe (pid=884)
When : 5/7/2007 11:9:51.767
Threads : 1
-
Computer Name : RANSOLMAN4
User Name : soladm
-
Number of Processors: 8
Processor Type: x86 Family 15 Model 2 Stepping 2
Windows Version : 5.2 Current Build: 3790
-
State Dump for Thread Id 17d8
eax=0132602a ebx=00af6240 ecx=4e4b3180 edx=7efefeff esi=00000051 edi=0132602a
eip=7c34177a esp=0131fb98 ebp=01326044 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
function : mbscpy
7c341759 741a jz mbscpy+0x2b (7c341775)
7c34175b 8a11 mov dl,[ecx] ds:4e4b3180=??
7c34175d 83c101 add ecx,0x1
7c341760 84d2 test dl,dl
7c341762 0f84b5f9ffff je 7c34111d
7c341768 8817 mov [edi],dl ds:0132602a=4e
7c34176a 83c701 add edi,0x1
7c34176d f7c103000000 test ecx,0x3
7c341773 75e6 jnz strlen+0x86 (7c34185b)
7c341775 bafffefe7e mov edx,0x7efefeff
FAULT-> 7c34177a 8b01 mov eax,[ecx] ds:4e4b3180=????????
7c34177c 03d0 add edx,eax
7c34177e 83f0ff xor eax,0xff
7c341781 33c2 xor eax,edx
7c341783 8b11 mov edx,[ecx] ds:4e4b3180=????????
7c341785 83c104 add ecx,0x4
7c341788 a900010181 test eax,0x81010100
7c34178d 7507 jnz mbscpy+0x4c (7c341796)
7c34178f 8917 mov [edi],edx ds:0132602a=454c444e
7c341791 83c704 add edi,0x4
7c341794 ebdf jmp strlen+0xa0 (7c341875)
7c341796 84d2 test dl,dl
--> Stack Back Trace <--
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
01326044 53574f44 3638585f 5f34365f 47505541 0132ca00 MSVCR71!mbscpy
4e49575f 00000000 00000000 00000000 00000000 00000000 <nosymbols>
-
<b>Start_dvebmgs00_ransolman4.pfl</b>
SAPSYSTEMNAME = SOL
INSTANCE_NAME = DVEBMGS00
SAPSYSTEM = 00
SAPGLOBALHOST = RANSOLMAN4
_DB = strdbs.cmd
Start_Program_02 = immediate $(DIR_EXECUTABLE)\$(_DB) SOL
MS = msgserver.exe
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\SOL_DVEBMGS00_RANSOLMAN4
_DW = disp+work.exe
Start_Program_04 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\SOL_DVEBMGS00_RANSOLMAN4
-
<b>default.pfl</b>
SAPSYSTEMNAME = SOL
rdisp/mshost = RANSOLMAN4
rdisp/sna_gateway = RANSOLMAN4
rdisp/sna_gw_service = sapgw00
rslg/collect_daemon/listen_port = 37
rslg/collect_daemon/talk_port = 13
rdisp/bufrefmode = sendoff,exeauto
ms/http_port = 8100
SAPDBHOST = RANSOLMAN4
dbms/type = mss
dbs/mss/server = RANSOLMAN4
dbs/mss/dbname = SOL
dbs/mss/schema = sol
-
<b>SOL_DVEBMGS00_RANSOLMAN4.pfl</b>
SAPSYSTEMNAME = SOL
INSTANCE_NAME = DVEBMGS00
SAPSYSTEM = 00
rdisp/wp_no_dia = 6
rdisp/wp_no_btc = 2
rdisp/wp_no_vb = 5
rdisp/wp_no_vb2 = 2
rdisp/wp_no_enq = 1
rdisp/wp_no_spo = 1
SAPGLOBALHOST = RANSOLMAN4
PHYS_MEMSIZE = 2265
DIR_TRANS = F:\usr\sap\trans
icm/server_port_0 = PROT=HTTP,PORT=8000,EXTBIND=1
Try deleting the contents of PUT directory (make a
backup copy just in case if you need it) and then run
PREPARE.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Sairam,
The problem has been solved. The error was in the naming of the mount directory path.
As per the upgrade guide - "The maximum length of the mount directory path is 94 characters. It may not contain any blanks or special characters."
But I found that even the above is not true entirely. Even after making the changes and ensuring the mount path to be less than 94 chars, it had problems recognising folder names.
So I made the paths really short....<i>\SM\master</i> etc.
Now it works. And yes, I have deleted the contents of the put directory.
Thanks for replying though.
Regards,
Prasad
User | Count |
---|---|
96 | |
11 | |
11 | |
10 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.