Quantcast
Channel: SCN : Popular Discussions - SAP Enterprise Portal: Migration and Upgrade
Viewing all 767 articles
Browse latest View live

Error during phase MAIN_NEWBAS/XPRAS_AIMMRG, upgrade from 7.02 to 7.3 using SUM

$
0
0

Hi,

 

I encountered an error during phase MAIN_NEWBAS/XPRAS_AIMMRG:

 

Checks after phase MAIN_NEWBAS/XPRAS_AIMMRG were negative!

Last error code set: Detected 3 aborted activities in 'XPRASUPG.ELG'<br/> Calling '/usr/sap/S01/DVEBMGS00/exe/tp' failed with return code 12, check /home/SUM/abap/log/SAPup.ECO for details

 

ERROR: Detected the following errors:

# /home/SUM/abap/log/SAPR730XPRA90000048.S01:

       1 ETP109 version and release : "380.08.46" "721"

       1 ETP198

       2 EPU126XPost-import methods for change/transport request: "SAPK730XPRA90000048"

       4 EPU111    on the application server: "linux-q0fx"

       2 EPU122XPost-import method "RS_AFTER_IMPORT" started for "BIXP" "L", date and time: "20140102072421"

       1AETR012XProgram terminated (job: "RDDEXECL", no.: "07242100")

       1AEPU320 See job log"RDDEXECL""07242100""S01"

 

 

SAPup.ECO:

EXECUTING /usr/sap/S01/DVEBMGS00/exe/tp  pf=/home/SUM/abap/var/XPRASUPG.TPP put S01
This is tp version 380.08.46 (release 721, unicode enabled)
Looking for effective putsteps ... ... ready (looking for putsteps)
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT

tp returncode summary:

TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
  A tool used by tp aborted
SAPup> Process with PID 55072 terminated with status 12 at 20140102072449!

 

 

XPRASUPG.ELG:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR730XPRA90000048.S01
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP109 version and release : "380.08.46" "721"
1 ETP198
2 EPU126XPost-import methods for change/transport request: "SAPK730XPRA90000048"
4 EPU111    on the application server: "linux-q0fx"
2 EPU122XPost-import method "RS_AFTER_IMPORT" started for "BIXP" "L", date and time: "20140102072421"
1AETR012XProgram terminated (job: "RDDEXECL", no.: "07242100")
1AEPU320 See job log"RDDEXECL""07242100""S01"
1 ETP111 exit code           : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<

XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.

Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<

 

 

I checked the job log:

Picture1.png

Also checked the message in tcode st22:

 

Category               ABAP Programming Error

Runtime Errors         CONNE_IMPORT_WRONG_STRUCTURE

Except.                CX_SY_IMPORT_MISMATCH_ERROR

ABAP Program           SAPLRSVERS

Application Component  BW-WHM-MTD

 

What happened?
    Error in the ABAP application program.

    The current ABAP program "SAPLRSVERS" had to be interrupted because it contains a statement that cannot be executed.
    When attempting to import data, the structure of the complex object "TH_TRKORR_IMPORT_ALL" was not compatible with
     the target object.

 

Error analysis

    An exception occurred that is explained in detail below.

    The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was

     not caught in procedure "ADJUST_OBJLIST_FOR_IMPORT_ALL" "(FORM)", nor was it propagated by a

     RAISING clause.

    Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated.

    The reason for the exception is:

    When attempting to import data, the structure of the complex object "TH_TRKORR_IMPORT_ALL" was not compatible with

     the target object. The error occurred with component no. "1-11".

 

How to correct the error
    Try to find out why the structure of the object is not correct.
    There are several possibilities:

    1.  The structure of the imported object has changed in the Data
        Dictionary. Make sure that the structure of the imported object
        matches the structure of the object in the Data Dictionary. If
        you cannot restore the data from another source, you must read
        the data using the "old" structure, convert it and reexport it
        using the new structure. This ensures that future IMPORTs always
        use the new structure.

    2.  A new program version is active which does no longer match
        the data set. Try to correct the error by regenerating the
        program "SAPLRSVERS". To do this, choose transaction SE38 in the SAP
        System. There enter the program name "SAPLRSVERS". Then choose the
        "Generate" function.

    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    please use the following search criteria:

        "CONNE_IMPORT_WRONG_STRUCTURE" "CX_SY_IMPORT_MISMATCH_ERROR"
        "SAPLRSVERS" bzw. "LRSVERSF30"
        "ADJUST_OBJLIST_FOR_IMPORT_ALL"

    The exception must either be prevented, caught within proedure "ADJUST_OBJLIST_FOR_IMPORT_ALL" "(FORM)", or its possible occurrence must be declared in the RAISING clause of the procedure.

 

 

