Upgrading to SolMan 4.0 - error in PARMVNT_XCNV phase

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETP345 10:01:27: Retcode 1: SQL-error "1452-ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys
2EETP345 found" in DDL statement for "IATNODE01 "
2EETP334 10:01:27: error in DDL, nametab for "IATNODE01" not activated
1 ETP111 exit code : "8"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Any suggestions on how to fix this?

Hi there,
As there are limited information provided, please find below some general SAP Notes that might be useful to you:
11369 - ORA-1452 during import after export from other system
617679 - Error due to incomplete column definitions
992956 - Duplicate keys in table UMGPMDIT after Unicode conversion
541538 - FAQ: Reorganizations
Alternatively, you can open a customer message to SAP Support for a more complete analysis on your system.
BR,
Jayne.

Similar Messages

Error in XPRA_EXECUTION phase while upgrading patch in solman 7.0.

Hi all,
I was upgrading solman system( 7.0 ) from patch level 10 to patch level 13 , while upgrading it throwed error in XPRA_EXECUTION phase. Error is in SAPK-40003INCPRXRPM and SAPK-40004INCPRXRPM.
Error log is as given below :
Post-import method SWO_OBJTYPE_AFTER_IMPORT started for SOBJ L, date and time: 20090415070141
Object type 'BUS2178' generated successfully
Object type 'BUS2177' generated successfully
Object type 'BUS2176' generated successfully
Object type 'BUS2175' could not be generated
The type 'DPR_SCHEDULING' is unknown.
Object type 'BUS2174' could not be generated
The type 'DPR_SCHEDULING' is unknown.
Object type 'BUS2173' could not be generated
The type 'DPR_SCHEDULING' is unknown.
Object type 'BUS2172' could not be generated
Please help me out as i am stuck.

HI,
Did u check is there any dependencies of Solman support packages with other support pakckages.
Object type 'BUS2174' could not be generated it seems there is a issues with dependencies only.
Please check the stack guide once then u will come to know all the dependencies.
-Srini

After Upgrading the SOLMAN to SPS12 the SAP EWA generation to word fail!

Hello,

after Upgrading the SOLMAN system to SPS12 the SAP Early WatchAlert generation to word fail. We use MS Word 2002 SP3!
EarlyWatch Alert Report, EarlyWatch Alert Report with Graphics, all Service Level Reportings -
No report can generate to a word report!
the following Error message appears:

Information:
Document generation failed

After confirming the information poopup, this Error message appears:

Error: Exception occurred (program: , include: , line: 0)., Program CL_DSMOP_HTML_SERVICE_OPEN====CP, Include CL_DSMOP_HTML_SERVICE_OPEN====CM00N, Row 103 
With SPS10 all generations were successfully!
Has anybody an idea?

Thanks a lot!

Regards,
matthias isenburg

Hello,
This is a known problem in the meantime!!!
We use MS Word 2002 SP3! This Version ist too old! The Templates which the Solman want to use are now in MS Word 2003 (minimum)!
The solution is to upgrade MS Word!!!
Best Regards,
Matthias Isenburg

IPod touch is not recognized by Windows (with a connect to iTune screen) after OS 5.1.1 upgrade and received an 1602 error

My iPod touch is not recognized by Windows 7 and will not appear on My Computer as a storage device after OS 5.1.1 upgrade and received an 1602 error. My iPod is now having a connect to iTune screen.

Error 1600, 1601, 1602: Try the following steps to resolve this error:
Ensure proper USB isolation troubleshooting has been performed, and test with a known-good cable.
Follow the steps listed for Error 1604.
This error may be resolved by disabling, deactivating, or uninstalling third-party security, antivirus, and firewall software. See steps in this article for details on troubleshooting security software.
http://support.apple.com/kb/TS3694#error1602

Support Pack upgrade error in Import Phase

