on 06-12-2018 2:52 PM
We are trying to use the service consumer "CollectiveLearningActivityReplicateRequest_Out" (class itnerface name: CO_PIQ_COLLECTIVELA_RQ) to send information to our external LMS system. However, when I try to create the logical ports for the service in the SOAMANAGER I keep getting the error: "Initialization of proxy 'CO_PIQ_COLLECTIVELA_RQ' failed: Web service object does not exist". Can anyone tell me why is this error popping up, is there some step in between we're missing out?
Hi Sashko,
This error can be caused by inconsistent data in tables SPROXHDR and SPROXDAT - ie. some objects might be present in one and not the other.
I would recommend that you compare these tables for the given proxy and you see any missing objects transport them from another system, where this is consistent. Maybe transporting the entire proxy would also solve the problem.
(This is just an idea based on the error message, the root cause could be completely different as well.)
Best regards,
Patrik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your comment Patrik. I can see that for the proxy: CO_PIQ_COLLECTIVELA_RQ I have 3 records in the SPROXDAT table (CLASS: CO_PIQ_COLLECTIVELA_RQ, and 2 methods: EXECUTE_ASYNCHRONOUS) while in SPROXHDR I only have 1 (the class CO_PIQ_COLLECTIVELA_RQ). Is that the inconsistency you're referring to, or are these two tables just a header and item tables and that should be expected?
By the way, it's the same case in all our environments (DEV,TEST & PRD) so I don't think we can transport them from another system (assuming that is the solution).
- Sashko
Hi Sashko,
If this is the same in other systems as well, most likely that's not the root cause here. The two tables don't have to contain the very same number of entries, so this by itself is not an indication for inconsistency.
Do you get a syntax error if you check the proxy class in SE80 or SPROXY_START? Otherwise I'm not sure what could be the reason, probably it worth to debug the logical port creation.
One more thing: Do you get the same error when you create the Logical port using a WSDL or manual config?
Cheers,
Attila
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.