I've generate the program SAPLRSVERS but the same error still occurs.

 

Could anyone pls. help?

Thank you!

 

Best Regards,

Carina Hu


Error During the Upgrade

$
0
0

Hello All,

 

    We are upgrading EP system from SAP NW 701 to SAP NW7.4. DB is SQL Server

 

During the upgrade, I'm struck up in the execution phase and I get the below error message.

 

 

ay 24, 2014 4:40:55 AM [Info  ]: Deployment message for component EP-APPS-EXT :

May 24, 2014 4:40:55 AM [Info  ]: Overal deployment message : Could not authenticate the given user with AS Java. Check that user and password are correct.

com.sap.engine.services.dc.api.AuthenticationException: [ERROR CODE DPL.DCAPI.1148] Could not establish connection to AS Java on [XXXXXX:52304]. Cannot authenticate the user. Wrong or missing security credentials (password) for principal [Administrator], or the specified principal has no permissions to perform JNDI related operations.

javax.naming.NoPermissionException: Exception during getInitialContext operation. Wrong security principal/credentials. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]

com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.

com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.

 

Administrator password has been changed in the middle after SUM was ready for the execution phase.

 

When I go to JAVA -> Reneter java passwords ,I'm 100% sure that I'm entering the correct password but still I'm being prompt for the valid password.

 

Did anyone has faced such issue? any suggestion please?

 

Thanks and Regards,

Vimalan

HTML 5 application does not run in IE11 Enterprise mode ?

$
0
0

Dear All,

 

I have a HTML5 Application which hosted on SAP Enterprise Portal. My Application run only in the IE Standard mode, but Enterprise mode.

 

If the Enterprise mode is enabled, there was some rendering issue, where all the UI's are displayed in the left side

When ever i click my application url, Enterprise mode is automatically Enabled. i had to disable every time when i access my application.

 

I have two question.

1. Mostly Web Application must run on both the modes . why the application run only on Standard mode but enterprise mode?

     When i checked about the functionality of Enterprise mode, i came to know that if the application does not work on Standard mode, enabling      Enterprise mode make it work . if the application still not work, maintaining the application url in the compatablity view settings make it work.

 

2. I have found a way to disable the Enterprise mode from Group policy editor(gpedit.msc) and regedit.

     Is there any way we can disable permanently from Browser setting? not to involve group policy editor and register edit

 

 

Appreciate your reply.IE11 Rendering issue.png

 

Thanks ,

Dayalan

SAP Portal upgrade 7.01 to 7.31 development taks

$
0
0

Hi,

 

We have just upgraded SAP Portal from 7.01 to 7.31. Can you please let me know what are the portal remediations tasks we need to carry? Kindly provide master list of development tasks?   Please provide what are the components need to be upgraded like WebDynpro development, ESS/MSS or Custom developments, PAR files etc.. in the task list.

 

Thanks and Regards,

Raghu.

SAP EP 7.0 to 7.3: Activating ESS and MSS standard Roles

$
0
0

Hi,

 

We are upgrading our EP from version 7.0 to 7.3. To do this, several of the standard applications must be migrated to WDA. We have taken the following steps in order to do so:

 

  • Installation of the ESS Business Package.
  • Activation of the WDA for ESS Business Function.
  • Basic service activation for ESS through SICF (hap_a_pmp_employee, hress_a_cats_1, HRESS_A_MENU, HRESS_A_PERSINFO) in order to make some tests.
  • Application testing through SE80 (with minimal or no customizing).
  • Role Assignment through PFCG.

 

After completing all these tasks, we have proceeded to test the aforementioned applications directly using the EP. However, we get the following error message:

 

Portal runtime error