Hello,
Currently I am upgrading SCM system with Support pack level 12 to 20 . When i am applying Basis 12 to 20. I got an error in Import_Proper phase.
Could you please help me on this? I tried and still searching solution for this..But no luck...
Os is : AIX and
Log File: /usr/sap/trans/log/SAPIB70013.xxx
Main import
Transport request : SAPKB70013
System : xxxx
tp path : tp
Version and release: 372.04.71 700
child process 934006 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_OBJECT_COLLECTION==========CT
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1212554 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_WDR_APPLICATION_WINDOW=====CT
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1171520 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_WDY_MD_EVENT_SOURCE========CI
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1331412 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_LOAD
tabname: ECSCR_DATA
len (char): 106
key: EC_TEST_DATA 00000000P10 IECATTDEFAULT
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
insert / update sequence failed due to an error in DBI.
maybe there's a concurrent process which inserted this table entry at the same time.
insert / update sequence failed due to an error in DBI.
maybe there's a concurrent process which inserted this table entry at the same time.
child process 1310922 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_END
tabname: WDY_APP_PROPERTY
len (char): 64
key: DEMO_UIEL_DROPDOWN_BY_IDX DEMO_VIEW
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
import portion 018446 - 999999 not imported because the child processes died for unknown reason
child process 1310924 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_WDY_MD_OUTGOING_EVENT======CT
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1286192 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_LOAD
tabname: ECSCR_DATA
len (char): 106
key: EC_TEST_DATA 00000000P10 IECATTDEFAULT
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
import portion 009158 - 018411 not imported because the child processes died for unknown reason
import portion 018412 - 018527 not imported because the child processes died for unknown reason
import portion 018528 - 999999 not imported because the child processes died for unknown reason
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_LOAD
tabname: ECSCR_DATA
len (char): 106
key: EC_TEST_DATA 00000000P10 IECATTDEFAULT
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
Main import
End date and time : 20100909034914
Ended with return code: ===> 12 <===
 | ######################################
Thanks and Regards,
Sankar
SAP BASIS Consultant

Hi,
Thanks for you reply. I restarted import but no luck still. I activated some object also not working. when i call SPAM it is not going to the SPAM pager. Showing dump...
Runtime Errors CALL_FUNCTION_NOT_FOUND
Except. CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time 10.09.2010 09:41:37
Short text
 Function module "POSS_UIREQ_OPT_SUBMIT" not found.
What happened?
 The function module "POSS_UIREQ_OPT_SUBMIT" is called,
 but cannot be found in the library.
 Error in the ABAP Application Program
 The current ABAP program "SAPLSTXC" had to be terminated because it has
 come across a statement that unfortunately cannot be executed.
Error analysis
 An exception occurred that is explained in detail below.
 The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
 not caught in
 procedure "OPEN_FORM" "(FUNCTION)", nor was it propagated by a RAISING clause.
 Since the caller of the procedure could not have anticipated that the
 exception would occur, the current program is terminated.
 The reason for the exception is:
 The program "SAPLSTXC" contains the CALL FUNCTION statement.
 The name of the function module to be called is "POSS_UIREQ_OPT_SUBMIT".
 No function module exists with the name "POSS_UIREQ_OPT_SUBMIT".
 All function modules are listed in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Pay particular attenti
 upper/lower case and underscores ("_").
 or
b) Transport error
c) In the case of an enqueue/dequeue module,
 the lock object may not have been activated
 (ABAP/4 Dictionary).
When i tried to check function module it is not there..
Could you please help on this?
Regards,
Sankar Basis Consultant

PI 7.1 upgrade error in GETSYNC_PROFILES_CHANGED phase

Hello
Currently I am upgrading an XI 7.0 system to PI 7.1. The downtime phases have just started and I've hit an error in the phase 'GETSYNC_PROFILES_CHANGED'; the error is 'Not enough space for string replacement'. Based on the phase name, and the previous phases, it looks as if the error is something to do with the profiles. The relevant upgrade logs have no useful info in them except for the string space message.
I have done the usual SDN, SAP Marketplace and Google searches but could not find an answer to my problem. I have also opened a high priority call with SAP but they have not come up with an answer yet. Does anybody have any useful advice?
The system being upgraded is running on Windows 2003 Server R2 64bit, has an Oracle 10.2.0.4 DB, and the source system was XI/PI 7.0 SP15.
Thanks.

