SAP Knowledge Base Article - Preview

2639905 - Issues in accessing the portal after VIM upgrade

Symptom

  1. When you click on certain tabs of Vendor Invoice Management(VIM) through Enterprise Portal, it gives a Windows security pop-up asking for user name and password.pop-up.JPG
  2. When you click cancel you are able to see the page correctly
  3. In HTTPwatch traces , you will find several 401 status code. For example in this screenshot, you can see 401 calls for several .gif filewatchtrace.JPG
  4. In default traces(location:/usr/sap/<SID>/<instance>/j2ee/cluster/serverX/log), you will find these entries (You will see these entries on setting DEBUG severity for trace location com.sap.engine.services.servlets_jsp.*  Refer to note 1095475 - How to enable HTTP tracing in the AS Java)

    REQUEST:
    GET /vimportal/images/panel-header/Header-BackGround.png HTTP/1.1

    #2.0#2018 06 12 09:23:49:953#0-500#Debug#com.sap.engine.services.servlets_jsp.Security#
    #BC-JAS-WEB#servlet_jsp#C0000A4B067C0A5A0000001600011711#481202450000000004#opentext.com/IM_APPROVAL_PORTAL7_5SP6#com.sap.engine.services.servlets_jsp.Security.doFilter(ServletRequest, ServletResponse, FilterChain)#Guest#0##2AD7F1566E4C11E88BAE00001CAE9112#345b55ff6e4c11e890de00001cae9112##0#Thread[HTTP Worker [@290029693],5,Dedicated_Application_Thread]#Plain##
    The request authorization failed for context root /vimportal and path /SapErrorHandlerServlet
    [EXCEPTION]
    com.sap.engine.services.security.exceptions.BaseLoginException: Login failed.


Read more...

Environment

SAP Netweaver Java with Vendor Invoice Management

Product

SAP ERP 6.0

Keywords

BasicPasswordLoginModule,SecuritySessionIDHTTPSProtection,SecuritySessionIdGracePeriod,javax.security.auth.login.LoginException,JSESSIONMARKID,Markids

  1. When you click on certain tabs of Vendor Invoice Management(VIM) through Enterprise Portal, it gives a Windows security pop-up asking for user name and password.

 

 

 

  1. When you click cancel you are able to see the page correctly
  2. In HTTPwatch traces , you will find several 401 status code. For example in this screenshot, you can see 401 calls for several .gif file

 

 

 

 

  1. In default traces(location:/usr/sap/<SID>/<instance>/j2ee/cluster/serverX/log), you will find these entries (You will see these entries on setting DEBUG severity for trace location com.sap.engine.services.servlets_jsp.*  Refer to note 1095475 - How to enable HTTP tracing in the AS Java)

REQUEST:
GET /vimportal/images/panel-header/Header-BackGround.png HTTP/1.1

#2.0#2018 06 12 09:23:49:953#0-500#Debug#com.sap.engine.services.servlets_jsp.Security#
#BC-JAS-WEB#servlet_jsp#C0000A4B067C0A5A0000001600011711#481202450000000004#opentext.com/IM_APPROVAL_PORTAL7_5SP6#com.sap.engine.services.servlets_jsp.Security.doFilter(ServletRequest, ServletResponse, FilterChain)#Guest#0##2AD7F1566E4C11E88BAE00001CAE9112#345b55ff6e4c11e890de00001cae9112##0#Thread[HTTP Worker [@290029693],5,Dedicated_Application_Thread]#Plain##
The request authorization failed for context root /vimportal and path /SapErrorHandlerServlet
[EXCEPTION]
com.sap.engine.services.security.exceptions.BaseLoginException: Login failed.
, KBA , BC-JAS-WEB , Web Container, HTTP, JavaMail, Servlets , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.