An exception occurred while processing your request. Send the exception ID to your portal administrator.

Exception ID 11:10_29/10/12_0004_363451350

See log file for details about this exception

Now this is what we found in the log when we recreated the exception:

Time: 2012 10 29 14:49:01:244
SourceName: com.sap.portal.sapapplication
Application: sap.com/com.sap.portal.appintegrator.sap
Location: com.sap.portal.sapapplication
User: Administrator
Session: 1
DSRTransaction: 347cbfc821fb11e2aafb000015a9d3d6
ThreadName: Thread[HTTP Worker [@485134117],5,Dedicated_Application_Thread]
Severity: Error
TZone: 0-430
CSNComponent: EP-PIN-PRT
DCComponent: tc~epbc~prtc~core
CorrelationID: 363451350000000004
DSRRootContextID: E8119D5F21FA11E296E4000015A9D3D6
DSRConnection: 347cbfc821fb11e2aafb000015a9d3d6
DSRCounter: 0
Text: Content pass of Application Integrator failed.
Component Name:       'com.sap.portal.appintegrator.sap.WebDynpro',
Context Name (iView): 'pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.wda.bp_folder/com.sap.pct.erp.ess.wda.roles/com.sap.pct.erp.ess.wda.Employee_Self_Service_WDA/com.sap.pct.erp.ess.wda.Employee_Self_Service/com.sap.pct.erp.ess.wda.Overview/com.sap.pct.erp.ess.wda.Overview',
Top Layer:            'WebDynpro/TopLayer',
Producer ID (FPN):    'null',
System Alias:         'SAP_ECC_HumanResources',

 

Time: 2012 10 29 14:49:01:245
SourceName: com.sap.portal.prt.connection
Application: sap.com/irj
Location: com.sap.portal.prt.connection
User: Administrator
Session: 1
DSRTransaction: 347cbfc821fb11e2aafb000015a9d3d6
ThreadName: Thread[HTTP Worker [@485134117],5,Dedicated_Application_Thread]
Severity: Error
TZone: 0-430
CSNComponent: EP-PIN-PRT
DCComponent: tc~epbc~prtc~api
CorrelationID: 363451350000000004
DSRRootContextID: E8119D5F21FA11E296E4000015A9D3D6
DSRConnection: 347cbfc821fb11e2aafb000015a9d3d6
DSRCounter: 0
Text: Exception ID:02:49_29/10/12_0013_363451350
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Application name : com.sap.portal.appintegrator.sap
Component : pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.wda.bp_folder/com.sap.pct.erp.ess.wda.roles/com.sap.pct.erp.ess.wda.Employee_Self_Service_WDA/com.sap.pct.erp.ess.wda.Employee_Self_Service/com.sap.pct.erp.ess.wda.Overview/com.sap.pct.erp.ess.wda.Overview
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : Administrator
at com.sap.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:786)
at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:245)
at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:107)
at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:141)
at com.sap.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:206)
at com.sap.portal.prt.pom.PortalNode.service(PortalNode.java:588)
at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:233)
at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:107)
at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:141)
at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:520)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:201)
at com.sap.portal.prt.dispatcher.DispatcherServlet.service(DispatcherServlet.java:132)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>;sap-ext-sid=<ESID[URL_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[URL_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&sap-ls-useAnimation=<User.DisableAnimation[OMIT BOOL_NEGATE SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 0. Cannot process expression <System.Access.WAS.protocol> because Invalid System Attribute:
System:    'System Alias: SAP_ECC_HumanResources, System ID: pcd:portal_content/Sistemas/com.polar.SAP_ECC_HumanResources',
Attribute: 'protocol'.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:171)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:143)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:213)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:129)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$5.service(RequestDispatcherFactory.java:308)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:270)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.service(RequestDispatcherFactory.java:298)
at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:229)
... 51 more
Caused by: com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>;sap-ext-sid=<ESID[URL_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[URL_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&sap-ls-useAnimation=<User.DisableAnimation[OMIT BOOL_NEGATE SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 0. Cannot process expression <System.Access.WAS.protocol> because Invalid System Attribute:
System:    'System Alias: SAP_ECC_HumanResources, System ID: pcd:portal_content/Sistemas/com.polar.SAP_ECC_HumanResources',
Attribute: 'protocol'.
at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.processTemplate(AbstractIntegrationLayer.java:543)
at com.sapportals.portal.appintegrator.layer.URLTemplateProcessLayer.processLayer(URLTemplateProcessLayer.java:33)
at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:175)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:111)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:70)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:398)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$1.service(RequestDispatcherFactory.java:168)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:270)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.handleEvent(RequestDispatcherFactory.java:158)
at com.sap.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:242)
at com.sap.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:342)
at com.sap.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:732)
at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:473)
... 43 more
Caused by: com.sapportals.portal.appintegrator.template_processor.TemplateParserException: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>;sap-ext-sid=<ESID[URL_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[URL_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&sap-ls-useAnimation=<User.DisableAnimation[OMIT BOOL_NEGATE SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 0. Cannot process expression <System.Access.WAS.protocol> because Invalid System Attribute:
System:    'System Alias: SAP_ECC_HumanResources, System ID: pcd:portal_content/Sistemas/com.polar.SAP_ECC_HumanResources',
Attribute: 'protocol'.
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processWholeTagExpression(TemplateProcessor.java:161)
at com.sapportals.portal.appintegrator.template_processor.compiler.TemplateCompiler.processWholeTagExpression(TemplateCompiler.java:54)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseSimpleExpression(TemplateParser.java:234)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:188)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpressionEx(TemplateParser.java:210)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:193)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpressionEx(TemplateParser.java:210)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:193)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpressionEx(TemplateParser.java:210)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:193)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseTagExpression(TemplateParser.java:170)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseTemplateExpressionPart(TemplateParser.java:97)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parse(TemplateParser.java:89)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parse(TemplateParser.java:83)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processImpl(TemplateProcessor.java:432)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.process(TemplateProcessor.java:399)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.process(TemplateProcessor.java:411)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessorService.processTemplate(TemplateProcessorService.java:55)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessorService.processTemplate(TemplateProcessorService.java:110)
at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.processTemplate(AbstractIntegrationLayer.java:522)
... 55 more
Caused by: com.sapportals.portal.appintegrator.template_processor.context.ContextException: Invalid System Attribute:
System:    'System Alias: SAP_ECC_HumanResources, System ID: pcd:portal_content/Sistemas/com.polar.SAP_ECC_HumanResources',
Attribute: 'protocol'.
at com.sapportals.portal.appintegrator.template_processor.context.SystemEP6Wrapper.getTerminal(SystemEP6Wrapper.java:86)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processWholeTagExpression(TemplateProcessor.java:157)
... 74 more

 