Hello Rohit
Freespace is more than sufficient:
C:\ = 5.2GB (O/S)
D:\ = 18.9GB (Oracle & SAP)
E:\ = 8.53GB (Oracle)
Andrew
Edited by: Andrew Turvey on May 28, 2009 3:48 PM

SRM 4.0 upgrade to SRM 7.0 - Error in Phase PARDIST_SHD

Hello,
I am upgrading the SAP SRM 4.0 / MSSQL 2005 / Windows 2003 (64 bit) to SRM 7.0 but I am getting this error in the phase PARDIST_SHD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DISTRIBUTION ERRORS and RETURN CODE in DS100310.SD1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EEDA300 No active nametab exists for "CDBC_LANG_TABLES"
Long text:
    Cause
      Thee is no active nametab in the system, although an
      active ABAP/4 Dictionary object was expected.
    System Response
      None
    What to do
      Reactivate the ABAP/4 Dictionary object.
2EEDA432 Termination due to inconsistencies
2EEDA471    Result   "CDBC_LANG_TABLES":    Action: "DNA"      Mode flag: "R"    Return code: "9"
2EEDA300 No active nametab exists for "CRMC_ADJCONT"
Long text: see above
2EEDA432 Termination due to inconsistencies
2EEDA471    Result   "CRMC_ADJCONT":    Action: "DNA"      Mode flag: "R"    Return code: "9"
2EEDA300 No active nametab exists for "CRMC_HH_SRV_SYNC"
Long text: see above
2EEDA432 Termination due to inconsistencies
2EEDA471    Result   "CRMC_HH_SRV_SYNC":    Action: "DNA"      Mode flag: "R"    Return code: "9"
2EEDA300 No active nametab exists for "CRMC_PROCESSFLTT"
Long text: see above
2EEDA432 Termination due to inconsistencies
2EEDA471    Result   "CRMC_PROCESSFLTT":    Action: "DNA"      Mode flag: "R"    Return code: "9"
2EEDA300 No active nametab exists for "CRMC_PROCESS_FLT"
Long text: see above
2EEDA432 Termination due to inconsistencies
2EEDA471    Result   "CRMC_PROCESS_FLT":    Action: "DNA"      Mode flag: "R"    Return code: "9"
2EEDA300 No active nametab exists for "IPCE_MON_NODES"
Long text: see above
2EEDA432 Termination due to inconsistencies
2EEDA471    Result   "IPCE_MON_NODES":    Action: "DNA"      Mode flag: "R"    Return code: "9"
What will I do now? How will resolve this issue? Please help me ASAP
Thanks
Gautam

Go to SE11, Menu->Utilities->Database Object->Check
            Menu->Utilities->Runtime Object->Check
If there are inconsistency, please follow note 211492 to adjust the inc
onsistency in original instance . But if these tables are obsolete,
for example doesn't exist in the system any more, you could also choose the option to 'Ignore' the error and
continue with the upgrade. But this is a BC-UPG issue.
Regards
Lauren

Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 537, state 3, severity 16

Hello,
I've encountered issue during installation of SP1 to SQL Server 2012. After upgrade I'm getting this error in Event Log:
Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 537, state 3, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline.
If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script
upgrade steps run to completion.
Can someone point me direction how I can fix it? This is a production server and currently only way to make it working is to use T902 flag in SQL Server startup params. I've found some suggestions to check Data path if it exists but it does so this is not
the issue here. Any ideas?
I've found also here
http://www.sqlservercentral.com/Forums/Topic1377073-1550-1.aspx#bm1378279
suggestions for similar issue with SQL Server 2008 which that I should do:
Via ssms:
From msdb:
Delete:
dc_admin role
Dc_operator role
Dc_proxy role
UlitityCMRReader role
UtilityIMRReader role
UtilityIMRWriter role
but for not I didn't tried it yet. This is standalone SQL Server instance.
Any help really appreciated.
Regards

