Skip to Content

ESS for end user: Error Typed model execution failed, see nested exception for details

Hi guys, I'm new to Portal administration.

I have a Portal version 7.4 with backend ERP 6.0 EHP7 . The ESS application is configured.

Today the Portal server was restarted (only Portal - Not ERP), and then in the ESS application when the actions for travel requests save the system displays this error:

"Sorry, a connection problem occurred. Error Typed model execution failed, see nested exception for details"

When I check the logs of the portals I find these errors:

com.sap.netweaver.bc.uwl.core.push.NotificationRegistrationManager
Location: Single Click Filter by Location Negative Single Click Filter by Location com.sap.netweaver.bc.uwl.core.push.NotificationRegistrationManager
Application: Single Click Filter by Application Negative Single Click Filter by Application sap.com/com.sap.netweaver.bc.uwl
Thread: Single Click Filter by Thread Negative Single Click Filter by Thread Thread[UWL Pooled Thread:3,5,ApplicationThreadGroup]

Error at NotificationListener unRegisterRFCNotifications
[EXCEPTION]
Fri Jun 16 16:38:24 BOT 2017
com.sap.portal.connectivity.destinations.PortalDestinationsServiceException: No se ha podido establecer la conexión para el alias UWL. Póngase en contacto con el responsable del sistema.
at com.sap.portal.connectivity.destinations.portal.PortalSystemLandscapeSource.getConnectionWithOverridingProps(PortalSystemLandscapeSource.java:123)
at com.sap.portal.connectivity.destinations.impl.DestinationServiceImpl.getConnection(DestinationServiceImpl.java:261)
at com.sap.portal.connectivity.destinations.DestinationsService.getConnection(DestinationsService.java:122)
at com.sap.netweaver.bc.uwl.utils.r3.Transaction.begin(Transaction.java:112)
at com.sap.netweaver.bc.uwl.utils.r3.Transaction.createInput(Transaction.java:216)
at com.sap.netweaver.bc.uwl.core.connect.webflow.WebflowChangeNotificationListener.unRegisterRFCNotification(WebflowChangeNotificationListener.java:300)
at com.sap.netweaver.bc.uwl.core.connect.webflow.WebflowChangeNotificationListener.unRegisterRFCNotifications(WebflowChangeNotificationListener.java:255)
at com.sap.netweaver.bc.uwl.core.push.NotificationRegistrationManager.onUsersLastSessionEnded(NotificationRegistrationManager.java:55)
at com.sap.netweaver.bc.uwl.core.session.SessionManager.cleanOneSession(SessionManager.java:607)
at com.sap.netweaver.bc.uwl.core.session.CleaningThread.run(CleaningThread.java:53)
at com.sap.netweaver.bc.uwl.core.ThreadManager$PoolWorker.run(ThreadManager.java:209)
Caused by: com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: A nested exception occurred. Could not initialize physical connection.
at com.sapportals.connectors.SAPCFConnector.SAPConnectorException.getNewConnectionFailedLocalizedException(SAPConnectorException.java:182)
at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnectionFactory.createManagedConnection(SAPCFConnectorManagedConnectionFactory.java:155)
at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:401)
at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:295)
at com.sap.engine.services.connector.jca.ShareableConnectionManager.allocateConnection(ShareableConnectionManager.java:54)
at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorConnectionFactory.getConnectionEx(SAPCFConnectorConnectionFactory.java:173)
at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:401)
at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:354)
at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:305)
at com.sap.portal.connectivity.destinations.portal.PortalSystemLandscapeSource.getConnectionWithOverridingProps(PortalSystemLandscapeSource.java:120)
... 10 more
Fri Jun 16 16:38:24 BOT 2017:com.sap.portal.connectivity.destinations.PortalDestinationsServiceException: No se ha podido establecer la conexión para el alias UWL. Póngase en contacto con el responsable del sistema.
at com.sap.netweaver.bc.uwl.utils.r3.Transaction.begin(Transaction.java:153)
at com.sap.netweaver.bc.uwl.utils.r3.Transaction.createInput(Transaction.java:216)
at com.sap.netweaver.bc.uwl.core.connect.webflow.WebflowChangeNotificationListener.unRegisterRFCNotification(WebflowChangeNotificationListener.java:300)
at com.sap.netweaver.bc.uwl.core.connect.webflow.WebflowChangeNotificationListener.unRegisterRFCNotifications(WebflowChangeNotificationListener.java:255)
at com.sap.netweaver.bc.uwl.core.push.NotificationRegistrationManager.onUsersLastSessionEnded(NotificationRegistrationManager.java:55)
at com.sap.netweaver.bc.uwl.core.session.SessionManager.cleanOneSession(SessionManager.java:607)
at com.sap.netweaver.bc.uwl.core.session.CleaningThread.run(CleaningThread.java:53)
at com.sap.netweaver.bc.uwl.core.ThreadManager$PoolWorker.run(ThreadManager.java:209)

I´m check the connection for JCOs and UWL is OK.

I do not know what to check.

I appreciate any help

regards.

Desirée.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Jun 19, 2017 at 10:47 PM

    Hi Desiree,

    Have you checked the Destinations in NetWeaver Administrator (NWA -> Configuration -> Security (or Infrastructure) -> Destinations)? Specifically, check WD_MODELDATA_DEST, and that the Authentication for this Destination is set to Current User (Assertion Ticket) (WD_RFC_METADATA_DEST, on the other hand, should be Technical User).

    The other place to check backend connections is from the Portal interface, via System Administration -> System Landscape.

    Cheers,
    Matt

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Matt.

      Thanks for replay.

      We find the errors and are functional product of a number conversion when recording a travel request. An abap consultant is already checking.

      Thanks for help me

      I´m close this message

      Desirée.

  • Jun 20, 2017 at 01:23 PM

    Hello guys i checked other errors in the log portal administration after restarted server:

    error-portal-2.txt

    error-portal-3.txt

    error-portal-4.txt

    Regards

    Desirée

    Add comment
    10|10000 characters needed characters exceeded