Time: 2012 10 29 14:49:01:258
SourceName: com.sap.portal.prt.runtime
Application: sap.com/com.sap.portal.runtime.system.hooks
Location: com.sap.portal.prt.runtime
User: Administrator
Session: 1
DSRTransaction: 347cbfc821fb11e2aafb000015a9d3d6
ThreadName: Thread[HTTP Worker [@485134117],5,Dedicated_Application_Thread]
Severity: Error
TZone: 0-430
CSNComponent: EP-PIN-PRT
DCComponent: tc~epbc~prtc~api
CorrelationID: 363451350000000004
DSRRootContextID: E8119D5F21FA11E296E4000015A9D3D6
DSRConnection: 347cbfc821fb11e2aafb000015a9d3d6
DSRCounter: 0
Text: 02:49_29/10/12_0013_363451350
[EXCEPTION]
com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>;sap-ext-sid=<ESID[URL_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[URL_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&sap-ls-useAnimation=<User.DisableAnimation[OMIT BOOL_NEGATE SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 0. Cannot process expression <System.Access.WAS.protocol> because Invalid System Attribute:
System:    'System Alias: SAP_ECC_HumanResources, System ID: pcd:portal_content/Sistemas/com.polar.SAP_ECC_HumanResources',
Attribute: 'protocol'.
at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.processTemplate(AbstractIntegrationLayer.java:543)
at com.sapportals.portal.appintegrator.layer.URLTemplateProcessLayer.processLayer(URLTemplateProcessLayer.java:33)
at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:175)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:111)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:70)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:398)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$1.service(RequestDispatcherFactory.java:168)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:270)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.handleEvent(RequestDispatcherFactory.java:158)
at com.sap.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:242)
at com.sap.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:342)
at com.sap.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:732)
at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:473)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:201)
at com.sap.portal.prt.dispatcher.DispatcherServlet.service(DispatcherServlet.java:132)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sapportals.portal.appintegrator.template_processor.TemplateParserException: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>;sap-ext-sid=<ESID[URL_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[URL_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&sap-ls-useAnimation=<User.DisableAnimation[OMIT BOOL_NEGATE SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 0. Cannot process expression <System.Access.WAS.protocol> because Invalid System Attribute:
System:    'System Alias: SAP_ECC_HumanResources, System ID: pcd:portal_content/Sistemas/com.polar.SAP_ECC_HumanResources',
Attribute: 'protocol'.
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processWholeTagExpression(TemplateProcessor.java:161)
at com.sapportals.portal.appintegrator.template_processor.compiler.TemplateCompiler.processWholeTagExpression(TemplateCompiler.java:54)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseSimpleExpression(TemplateParser.java:234)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:188)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpressionEx(TemplateParser.java:210)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:193)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpressionEx(TemplateParser.java:210)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:193)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpressionEx(TemplateParser.java:210)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:193)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseTagExpression(TemplateParser.java:170)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseTemplateExpressionPart(TemplateParser.java:97)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parse(TemplateParser.java:89)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parse(TemplateParser.java:83)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processImpl(TemplateProcessor.java:432)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.process(TemplateProcessor.java:399)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.process(TemplateProcessor.java:411)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessorService.processTemplate(TemplateProcessorService.java:55)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessorService.processTemplate(TemplateProcessorService.java:110)
at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.processTemplate(AbstractIntegrationLayer.java:522)
... 55 more
Caused by: com.sapportals.portal.appintegrator.template_processor.context.ContextException: Invalid System Attribute:
System:    'System Alias: SAP_ECC_HumanResources, System ID: pcd:portal_content/Sistemas/com.polar.SAP_ECC_HumanResources',
Attribute: 'protocol'.
at com.sapportals.portal.appintegrator.template_processor.context.SystemEP6Wrapper.getTerminal(SystemEP6Wrapper.java:86)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processWholeTagExpression(TemplateProcessor.java:157)
... 74 more

 