Script returns the same error.
System databases:
1   1   760   -1   10   1048578   0   1   master       C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
2   0   12768   -1   10   1048642   0   1   mastlog       C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
1   1   1024   -1   10   1048578   0   2   tempdev       C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\tempdb.mdf
2   0   64   -1   10   1048642   0   2   templog       C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\templog.ldf
1   1   288   -1   128   2   0   3   modeldev   C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\model.mdf
2   0   4464   -1   10   1048642   0   3   modellog   C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\modellog.ldf
1   1   28936   -1   10   1048578   0   4   MSDBData   C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\MSDBData.mdf
2   0   3352   268435456   10   1048642   0   4   MSDBLog   C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\MSDBLog.ldf
are all in place where path shows.
Before sending my message I've searched update script for "FROM master.sys.master_files" and I found script which you are showing me. I've made some digging and when I runned:
       SELECT physical_name
       FROM master.sys.master_files
       WHERE (name = N'master')
it returned also path to one my customers database name which has filename set correctly but it's Logical DB name is master and mastlog. I'm running shared hosting company and I allow my customers to restore their DBs from .bak files but I have no idea why
this customers logical name is set to master and mastlog. Probably when I change this names update script will work as it should. On the other hand in my opinion there should be some kind of fail safe mechanism for situations like this one.
EDIT: After changing logical name for DB and log for mentioned DB your script runned fine so probably now when I remove T902 flag and restart my SQL Server update will run correctly. Big thanks for resolving this issue.

Error in ACTIVATE_CURRENT_USAGES phase of portal upgrade (NW04 to NW04s)

