Migration SAP VM to SAP LSO

Hey everyone,
we need to migrate our Training data from SAP VM to SAP LSO. Does anyone have best paratices about how we whould aproach that?
We have new naming conventions and new objects ids (no external IDs, but the numbers objects are given by migrating into the new system).
Is LSMW the best way?
Should we migrate objects (E;D;L;Q;QK;U;F;G ...) or should be set up the migration by Infotyp (IT1000, IT1001, etc.)?
Any help is highly appreciated.
Thanks,
Nadja

What is SAP VM ?
Regards,
Ravi Sekhar

Similar Messages

  • Error while installing Migration Tool kit for SAP BPC7.0

    Hi all,
    We are implementing SAP Business Planning and Consolidation Migration Process to BPC 7.0.
    We are trying to installin Migration Tool Kit. In this kit we are having two set up files - one for BPCMigrationClient and another for BPCMigrationServer.
    When i am trying to install the BPCMigrationServer set up file it diaplays a screen which says - Enter the service type accounts.- it has the following items - 1. System Admin ID, 2. password, 3. Admin ID, 4. Admin Password, 5. User ID, 6. User Password.
    1. System Admin ID already has the id ( through which i have logged on to the system). This option is non editable.
    2. password: gives option to type in the password.
    3, 4, 5, 6 options are disabled and are blank. we are not able to edit them or write anything in them.
    After entering the password when clicked on next , it gives us message saying Invalid Admin ID (3). But the problem here is that the 3,4,5 and 6 options are disabled. We cannot write anything in them. We are not able to install the migration tool kit because of this.
    Can anyone help us out in solving this issue.
    Thanks,
    Madhav

    CAn you precise also what Migration tool are you using?
    Migration from 5.1 to SAP BPC 7.0 NW?
    In that case when you are speaking about the installation about what part are you speaking?
    I think actually you are speaking about the migration tool from 4.2 to 7.0 Microsoft version .
    In that case you can install the mIgration tool just with SAP BPC sys admin users and you have to input the password for that user. Sys admin user for BPC is usually the user used for installation of SAP BPC server.
    Any way I suggest to follow the Migration tool training document and there you will find all the information necessary.
    Regards
    Sorin Radulescu

  • MII 14.0 SP4 :Migration error while importing SAP BM Templates

    Hi Experts,
    I am facing some migration errors while importing SAP Batch Manufacturing Templates into MII 14.0 SP4.
    There are almost 23 transactions which are not getting imported and the error message for all of them is-
    "Unable to migrate transaction Unable to import file
    <Name of the Transaction>"
    Any first hand experiences will be really helpful for me to proceed further.
    Regards,
    Muddassar Khan

    Hi All,
    Got the solution. The STARTUP.BAT file is been placed in the installation directory(usr/sap) and then it works fine. Also I have installed the patches and all working fine.
    Any way thanks for the answer christian libich.
    Regards
    G.Partheeban

  • What are  Pre Database Copy and Post data base copy activity list, Pre Migration and Post Migration activity list from SAP BW 7.0 to SAP BW 7.4 SPS6.

    BW on HANA :  Pre Database Copy and Post data base copy activity list, Pre Migration and Post Migration activity list from SAP BW 7.0 to SAP BW 7.4 SPS6.
    We are trying to copy database from SAP BW7.0 to SAP BW on HANA 7.4 SPS6 so we are in search for list of steps or activities during database copy both pre and post steps.
    Along with the above we are in search of Pre and post migration steps ones database is transferred successfully from oracle to HANA on 7.4 SPS6.
    Kindly help us in getting the exact course of action as requested.
    Thanks and Regards,
    Lavina Joshi

    Hi Lavina,
    try this link for starters: Upgrade and Migration - BW on HANA | SAP HANA
    Points to remember are:
    Preparation:
         -- Hardware Sizing
         -- Preparation of Data Centres
         -- HANA Hardware preparation
         -- System Landscape Readiness (upgrade software downloads, system readiness checks, etc)
         -- House Keeping activities on BW system (data clean up, etc)
    Post Installation:
         -- Sanity checks / Preparation and License checks
         -- JAVA Configurations
         -- Infoprovider conversions 
    Overall Stages are described below:
    # Environmental setup (HANA box)
         -- Initial system checks and Building Activities (system copy, Appln server setups, etc)
    # System readiness
                   - ZBW_HANA_COCKPIT Tool
                   - ZBW_HANA_CHECKLIST Tool
                   - ZBW_ABAP_ANALYZER Tool
                   - ZBW_TRANSFORM_FINDER Tool
                   - SIZING Report
                   - System Clean up Activities
                   - Impact of 7.4 on source system checks
                   - Java Upgrade for portal
    # DMO Stages
                   - Preparation & Pre Migration checks
                   - Execution / Migration
                   - Post Migration Activities
    # Testing Phase
                   - Source system checks/Activities
                   - System and Integration Testing
                   - End to End Testing
                   - Performance testing
                   - Reports
                   - BO reports / Interfaces
    Do let me know if you require any further information.
    Regards,
    Naren

  • Migration from SAP BC To SAP P.I

    HI Experts ,
    I am required to do migration from SAP BC to SAP P.I. I would require the following Info/Help from you as i have not worked on such scenario before this!
    1) What kind of challenges can be faced during migration from BC to XI?
    2) What is the best practise for doing the same?
    3) Can you share some scenario from where i can have some idea how to do migration?
    4) Generally how much time it takes in migration activity if ther are not much interfaces involved in it?
    Would appreciate your valuable inputs on the same!
    I have read How to guide docs on how to do migration from BC to XI but not convinced with the content
    Regards
    Saras Jain

    Hi Saras,
    I am giving you an example senario and a how to do all the steps and why it needed. if you need more information just mail me i'll give you the concerned PDF.
    Scenario
    SAP Business Connector enables data exchange between an SAP system and
    external systems using HTTP and e-mail. SAP Exchange Infrastructure (SAP XI)
    replaces SAP Business Connector (SAP BC).
    We distinguish between standard scenarios (that do not contain customer-specific
    development) and individual scenarios (that do contain services or mappings created
    by the customer). The following sections describe how to migrate both types of
    scenarios to SAP XI.
    Scenario 1 (IDoc – HTTP, HTTP – IDoc)
    An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to
    XML. It is sent to an external business partner by using HTTP.
    An external business partner sends an XML document by using HTTP to SAP BC or
    to SAP XI. The document is converted to an IDoc and sent to a connected SAP
    system in the internal system landscape.
    Scenario 2 (IDoc – Mail, Mail – IDoc)
    An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to
    XML. It is sent to an external business partner as an e-mail.
    An external business partner sends an e-mail to SAP BC or to SAP XI. The
    document is converted to an IDoc and sent to a connected SAP system in the
    internal system landscape.
    Flow Services
    Flow services are services that are written in the proprietary graphical-based flow
    language of SAP BC.
    Java Services
    Java services are services that are written in the Java language.
    There are several platforms that support Java, including SAP XI. However, the data
    model used in the Java services in SAP BC is proprietary.
    Stylesheet Transformations
    Stylesheet transformations are often used for mapping purposes. They take an XML
    document as input, convert it according to rules defined in the stylesheet, which is
    also an XML document, and produce an XML document as output.
    The XML Stylesheet Transformation Language (XSLT) was defined by W3C (World
    Wide Web Consortium), the consortium that defines most of the common standards in modern internet communication, such as HTML and SOAP.
    SAP NetWeaver is the open integration and application platform from SAP. With
    NetWeaver ’04, there is a significant overlap between the functions of SAP
    NetWeaver and SAP BC. Many functions provided by SAP BC are offered by SAP XI
    as part of SAP NetWeaver, for example, conversion of an IDoc to an XML message,
    mapping, routing, and adapters to connect to a large number of third-party back-end
    systems. SAP BC is therefore no longer needed. New or updated SAP solutions are
    based on SAP NetWeaver. Customers looking for a strategic integration solution for
    the complete application landscape should therefore now favor SAP NetWeaver.
    The last version of SAP BC was SAP BC 4.7, which was released in June 2003. SAP
    BC has not been developed further since this release. SAP BC is not released for
    any further platforms (such as Windows 2003) and does not support any further JDK
    versions, including the current version (Version 1.4).
    For information about the supported SAP BC versions, JDKs, and operating systems,
    see SAP Note 309834. For information about the support and maintenance strategy
    for SAP BC, see SAP Note 571530. Customers who still use SAP BC need to be
    aware of the following:
    • A solution based on SAP BC cannot be a strategic, long-term solution.
    • A solution based on SAP BC is based on technology that was implemented in
    2003 and that is no longer further developed.
    • SAP BC is supported on limited platforms and for limited JDKs only. Vendor
    support for some of these platforms and JDK versions will soon be
    discontinued.
    SAP BC and SAP NetWeaver are based on different technologies: SAP BC is based
    on webMethods’ proprietary Integration Server, whereas SAP NetWeaver is based
    on open standards, such as BPEL4WS (business process execution language for
    web services). Therefore, only parts of an SAP BC implementation, such as XSLT
    mappings, can be migrated to a solution based on SAP NetWeaver. Any custom
    programming based on SAP BC, such as SAP BC flow language, is unlikely to be
    reusable in the SAP NetWeaver context.
    Purpose of this Migration Guide
    The purpose of this migration guide is to provide scenario-based descriptions of the
    migration from a company’s system landscape that uses SAP BC to exchange
    documents with business partners, to a system landscape that uses SAP XI instead.
    This migration guide outlines, for certain scenarios, the individual steps a company
    has to take to replace an existing SAP BC implementation with SAP XI.
    The basic steps in the back-end systems are:
    • Defining the logical systems
    • Maintaining the ALE distribution model
    • Maintaining partner profiles and EDI ports
    • Maintaining RFC destinations
    The basic steps in the SAP XI system are:
    • Maintaining the System Landscape Directory
    • Configuring the IDoc adapter
    • Maintaining the receiver determinations, interface determinations, and
    interface agreements
    • Maintaining the communication channels
    The type of scenario to migrate typically has an impact on the communication channels only.
    Scenario 1 IDoc/HTTP
    IDoc – HTTP Using SAP BC
    Within the system landscape of a company, an SAP system sends an IDoc
    asynchronously to SAP BC. SAP BC converts the IDoc into a standard IDoc XML
    document. The fields of the IDoc are not modified, that is, the conversion does not
    involve any mapping of source fields to target fields. After conversion, SAP BC uses
    HTTP to send the XML document synchronously to an external URL of a business
    partner.
    System Landscape
    • An SAP system and SAP BC are installed within the same system landscape
    of a company.
    • The following information is defined in the SAP system to allow data
    exchange between the SAP system and SAP BC:
    o An RFC destination and a logical system for SAP BC
    o The distribution model is maintained, if necessary
    • The following information is defined in SAP BC:
    o An SAP server with an alias is defined. For this SAP server, the
    information that the SAP BC requires to connect to the SAP system is
    specified.
    o A listener is configured to listen to requests from the SAP system.
    o A routing rule with the transport type “XML” is configured for the
    specific sender, receiver, and message type. The routing rule
    determines how a message is to be routed and where it is to be routed
    to. The scenario described does not use an ACL, (Access Control List
    to restrict execution permissions for this routing rule) or pre-processing
    or post-processing SAP BC services.
    4.2 IDoc – HTTP Using SAP XI
    Check the prerequisites described above under Prerequisites for Standard
    Scenarios.
    The IDoc adapter is used to receive an IDoc from an SAP back-end system and
    convert it to XML.
    The adapter used to post this XML to an external destination is the plain HTTP
    adapter.
    To set up the communication channel, perform the following steps:
    1. Locate the routing rule in SAP
    Business Connector.
    In the Administration View, choose
    Adapters – Routing to navigate to
    Routing Rules.
    2. Select the details of the relevant routing rule.
    To display the details, choose the green triangle (Edit).
    Transport is typically set to XML and a URL is specified. You can use this
    URL in your SAP XI settings.In some cases, Transport is set to
    B2B Service and the parameters Server Alias, Folder and Service
    exist. This is the same as when Transport is set to XML and has the
    URL http://<serverhost>:<port>/invoke/<folder>/<service>.
    You can find <serverhost> and<port> in the definition of the
    remote server under Settings –>Remote Server in the Administration
    View.
    3. Set up the communication channel in the Integration Directory using the parameters from the SAP BC routing rule.
    Use the following settings:
    • Adapter Type: HTTP Receiver
    • Transport Protocol: HTTP 1.0
    • Message Protocol: XI Payload in HTTP Body
    • Adapter Engine: Integration Server
    • Addressing Type: URL Address
    • Target Host, Service Number,and Path need to be set in accordance with the SAP BC routing rule. HTTP Proxy Host and HTTP Proxy
    Port can be set if required.All other parameters have no corresponding values in SAP BC and should be set to their default values.
    regards
    Aashish Sinha
    P : Reward points if helpful

  • Migrating sapwsdl file using SAP ES Explorer

    Is there any way to use the existing sapwsdl file which is created using SAP connector to SAP ES Explorer?
    Our aim is to use the SAP ES Explorer with Visual Studio 2005 version.
    Or is there any other way to migrate the application using SAP ES Explorer without using service registry.Please reply as soon as possible as we are not able to proceed further.
    Thank You,
    Juhi

    Hi Juhi,
    Pls. find my comments below-
    >>Is there any way to use the existing sapwsdl file which is created using SAP connector to SAP ES >>Explorer?
    Well, you need to understand that the working and underlying principles of Connector and ES explorer is different.
    1.SAP Connector is there to expose the RFC/BAPI from SAP ERP system and provide design time and runtime support for application development.
    2. ES explorer provides access to the services published into Service Registry, which can be consumed by application.
    >>Our aim is to use the SAP ES Explorer with Visual Studio 2005 version.
    >>Or is there any other way to migrate the application using SAP ES Explorer without using service >>registry.Please reply as soon as possible as we are not able to proceed further.
    Bottom line is, if you want to use ES Explorer you would have to ensure that there exists a Service Registry and Services are publish in that.
    Hope to clarify some of your points.
    Regards.

  • Migration of training catalogue (SAP HR)

    Hi,
    Can anybody tell me if there are some standards sap programs to migrate the training catalogue from a flat file system to new sap system.
    thanks
    Abdel Bakkali

    SAP Easy Access > SAP Menu > Organizational Management> Organizational Plan > Organization and staffing > PPOCE
    SAP Easy Access > SAP Menu > Organizational Management> Organizational Plan > Organization and staffing > PPOME
    SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD Change
    SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD Change > Go to > Reporting structure
    SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD > Go To > Account Assignment > maintain cost center
    SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Position
    SAP Easy Access > SAP Menu > Organizational Management> Organizational Plan > Organization and staffing > PPOCE
    SAP Easy Access > SAP Menu > Organizational Management> Organizational Plan > Organization and staffing > PPOME
    SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD Change
    SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD Change > Go to > Reporting structure
    SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD > Go To > Account Assignment > maintain cost center
    SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Position
    SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD > Go To > Account Assignment
    SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD > Go To > Cost Distribution
    i willl let u know abt the rest
    Edited by: Sikindar on Dec 13, 2008 11:21 AM

  • Migration of "CRONACLE for SAP solutions" to "SAP CPS for Netweaver"

    Hi,
    We have standalone  Cronacle/CPS 6.02.  We are in the process of researching about migrating to  "SAP CPS for Netweaver"  like SAP CPS M33. We have the following questions.
    1)Is a migration path available to migrate from "CRONACLE for SAP solutions" to "SAP CPS for Netweaver" ?.
    2)What are the benefits of going to "SAP CPS for Netweaver" ?.
    3)Is the migration can be done by ourselves or any SAP migration consultant is required?.
    Please advise.
    Thanks.
    Raj.

    Hi Laurence, Raj,
    This question is very old and I had not seen it before.
    To upgrade from CPS 6.0.2 or 7.0.4 to 8.0.0 (aka M33). I do not know if SAP consultancy offers anything for this, you want to check with them. SAP might refer you to Redwood, though.
    As for the differences, where do I start ... ;-)
    Actually, CPS 8 is a major platform shift. Version 6 and 7 were PL/SQL-based solutions, version 8 is Java-based. You have many more possibilities built-in, such as better XBP 3.0 support, web services, SAP BusinessObjects, SAP PI/XI control, ... the list could go on forever.
    Some older platforms (very, very old) are no longer supported, afaik, but you get native z/OS (mainframe) platform agents, AS/400 agents ... the user interface is platform independent, so you can access it from any OS including, but not limited to, Windows, Unix, Linux, and Mac OS X. There is even an iPhone/iPad client.
    BTW, I do not know how long version 6 and 7 are supported.
    The platform shift means that you might have to use a PL/SQL API in version 8. I guess it depends on how much PL/SQL you use. If most of your jobs are SAP and OS jobs, you would not even need that.
    Regards,
    HP

  • Migration from UC4 to SAP CPS

    All Experts,
    Currently we are running UC4 for our batch scheduling requirements and are considering to migrate to SAP CPS.
    We have around 10K+ jobs to be migrated from UC4 to SAP CPS.
    Does SAP provide any migration tool for this? or we have to do it manually?
    Kindly suggest any other vital information related to this topic.

    Hello,
    Migration services for migrating other scheduler solutions to SAP CPS automatically are available through Redwood Services, they have years of experience in this area. You can contact your account representative on the complete details.
    Regards Gerben

  • Is there any upragde tools for SAP B1 to SAP ERP?

    Hi,
    I know, SAP B1 and SAP ERP are totally different SAP products.
    In my mind, maybe we should implement the new SAP ERP, and then, migrate the old master data from B1 to ERP...
    So, is there any upragde tools or procedure (or data migration tools)for the project of upgrade SAP B1 to SAP ERP?
    Is there any documentation for this?
    Many thanks in advance.
    BR,
    Randy

    It is not listed on the official roadmaps
    Lumira:
    https://websmp206.sap-ag.de/~sapidb/011000358700000212382013E.pdf
    Analysis Office:
    https://websmp206.sap-ag.de/~sapidb/011000358700000395262012D.pdf
    For Lumira we asked at BI 2014 the other week and they said they were working on it.
    You can register for this ASUG Analysis Office Roadmap and ask SAP on the webcast about it:
    May 12: Analysis Office Roadmap
    Same for Lumira - see these upcoming ASUG webcasts - especially Q&A:
    May 15: Lumira Self Service for Business User
    May 21: SAP Lumira Question and Answer Session

  • Replacing SAP BC by SAP XI

    Hi All,
    we try to replace a SAP Business Connector installation by a SAP XI 2.0 installation.
    We currently exchange IDOCs via SAP BC over http(s) with our suppliers. If we substitute SAP BC by SAP XI we don't want our suppliers to be affected. So the http(s) post from XI should be identical to the SAP BC http post.
    Unfortunately the two posts differ on header fields and parameter passing like the following example shows.
    <b>SAP BC post:</b>
    <i>  POST /LieferantB HTTP/1.0
      User-Agent: Mozilla/4.0 [en] (WinNT; I)
      Accept: image/gif, /
      Host: fs6509.hannover.is-energy.de:8891
      Content-type: application/x-sap.idoc
      X-tid: 0A108469607640D99CD00535
      Content-Length: 14248</i>
    <b>SAP XI post:</b>
    <i>  POST /LieferantB?msgguid=40D77B9EF194003602000000C0A8BD3F&bs=ISE_BS_Auftraggeber_ise&namespace=urn%3ais-energy%2ede%2fbestellwesen&interface=ORDERS%2eORDERS02&qos=EO HTTP/1.0
      content-type: application/x-sap.idoc
      content-length: 4743
      connection: close
      accept: /
      user-agent: SAP Web Application Server (1.0;620)
      host: fs6509.hannover.is-energy.de:8891
      accept-encoding: gzip</i>
    So how may I get rid of the ?msguid=...?bs=... stuff?
    And what's about the X-tid of the SAP BC post?
    Any hints even links to documentation are welcome!
    Regards
    Marc

    Hi,
    >>>>Can i use SAP BC adapter in my XI and use everything that is being used in SAP Business connector
    Answer is no. But for BC to XI migration there is lots of documents available. I also posted some of them in your earlier posts for same issues.
    Can you please close that thread and opn only one thread for one subject.Also mark that thread answered.
    Please refer your unanswered link.
    Re: Migration from SAP BC To SAP P.I?
    Regards
    Aashish Sinha
    PS : reward points if helpful

  • Open HUB ( SAP BW ) to SAP HANA through DB Connection data loading , Delete data from table option is not working Please help any one from this forum

    Issue:
    I have SAP BW system and SAP HANA System
    SAP BW to SAP HANA connecting through a DB Connection (named HANA)
    Whenever I created any Open Hub as Destination like DB Table with the help of DB Connection, table will be created at HANA Schema level ( L_F50800_D )
    Executed the Open Hub service without checking DELETING Data from table option
    Data loaded with 16 Records from BW to HANA same
    Second time again executed from BW to HANA now 32 records came ( it is going to append )
    Executed the Open Hub service with checking DELETING Data from table option
    Now am getting short Dump DBIF_RSQL_TABLE_KNOWN getting
    If checking in SAP BW system tio SAP BW system it is working fine ..
    will this option supports through DB Connection or not ?
    Please follow the attachemnet along with this discussion and help me to resolve how ?
    From
    Santhosh Kumar

    Hi Ramanjaneyulu ,
    First of all thanks for the reply ,
    Here the issue is At OH level ( Definition Level - DESTINATION TAB and FIELD DEFINITION )
    in that there is check box i have selected already that is what my issue even though selected also
    not performing the deletion from target level .
    SAP BW - to SAP HANA via DBC connection
    1. first time from BW suppose 16 records - Dtp Executed -loaded up to HANA - 16 same
    2. second time again executed from BW - now hana side appaended means 16+16 = 32
    3. so that i used to select the check box at OH level like Deleting data from table
    4. Now excuted the DTP it throws an Short Dump - DBIF_RSQL_TABLE_KNOWN
    Now please tell me how to resolve this ? will this option is applicable for HANA mean to say like , deleting data from table option ...
    Thanks
    Santhosh Kumar

  • Log On problem via webgui. sap/bc/gui/sap/its/webgui

    Hello, would you be so kind to help me in my problem.
    I have sap web as 7.00, and i have published a service for using "sap gui for html" via browser from the Remote Place.
    http://........./sap/bc/gui/sap/its/webgui
    icm/server_port_0 i made 80 in the profile
    (icm/server_port_0     = PROT=HTTP,PORT=80).
    But there is such a problem.
    When u try to connect using this url it gives u the log on screen to enter your user/password (u can even change it!!)
    but when you try to log on it just refreshes the screen and nothing actually happens.
    The same time when you are doing it licaly in the office everything works fine.
    Does anybody know what can be the solution of this problem?
    Dmitry.

    Hi! &#1055;&#1088;&#1080;&#1074;&#1077;&#1090;.
    Well i have tried to use this transaction (SIAC_PUBLISH_ALL_INTERNAL) and it published a lot of services, but still i can't log on from home, for example, to the system in our office where ICM and ITS are running.
    I found an interesting link
    /people/durairaj.athavanraja/blog/2005/08/21/running-your-first-its-webgui-application-in-sap-netweaver-04-abap-edition--nsp
    And i tried mannually to publish "SYSTEM"  and "SHUFFLER" services. The same time "WEBGUI" service works fine in the office. Those two i also can publish, but i can't start them in SE80.
    It is written that
    sap/bc/gui/sap/its/system/ call was terminated because the corresponding service is not available. And i can't find such a service following that link... Still it shows that it has been published.
    May be it is so because i can't test the service
    /default_host/sap/public/bc/its/mimes
    The error is
    The URL http://.../sap/public/bc/its/mimes was not called due to an error.
    Note
    The following error text was processed in the system S01 : Illegal access to a string (offset too large)
    The error occurred on the application server s00-5000_S01_01 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: SPLIT_PATH_GIVE_ROOT of program CL_IAC_HELPER=================CP
    Method: SPLIT_PATH_GIVE_SERVICE of program CL_IAC_HELPER=================CP
    Method: GIVE_MIME_CONTENT_USING_PATH of program CL_IAC_HELPER=================CP
    Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_HTTP_EXT_ITS_MIMES=========CP
    Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
    Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
    Module: %_HTTP_START of program SAPMHTTP

  • Is this possible: SNC connection from SAP GUI to SAP Router, and ...

    Hi,
    I have (stupid perhaps) question.
    Is this scenario possible:
    SNC connection from SAP GUI to SAP Router, and non-SNC connection from SAP Router to SAP System.
    I know how to set up scenario like this:
    SAP System --- (non-SNC conn) --- saprouter1 --- (SNC conn) --- saprouter2 --- (non-SNC conn) --- SAP GUI.
    Best regards,
    Marek Majchrowski

    Wolfgang,
    To be sure myself and Marek understand, can you confirm the different scenarios supported:
    Scenario 1:
    SAP GUI --- (non SNC conn) --- saprouter1 --- (SNC conn) --- saprouter2 --- (non-SNC conn) --- SAP System
    With this scenario, it would be possible for a user to logon using SAP GUI onto the SAP System, but without SAP GUI SNC.
    Scenario 2:
    SAP GUI --- (SNC conn) --- saprouter1 --- (non SNC conn) --- saprouter2 --- (SNC conn) --- SAP System
    With this scenario it would be possible to logon to the SAP System using SAP GUI, and using SNC authentication.
    Also, with this scenario the SAP GUI software and SAP System software would consider this to be similar to:
    SAP GUI -- (SNC conn) -- SAP System
    Scenario 3:
    This is the scenario mentioned by Marek in his initial question:
    SAP GUI -- (SNC conn) -- saprouter1 -- (non SNC conn) -- SAP System
    With this scenario it will not be possible to logon to SAP System using SNC, and only possible if the SAP GUI is configured to not use SNC. In other words the SNC connection between SAP GUI and saprouter1 is available, but cannot be used.
    Thanks,
    Tim
    Edited by: Tim Alsop on Feb 25, 2008 5:24 PM

  • Com.sap.portal.appintegrator.sap doesn't work

    Hi all,
    I needed to change the file 'WinGuiRenderLayer.properties'
    I found the par under 3 locations:
    d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap
    d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
    d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\temp
    I changed the file in those locations (I removed the bak extension and restarted the server).
    Also, I made sure that the pars/directory contains the jar files.
    After I restarted the server the application integrator iviews doesn't work (Web Dynpro, Transaction...).
    Before I did the changes, I backed up the original pars/directory.
    Copying the original pars didn't help.
    How can I solve this?
    Portal is EP6.16
    Attched exception details:
    Date : 10/25/2007
    Time : 13:56:51:765
    Message : [PortalNode.fireEventOnNode.toEventListener] event=onNodeReadyEvent, target=com.company.Orders, operation failed
    [EXCEPTION]
    com.sapportals.portal.prt.component.PortalComponentException: Error in init method
    Component : com.sap.portal.appintegrator.sap.WebDynpro
         at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
         at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
         at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
         at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
         at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
         at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
         at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
         at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
         at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
         at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
         at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
         at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
         at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
         at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
         ... 41 more
    Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
    Loader Info -
    ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
    Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
    References:
       not registered!
    Resources:
       D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
       D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
    The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
         at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
         ... 45 more
    Severity : Warning
    Category : /System/Server
    Location : com.sap.portal.portal
    Application : sap.com/irj
    Thread : SAPEngine_Application_Thread[impl:3]_27
    Datasource : 6397450:D:\usr\sap\SPD\JC00\j2ee\cluster\server0\log\defaultTrace.trc
    Message ID : 000E7F3049DE005C0000002100001C4000043D4FEE02FB46
    Source Name : com.sap.portal.portal
    Argument Objs : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
    Component : com.sap.portal.appintegrator.sap.WebDynpro
         at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
         at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
         at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
         at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
         at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
         at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
         at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
         at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
         at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
         at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
         at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
         at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
         at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
         at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
         ... 41 more
    Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
    Loader Info -
    ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
    Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
    References:
       not registered!
    Resources:
       D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
       D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
    The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
         at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
         ... 45 more
    Arguments : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
    Component : com.sap.portal.appintegrator.sap.WebDynpro
         at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
         at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
         at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
         at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
         at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
         at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
         at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
         at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
         at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
         at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
         at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
         at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
         at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
         at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
         ... 41 more
    Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
    Loader Info -
    ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
    Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
    References:
       not registered!
    Resources:
       D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
       D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
    The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
         at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
         ... 45 more
    Dsr Component : <Server Name>
    Dsr Transaction : 5a4c6ec082f111dccf17000e7f3049de
    Dsr User : <User>
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 1
    Relatives : /System/Server
    Resource Bundlename :
    Session : 44
    Source : com.sap.portal.portal
    ThreadObject : SAPEngine_Application_Thread[impl:3]_27
    Transaction :
    User : <User>
    Thanks,
    Omri

    Solved it.
    This is what I did:
    1) Took par from my production environment (same SP level)
    2) Clear the par (by using 'Archive Remover')
    3) Clear the pcd cache
    4) Upload the par (redploy)\
    5) Restart the portal
    Thanks,
    Omri

Maybe you are looking for

  • Issue at runtime with Mapping in orchestration.

    Hi All, I am getting the below issue at runtime in the orchestration. Exception thrown from: segment 1, progress 16 Inner exception: Error encountered while executing the transform C_BT.Orchestrations.CheckInvalidRecords. Error:Invalid input/output d

  • Problem in password recovery

    I am suffering from the problem of the restoration of the password is the first time you log in, and I've been showing me the error message that the password is incorrect and the truth password is incorrect I've restore password from email, but I fig

  • 0xc0000428 error code on boot no installation media

    When I turn on my laptop it comes up with the blue screen of death and it says recovery at the top. It then says error code: 0xc0000428 I'm not an IT wiz and have no idea how to solve it. Can anyone help

  • Dashed Line in Smartform

    Hi, I wanted to know how we can draw a dashed vertical line in smartform.

  • Working with folders Folders

    Can anyone help me????? I work with folders in logic 7.2.3 for example I have my drums in a folder, vocs in a folder, as well as guitars and other instruments. The problem occurs when I record say vocals, because after the recording stops logic jumps