Keep in mind that we have used the application’s URL we get from SE80 directly in the browser and it does work, but through the EP we have only received this message for every dynpro tested.

 

Furthermore, it would be really helpful if you could provide a list of steps or tasks we must complete in order to set up ESS and MSS for EP 7.3.

 

Thanks in advance,

 

Zaida Superlano.

 

 

A communication error occured, with the TREX TcpIp Server (Errorcode 2982)

$
0
0

Hi All,

       We are in the process of Migrating our EP 5.0 --> EP 6.0. While upgrading TREX, I am getting following error:

"Error occurred during search: com.sapportals.wcm.WcmException: <b><u>A communication error occured, with the TREX TcpIp Server (Errorcode 2982)</u></b>

A communication error occured, with the TREX TcpIp Server (Errorcode 2982)"

       Has any one came across this type of error ?

 

<b>Software version details:</b>

EP 5.0 SP6 Patch 1 Hotfix 8

CM SP 6 Patch 1 Hotfix 21

Trex (Earlier 6.0.0.0)---> TREX 6.0 SP 1 Patch 6 (6.0.1.6.0)

 

 

Regards

Sunil Kulkarni

Migration from Oracle to DB2

$
0
0

Hi,


We are planning to Migrate from Oracle to DB2 version 10.5 Database.Can you please help us or share any document/link how we can proceed with this migration .

We have our SAP System ECC6.0 EHP5 .Oracle Version is 11.2.0.2.

Thanks in advance

 

Regards

Amit Shedge

Upgrade Netweaver BW 7 Ehp1 towards BW 7.4 with RTLPOSDM

$
0
0

Hi SCN,

 

I've got a bit of a nasty problem during an upgrade.

 

System is running on enterprise linux 6 and with a Oracle DB 11.2.0.3

 

According to MOPZ:

 

Source release:

 

SBOP PC 7.5 FOR SAP NW

SP Stack 01

Add-on