hello gurus,
i am upgrading Netweaver 04 to netweaver 04s (Enterprise Portal)
oracle upgrade from 9.2.0.7 to 10.2.0.1 successfully
but i am getting error in 78 phase out 100 in java upgrade program management
ACTIVATE_CURRENT_USAGES
i am unable to track the cause.......
log file is shown below
kindly help......
its urgent
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[D:\usr\sap\jupgrade\log\ACTIVATE_CURRENT_USAGES_ACU_07.LOG]/>
<!PATTERN[ACTIVATE_CURRENT_USAGES_ACU_07.LOG]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
#1.5#C000AC1908C2000000000029014A8CD1000432D6B5DD7008#1181797662421#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:713)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:713)#Java###Phase has been started.#1#UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES#
#1.5#C000AC1908C200000000002A014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:714)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:714)#Java###Phase type is .#1#com.sap.sdt.ucp.phases.PhaseTypeExecuteTask#
#1.5#C000AC1908C200000000002B014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#Java### Parameter =#2#inputFile#ExecuteTasks.xml#
#1.5#C000AC1908C200000000002C014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#Java### Parameter =#2#taskName#ACTIVATE_CURRENT_USAGES#
#1.5#C000AC1908C200000000002D014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.checkParameters(PhaseTypeExecuteTask.java:191)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.checkParameters(PhaseTypeExecuteTask.java:191)#Java###Phase parameters have been checked. All required phase parameters have been set.#1#2#
#1.5#C000AC1908C200000000002E014A8CD1000432D6B5F009C0#1181797663640#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#Java###Configuration has been built from input file .#1#D:/usr/sap/jupgrade/config/ExecuteTasks.xml#
#1.5#C000AC1908C200000000002F014A8CD1000432D6B5F13A70#1181797663718#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#Java###Configuration has been built from input file .#1#D:/usr/sap/jupgrade/config/ExecuteTasks_WIN.xml#
#1.5#C000AC1908C2000000000030014A8CD1000432D6B5F13A70#1181797663718#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.cfg.ConfigurationBuilder.buildGlobalConfiguration(ConfigurationBuilder.java:251)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.cfg.ConfigurationBuilder.buildGlobalConfiguration(ConfigurationBuilder.java:251)#Java###Global configuration has been built from input file .#1#D:/usr/sap/jupgrade/config/ExecuteTasks.xml#
#1.5#C000AC1908C2000000000031014A8CD1000432D6B5F13A70#1181797663718#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#Java###Java process ID , name has been started.#2#2#com.sap.engine.offline.OfflineToolStart#
#1.5#C000AC1908C2000000000032014A8CD1000432D6B5F178F0#1181797663734#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#Java###Command line: #2# #C:
j2sdk1.4.2_09
jre
bin
java.exe -cp d:/usr/sap/W60/SYS/global/sltools/sharedlib/launcher.jar;d:/usr/sap/W60/SYS/global/sltools/sharedlib; com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain d:/usr/sap/W60/SYS/global/sltools/sharedlib;D:/usr/sap/W60/SYS/global/security/lib/tools;D:/usr/sap/w60/jc00/exe/classes12.jar -activated -sid=W60 -dsn=jdbc/pool/W60 -ssprops=D:/usr/sap/W60/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/W60/SYS/global/security/data/SecStore.key -log=D:
usr
sap
jupgrade
log/ACTIVATE_USAGE_AS.LOG -prod_name=NetWeaver -usage_name=AS -usage_vendor=sap.com -action=true#
#1.5#C000AC1908C2000000000033014A8CD1000432D6B5F178F0#1181797663734#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#Java###Standard out: #2# #D:
usr
sap
jupgrade
log
ACTIVATE_USAGE_AS_ACU_01.OUT#
#1.5#C000AC1908C2000000000034014A8CD1000432D6B5F178F0#1181797663734#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#2#
#1.5#C000AC1908C2000000000035014A8CD1000432D6B5F1B770#1181797663750#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#2#java.exe#
#1.5#C000AC1908C2000000000036014A8CD1000432D6B6B9BE78#1181797676859#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#2#java.exe#64#
#1.5#C000AC1908C2000000000037014A8CD1000432D6B6B9BE78#1181797676859#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:735)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:735)#Java###Exception has occurred during the execution of the phase.##
#1.5#C000AC1908C2000000000038014A8CD1000432D6B6B9FCF8#1181797676875#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.execute.AbstractExtProcessOperation.generateResultProcessingException(AbstractExtProcessOperation.java:579)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.execute.AbstractExtProcessOperation.generateResultProcessingException(AbstractExtProcessOperation.java:579)#Java###Could not activate usage AS. Could not execute 'C:
j2sdk1.4.2_09
jre
bin
java.exe -cp d:/usr/sap/W60/SYS/global/sltools/sharedlib/launcher.jar;d:/usr/sap/W60/SYS/global/sltools/sharedlib; com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain d:/usr/sap/W60/SYS/global/sltools/sharedlib;D:/usr/sap/W60/SYS/global/security/lib/tools;D:/usr/sap/w60/jc00/exe/classes12.jar -activated -sid=W60 -dsn=jdbc/pool/W60 -ssprops=D:/usr/sap/W60/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/W60/SYS/global/security/data/SecStore.key -log=D:
usr
sap
jupgrade
log/ACTIVATE_USAGE_AS.LOG -prod_name=NetWeaver -usage_name=AS -usage_vendor=sap.com -action=true', return code '64'. You can check the file(s) 'D:
usr
sap
jupgrade
log/ACTIVATE_USAGE_AS_ACU.OUT', 'D:
usr
sap
jupgrade
log/ACTIVATE_USAGE_AS_ACU.ERR' to which the output of the process has been redirected.##
#1.5#C000AC1908C2000000000039014A8CD1000432D6B6B9FCF8#1181797676875#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.execute.AbstractExtProcessOperation.execute(AbstractExtProcessOperation.java:176)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.execute.AbstractExtProcessOperation.execute(AbstractExtProcessOperation.java:176)#Java###Error while processing the result.##
#1.5#C000AC1908C200000000003A014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.execute(PhaseTypeExecuteTask.java:173)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.execute(PhaseTypeExecuteTask.java:173)#Java###Error while executing PhaseTypeExecuteTask with input file ExecuteTasks.xml and task ACTIVATE_CURRENT_USAGES.##
#1.5#C000AC1908C200000000003B014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:779)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:779)#Java###Phase has been completed.#1#UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES#
#1.5#C000AC1908C200000000003C014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:780)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:780)#Java###Start time: .#1#2007/06/14 10:37:42#
#1.5#C000AC1908C200000000003D014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:781)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:781)#Java###End time: .#1#2007/06/14 10:37:56#
#1.5#C000AC1908C200000000003E014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:782)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:782)#Java###Duration: .#1#0:00:14.453#
#1.5#C000AC1908C200000000003F014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:783)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:783)#Java###Phase status is .#1#error#
waiting for solution
thankx in advance....
shoeb

