Error in stack.xml - Upgrade to EHP1 SPS 8 using SUM

Hello
we're currently upgrading our PI-system. We use SUM
as upgrade tool.
I've opened a maintenance task in solution manager and defined the
target support package stack (SAP PI 7.1 EHP 1 SPS8).
During the upgrade procedure (step 2: Select Target) in SUM I get an
error, after selecting the stack xml file:
Cannot construct a support package stack from
file /usr/sap/trans/EHPinstfiles/SMSDXML_XIT_20111010063232.419.xml.
Stack definition
file /usr/sap/trans/EHPinstfiles/SMSDXML_XIT_20111010063232.419.xml is
rejected.
See error messages in /usr/sap/XIT/SUM/sdt/log/SUM/DEFINE-TARGET-
SOURCE_09.LOG.
DETECT  define_target  define-target-dialog  define-target-
source  com.sap.sdt.j2ee.services.servicesimpl.DefineTargetService  class com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParserException
Next an outtake of the log-file:
Oct 12, 2011 10:31:41 AM [Info  ]: Basic component properties of SDU file DEPLOYARCHIVES/sap.com~tc~lm~itsam~co~ui~xi~msg~wd.ear have been read. Component name is sap.com/tc/lm/itsam/co/ui/xi/msg/wd and version is 7.11.
Oct 12, 2011 10:31:41 AM [Info  ]: Subcomponents of component sap.com/SOAMONBASIC have been processed.
Oct 12, 2011 10:31:41 AM [Info  ]: File /usr/sap/trans/EHPinstfiles/SOAMONBASIC08_0-10006070.SCA has been analyzed for deployment components.
Oct 12, 2011 10:31:41 AM [Error ]: Component with name SERVERCORE and vendor sap.com has multiple archive names.
Oct 12, 2011 10:31:41 AM [Info  ]: Parsing of stack definition file /usr/sap/trans/EHPinstfiles/SMSDXML_XIT_20111010063232.419.xml has finished.
Oct 12, 2011 10:31:41 AM [Error ]: The following problem has occurred during step execution com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParserException: Cannot construct a support package
stack from file /usr/sap/trans/EHPinstfiles/SMSDXML_XIT_20111010063232.419.xml.
Stack definition file /usr/sap/trans/EHPinstfiles/SMSDXML_XIT_20111010063232.419.xml is rejected. See error messages in /usr/sap/XIT/SUM/sdt/log/SUM/DEFINE-TARGET-SOURCE_12.LOG.
Regards
Christian Kaiser

Hello
I've solved the problem.
In the stack.xml file are multiples software-components with the same name, here "SERVERCORE".
I had 3 entries, two with patch-level 0 and one with patch-level 1.
I've deleted the two entries with patch-level 0 and then it works.
Regards Christian