SAP EHP1 FOR SAP NETWEAVER 7.0

07 (07/2010)

NetWeaver

 

Target Release:

 

SBOP PC 10.0 FOR SAP NW

Stack 03 (May 2013)

Add-on

SAP NETWEAVER 7.4

04 (10/2013)

NetWeaver

 

The upgrade didn't get any farther than the calculation of the queue and then it stopped mentioning that it was missing files for RTLPOSDM to be able to calculate the queue.

 

  error_upgrade.jpg

Since BI_CONT was on a reasonably old version (and still with the RTLPOSDM packages included in BI_CONT) I decided to upgrade to BI_CONT 707 and RTLPOSDM 100_700. AFfer installing this, this is now the source release.

 

SBOP PC 7.5 FOR SAP NW    SP Stack 01 (Add-on)

SAP POS DM 1.0 (Add-on)

SAP EHP1 FOR SAP NETWEAVER 7.0   11 (03/2012) (Netweaver)

 

When running MOPZ now I do get the following warnings, which are worrying me slightly :-)

warning_mopz.jpg

 

Has anyone else come across this problem or any experience in upgrading from NW 7.0 EHP1 to NW 7.4? I've done an upgrade from a BW 7 Ehp1 to BW 7.3 Ehp1 in the past .But there was no RTLPOSDM component (logically since it was not a retail customer)

 

Thanks in advance for your help/tips/suggestions.

 

Dieter


Big Endian and Little Endian.

$
0
0

Hi,

 

Actually I have a query regarding Big Endian and Little Endian, During the Export of Database, Target Hardware Platform need to be mention as Big Endian or Little Endian (screenshot attached). Now my concern is this, suppose we are migrating from Windows to AIX and I selected my target system as Little Endian (but ofcourse AIX memory architecture is Big Endian). Will I be able to import my DB in AIX although I mentioned my target system as Little Endian. If NO, what need to be done?

Shall I take the complete export again or with some modification we can import it in AIX.

 

Thanks and Regards,

Ankit Mishra

NW 7.4 upgrade fails to start shadow instance

$
0
0

Hi all,

 

I'm trying to upgrade our EP (Java only) from NW 7.0 to NW 7.4. We did a test on a POC server last Summer and it went fine.

Now, it's time to do real upgrade on our servers; of course, the old SUM version doesn't work anymore. I used MOPZ to generate new stack files, download the latest components and all.

Somehow, the SUM kept failing at step 5.5 - Preprocessing when it tries to Start shadow instance SCS.

 

The log only indicates that SUM tried to start the instance a 20 times (with 15-second pauses in between) so it gave up. The last part of the log shows

------------------------

Feb 11, 2014 1:50:36 PM [Info  ]: All retrieved instances : 3

Feb 11, 2014 1:50:36 PM [Info  ]: Correctly detected instance: 70 on host mydev

Feb 11, 2014 1:50:36 PM [Info  ]: Correctly detected instance: 2 on host mydev

Feb 11, 2014 1:50:36 PM [Info  ]: Correctly detected instance: 0 on host mydev

Feb 11, 2014 1:50:36 PM [Info  ]: Instance has status STOPPED.

Feb 11, 2014 1:50:36 PM [Info  ]: Starting instance number 2 on host mydev with timeout of 7200 seconds.

Feb 11, 2014 1:50:36 PM [Error ]: The maximum retry count (20) was reached.

Feb 11, 2014 1:50:36 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Could not start SAP instance  with number 2.

Could not send the command to start the instance with number 2 on host mydev.

Error starting instance 2 on host mydev with timeout of 7200 seconds.

Errors while starting the instance.

javax.xml.ws.soap.SOAPFaultException: Invalid Credentials

--------------------------

 

The only SAP Note I found is 1937296 where it says you'd need the latest kernel. But I've already had the latest kernel.

What bothers me is "Invalid Credentials" --> which credentials?

 

I tried several different things. Reset the upgrade, cleaned up the SUM directory, re-start the upgrade from scratch several times. I've also tried to re-start the instance; even re-started the server a couple of times ... to no avail :-(

 

I also tried to run the sapstartsrv command line

## ../SUM/sdt/data/kernel/sapstartsrv pf=../../DPK_SCS02_mydev -D

