| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SAP Request 8.0.0.5 Error 3424 if Library is used for SAP |
« View previous topic :: View next topic » |
| Author |
Message
|
| LiamDuffield |
 Posted: Mon Apr 13, 2015 2:20 am Post subject: SAP Request 8.0.0.5 Error 3424 if Library is used for SAP |
 |
|
Newbie
Joined: 14 Mar 2014
Posts: 7
|
Hi All,
Recently applied fixpack 8.0.0.5 from 8.0.0.1 and I am currently receving the following error message when the integration pieces attempt to call our SAP system:
"attempted to use type which is not in the message set. TypeName:SAPFIELDNAMEHERE Application: Valid Types:"
These have previously worked correctly.
This only appears to happen on flows that use a library for their SAP adapters/XSDs.
If the adapter/XSDs are in the application, all works correctly.
User/Service trace don't seem to give me anything useful to go on.
Has anyone else seen this behavior at all before I look at raising a PMR? |
|
| Back to top |
|
 |
| LiamDuffield |
| Posted: Mon Apr 13, 2015 3:35 am Post subject: |
|
|
Newbie
Joined: 14 Mar 2014
Posts: 7
|
Quick update.
Re-deploying the application seems to work, until the EG is restarted, then it fails to call SAP with the same error message.
This also occurs if the EG is stopped, then started.
Edit:
I've raised a PMR with IBM for this. I'll update if I hear anything. |
|
| Back to top |
|
|
| ipujals |
| Posted: Tue Jun 09, 2015 5:55 am Post subject: |
|
|
Apprentice
Joined: 26 Jun 2012
Posts: 31
|
Hi Liam,
I have the same problem. Were you able to get a solution for this?
Thanks!! |
|
| Back to top |
|
|
| tth |
| Posted: Wed Jun 24, 2015 5:54 am Post subject: |
|
|
Newbie
Joined: 24 Jun 2015
Posts: 1
|
Hi All,
a customer is experiencing the same error after updating Integration Bus 9.0.0.0 to 9.0.0.3, was anyone able to solve this yet?
Thank you! |
|
| Back to top |
|
|
| LiamDuffield |
| Posted: Thu Jun 25, 2015 1:09 am Post subject: |
|
|
Newbie
Joined: 14 Mar 2014
Posts: 7
|
Hi All,
Sorry the delay in replying.
We raised the PMR with IBM and it was an issue with the latest fixpacks of Broker V8 and V9.
We tested the APAR interim fix in our DEV and QAS environments and haven't seen the issue since.
APAR is IT08961 |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
