Solman upgrade 7.1 error in PREPARE_JSPM_QUEUE

Hi All,
We are upgrading solman from 7.0 EHP1 to 7.1 , getting the below error in PREPARE_JSPM_QUEUE phase
" Checking whether product SAP SOLUTION MANAGER with version 7.1 is supported by this EHP Installer.
Feb 21, 2012 6:04:32 PM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.validateProducts(JSPMSpStackQueuePreparator.java:309) [Thread[main,5,main]]: The product is not supported.
Feb 21, 2012 6:04:32 PM [Error]: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase."
I had checked the note Note 1431340 - EHPI fails at PREPARE_JSPM_QUEUE phase - stack rejected, no solution got .
Can anyone advice please
Regards,
Nibu Antony

Hi
@ Nirmal
For solman upgrade tool is Solmanup nad version is as below:
Client Version 1.5.0 Server Version 1.5.0 Server Port 4241 DSUService
Version: 1.1.6 Configured Plugins
Plugin ABAP at Version:
1.0.3
Plugin J2EE at Version:
1.0.5
I had already gone through the thread and the note as mentioned in initially, no luck still..

Similar Messages

Error in prepare_jspm_queue in Ehp installer for ecc6.0

Hi,
When I am running EHPI for our ecc6.0, i getting error in prepare_jspm_queue phase, Log file says 'stack.xml contains no components for this system.' It searched the xml file and gave the error. But in my environment we are not using any java components. But I started the ehpi with both abap and java. now i would like to run abap only if possible. other wise what i can do to over come this error.
any help is appreciated.
I am attaching the log here.
Nov 7, 2011 11:41:36 AM [Info]:                      com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:754) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been started.
Nov 7, 2011 11:41:36 AM [Info]:                      com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:755) [Thread[main,5,main]]: Phase type is com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue.
Nov 7, 2011 11:41:36 AM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter inputFile=EHPComponents.xml
Nov 7, 2011 11:41:36 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMQueuePreparatorFactory.createJSPMQueuePreparator(JSPMQueuePreparatorFactory.java:93) [Thread[main,5,main]]: Creating JSPM SP Stack queue preparator.
Nov 7, 2011 11:41:37 AM [Info]: com.sap.sdt.ucp.dialog.elim.DialogEliminatorContainer.canBeOmitted(DialogEliminatorContainer.java:96) [Thread[main,5,main]]: Dialog eliminator spStackDialogEliminator allows to omit dialog SPStackLocationDialog
Nov 7, 2011 11:41:37 AM [Info]:                  com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator RequiredFields.
Nov 7, 2011 11:41:37 AM [Info]:                  com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator SPStackLocationValidator.
Nov 7, 2011 11:41:37 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:115) [Thread[main,5,main]]: Using SP Stack D:\sap_downloaded\stack.xml.
Nov 7, 2011 11:41:37 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:488) [Thread[main,5,main]]: STACK-SHORT-NAME tag is missing. The CAPTION of the stack will be used as stack name.
Nov 7, 2011 11:41:37 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:582) [Thread[main,5,main]]: PRODUCT-PPMS-NAME tag is missing. The CAPTION of the product will be used as product PPMS name.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature SAP ERP 6.0 : SAP ECC Server - 20 (09/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:473) [Thread[main,5,main]]: SAP-NOTE tag is missing in the stack definition file.
Nov 7, 2011 11:41:37 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:488) [Thread[main,5,main]]: STACK-SHORT-NAME tag is missing. The CAPTION of the stack will be used as stack name.
Nov 7, 2011 11:41:37 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:582) [Thread[main,5,main]]: PRODUCT-PPMS-NAME tag is missing. The CAPTION of the product will be used as product PPMS name.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature SAP EHP2 FOR SAP NETWEAVER 7.0 : Application Server ABAP - 09 (09/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:488) [Thread[main,5,main]]: STACK-SHORT-NAME tag is missing. The CAPTION of the stack will be used as stack name.
Nov 7, 2011 11:41:37 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:582) [Thread[main,5,main]]: PRODUCT-PPMS-NAME tag is missing. The CAPTION of the product will be used as product PPMS name.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Catch Weight Management - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Central Applications - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Defense & Public Security - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Discrete Ind. & Mill Products - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : ERecruiting - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Financial Services - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Financial Supply Chain Mgmt - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Global Trade - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Learning Solution - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Human Capital Management - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Leasing/Contract A/R & A/P - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Media - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Oil & Gas - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Oil & Gas with Utilities - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Hospital - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Strategic Enterprise Mgmt - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Utilities/Waste&Recycl./Telco - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Public Sector Accounting - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Insurance - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : SAP ESA ECC-SE - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : PLM Core - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : EAM config control - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Defense - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
Nov 7, 2011 11:41:37 AM [Info]:                      com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSPXml(SPXmlParser.java:424) [Thread[main,5,main]]: Parsing of stack definition file D:\sap_downloaded\stack.xml has finished.
Nov 7, 2011 11:41:37 AM [Error]:                       com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
Nov 7, 2011 11:41:37 AM [Error]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:145) [Thread[main,5,main]]: The stack D:\sap_downloaded\stack.xml contains no components for this system.
Nov 7, 2011 11:41:37 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been completed.
Nov 7, 2011 11:41:37 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2011/11/07 11:41:36.
Nov 7, 2011 11:41:37 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2011/11/07 11:41:37.
Nov 7, 2011 11:41:37 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:00:00.437.
Nov 7, 2011 11:41:37 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
Regards
K.Prakash