Could you please share us the solution?

Following the recent iTunes upgrade I am getting two error messages (-42404) and (-50). Any ideas how to rectify?

Using iTunes for the first time since the upgrade I am plagued with error messages - one telling me that a required component is not installed (-42404) and a second that my iTunes store request cannot be completed (-50). I've reset my old iPod as the message tells me but am reluctant to do that on my iPhone and risk loosing content. I've uninstalled and reinstalled iTunes but it's made no difference. Any ideas how to fix please?

Disable your firewall/security software.

ISA550 After upgrade 1.2.17 many error messages in the log

Hi,
After upgrade> 1.2.17 many error messages in the log
Hello,
after upgrading from 1.2.15> 1.2.17 have infinitely many errors in the log:
Err - System: sdsd: msgq_open: Error: mq_open () failed on msg queue / sdsd, errno = 2
Err - System: sdsd: open_control_msgq: Failed to open sdsd control message queue, errno = 2 (No such file or directory)
These errors occur repeatedly (300 times per minute). So I went back to the FW 1.2.15.
Does anyone have an idea?
Thanks and regards
Claus

Hi John,
Has this issue been resolved yet ?
I'm facing the same issue after upgrading to 1.2.18
11/11/2013 10:42    Error    System    sdsd: msgq_send: name /sdsd: pid 27242: mq_timedsend failed, errno = 9
11/10/2013 12:42    Error    System    sdsd: http_post: Error: Failed to open connection to v1.sds.cisco.com
11/10/2013 12:42    Error    System    sdsd: open_connection: TCP connection failed on connection 0x1B1C60F8
11/10/2013 12:42    Error    System    sdsd: tcp_connect: Couldn't connect socket, errno = 110
11/10/2013 0:22    Error    System    sdsd: http_get: Error: Failed to open connection to v1.sds.cisco.com
11/10/2013 0:22    Error    System    sdsd: open_connection: TCP connection failed on connection 0x1AFC4DC0
11/10/2013 0:22    Error    System    sdsd: tcp_connect: Couldn't connect socket, errno = 110
11/9/2013 18:43    Error    System    sdsd: http_post: Error: Failed to open connection to v1.sds.cisco.com
11/9/2013 18:43    Error    System    sdsd: open_connection: TCP connection failed on connection 0x1B1C60F8
11/9/2013 18:43    Error    System    sdsd: tcp_connect: Couldn't connect socket, errno = 110
Please let me know how to make this go away.
What are these errors about anyway ?? What causing it ??
Thanks
Lutfi
2013-11-11 10:42:29
Error
System
sdsd: msgq_send: name /sdsd: pid 27242: mq_timedsend failed, errno = 9
2013-11-10 12:42:59
Error
System
sdsd: http_post: Error: Failed to open connection to v1.sds.cisco.com
2013-11-10 12:42:59
Error
System
sdsd: open_connection: TCP connection failed on connection 0x1B1C60F8
2013-11-10 12:42:58
Error
System
sdsd: tcp_connect: Couldn't connect socket, errno = 110
2013-11-10 00:22:57
Error
System
sdsd: http_get: Error: Failed to open connection to v1.sds.cisco.com
2013-11-10 00:22:57
Error
System
sdsd: open_connection: TCP connection failed on connection 0x1AFC4DC0
2013-11-10 00:22:56
Error
System
sdsd: tcp_connect: Couldn't connect socket, errno = 110
2013-11-09 18:43:17
Error
System
sdsd: http_post: Error: Failed to open connection to v1.sds.cisco.com
2013-11-09 18:43:16
Error
System
sdsd: open_connection: TCP connection failed on connection 0x1B1C60F8
2013-11-09 18:43:16
Error
System
sdsd: tcp_connect: Couldn't connect socket, errno = 11011/11/2013 10:42    Error    System    sdsd: msgq_send: name /sdsd: pid 27242: mq_timedsend failed, errno = 9
11/10/2013 12:42    Error    System    sdsd: http_post: Error: Failed to open connection to v1.sds.cisco.com
11/10/2013 12:42    Error    System    sdsd: open_connection: TCP connection failed on connection 0x1B1C60F8
11/10/2013 12:42    Error    System    sdsd: tcp_connect: Couldn't connect socket, errno = 110
11/10/2013 0:22    Error    System    sdsd: http_get: Error: Failed to open connection to v1.sds.cisco.com
11/10/2013 0:22    Error    System    sdsd: open_connection: TCP connection failed on connection 0x1AFC4DC0
11/10/2013 0:22    Error    System    sdsd: tcp_connect: Couldn't connect socket, errno = 110
11/9/2013 18:43    Error    System    sdsd: http_post: Error: Failed to open connection to v1.sds.cisco.com
11/9/2013 18:43    Error    System    sdsd: open_connection: TCP connection failed on connection 0x1B1C60F8
11/9/2013 18:43    Error    System    sdsd: tcp_connect: Couldn't connect socket, errno = 1