and I'd get the error

--------------------

Could not open the ICU common library.

   The following files must be in the path described by

   the environment variable "LD_LIBRARY_PATH":

   libicuuc.so.50, libicudata.so.50, libicui18n.so.50 [/bas/741_REL/src/flat/nlsui0.c 1535] pid = 18978

LD_LIBRARY_PATH is currently set to /usr/sap/DPK/SYS/exe/run:/oracle/client/11x_64/instantclient  [/bas/741_REL/src/flat/nlsui0.c 1538] pid = 18978

--------------------

 

Any help and/or suggestion would be greatly appreciated.

 

Regards,

Dao

Input Java administrator user credentials step Fails

$
0
0

HI All,

 

We are upgrading PI System from 7.0 to 7.31, where we are facing an issue in Configuration phase as below

 

An error has occurred during the execution of the Input Java administrator user credentials step.

Could not display dialog UserPasswords. Could not execute dialog UserPasswords. See previous messages. SDM connection error when try to connect to SDM server on host xxxx listening on port 50018. com.sap.sdm.apiimpl.remote.client.APIRemoteExceptionImpl: Server XXX did not accept login request as XXX on port 50018 - Connection between SDM client and server is broken

 

KIndly help!!

 

We have already maintained the admin credentials in secure store - configtool.

 

Thanks,

Preetha Balan


How to configure LDAP Server

$
0
0

Hi Gurus,

 

You can maintain user details in three places rite.

 

1,Portal DB,

 

2,R/3 End

 

3,Configuring LDAP server.

 

Can you please throw some clue for the above said tyeps and differences and advantages of each and tell me how to configure LDAP Server.

 

If anyone have step by step document pls send it to shakthigin@yahoo.co.in

 

Higher points will be rewarded for useful inputs.

 

Thanks in Advance,

Dharani.

Mashead par file migration from 7.0 to 7.3 portal

$
0
0

Hello All,

 

We are upgrading our portal to the latest 7.3 portal and we are having issues with the mathead PAR file.

 

I imported the par file into NWDS 7.3 and deployed the EAR from NWDS to the 7.3 portal system. However when I try previewing the iView it gives Portal Runtime Exception. I also tried with the PAR Migration tool just to ensure I am not missing something when importing through NWDS. Still the same error with the iView.

 

My JSP code has errors in NWDS. But as the blogs on SDN says we are getting errors in the code since JSP doesnt compile at runtime, which is correct. I am still able to bundle it in an EAR and deploy successfully. However, is there anything I need to change.... any class references when importing masthead par from 7.0 to 7.3 ? Do I need to add any external libraray JARs for the below imports or we can simply ignore these errors?

 

 

 

<%@ page import = "com.sapportals.portal.prt.service.laf.*" %>

<%@ page import = "com.sap.security.api.UMFactory" %>

<%@ page import = "com.sapportals.portal.prt.service.license.ILicenseService"%>

<%@ page import = "com.sapportals.portal.navigation.*" %>

<%@ page import = "com.sapportals.portal.prt.runtime.PortalRuntime" %>

<%@ taglib uri="prt:taglib:tlhtmlb" prefix="hbj" %>

 

Also please see the attached trace file, the masthead Header iView shows records the below exception w.r.t LoginModuleClass in the trace logs -

 

Exception ID:04:04_01/05/12_0016_4480450
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Application name : CompassMastHeadNew
Component : pcd:com.sap.portal.system/gpal_hidden_content/gpar/CompassMastHeadNew/default...

Cannot load login module class com.sap.security.core.server.jass.HeaderVariableLoginModule.
[EXCEPTION]
java.lang.ClassNotFoundException: No application classloader can load login module class: com.sap.security.core.server.jass.HeaderVariableLoginModule
at com.sap.engine.services.security.server.deploy.LoginModuleContainer.getLoginModuleClass(LoginModuleContainer.java:166)
at...

No application classloader can load login module class: com.sap.security.core.server.jass.HeaderVariableLoginModule. Probably application that deployed the login module is stopped and cannot be started.

 

Please assist. Appreciate all your help truly.

 

Thanks and Regards,

Samta.

JAR files required for Portal Application

$
0
0