Hi,
You can start EHPi tool to upgrade ABAP as well. Please follow SAP note 1245473. Please find below extract from this note:
< D030182 JUL/02/09 > -
Dual-Stack Systems Only: Disabling the Java Stack Handling
If you have updated your ERP 6.0 system with EHP4 and later want to install
further technical usages for the ABAP stack only, you can disable the Java
stack handling. Do not use this option for any other purpose then the one
stated above.
This option is available as of SAP EHP Installer 7.00 patch level 18. To
disable the Java stack handling, start the installation program by entering
the following additional parameter for executing the STARTUP script:
-srvarg=/DSUService/javadisabled=true
Thanks
Sunny

SharePoint 2013 site collection 'upgrade completed with errors'

Hi All,
I am in process to upgrade SharePoint 2010 to SharePoint 2013 with all steps as mentioned in TechNet.
I was able to get all the SP2010 UI in SP2013 environment. However, when I navigated to top level site and clicked on “Site
Collection health checks”. In SP2010 environment I never used (as Farm Admin) any Video content type. It belongs
to out-of-the-box "digital asset content types" and cannot be deleted.
Therefore I changed the name of Video to our department name like "Video - Company" and ran the site collection health check again. This time there was no conflict for content types.
After ran the site collection upgrade I got following error.
-------------------------------------------START------------------------------------------
05/05/2014 14:34:28.66 OWSTIMER (0x1474)
0x123C SharePoint Foundation Upgrade
SPFeatureDefinition aj2bj
ERROR Feature upgrade action 'AddContentTypeField' threw an exception upgrading Feature 'CTypes' (Id: 15/'695b6570-a48b-4a8e-8ea5-26ea7fc1d162') in Site 'http://sp13fe01-dev': Field type
Rating is not installed properly. Go to the list settings page to delete this field.
32d48d9c-70d4-f09a-6073-526808f844be
05/05/2014 14:34:53.04 OWSTIMER (0x1474)
0x123C SharePoint Foundation Upgrade
SPSiteWssSequence2 ajy6m
ERROR Feature upgrade incomplete for Feature 'CTypes' (Id: 15/'695b6570-a48b-4a8e-8ea5-26ea7fc1d162') in Site 'http://sp13fe01-dev'. Exception: Field type Rating is not installed properly. Go to the list settings
page to delete this field. 32d48d9c-70d4-f09a-6073-526808f844be
05/05/2014 15:18:43.95 OWSTIMER (0x1474)
0x123C SharePoint Foundation Upgrade
SPManager ajxoe
ERROR RunUpgradeSiteSession [SPSite Url=http://sp13fe01-dev] failed.
32d48d9c-70d4-f09a-6073-526808f844be
05/05/2014 15:18:44.16 OWSTIMER (0x1474)
0x123C SharePoint Foundation Upgrade
SPManager ajxoe
ERROR Exception: Upgrade completed with errors. Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS\SiteUpgrade-20140505-143330-61.log. The
number of errors and warnings is listed at the end of the upgrade log file.
32d48d9c-70d4-f09a-6073-526808f844be
05/05/2014 15:18:44.16 OWSTIMER (0x1474)
0x123C SharePoint Foundation Upgrade
SPManager ajxoe
ERROR at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint() at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd() at Microsoft.SharePoint.Upgrade.SPManager.RunUpgradeSiteSessionCore(Object
lockObject, SPSite site, SPUpgradeOperationFlags upgradeOperationFlags, Boolean checkConcurrentSiteUpgradeSessi
32d48d9c-70d4-f09a-6073-526808f844be
-----------------------------------END-------------------------------------
Feature ID 695b6570-a48b-4a8e-8ea5-26ea7fc1d162 is Standard Content Type Definitions https://social.technet.microsoft.com/wiki/contents/articles/7695.sharepoint-2010-list-of-features-id-displayname-and-scopes.aspx.
Any expert to solve the issue??
Thank you.
regards,
Aroh Shukla

Hi All and Inderjeet,
Thanks for your reply and pointers.
I did follow the steps as mentioned in the links above. I used some third party solutions but not for any Video solution. I was able to successfully migrated the SP2010 (WSS_Content) to SP2013 (WSS_Content) environment a few weeks back with exactly same
third party solutions and no site collection error:
I renamed the default and out-of-the box video site content type as shown:
I ran the "Site Collection Health Check" and did not receive any error as in my second screenshot.
But, after upgrade the Site Collection Upgrade and got the same errors.
I don't know if there is any SharePoint Server 2013 patch gave this error as I keep run the Windows Server 2012 (not running R2) and SharePoint Server 2013 regularly.
Can suggest how to resolve this error?
Many Thanks!!
--Aaroh
Aroh Shukla
The same here. Opening a support ticket with MS.

Itunes was working fine. Tries to install latest upgrade and get error message about an invalid character in the path "Program Files (x86)". PC, Win7, nothing else appears to be having same issue.

Itunes was working fine. Tried to install latest upgrade and get error message about an invalid character in the path "Program Files (x86)". PC, Win7, nothing else appears to be having same issue. Program still works, simply cannor upgrade.

Thanks b noir,
I tried this solution without success. After FixIt ran and didn't find a problem, either in looking for issues with "software upgrade" or "iTunes" it kindly offered to help me uninstall iTunes. I had thought of this as a possibilty but it seems to me that if you do that you lose a lot of "non-native-to-Apple" information you might have entered. I did this once and recovery was painfull. Is there a way to uninstall iTunes without losing all of that sort of thing? Any help would be appreciated.

Startup upgrade ORA-00205: error in identifying control file

Hi,
I am doing a manual upgrade from 10.2.04 to 11.2.03.
I have installed 11.2.0.3.
Ran utlu112i.sql
Copied TNSNAMES and LISTENER.ora,init.ora from 10g home to 11g home respective directories.
Commented all dump_dest paramteres in 11g init.ora and added diagnostic_dest parameter
exported all the varaiables as follows.
export ORACLE_HOME=/oracle/ora11203
export PATH=$ORACLE_HOME/bin:$PATH
export ORACLE_SID=OMIGTEST
export TNS_ADMIN=$ORACLE_HOME/network/admin
export ORACLE_BASE=/oracle/ora11203/app/ora11203
Now when i try to start DB from the unix session where all of above variables are set,i am getting following issue.
SQL> startup upgrade
ORACLE instance started.
Total System Global Area 1636892672 bytes
Fixed Size                  2183056 bytes
Variable Size            1090519152 bytes
Database Buffers          536870912 bytes
Redo Buffers                7319552 bytes
ORA-00205: error in identifying control file, check alert log for more info
Alert log says as below.
ORACLE_BASE from environment = /oracle/ora11203/app/ora11203
Thu Aug 23 15:03:36 2012
ALTER DATABASE   MOUNT
ORA-00210: cannot open the specified control file
ORA-00202: control file: '/oracle/ora11203/dbs/cntrlOMIGTEST.dbf'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
ORA-205 signalled during: ALTER DATABASE   MOUNT...In init.ora of 11g (which is copied from 10g) ,i have commented our control file path entry.
Kindly assist me as i am doing upgrade for the first time.
Thanks
Edited by: user10698496 on Aug 24, 2012 2:47 AM

Hi,
Issue of sqlplus is solved after setting proper LD_LIBRARY_PATH.
But eve after that startup upgrade showing same error.
sqlplus '/as sysdba'
SQL*Plus: Release 11.2.0.3.0 Production on Thu Aug 23 16:22:16 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing optionsSQL> startup upgrade
ORACLE instance started.
Total System Global Area 1636892672 bytes
Fixed Size 2183056 bytes
Variable Size 1090519152 bytes
Database Buffers 536870912 bytes
Redo Buffers 7319552 bytes
ORA-00205: error in identifying control file, check alert log for more info
Do i copy control file from 10g home and place in in 11g path and mention it in init.ora before upgrade?
Thanks

Upgrade - Health Check Error

Hi All, I am upgrading the site collection which has NO workflow implemented in 2010. When I am doing health check before the upgrade I am getting this
•<websiteUrl>/_catalogs/wfpub/Approval - SharePoint 2010/ReviewApproval_1033.vdw - Reset page to default
•<websiteUrl>/entsearch/Pages/peopleresults.aspx - Reset page to default
•<websiteUrl>/_catalogs/wfpub/Collect Feedback - SharePoint 2010/ReviewFeedback_1033.xoml.wfconfig.xml - Reset page to default
•<websiteUrl>/_catalogs/wfpub/Approval - SharePoint 2010/ReviewApproval_1033.xoml.wfconfig.xml - Reset page to default
•<websiteUrl>/_catalogs/wfpub/Collect Feedback - SharePoint 2010/ReviewFeedback_1033.vdw - Reset page to default
•<websiteUrl>/_catalogs/wfpub/Collect Signatures - SharePoint 2010/Signatures_1033.vdw - Reset page to default
•<websiteUrl>/entsearch/Pages/results.aspx - Reset page to default
•<websiteUrl>/_catalogs/wfpub/Collect Signatures - SharePoint 2010/Signatures_1033.xoml.wfconfig.xml - Reset page to default
•<websiteUrl>/Education Documents/Forms/template.dotx - Reset page to default
•<websiteUrl>/_catalogs/masterpage/VariationRootPageLayout.aspx - Reset page to default
What is this error about? Should I proceed the upgrade with this error or resolve?
Please advice.
Regards,
Khushi
Khushi

Hi,
According to your post, my understanding is that you got “Reset page to default” error in Health Check.
If you haven't customize any workflow or anything, you can just reset them to the default, it’s OK.
Because in the database the sourse pages were completely uncustomized, out of the box.
So, you can reset them to the default, then check with Health Check, it would no error again.
http://www.chrismcnulty.net/blog/Lists/Posts/Post.aspx?ID=113
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

SAP Solman EWA System ABAP error

Hi,
SAP Solman EWA services trows error .
The job which refreshes Service sessions (for Early Watch Alerts) in SolMan 4. gets cancelled with the message:
Syntax error in program "RDSVASAEA_ROOT_____________061".
The following syntax error occurred in program "RDSVASAEA_ROOT_____________061"
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000208" not found."
It throws same error for
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000300" not found."
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000315" not found."
**I tried the function module "BDL_GENERATE_LOGFUNC_INCLUDES" with the value "ALL" in the 'OPTION' field.
As well as 'UPDATE' but it throws error for these includes mentioned above.
Can anyone help for the same without SAP NOTE - 727998
Thanks in advance
Sachin Soni

>
Sachin Soni wrote:
> The job which refreshes Service sessions (for Early Watch Alerts) in SolMan 4. gets cancelled with the message:
>
> Syntax error in program "RDSVASAEA_ROOT_____________061".
>
> The following syntax error occurred in program "RDSVASAEA_ROOT_____________061"
Have you reported the correct program name?
According my information, "RDSVASAEA_ROOT_____________061" has not been created (nor shipped to customers).
You stated, that the recommended SAP Note did not help. I would suggest to request help from SAP Support via a customer message on SV-SMG-SDD.
Best regards,
Ruediger

Upgrade assistant Server error: your username is root, but must be SID adm

Hi GURU's,
I am working on "Combined Upgrade & Unicode Conversion" 4.6C ==> NW2004s
When starting Upgrade assistant and continuue with upgrade getting following error:
Server error: your username is root, bu must be <SID>adm
I have option to continue, or cancel
When I choose "Continue" Upgrade assistant disconects from Upgrade server
Has someone any idea, what is the reason, and how can I solve this issue.
PS: I have also tried to start upgrade with <SID>adm user, but the same error.
Thanks for your help in advance.

Hi,
The whole upgrade should only be executed using <sid>adm, not root. I suggest to re-run the upgrade using <sid>adm user.
Also ensure all files in /put directory have correct permissions.
Cheers!

Upgrade file pattern error

Model BEFW11S4
Version 3
Firmware 1.2.
I have connected my Win XP laptop with cable directly to the router, and I am trying to update firmware to version 1.45.10 which should be the correct update for my model, but the upgrade is interrupted with "Upgrade file pattern error".
I have tried hard-resetting the router before upgrading, but with the same result.
What to do?

How are you upgrading the routers firmware? Are you using the router web-based user-interface? If you are then try using this alternate way...
Go to www.linksys.com/downloads .. search for BEFW11S4 v3 ... then download the Set-up Wizard. Use this to upgrade your router instead. When you run this program, it will ask you for a server, password and then a file. Server is the router IP, password is the router password (default is admin) and file would be the firwmware you downloaded... once you input the necessary info... hit upgrade and you should be good to go.

ITunes upgrade/fresh install error!

Hello all.
I am using an iPod Touch second generation. Tried to upgrade to iOS5 but it required me to upgrade my iTunes to the latest version. Tried to upgrade and an error popped up "Package installer error" or some sort. Been told to redownload the installer package or try to reinstall. Tried both but to no avail. I thought my current iTunes was the culprit so I uninstalled my iTunes and tried again installing the latest iTunes. But the same error popped up again!
Now I don't have any itunes, and I dont know where does the previous itunes keep my iPod backup files. I have thousands of apps over there and it would be really frustrating to lose it.
Someone please help me. Thanks in advance.

"Package installer error"
What's the precise text of that error message, please? (There's a few different ones I can think of that you might be getting.)

Solman Upgrade: impacts on TAO 2.0

Hi Expert,
I'm planing to upgrade solution manager from 7.0 to 7.1 sp11. Currently I have SAP TAO 2.0 SP7 (ST-TAO 200) and HP QC adapter version 1.0 (ST-QCA 100) installed in my SAP SM 7.0. I would know if I will have any impact on these 2 components after the upgrade. In particular I sow that in SM 7.1 the new SAP TAO version has been included in the SAP TST addon. My question is, can I still use the add-ons ST-TAO 200 and ST-QCA 100 in my SM 7.1 SP 11?
Thanks in advance for the support.
BR
gio'

Hello Gio'
As Divyanshu pointed, ST-TAO 2.0 is compatible with 7.1
Also ST-QCA 100 doesn't change.
I first personally upgraded from 7.01 SP25 to 7.1 SP07 last year and decided to do the TAO upgrade from 2.0.4 to 3.0 SP02 a few weeks after the solman upgrade as the solman upgrade is quite an exercise on its own.
Just one note in regards to the QC adapter, if you're on solman 7.0, after the upgrade to 7,1, you will have to update the message ID protocol with the option “Suppress ID transfer".
Also in regards to QC, I was just using the requirements and test results transfers [I wasn't using defect management integration so I cant tell you if extra work would be required for this 2nd area of the QC integration]
Cheers
Francois

Attempted a down load of an upgrade, it failed, error R6034 C runtime library incorrectly, now I cannot get access to my old iTunes

attempted a down load of an upgrade, it failed, error R6034 C runtime library incorrectly, now I cannot get access to my old iTunes
How do I recover and upgrade

I have seen a number of conversations where you need to uninstall iTunes and various other pieces of software and re-install ... if Apple is such a great company, why don't they just fix their update process so we users don't have to mess around with this ... :-(

Tried to run ios5 upgrade, get unkown error 0xE8000065 and now ipad does not work at all and is frozen can not even switch off

tried to run ios5 upgrade, get unkown error 0xE8000065 and now ipad does not work at all and is frozen can not even switch off

Try a hard reset and go from there. You might try a manual install (using DFU Mode), as outlined in the link below.
Basic troubleshooting steps
17" 2.2GHz i7 Quad-Core MacBook Pro  8G RAM  750G HD + OCZ Vertex 3 SSD Boot HD 
Got problems with your Apple iDevice-like iPhone, iPad or iPod touch? Try Troubleshooting 101
 In Memory of Steve Jobs 

Stack error in PREPARE_JSPM_QUEUE phase

Hi all,
We are upgrading our Enterprise Portal system SAP NW 7.0 EHP1 to EHP2. We generated the stack XML file through MOPZ whereby we did select EHP2 Stack 9 and started the EHPI. However, it failed in the configuration step in the PREPARE_JSPM_QUEUE phase. For example, the error log says:
Software component sap.com/SAPJTECHF with version 7.01.5.4 is found on the system but in the stack it is listed with version 7.01.0.0.
For several components, it gives error as above.
Note our Portal system comprises of EP, EP CORE, AS JAVA, BI JAVA and industry package like Tax Officer. As of now we have not included the SCA file for Tax Officer (We intend to upgrade this later).
Please provide us your feedback what may be causing this error.
Thanks & regards.

Hi,
We removed the tags and repeated the phase; it ran successfully but this time the JSPM is confused about the Kernel files because we have placed both the Kernel 7.20 and Kernel 7.20 EXT files. Can both be used?
We removed the EXT files. But it is asking for these files now because I guess they are present in the XML file. Any suggestion regarding this?
--> you only need Kernel 7.20. Is either you generate the mopz or remove all entries with 7.20 EXT
As regards to the software components being correctly entered in SOLMAN (SMSY), we have only one concern - the products are displayed correctly but the SP level are not displayed at all in the Instances tab. Our Solman is on EHP1 stack 25.
--> Have you check the data in SLD? and have apply Note 1485385 - MOpz: Collective corrections 25
Thanks,
Nicholas Chang

Error in PREPARE_JSPM_QUEUE during EHP4 install

Hello,
I'm upgrading my ECC 6.0 system to ECC 6.0 EHP4. in the JAVA configuration phase PREPARE_JSPM_QUEUE I get the following error:
Apr 5, 2011 4:44:04 PM [Error]: Software component sap.com/SAP_JTECHF with version 7.00.21.8 is found on the system but in the stack it is listed with version 7.00.21.0.
Apr 5, 2011 4:44:04 PM [Error]: Software component sap.com/SAP_JTECHS with version 7.00.21.14 is found on the system but in the stack it is listed with version 7.00.21.0.
Apr 5, 2011 4:44:04 PM [Error]: Software component sap.com/LM-TOOLS with version 7.00.21.1 is found on the system but in the stack it is listed with version 7.00.21.0.
Apr 5, 2011 4:44:04 PM [Error]: Software component sap.com/CORE-TOOLS with version 7.00.22.1 is found on the system but in the stack it is listed with version 7.00.22.0.
Apr 5, 2011 4:44:04 PM [Error]: Software component sap.com/SAP-JEE with version 7.00.21.8 is found on the system but in the stack it is listed with version 7.00.21.0.
I have configured the JAVA stack in the Solution Manager so the XML stack contains SP level 21 for software component SAP_JTECHS. What I donu2019t understand is how could the installer read a SP level 21.8. I didn't know the sub versions exists.
Does anyone know how to fix this problem so I could go on with the upgrade.
Kind regards,
Richard Meijn

Hello Richard,
check the XML file generated, on the entries for SAP_JTECHF, SAP_JTECHS, LM-TOOLS, CORE-TOOLS and SAP-JEE components.
For example:
- <software-component>
<caption>SAP_JTECHF</caption>
<ppms-number>xxxxxxxxxxxxxxxxxxx</ppms-number>
<runtime-type>J2EE</runtime-type>
<name>XXXXXXXXXXXXX</name>
<version>7.00</version>
<vendor>sap.com</vendor>
- <support-package>
<caption>SP021 for SAP_JTECHF 7.00</caption>
<name>SP021</name>
<vendor>sap.com</vendor>
<ppms-number>xxxxxxxxxxxxxxxxxxx</ppms-number>
<sp-level>021</sp-level>
<patch-level>0</patch-level>
- <archives>
You'll see on the "patch level" entry (which means the sub version you're referring to) that it should be '0' on the XML file.
The main possibility for this is that MOPZ generated the XML file incorrectly, based on the information it fetched from the SolutionManager. This issue is occuring probably because you have an outdated information or there are missing information in transaction SMSY. Check in SMSY if the Software components for the system are up to date. If not you need send the
system data to a SLD and use LANDSCAPE FETCH to update the JAVA data in SMSY. After have JAVA system components data updated in SMSY you must create a new mopz transaction. This new mopz transaction will not include wrong information in the XML file then.
(remember you need a SLD to maintain the JAVA information. You can use the SLD of the solution manager. Go to the Visual Administrator of the system that you want upgrade and in SLD Data Supplier Service, maintain the User/password/host/port of the SLD of solman and trigger the service. The SLD of solman will be updated with the JAVA information of this system and after run LANDSCAPE fetch job, SMSY will be populated with JAVA information up to date. If you created manually the JAVA instances, MOPZ will not know the SOURCE software components and this will have a big impact in the calculation as MOPZ will not know the source components version.)
Alternatively you can create a XML file manually (with the correct SP and patch levels, of course). This method is supported too, just keep in mind that if you have a ERP system that you want upgrade to EHP4 or a higher EHP version, you must
use MOPZ. If you're implementing EHP1 in Netweaver, you can use the XML file generated in the Service Marketplace without problems.
I hope all this information helps.
Best regards,
Tomas Black

Solman upgrade 7.1 error in PREPARE_JSPM_QUEUE

Similar Messages

Maybe you are looking for