Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 10498

Service Group error after portal migration to 7.3

$
0
0

Hello All,

 

We're currently facing some issues with our webdynpro application after a migration to netweaver portal 7.3.

it is seems like a problem with the web service.

 

When we try to open the webdynpro application we get a error message:

  1. init...:while trying to invoke the method com.sap.tc.webdynpro.progmodel.api.IWDMessageManager.reportException(java.lang.String) of an object loaded from field ****.********.approval.srm.SRMApprovalComp.manager of an object loaded from local variable 'this'

 

After a redeployment of the exact same application the error message in is changed to:

 

init...:Exception on creation of service metadata for web service mass config parameters service reference ID 'aa8dabb6-a894-4262-8f60-bb5b4e0b71a5' and application name '**********.**/dev~srm_app'. Check mass configuration has been done properly.

 

After some research I discovered another problem(i'm not sure if they're connected to eachother)

I checked the service groups and the group for our application gives warning after processing:

 

Configuration of logical ports for [sap**_********_local] service group finished with warning. The provider system successfully found the needed service, but its wsdl is without webservice policy. Thus the generated client configuration might not work because of different configurations between service and client (most probable a difference in the security settings). Either assign a provider system with access to wsdl with policy or manually create the client configuration. For more information increase severity of the default trace com.sap.esi.esp.service.server.mass.BatchJobRun to WARNING and reassign the service group. Details: [**.SystemHome.db**.Java] provider system, [********.***/dev~srm_app] service group application

 

i've tried to create a webservice policy on "nwa/auth" but it did not work.

 

i've imported the WSDL file into my NWDS and made some changes that SAP suggested.

I Rebuild the project, deployed it to the server and did AS Java a restart.

 

When i checked the WSDL file on the server, nothing was changed.

 

Did somebody experienced such problems before and found a solution.

Or does somebody have any suggestions how i can solve it.

 

Thanks in advance

 

 

 

 



Viewing all articles
Browse latest Browse all 10498

Trending Articles



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