|
Home > Archive > BizTalk Server General > March 2005 > Error: The document is empty. Contact the sender.????
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Error: The document is empty. Contact the sender.????
|
|
| trinity 2005-03-24, 5:50 pm |
| I am getting this strange error:
"The document is empty. Contact the sender.
target document is empty"
The document is most definitely not empty.
In the same orchestration, I have 2 send ports at the end. 1 creates
an EDI file, the other creates an XML file. The one that creates the
XML file works fine, but the one that creates the EDI file gives the
error above. Both sends come from the same ConstructMessage object,
so how can the EDI one be empty?
When I go into the EDI reports in HAT, and do a show EDI message, it
shows the contents of the data to be converted to EDI, and it isn't
empty. It actually is the same as the XML file created by the other
send object.
Any ideas?
Thank you!
| |
| trinity 2005-03-28, 6:12 pm |
| To answer my own question again (but hopefully someone else will get
something out of this, and will bang their head less than I did)
So, I think the problem was caused by my not having the Covast EDI
extension turned on for my EDI schema (810schema.xsd). I reason I
turned it off is because it increases compile time on the project
dramatically, and on my development machine, I noticed that it did
not need to be turned on for the project to compile successfully.
But, I think when I moved to the new server, somehow, on the FIRST
compile, it needs to have the extension turned on, so to actually
compile it. Because once I did that, everything worked. And then
after that, I turned it off (like I did on the development machine),
and the project still compiled and works successfully.
| |
|
| Hi,
for an explanation of what's going on refer to article 887481
In the base EDI adapter the Schema are the distribution channel for the edi
tables as well as the xml schema. So every time you do a compile or validate
on the schema it seems to re-populate the EDI adapter database. As you found,
if you are using standrd edi it is pointless doing this every time. You may
be able just to deploy live.eif from the development system. I'm note quite
sure about the partners though.
m
"trinity" wrote:
> To answer my own question again (but hopefully someone else will get
> something out of this, and will bang their head less than I did)
>
> So, I think the problem was caused by my not having the Covast EDI
> extension turned on for my EDI schema (810schema.xsd). I reason I
> turned it off is because it increases compile time on the project
> dramatically, and on my development machine, I noticed that it did
> not need to be turned on for the project to compile successfully.
> But, I think when I moved to the new server, somehow, on the FIRST
> compile, it needs to have the extension turned on, so to actually
> compile it. Because once I did that, everything worked. And then
> after that, I turned it off (like I did on the development machine),
> and the project still compiled and works successfully.
>
>
|
|
|
|
|