Ok, well you did help me out after all!
I did not get any compile errors on my project but, when I
Orchestrations-project keyfile I noticed it was different then the other
project. I think I moved it in the middle of building the project. So, I
was
able to config the Flat file assembly correctly after that. Then I had to
undeploy and redeploy (after figuring out how to redeploy a project) and I
was able to add the send ****t correctly.
Although, the files still are not being delivered to the new locations. I
guess I can use the HAT tool to do some debugging on message delivery.
"Jan Eliasen" wrote:
> On Thu, 12 Apr 2007 00:53:32 +0200, Jan Eliasen
> <eliasen@[EMAIL PROTECTED]
> wrote:
>
> >Feel free to email me your project, and I will take a look at it. If
> >you choose to email me the project, please include some reference to
> >this thread in the email, so I can find it.
> And you did! :-)
>
> Well, I'm afraid I had no problems with your solution at all.
>
> First, I compiled the solution. That gave me a cruptographic error,
> because the Orchestrations-project had the wrong path to the keyfile.
> Once that was fixed, your solution compiled just fine.
>
> Then, I opened your ERPPipeline, and clicked on the flat file
> assembler. Then, I clicked on the dropdown box, and at the very end of
> that list, your two schemas appeared. I chose the .Request schema, and
> rebuild the project. No problems. Then, I changed the servername to be
> deployed to in the properties of your projects and I deployed the
> EAISchemas project. I refreshed BizTalk Explorer, and created a new
> send ****t. The pipeline showed up just fione in the drop down for
> pipelines.
>
> So basically, there is nothing wrong with your files :-)
>
> I hope there was something in the description of what I did that made
> you think "Damn, I forgot that..." and then it all works. The only
> thing I can think of to troubleshoot any further is, if you can give
> me remote access to your machine?
>
> --
> eliasen, representing himself and not the company he works for.
>
> Private blog: http://blog.eliasen.dk
>
> Private email: jan@[EMAIL PROTECTED]
>
|