Similar Messages

  • EHP1 Installation - error during the XML stack file check.

    Hello SAP fans and gurus.
    I'm updating CRM with EHP1 and I'm stuck at the phase PREP_EXTENSION/SUBMOD_EXTENSION_NEW/SELSTACKXML. Something wrong with the XML stack file. I get this error:
    Severe error(s) occured in phase PREP_EXTENSION/SUBMOD_EXTENSION_NEW/SELSTACKXML!
    Last error code set: Error reading stack info, return Code = -1, Reason = 'The stack configuration is not valid for the system CRM, inst.-no. 0020652601'
    The trouble ticket isn't saying much, but I'll post it anyway:
    This trouble ticket was created by SAPehpi on 20110520102342
    SAPehpi broke during phase SUBMOD_EXTENSION_NEW/SELSTACKXML in module PREP_EXTENSION / Extension module for start release >= 40B
    Error Message: Error reading stack info, return Code = -1, Reason = 'The stack configuration is not valid for the system CRM, inst.-no. 0020652601'
    Summary of SAPehpi:
    SAPehpi Release:     lmt_001
    SAPehpi Version:     40.005
    Start Release:          701
    Target Release:          701
    Summary of host system details:
    SID:               CRM
    Host:               sapvmcrm
    MS Host:          sapvmcrm
    GW Host:          sapvmcrm
    Start Path:          /usr/sap/CRM/DVEBMGS00/exe     
    Kernel Path:          /usr/sap/CRM/DVEBMGS00/exe
    Summary of operating system details:
    OS Type:          Linux X86_64
    OS Version:          2.4
    Summary of database details:
    Database Type:          ada
    Database Version:     7.7.07.014
    Summary of RFC details:
    Host:               sapvmcrm
    GW Host:          sapvmcrm
    Client:               000
    Destination:          CRM
    Language:          
    System No.:          00
    There's one problem with the file SAPEXEDB_82-10007250.SAR, which was in the download basket, but is not available for download. I deleted the record in the XML stack file and tried the phase again... with no success. Going through the XML file and checking if the packages have been downloaded is a real pain in the ***.
    Anyway, can I somewhere download this file SAPEXEDB_82-10007250.SAR?
    Or can anyone help me, how solve this issue different way?
    Thanks a lot in advance.
    -Stefan

    OK, I got it. Wrong installation number. We had to change the installation number in the stack file according the system in the Solution Manager via transaction SMSY. Then it worked like a charm.

  • XML Forms Builder Errors after SP Stack 14 upgrade

    Hello,
    I upgraded development portal to NW04s SPS14 (from SPS11).
    In XML Forms Builder, try to open my existing project but not succedd. I get the message "Operation Timeout".
    "The current operation timed out and was aborted. This was caused by network communication problems . Some data may have been lost.try again later"
    After click cancel, I get a second message:
    "There are no projects stored on the server"
    In KM content, etc folder, xmlforms , I can see all my projects !!!
    Of course, no network problems exists.. portal is working ok, ...
    I applied OSS note 1150307 - "Internal Server Error when accessing XML Forms Builder" but I have the same problem.
    Any idea¿?
    Thanks and Regards
    Noemí Llano

    Hello, I did a test...
    from the same client machine ...(with JRE 1.6.0_03) I start XML Forms ....
    with SPS11 portal, I can see the Projects.
    With SPS14 portal, I can not see the projects
    Thanks and Regards
    Noemí

  • How to get stack.xml for EHP2 Netweaver BI 7.0 Upgrade without SolMan?

    Hi Experts,
    We are planning for BI 7.0 EHP2 upgrade from BW 3.5
    SAP_ABA u2013 6.40 - 24
    SAP_BASIS u2013 6.40 - 24
    PI_BASIS - 2006-1-640 - 8
    SAP_BW u2013 3.50 - 24
    To Target version of NW BI 7.0 EHP2,
    In SAP Support Package Stacks, Itu2019s not showing SPS (SAP Support Package Stacks) for NW BI 7.0 EHP2 but itu2019s showing NW BI 7.0 EHP1, Please advise, how to download SPS for NW BI 7.0 EHP2 with stack.xml file.
    Thanks & Regards
    Raja

    Hi Experts
    After getting the stack.xml file, we started the process of upgrading our BW 3.5 system to BW 7.0 EHP2. We
    have downloaded all media list and EHPI tool. The EHPI tool latest
    version SAPehpi_111-10005800.SAR has been used and we are getting the
    following error.
    Release '640' is not supported by this tool.
    Request you to please suggest the solution.
    Regards,
    RajaMurugesan,PMP

  • Error while generating stack.xml file in solman

    Hi All,
    I am unable to generate a stack.xml file in solman,  below is the error.
    Also, how to select a patch for Java stack JVM in solman. Please help me.
    Thanks,
    Dheeraj

    Hi Kartik,
    Thanks for the info.
    I am trying to upgrade SAP JVM from 6.1.49 to 6.1.64,
    I tried by manually downloading the file and upload it through SUM it was not successful.
    Now I am trying with stack.xml and some product instance are not installed.
    Any suggestions??
    Regards,
    Dheeraj

  • Upgrade FI-CAX 600 to FI-CAX 617 - how to calculate stack.xml?

    Hi experts,
    I'm currently on the task to update our FI-CAX from 600 to 617 on our ERP 6.0 EhP7 Utilities system. In SAINT I get the message that this upgrade can only be done with a calculated STACK.XML file, but unfortunatly I'm not able to select FI-CAX in MOPZ. Can anyone guide me through MOPZ and selecting the correct packets?
    Kind regards
    Roland

    Hi Roland,
    please open a new Maintenance Optimizer Session. Then you have to choose "Enhancement Package Installation". Please select technical usage "Leasing/Contract A/R & A/P". This will calculate Fi-CA and FI-CAX 617.
    Cheers,
    Andreas

  • Stack.xml There are no stack independent files in your selection error

    Hi experts,
    I am trying to do EHP upgrade from SR3 to EHP 6 , while generating stack.xml file using MOPZ I am  facing the problem as like...
      " There are no stack independent files in your selection " 
    Please find the attachment and help us if any one aware of it.
    Note: Windows 2008 on Oracle 10 .2 

    Hi
    Manu Mohandas
    Thanks for your reply,
    But We have selected those DB dependent Kernel files and DB independent kernel files in the previous step.
    As you said we have clicked the " continue" .
    PFA of next screen It is giving the same as previous ...
    CHEERS
    HSK

  • Error while creating webdynpro iview after  portal upgrade to ehp1

    Hello  All
    We have upgraded  our portal from 7.0  sp  15   to  portal  7.01  sp  3    .
    After upgrade we can create  iviews using portal components  but we are not able to create  iview using Iview template
    We are getting following  error  while creating  webdynpro java  iview
    java.lang.NoSuchMethodError: com.sapportals.portal.pcd.gl.PcdSearchControls.addExplicitAttributeCheck(Lcom/sapportals/portal/pcd/gl/IPcdAttribute;)V
         at com.sap.portal.pcm.iviewserver.cache.TemplatesCacheSrv.getPCDCatalog(TemplatesCacheSrv.java:184)
         at com.sap.portal.pcm.iviewserver.cache.TemplatesCacheSrv.refresh(TemplatesCacheSrv.java:589)
         at com.sap.newpage.pagewizardpanes.PageTemplateSelection.initTemplates(PageTemplateSelection.java:229)
         at com.sap.newpage.pagewizardpanes.PageTemplateSelection.wdDoModifyView(PageTemplateSelection.java:172)
         at com.sap.newpage.pagewizardpanes.wdp.InternalPageTemplateSelection.wdDoModifyView(InternalPageTemplateSelection.java:305)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
         at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
         at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1300)
         at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:327)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:869)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Regards
    Rajendra

    Hello Rajendra,
    please can you tell me, if you finally get a Solution for this Problem about  iviews creation with template Error after upgrade.
    Thanks and take Care
    Gedeon

  • Upgrade to EHP1 java (Portal) alone from NW 7.0 SP12

    Hi
    We are in the process of upgrading our portal NW 7.0 SP12 to EHP1 SP06.
    Java FAQs says that we can use just JSPM to deploy as its just a java standalone.
    Has anyone used JSPM to upgrade to EHP1 from NW7.0? instead of EHPi?
    Thanks

    U are giving me some confidence sunny.
    I tried using JSPM but its not deducting the xml file and also I choose the single support pack (advance option) its only picking up the source version as 12 and the target version says not found?
    Does that mean I have not downloaded all the components required in EPS/in directory? if so what all components I have to download? 
    Bcos in the market place if I choose NW 7.0 ---> Link to sp stack it shows me till SPS22.
    And for EHP1NW 7.0 it starts from EHP1 ISS initial shipment stack to SPS07.
    If I download both the above I will get two stack files?
    Should I update till SP22 in NW 7.0 and then start applying EHP1?
    Thanks

  • SAP_BS_FND addon was not selected as part of the stack xml

    We are in a process of upgrading production system (SAP NW 7.0) to EhP1, we
    have components SEM-BW,FINBASIS installed in the Netweaver system, we have added the system under Netweaver
    We have generated the stack xml file using solution manager MoPZ but we are not
    getting the option to select the upgrade addon SAP_BS_FND as part of
    stack xml file
    where in we had an option to select the SAP_BS_FND for Development
    and Quality and we have included the addon SAP_BS_FND in stack xml file
    my main question was why the component is not available for Production for selecting the option ??
    Please suggest us how to proceed further, we have read the note Note
    1326576 - SAP NetWeaver Systems Containing SAP ERP Software Components
    which says to install the addon after upgrade
    generating the stack file from Service Market Place too is not including the SAP_BS_FND in the stack xml
    Please help why it is behaving different for production
    Thanks,
    Ravi
    Edited by: ravi prasad on Aug 8, 2011 9:56 AM

    Hi,
    >The note says that if going with EhP1 with ERP components then it asking to register the system in Netweaver and then >upgarde the addon package with SAINT
    You should read the note carefully, below is extract from this note:
    Maintain your SEM, E-Recruiting or SAP Learning Management system as an ERP
    system in SMSY in order to download the EHP packages and to be able to
    maintain the system. Afterwards you must not use the generated Stack XML,
    but instead use a generated Stack XML from SAP Service Marketplace and
    include the packages for ERECRUIT, SEM-BW, FINBASIS or LSOFE in the
    IS_SELECT phase during the installation of EHP1 for SAP NetWeaver 7.0.
    Thanks
    Sunny

  • Solution manger upgrade to ehp1 from 7.0

    Hi
    we have solution manger 7.0 on windows 2003 with db2 9.1 database. I want to upgrade to ehp1. I mainted the solutionmanger 7.0 sp17 for the upgrade. I started the upgrade first ASJAVA using jspm with stack. First it upgraded the kernel 701. immediatly the java egine is stopped. ichecked the MMC it is not shwoing any process fro J2EE. But the asABAP WP are running successfully i am able to login also. please provide me how to reslolve this issue. Some of the logs i am psting here.
    ACCESS.ERROR#sap.com/com.sap.lcr*sld#LcrSupport#SAP-J2EE-Engine#administrators
    ERROR => Can't attach to administration shared memory (rc = 3) [jcmonxx.c    228]
    Thr 6180] *** ERROR => invalid return code of process [bootstrap] (exitcode = 66) [jstartxx.c   1642]
    [Bootstrap module]> Problem occurred while performing synchronization
    ejb-local-ref with ejb-ref-name SDCSPCallerBean cannot be linked
    ejb-ref with ejb-ref-name ejb/LogicalItemEJBBean cannot be linked
    ejb-local-ref with ejb-ref-name ejb/sap.com/slm/JNetDataProviderBean
    sap.com/tcslmslmapp has a weak reference to resource SAPIJ1DB with type javax.sql.DataSource but the resource is not
    available and the application may not work correctly
    com.sap.engine.core.thread.impl5.SingleThread#Java###Thread [] did not receive Task to process for [] seconds and is goingdown.#2#SAPEngine_System_Thread[impl:5]_11#0#
    Listener##0#0#Info#1#com.sap.engine.core.cluster.impl6.ms.MSListenerQueue#Plain###MSLib: Received error command to stoplistener queue.#
    com.sap.engine.core.thread.impl3.ThreadManagerImpl#Plain###ThreadManager stopped.#

    Hi,
    Could you please paste bootstrap log here from your work directory ?
    Thanks
    Sunny

  • Stack XML creation for specific package

    Hello
    I want to upgrade my ERP 6.0 EHP4 system's LSOFE 603 to 604 but I received I need a stack.xml for upgrade. Our Solution Manager 7.0 EHP1 system is recognising ERP system's SP levels but it is not giving me an upgrade option for LSOFE. I only saw latest SP which was 7 and all other SP's latest levels but not upgrade packages.
    How can I create a stack.xml for LSOFE 604?

    hi,
    If you operate a Netweaver system that contains at least one ERP software component (ERECRUIT, SEM-BW, FINBASIS or LSOFE), you must not use a stack XML file created for an SAP ERP system. Instead, you have to use a stack XML file for SAP NetWeaver systems. The EHP4 packages for the ERP software components have to be added manually in phase IS_SELECT.
    Generating the Stack XML File
    First of all, create a stack XML file for NetWeaver systems. This can be done either via the SAP Service Marketplace or in the Maintenance Optimizer of your SAP Solution Manager.
    check and update.
    Jansi

  • Stack.xml file

    Hi,
        Currently we have NW7.0 SR3 (ABAPJAVA),  Now we are planning to upgarde to EHP1 through ehp1 tool. how i can generate stack.xml file for (ABAPJAVA) stack without solution manager. Kindly help me
    Regards,
    Sampath.

    Hi,
    https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/swdc/sps/index.do?pvnr=01200615320900001250&u=&session_id=saS000427859520110124070001SID%3aANON%3apwdf4962_OW1_01%3aBkxYmOjMQn50g5RGGRAOjSdi_oZwuReU3be5uAej-ATT
    Check here.
    You have NW 7.0 as source and EHP1 is present in target.
    Regards,
    Nirmal.K

  • PREPARE_JSPM_QUEUE stuck message "The Stack XML .... is not supported"

    Hi All
    We have recently upgraded from SAP 4.7 SR1 to SAP ECC 6.0, Netweaver 7.00 EPH1.  We are in the middle of installing EHP4.  We have managed to get through the ABAP phase.  We are now on the J2EE phase.  We immediately received the following error:
    "An error has occurred during the execution of the PREPARE_JSPM_QUEUE phase."
    "The stack XML /usr/sap/trans/EPS/in/SMSXML_CROSSSYS_20100211171349.693.xml" is not supported by this EHP installer".
    I have looked at error logs PREPARE_JSPM_QUEUE_CSZ_01.LOG and TroubleTicket_01.txt but don't see anything wrong but I could be reading the logs incorrectly.
    The .SCA files referred to in the xml file  are in the ../ESP/in subdirectory.  This problem seems similar to thread:
    /thread/1562459 [original link is broken]
    but I can't resolve the issue.
    Any suggestions.
    Thanks.
    Stephen

    for the other guys that had the same problem.
    the problem is the generated xml file .
    make sure
    1) you have filled all the fields in SMSY for the landscape components under
    SERVER
    DATABASE
    PRODUCT
    2) you have connected the system with RFC wizard
    3) for dual stack (very important)   you have
        a) flagged the NW AS JAVA and flagged the connection to system component of type JAVA (see the next point)
        b) flagged the NW ADOBE DOCUMENT SERVICES and flagged the connection to system component of type JAVA (see the next point)
    4) created under LANDSCAPE COMPONENT --> SYSTEM COMPONENT --> JAVA
    for
    a) your solution manager entry  and compiled all the fields EVEN the part releated to DATABASE (otherwise you could have the error SYSTEM NO HOST in mopz)
    b) your system in the case you cannot put your system under the SLD of solution manager SLD and in this case you MUST point your system to this entry
    example of correct entry for JAVA
    messageserver : hostname
    dispatcher : hostname.domain..
    PORT : java port
    DATABASE : what you have put on database (with all the fields compiled even for it)
    DB SCHEME : what you see from system-> status
    Doing this you can selecte the dual stack XML that should have the CROSS in the middle of its name
    Edited by: Bruno Astorino on Mar 31, 2010 6:07 PM

  • After upgrading to 27, firefox will not start. Saw an error message during the upgrade process.

    After upgrading to 27, firefox will not start. Saw an error message during the upgrade process but cannot remember.
    Tried to run firefox.exe -P but receive error message:
    XML Parsing error: undefined entity
    Location: chrome://mozapps/content/profile/profileSelection.xul
    Line number 18, Column 1:
    <dialog
    ^
    Running on Windows XP SP3. No problem whatsoever before upgrading to 27. Sending this from Chrome as I cannot open Firefox at all.

    Thanks jschaer2000: after starting it once in safe mode, I closed Mozilla and tried several restarts in normal mode. So far, all worked:-)
    Thank you very much again.
    Still the automatic update process bothers me: it took me several days to discover the reason to the malfunction, since when I removed the problematic version from Add and Remove Programs, I didn't pay attention at first that it was another version, not v26 which I installed from my folder.
    In addition, I like to save the installation files before I run new programs and if I didn't have v26 exe file, I couldn't have operated Mozilla at all. Not that it was fun to remove and install again each time v27 didn't react, but it was better than nothing, I still prefer Mozilla over its competition.

Maybe you are looking for