How to upgrade from Solman 7.0 to 7.0 EHP1?

Hi,
In the SAP note 1169247, it talks about doing the upgrade from 7.0 to EHP1 using SAINT and JSPM. But in the Upgrade Guide SAP Enhancement Package 1 for Solution Manager 7.0 - UNIX Oracle˝, it talks about running the upgrade using an Upgrade MAster DVD.
1. Now is this the same as the EHP installer? If so, why is it not mentioned anywhere in the upgrade guide that we have to use EHPI? If not, what is this Upgrade Master installer?
2. Should I use SAINT/JSPM for the upgrade to solman 7.01?
Your answers to these questions will be highly appreciated.
Thanks,
Ajay

Hi Ajay,
I had the same question a few day's ago.
The difference between these two methods are the word updarte and upgrade.
If you are on Solman 7.0 you have to do a update with SPAM/SAINT.
If you are on Solman 3.0 or something you have to do a upgrade with the master dvds. You can read this on one of the first sites of the upgrade guide.
So you have to use SPAM/SAINT, and the Update Guide for EHP1 Using SPAM/SAINT will help you.
[Update Guide on Marketplace|https://websmp101.sap-ag.de/~sapidb/011000358700000427772009E.PDF]
Regards
Tobias

Upgrade to Solman 7.1 from Solman 7.01

Dear experts,
For the upgrade to Solman 7.1, I saw there were high impacts for ChaRM and Service Desk !
My questions are:
What are these impacts ?
I saw there was CRM Web UI to manage tickets, is it mandatory to install CRM to use it ?
Best,
Alexiel Green.

Hello Alexiel,
Please read:
Solution Manager 7.1 - Installation from scratch or upgrade - Take a look at the real cost
https://websmp203.sap-ag.de/~form/handler?_APP=00200682500000002672&_EVENT=DISPLAY&_SCENARIO=&_HIER_KEY=5011000358700000…
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0ed3f8b-ac55-3010-779c-aa6eebf10bf1?overridelayout=t…
CRM Web UI comes with Solution manager 7.1 version and it's included:
781448 - Support Package levels for SAP Solution Manager installations/upgrades
BR,
K>

Error Upgrade BW 7.01 to 7.3 in Phase DEPLOY_ONLINE_SHD_DM

Hello,
i have a problem by upgrading BW 7.01 to 7.3 in Phase DEPLOY_ONLINE_SHD_DM
An error has occurred during the execution of the DEPLOY_ONLINE_SHD_DM phase.
Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action. Deployment error. See log /usr/sap/TTW/upg/java/log/deploy_api.2.log for details. com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException. Reason: ASJ.dpl_dc.001085 Operation [deploy] of [sap.com_xappsanalyticsdm_par] failed com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [sap.com_xappsanalyticsdm_par] failed com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] Operation [deploy] of [sap.com_xappsanalyticsdm_par] failed com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [deploy] of [/usr/sap/TTW/upg/java/TTW/JC05/j2ee/cluster/server0/./temp/tcbldeploy_controller/archives/38/OPMFNDUI10_0-20004035_SCA1317900827022/DEPLOYARCHIVES/xappsanalyticsdm_par.sda] failed com.sap.engine.services.deploy.container.DeploymentException: Exception during deploy: par files are no longer supported. Please use the migration tools for migrating your file. com.sap.portal.prt.sapj2ee.deployment.PortalDeploymentException: par files are no longer supported. Please use the migration tools for migrating your file. at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.deploy(PortalRuntimeContainer.java:244) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:309) at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:519) at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:182) at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:203) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473) at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1828) at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:358) at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:311) at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139) at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138) at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57) at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213) at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67) at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282) at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84) at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100) at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Thanks
Steven

