| Author |
Message
|
| LH33 |
 Posted: Thu Dec 23, 2004 6:42 am Post subject: HELP!! - BIP0062E Cannot read the XML data stream |
 |
|
Master
Joined: 21 Nov 2002
Posts: 200
|
I added a message flow to my workspace, modified 2 lines of code and attempted to check it back in to deploy and test. I received the following error when checking back in:
********************************************************
BIP0062E Cannot read the XML data stream for a resource.
This is an internal error.
The following error occurred when parsing an XML data stream.
Processing d6a0d58a-0001-0000-0080-dbb6074ea8f4, at line 391 before column 30, Invalid XML character. (Unicode: 0x0)
Turn on Control Center tracing to capture details of the error.
Retry the operation and contact your IBM support center.
********************************************************
Does anyone know how to fix this so I can check the flow back in?
Thanks, Lisa |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Dec 23, 2004 6:48 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I am assuming you retried it, and you get the same error.
I am assuming you tried restarting your Control Center, and still got the same error.
Try cutting your ESQL out of the editor, paste it into Notepad. Close the Compute node window, and then open it again. Recopy your ESQL ouf ot Notepad and back into the code area.
If this doesn't work... and since it's only TWO lines of code... try unlocking the flow, removing it from your workspace, restarting the Control Center, and start over.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| LH33 |
| Posted: Thu Dec 23, 2004 7:20 am Post subject: |
|
|
Master
Joined: 21 Nov 2002
Posts: 200
|
I tried all of that. I tried the unlock and it gave me the same message. Any other ideas?
Thanks! |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 23, 2004 7:39 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Try restarting your config manager...
or, of course...
| Quote: |
Turn on Control Center tracing to capture details of the error.
Retry the operation and contact your IBM support center. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sieijish |
| Posted: Thu Dec 23, 2004 8:33 am Post subject: |
|
|
Acolyte
Joined: 29 Nov 2004
Posts: 67
Location: London
|
- "at line 391 before column 30, Invalid XML character"
Check your input xml data. It has some invalid xml characters (eg: you can't have '<' char in your message data unless it is in CDATA section). Remove those & try again.
Try opening the xml in any standard xml editor or even IE and you can easily detect such parsing errors. |
|
| Back to top |
|
|
| LH33 |
| Posted: Thu Dec 23, 2004 8:35 am Post subject: |
|
|
Master
Joined: 21 Nov 2002
Posts: 200
|
| The error is in the XML that WMQI generates to identify the Message Flow. It is not in my code. I looked at that and there are no invalid characters. |
|
| Back to top |
|
|
| sieijish |
| Posted: Thu Dec 23, 2004 9:05 am Post subject: |
|
|
Acolyte
Joined: 29 Nov 2004
Posts: 67
Location: London
|
If the xml files representing the message flow or mapping node is corrupted, it won't show up properly in your workbench.
At what point in the message flow are you getting the error? Is it getting past your input node? Are you using XML domain? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 23, 2004 9:20 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| sieijish wrote: |
If the xml files representing the message flow or mapping node is corrupted, it won't show up properly in your workbench.
At what point in the message flow are you getting the error? Is it getting past your input node? Are you using XML domain? |
Lisa is using version 2.1. She doesn't have mapping nodes or workbenches.
She has not deployed the flow yet. She is not experiencing the error during runtime.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 23, 2004 9:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Did you try restarting your config manager? Did it give you errors during startup?
You can try forcing the unlock from the IBMMQSI2 user. Then try checking the flow out onto a different computer. If that is successfully, try deleting the workspace on your "bad" computer.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