Hi Experts

 

I am currently migrating my custom Masthead application from NW 7.0 to NW 7.3. However, when I migrated the PAR into EAR using migration tool from Portal and imported this EAR file into NWDS7.3, the JSP pages in it shows error. Also when this EAR is directly deployed on the NW 7.3 system, it gives Portal Runtime exception.

 

<%@ page import = "com.sapportals.portal.prt.session.IUserContext" %>

<%@ page import = "com.sapportals.portal.prt.component.*" %>

<%@ page import = "com.sapportals.portal.prt.service.laf.*" %>

<%@ page import = "com.sap.security.api.*" %>

<%@ page import = "com.sapportals.portal.prt.service.license.ILicenseService"%>

<%@ page import = "com.sapportals.admin.wizardframework.util.ILocaleListService"%>

<%@ page import = "com.sapportals.portal.navigation.*" %>

<%@ page import = "com.sapportals.portal.prt.runtime.PortalRuntime" %>

<%@ page import = "com.sapportals.portal.prt.util.StringUtils" %>

<%@ taglib uri="prt:taglib:tlframework" prefix="frm" %>

 

 

The errors shown in the JSP page are due to missing JARs. But I am having trouble in locating the required JAR files on the server. Can anybody tell about which all JARs are required and where i can find them??

Also the imported Framework library is not accessible in the application thus there is error "Can not find the tag library descriptor for "prt:taglib:tlframework"".

 

Can anybody tell me what i am missing here??

 

Regards,

 

Deepak

SAP portal upgrade 7.0 to 7.4- Manual content transport

$
0
0

Hi all,

 

I have a old portal 7.0 and a new portal in versión 7.4. Now I need transport all portal content (roles, iviews, workset, themes..., KM content) , users, groups, etc.. to this new portal.

 

Are there any restriction in to realize this manual content transport?

 

what can be the key points to consider?

 

Thanks and best regards

 

Mónica


KM: document migration

$
0
0

Hi

 

I’m currently planning the migration of our EP5 portal to EP6 NW04. I would like to know if the KM migration tool migrates repository document and folder information, like :

ACL, author, creation date, description, custom properties, previous document version, approval status/data, ...

 

Thanks,

 

Martin

How to get the login user details?

$
0
0

Hi Gurus,

 

How to see the logged in user in Portal.

 

Thanks in Advance,

Dharani

EP OS Migration

$
0
0

Hi,

 

We want to migrate only EP Application server from W2K8 to RHEL, the DB is Oracle on AIX which will remain as it is.

can somebody help me with the migration steps and integration with the existing DB?

 

DEV-Staging-Production & DR servers to be migrated

 

DR will be migrated along with Oracle on RHEL on 1 physical server

Thanks,

 

Anand

SAP Portal 7.4 compatibility with webdynpro abap 7.02

$
0
0

Hi all,

 

I had a portal 7.0 and a SAP SRM 7.02 EHP2.

 

We were installed a new portal 7.4 and we have transported all content of our portal 7.0 to the portal 7.4.

 

In the portal we are calling a several webdynpro Abap (SRM 7.02) the wendynpro abap work correctly but the problem is with the visualization. For example with the style(color and shape) of tabs.

 

New portal:

 

new.JPG

 

Old portal:

 

old.JPG

 

I dont know what is the problema, Is necessarry the intallation some patch in portal or R3?

 

Please can you help us?

 

Thanks and best regards

Upgrading BW3.5 to 7.x

$
0
0

Hello,

 

I'm planning the following upgrade for BW:


Source
Windows 2003 32bit
SAP BW 3.5
SQL Server 2000 32 bit

Target(New Server)
Windows 2008 R2
SAP NW7.4
SQL Server 2012 64bit

Steps :
1.Install SQL Server 2005 on the target system.
2.Install BW3.5 .
3.Restore Production Copy
4.Upgrade SQL Server 2005 32 bit to 2012 64 bit.
5.Upgrade BW to 7.x


(Collation: is not SQL_Latin1_General_CP850_BIN2)

I’m not sure that it’s possible to Upgrade SQL Server 2005 32 bit to 2012 64 bit directly.
Do you have any idea?

 

Thanks

Viewing all 767 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>