Steven Bier wrote:>
>
>H/38/OPMFNDUI10_0-20004035_SCA1317900827022/DEPLOYARCHIVES/xappsanalyticsdm_par.sda] failed >com.sap.engine.services.deploy.container.DeploymentException: Exception during deploy: par files are no longer supported. >Please use the migration tools for migrating your file. com.sap.portal.prt.sapj2ee.deployment.PortalDeploymentException: par >files are no longer supported. Please use the migration tools for migrating your file. at
>
>
If you will check above logs then it is saying your parfile is not supported. Either you should migrate or un-deploy it and then upgrade.
Thanks
Sunny

System Copy -Solman 7.1 Adjust name table phase error

Dear Experts,
I am on way of performing the system copy for solman 7.1 from prod to dev system.We are encountering the error in the adjust name table phase .Below is the log :
ERROR in initialization (can't get R/3-version)
ERROR in initialization (can't get R/3-version)
D:\usr\sap\\D00\log\SLOG00.LOG: No such file or directory
rslgwr1(20): rstrbopen cannot open pre-existing SysLog file.
D:\usr\sap\\D00\log\SLOG00.LOG: No such file or directory
rslgwr1(11): rstrbopen cannot open SysLog file.
SysLog:iE1020140515082322000000000000 this TTY
      :                                                            0000
      :SCSA         4096
SysLog:hBZA20140515082322000000000000 this TTY
      :                                                            0000
      :SVERS                                               dblink 1323
OS:Windows 2008
Database :Sybase Ase 15.7 ,and the weird thing is my SID is different .
Appreciate your responses
Thanks
Asim

Hi Asim,
1.I was getting error at Abap phase load error .So i have merge the tsk & bak files by r3laod and manually set ign in tsk files .Should i change the ign status back to error.Is this could be the problem causing in adjusting table name phase.
Status "ign" will ignore the object from being imported into the database. This may lead to inconsistency and loss of data.
2.We have used abap export using Sap inst only .Will that not effect if using import by SWPM
Actually SWPM also contains sapinst tool. But As I never never used this approach , I would suggest you to give a try and check.
Else you may need to perform fresh export and then import using SWPM.
Hope this helps.
Regards,
Deepak Kori

Upgrading to SolMan 4.0 - error in PARMVNT_XCNV phase

Similar Messages

Maybe you are looking for