Warning#1#com.sap.sup.admin.scheduler.JmsScheduler#Plain

hi
In our SAP portal server's default traces and application logs we are constantly seeing warning messages as follows
#1.#00144F54B441000A0000007800002B75000456B6617AB4F7#1221241226310#com.sap.sup.admin.scheduler.JmsScheduler##com.sap.sup.admin.scheduler.JmsScheduler####n/a##6db45ff07fa211ddc2a600144f54b441#SAPEngine_System_Thread[impl:5]_54##0#0#Warning#1#/Applications/AdminConsole/Scheduler#Plain#[3989] The Scheduler is inactive: the Maintenance Mode is enabled!###
could you guide on how do we get rid of this warning messages as this is filling up the filesystem
Thank you
Jonu Joy

hi
When i stop this application from NWA    - tcwebadministratorsolmandiag
which is a part of LM Services Patch 15,  i do not see the warning messages any more in my j2ee application logs and default traces.
Thank you
Jonu Joy

Similar Messages

  • How to get this  com.sap.portal.admin.wizardframework_api.jar file

    Hi this is related to the wizard creating component required .jar file. Can any body tell me , how to get this jar file. I have searched in my IDE plug-in's folder. But i have nt find this.
    com.sap.portal.admin.wizardframework_api.jar
    how to get thid jar file.
    REgards
    Vijay

    Hi,
    You should have com.sap.portal.admin.wizardframework in your SharingReference:
    <property name="SharingReference" value="com.sap.km.application, com.sap.portal.admin.wizardframework"/>
    Pls check this link,
    http://help.sap.com/saphelp_nw2004s/helpdata/en/42/bf4172cb951d66e10000000a1553f6/content.htm
    Hope this helps !
    Regards
    Srinivasan T

  • How to get the com.sap.portal.admin.wizardframework_api.jar file

    Hi this is related to the wizard creating component required .jar file. Can any body tell me , how to get this jar file. I have searched in my IDE plug-in's folder. But i have nt find this.
    com.sap.portal.admin.wizardframework_api.jar
    how to get thid jar file.
    REgards
    Vijay

    Vijay,
    You can access the above mentioned par file from this location,
    System Admin -> support -> Support Desk->ROOT/WEB-INF/deployment/pcd (download this folder)
    ->com.sap.portal.admin.wizardframework.par.bak->extract the file
    alternatively,
    u can find the same in,
    \j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.admin.wizardframework\lib
    Thanks & Regards,
    Ramganesan K
    Keane Inc

  • Com.sap.portal.admin.acleditor.par not deployed properly during ep install

    Hi,
    We are installing ep on top of a java add-in.
    The version of ep is sp3. After the installation when i check the pcd folder coom.portal.admin.acleditor.par is not deployed.
    Log has Fatal applciation upload failed. and there is some error which says xml declaration is not allowd here.
    When i try to access the portal page its loading for a long time and giveing page cannot be displayed.
    Portal analyzer gives clean results except for this par file.
    Please help.
    Regards
    Bharathwaj

    Hi Bharathwaj,
    > Do you think the upgradation of the this
    > to SP13 will solve the issue. ??
    No, I wouldn't advise to upgrade a really broken installation. You may give it a try, but the success probability I wouldn't expect as too high...
    > Does a EP upgrade create a clean install again..
    > or just add a few more files ???
    It deploys new portal applications and/or redeploys existing ones which have changes (bug fixed). So theoratically if a PAR is broken, a new one may be fixed; on the other hand, the installation seems to be buggy in it's kernel, in such a case, the root cause seems to be something else than "only" one failed PAR upload.
    > Is there any log file which says what are the steps
    > it had skipped..
    Beneath the default.trc to check for the portal runtime, SAPInst has it's own logs under the temporary inst dir.
    Hope it helps
    Detlev

  • JCO - RFC_ERROR_SYSTEM_FAILURE: com/sap/mw/jco/JCO$Server

    Hi,
    I call from Java an ABAP RFC and this RFC in turn call back the Java stack and it fails.
    At Java side I get:
    #1#com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: com/sap/mw/jco/JCO$Server
         at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)
         at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1515)
         at com.sap.mw.jco.JCO$Client.execute(JCO.java:3996)
         at com.sap.mw.jco.JCO$Client.execute(JCO.java:3544)
         at com.sap.sup.admin.setup.SolManRfcAdapter.getJabapLandscape(SolManRfcAdapter.java:787)
         at com.sap.sup.admin.setup.SetupUpgrader.execute(SetupUpgrader.java:52)
    At ABAP side I get:
    Category               ABAP Programming Error
    Runtime Errors      CALL_FUNCTION_REMOTE_ERROR
    ABAP Program      CL_DIAGLS_SMSY_FACTORY========CP
    Application Component  SV-SMG-DIA
    Date and Time        21.09.2009 17:50:59
    Short text
         "com/sap/mw/jco/JCO$Server"
    Is it allowed to call JAVA -> ABAP -> JAVA from JCO point of view?
    Thanks in advance!
    Regards,
    Serge.

    Hi Serge,
    Two doubts:
    - Does your RFC work when you call it directly from the SE37 puting the same input parameters used by Java application?
    - Was the RFC changed after the coding of Java application? If so, the interface between Java and RFC must be regenerated.
    Regards,
    Rodrigo.

  • Why I upload com.sap.portal.usermanagement.admin.par,Portal can't modify?

    Hi,
    I change jsp in com.sap.portal.usermanagement.admin.par ,then upload it to PCD,but the portal can't change?
    what can i do?
    Thanks.

    Login with System Admin user and then Goto
    System Admin---> Support --> Portal Runtime --> Admin Console
    Now you have to clean the existing Add with the name
    com.sap.portal.usermanagement.admin.par
    if you come down to Admin Console you can find all the Par App by DropDown Box
    select the com.sap.portal.usermanagement.admin.par and clean it
    Now upload you updated com.sap.portal.usermanagement.admin.par to Pcd
    Thanks,
    Sreeni.

  • How to change com.sap.portal.usermanagement.admin.par file

    Hi
    Requirement is
    1)using com.sap.portal.usermanagement.admin.par file provide the UserUpdate view(With out developing ur own GUI and code to update the userprofile).
    2)Department and Position is not visible to the user at the time of updation.
    so to achive this i imported com.sap.portal.usermanagement.admin.par file into NWDS after that i have confiused to change the files. can u give the procedure to follow the things.
    Regards
    Srinivasu.y

    Hi,
    Your question is not clear. Second, people are bound to get offended if words like "Urgent Requirement" or words like "clearly state the files " is used.
    Please clearly state the requirements. If people know the solution they would answer it. This is not a support portal , so please make sure that you do not offend the community.
    Go through this link
    <a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=285259&tstart=0">Rules of Engagement</a>
    And do state your question clearly.
    Thanks and Regards
    Bharathwaj

  • Failure in Model Create Step: com.sap.mw.jco.JCO$Exception: Missing R3NAME=

    Hi,
    I am running NW04sp10 and am trying to connect my WebDynPro to my R/3 backend app server - am running through the FlightChecking example using DevStudio 2.0.10.
    Have successfully created my meta + app data JCo's, they test and ping OK from the Content Manager.  SLD is fine, connecting happily to the NW and R/3 boxes.  One is message server, one central instance.
    When the 'create model' wizard tries to build the java proxies though, it comes back with this:
    [Fatal]:     com.sap.mw.jco.JCO$Exception: Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
    Can anyone help?
    Cheers guys,
    Andy

    Hi Wael,
    I'm using the tutorial 'Handling Transactions with BAPIs in Web Dynpro' [part of SAP Online Help].
    The BAPI does work in se37, it's just a standard SAP delivered BAPI, and I've tried a few different ones to make sure it wasn't a BAPI specific problem.
    In the content admin I've navigated through the local/FlightChecking/Applications/FlightCheckingComp and then used the wizard to add the 2 JCOs [I've kept the default names for now after your previous advice]
    The data is like this:
    WD_MODELDATA_DEST:
    Name                  WD_MODELDATA_DEST
    Client                800
    J2EE Cluster Name     NW1 on chippy
    USER                  USER1
    Password              <password>
    Application Server    nero
    System ID             00
    WD_RFC_METADATA_DEST:
    Name                  WD_RFC_MODELDATA_DEST
    Client                020
    J2EE Cluster Name     NW1 on chippy
    USER                  USER1
    Password              <password>
    Application Server    chippy
    System name           NW1
    Logon Group           PUBLIC
    My landscape here is of 2 servers:
    'Nero'    SAP r/3 4.7 Application Server System ID ACI
    'Chippy'  SAP WebAS640 NW04 System ID NW1 ABAP+J2EE stack
    The JCOs 'test' and 'ping' successfully.  My WD_RFC_METADATA_DEST connection is to a message server, the WD_MODEL_DEST is to a central instance.
    Here's the full log from the create model wizard [I used a random BAPI for testing, BAPI_GET_PAYSLIP, so don't worry about that]:
    [Warning]:     Creating a connection with Metamodel language <en_GB> failed.  Continuing with language <EN>
    [Fatal]:     com.sap.mw.jco.JCO$Exception: Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
    [Info]:     Creating Model: FlightChecking
    [Info]:     Creating Model Class: Bapi_Get_Payslip_Input
    [Info]:     Creating Model Class: Bapi_Get_Payslip_Output
    [Info]:     Creating Model Class: Bapireturn1
    [Info]:     Creating Model Relation: Bapi_Get_Payslip_Output:Return
    [Info]:     Creating Model Class Property: Type
    [Info]:     Creating Model Class Property: Id
    [Info]:     Creating Model Class Property: Number
    [Info]:     Creating Model Class Property: Message
    [Info]:     Creating Model Class Property: Log_No
    [Info]:     Creating Model Class Property: Log_Msg_No
    [Info]:     Creating Model Class Property: Message_V1
    [Info]:     Creating Model Class Property: Message_V2
    [Info]:     Creating Model Class Property: Message_V3
    [Info]:     Creating Model Class Property: Message_V4
    [Info]:     Creating Model Class Property: Employeenumber
    [Info]:     Creating Model Class Property: Payslipvariant
    [Info]:     Creating Model Class Property: Sequencenumber
    [Info]:     Creating Model Class: Bapi7004_Payslip
    [Info]:     Creating Model Relation: Bapi_Get_Payslip_Input:Payslip
    [Info]:     Creating Model Class Property: Format_Col
    [Info]:     Creating Model Class Property: Text_Col
    [Info]:     Creating Model Relation: Bapi_Get_Payslip_Output:Payslip
    [Info]:     Creating Model Relation: Bapi_Get_Payslip_Input:Output:Bapi_Get_Payslip_Output
    So it seems to actually be able to retrieve the metadata for the BAPIs, but not to make the relevant JCo's.  I've not gone on and completed the tutorial, assuming it won't work until I can sort out the above 'fatal' error.
    Thanks again for all of your good advice.
    Cheers,
    Andy

  • Com.sap.portal.connectivity.destinations.PortalDestinationsServiceException

    Hi
    I am getting this error for some users in the portal.
    com.sap.portal.connectivity.destinations.PortalDestinationsServiceException:User is missing credentials for connecting to alias SAP_R3_humanResources.
    This is only happenning for some of the users at the moment and I cannot figure out what is causing it.
    We have:
    EP7 for Online Expenses
    ECC6
    I have re-registered the WebFlowConnector just to see if thats the problem.
    I have checked the users portal roles and his backend roles and all are OK
    I have also checked the Web Dynpro connector for SAP_R3_HumanResources.
    Can anybody help me out on this please.
    Many Thanks
    Steve

    Got this from SAP
    1st reply
    The UWL_service was introduced in NW 700. So, 1133821 will not be relavant for NW 6.40. However, in 640 system we use Basis plugins.
    So, to check that please provide me the complete backend system version. The UWL uses functions from the Basis plug in instead of the Enterprise Portal plug in (WP-PI 6.0) for back end systems using Release 640. Support Package 12 makes the necessary functions available in the Basis. You can make the necessary changes in the Basis plug in (PI_BASIS) using notes or Support Packages.
    Could you please check which release are you on? Remember after you applies this (SP12), you will need to reregister the UWL system in the system admin on the portal. *This is not only for substitution, but for other functionality as well* We recommend this for 640 systems in general that the PI_BASIS is maintained at the highest level.
    This warning message will occur for users that do not have access to the systems that are configured in the UWL UI. For example, if we have 1. BW system 2. SRM system, and you 'steve', are able and have access to the BW system, but do not have a Userid in SRM backend, you will receive this msg. This is normal behaviour for the Universal worklist. So your option there would be to create a dummy id for you on the backend system so that your id can connect but that you don't have auth to.
    2nd reply
    You seems to be on lower version for Basis Plug-ins. The basis plug in should be at version 12 or higher and is at version 9. You will need to ensure that the users exist in both systems to get rid of the warning messages. Details for the Basis Plug-ins can be found on Note:883558.
    3rd reply
    If I am right then you are talking about the solution provided to get rid of the warning message.
    So, in this regard as Steve already mentoned The Portal is an EP7 portal running on NW 7.0 SP20. It has to connect to {2 different R3 backends}.
    1. ECC 6 running on NW 7.0 and UWL is configured with a SAP_ECC_TRAVEL WebFlow Connector (this works perfectly)
    2. ECC 5 running on NW 6.40 and UWL is configured with a SAP_R3_HumanResources WebFlowConnector (please see attachment for error)
    So, In reply to this I mentioned that to get rid of the warning message you have create users in both the systems. May be you do not grant authorization as per your requirement.
    because these warning message are been displayed because the UWL UI havebeen configured to pull tasks from 2 backends. and User logging in mighthave access to only one backend system so, that's the reason for other R3 system they get the warning message.
    Or if there is a concern with basis Plug-ins then it will be adviced to refer to the Notes, as those are system requirement.

  • Error after inital login to EP6 SP4: com.sap.portal.frameworkpage

    Dear all,
    I'll be very thankfull if somebody could give me a hint:
    Initially we've installed an EP6 SP3 on WAS 6.40 J2EE SP3. After that we've applied SP4 for the WAS 6.40 and then SP4 for EP6.
    When to login to the portal for the first time after installation with the Admin-User "Administrator", i get the following error message:
    "error occurred while trying to access framework page: "pcd:portal_content/com.sap.pct/every_user/general/com:sap.portal.frameworkpage", The object does not exist or you are not authorized to access it....
    Any idea about the problem ?
    Thanks a lot in advance,
    Jörg

    Hello
    I had the same message yesterday.
    In my case, it cames from a rule in main_rules that mapped the user to an invalid Desktop (in fact, a desktop with an invalid workset).
    If you got a user that does not have this problem, you may go to system admin / portal display / rules & desktop. Under super-administration, the objet main_rule is the object to change.
    if you can not login with any user, then you may access directly the page using the URL described in
    Re: Portal Desktop Deleted and cannot log on
    Hope it helps
    Guillaume PATRY

  • URL Navigation not working for non-super admin

    I am trying to set up a URL navigation to Home>>Portal Information page in End-User role, so I created a URL as
    http://portalserver/irj/portal?NavigationTarget=ROLES://portal_content/com.sap.pct/every_user/general/pages/com.sap.portal.portal_information
    This link works fine for users in super admin role. For other users, this link bring them into EP and show a page with no content (only header and TLN). Does anyone know where to look to fix this? All users can go to Home>>Portal Information via normal navigation

    Hi Ben,
    this is sometimes confusing, as there are quite some "Portal Information" Pages in the PCD. Some are as objects in the Portal Content Studio Navigation (as the one you mentioned), some are copied in Roles like the End-User-Role and not linked by Delta-Link.
    The best thing to do is to login with a normal user, navigate to Home -> Portal Information, and from the Page Title Bar - Context Icon you choose "Add to Browser Favorites". In your Browser Bookmarks you will then see the correct NavigationTarget.
    My guess is that it will be: http://portalserver/irj/portal?NavigationTarget=ROLES://portal_content/every_user/general/eu_role/com.sap.portal.eu_ws/com.sap.portal.portal_information
    Hope this helps,
    Robert

  • Calendar Notification + Google Apps + Super Admin + Macs + Notifications

    Background: I’m a Google Apps Super Admin which means that I have access to almost everything, including everyone’s calendar.  They show up under “My Calendar”
    Issue: I have a few users under our account. ALL of their calendar’s show up on my account (it’s a super admin thing, cant be removed because that’s the way it is).  My problem is that, I get notification for EVERYONE, for every event… because as far as the system is concerned, ALL of their calendars are my calendar.  This is specifically annoying because every 15/30 mins or hour I get everyone’s notifications on my iPhone, mac, etc.
    No I don’t want to set up another account and set them as admin, it causes too much confusion.
    Please reply if you actually know about resolutions rather than speculations. I’ve had many threads where it went on forever because everyone thought they were an expert (I say this with totally respect).

    This may give you results you seek - if you mainly just want the alerts to stop on your iOS devices
    http://n8henrie.com/2012/12/google-calendar-delegates-and-mountain-lion-calendar /
    I'm also a gApps admin and have had similar issues. USUALLY, I could simply uncheck co-workers calendar listed in 'My Calendars' or 'Other Calendars' ( yes, they can appear in either place, don't ask, it's a Google Admin stupidity) to hide their schedule from my calendar. USUALLY, if i didn't see their schedule, I wouldn't see any alerts on my iOS hardware.
    BUT. One colleague kept showing up no matter what.
    I noticed most alerts I saw were invites, awaiting for me to accept (although I obviously was NOT) so I've tried the following on my iPhone (iOS 7)
    Go into Settings > Mail, Contacts, Calendars
    (scroll down to Calendars section at bottom)
    Turn OFF New Invitation Alerts
    Your mileage my vary.
    I finally decided I don't typically need my co-workers schedule on my iPhone, so I went nuclear and went to my Google – iPhone/iPad calDav settings found at this Link: https://www.google.com/calendar/syncselect and turned off ALL of my co-worker calendar calDav syncing.
    If you DO occasionally need to look at your co-workers schedules, use the iOS google calendar Web App:
    Visit your Google Apps using Safari on your iPhone, iPad, etc.
    Go to the Calendar and
    Add it as a Web App to your iDevice (http://blog.blueleaf.com/how-to-save-your-favorite-website-as-an-iphone-app-vide o/)
    Now when you need to check co-workers schedules – launch your new gCal webApp and scroll to the bottom, click the settings button to choose which co-worker schedule you want to view, save and voila.
    Hope this helps.

  • TmHttpclientPool-664 [com.sybase.sup.server.http.TmApplicationHandler] [] [] On connection expired .....

    Hello,
    We have SAP CRM REX 3.1.9 installed for our client with iPad as frontend.  Im getting following error in the SUP prod environment.
    this error did not occur in QA or Dev system anytime during our testing.
    2014-04-01 15:26:12.687 INFO    MMS          TmHttpclientPool-664 [com.sybase.sup.server.http.TmApplicationHandler] [] [] On connection expired .....
    2014-04-01 15:27:08.419 INFO    MMS          TmHttpclientPool-664 [com.sybase.sup.server.http.TmApplicationHandler] [] [] On connection expired .....
    2014-04-01 15:28:05.939 INFO    MMS          TmHttpclientPool-664 [com.sybase.sup.server.http.TmApplicationHandler] [] [] On connection expired .....
    2014-04-01 15:30:39.481 INFO    MMS          TmHttpclientPool-664 [com.sybase.sup.server.http.TmApplicationHandler] [] [] On connection expired .....
    2014-04-01 15:31:16.950 INFO    MMS          TmHttpclientPool-664 [com.sybase.sup.server.http.TmApplicationHandler] [] [] On connection expired .....
    Sync doesn't work at first time for most of the Users but repeated sync requests finally end up having a successful sync at some point of time.
    System landscape is
    - 2 SUP server
    - 1 DB server
    - devices are connecting through reverse proxy to SUP server from outside
    - Users connect using 3G/4G network or Wifi, I know there is known issue with 3G/4G network connecting to SUP, but Users face same issue while on WIFI also.
    Share your thought if someone has faced/fixed similar issue.
    Regards
    Sameer

    Hi Michael  and all,
    I am also facing the same issue as you, I have installed SUP 2.01 and using Sybase Mobile Sales 1.2.
    I have deployed Mobile Sales application on my windows Mobile simulator also connect to the device created in Sybase control center.
    When i try to connect Mobile Sales application to the server, initially it shows downloading Activity,leads, Opportunity etc in the status bar, but after some time, it kept saying Checking for Initial Data, and runs never ending. And we are not facing any connectivity issues.
    In DOE Session Monitoring we can see status of all the data Objects without errors.
    When we checked in the DOE logs, we are getting below 2 warning.
    Unable to determine dialect of the StAX implementation at jar:file:/C:/Sybase/UnwiredPlatform/Servers/UnwiredServer/lib/ext/sup-ds.jar!/
    Anonymous transaction context. Any attempt to acquire a transactional resource in this context might result in a resource
    Micheal, did it work for you further, can you suggest anything on this issue.
    Your help will be appreciated.
    Thanks and Regards,
    Peter Dinesh.

  • Com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or passwo

    Hi All,
    I'm configuring the Solution Manager Diagnostics.
    I have all my agent SMD and IS installed.... but when I run the Setup Wizard, I received the following error:
    Step Wilyhost Agent Details
    Created destination BD1_DVEBMGS00_server0
    Created destination SapStartSrv_bnsr3dci_BD1_00
    Created destination BD1|bnsr3dci_BD1_00
    Created action SAP GC|BD1_DVEBMGS00_server0 - SAP GC|BD1_DVEBMGS00_server0
    Created action BD1|bnsr3dci_BD1_00 - SapStartSrv_bnsr3dci_BD1_00
    Created action BD1 - BD1 AbapSystem
    Created action BD1|bnsr3dci_BD1_00 - BD1|bnsr3dci_BD1_00 AbapInstance
    Created 4 action(s).
    0 Wilyhost Agent(s) from host bnsr3dci are connected to the EM.
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (bnssmpci.bns.local:6001) no Wilyhost Agent was detected from host bnsr3dci. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
    and checking the jvm_smdagent.out file on managed system
    Running SMD Agent ...
    [ms://bnssmpci:8101/P4] Agent ready.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Introscope Agent Release 8.0.2.0 (Build 470970)
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Using Java VM version "SAP Java Server VM 1.5.0_17" from SAP AG
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.agentProfile"
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Trying to load file from /usr/sap/DAD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily
    host/IntroscopeSapAgent.profile
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Loaded file from /usr/sap/DAD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wilyhost/Int
    roscopeSapAgent.profile
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging is turned off
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.heartbeatInterval is set to 1800
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.dataChunk is set to 500
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.numberTimeslices is set to 3000
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions director
    y.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] The agent extensions directory /sap_mirrlog/sap/DAD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.ap
    plication.wilyhost/ext was successfully located
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Introscope Agent startup complete.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent SMDA97" based on the value of the System Property "com.wily.introscope.a
    gent.agentName".
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent SMDA97
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Started Error Reporting service
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    10/27/09 02:58:20 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (1).
    Initialization done.
    10/27/09 02:58:30 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (2).
    10/27/09 02:58:40 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (3).
    10/27/09 02:58:50 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (4).
    10/27/09 02:59:00 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (5).
    10/27/09 02:59:11 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (6).
    10/27/09 02:59:21 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (7).
    10/27/09 02:59:31 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (8).
    10/27/09 02:59:41 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (9).
    10/27/09 02:59:51 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (10).
    10/27/09 02:59:51 PM EDT [INFO] [IntroscopeAgent.ConnectionThread] The Agent will continue to attempt to connect to Introscope Enterprise Manager. Further fai
    lures will not be logged.
    [ms://bnssmpci:8101/P4] Agent ready.
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Initialization done.
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    This is error common ?
    Any idea ?
    Weird for me is this line:
    "Failed to connect to the Introscope Enterprise Manager at localhost:6001"
    Because my INtroscope Enterprise Manager name is bnssmpci
    Thanks and Regars,
    Juan.

    SOLVED !!!
    Restart the J2EE Managed System and check the SAP Note - WilyHost agent fails to connect to ABAP stack (bad password

  • 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