community-content

Forum Replies Created

Viewing 15 posts - 1,576 through 1,590 (of 9,648 total)
  • Author
    Posts
  • in reply to: BizTalk SQL adapter and the SQL 2005 XML datatype #24307

    I found that run in query analyser the insert query was ok and actually ran incredibly quick.

    There are a few techniques. 

    Alter the database design to save individual messages or smaller batch sizes and submit the data a few rows at a time (kinda obvious and easy, but too me this was ugly, but in the end the solution we plumbed for)

    Use the sql bulk load adapter written by .  While this works, the company I was working for would not allow an adapter that was not built and tested in house.  http://blog.biztalk-info.com/archive/2009/02/18/SQL_Bulk_Load_adapter.aspx

    Am on an extended holiday at the mo, so this is all from (hazy) memory.

    Hope this helps..

     

    3.

    Hi Raj,

        I still have this issue. I am looking for a solution.

     

    Please help.

     

    Thanks

    Mallesh B

    in reply to: Exception with two-way receive port direct binding #24305

    I have the same problem, but i set the BTS.EpmRRCorrelationToken value to a random value, new GUID in my case, in the first orchestration before send to the direct binding port and then in the secod orchestration i copy the value from the inputMessage to the outputMessage, so the value remains the same. With this method BizTalk knows how to correlate the response back to the caller.

    in reply to: BizTalk SQL adapter and the SQL 2005 XML datatype #24303

    Hi Dino,

     

    could you give me a hint how you are getting around this error?

     

    Thanks and regards,

    Julian

    Hi Mallesh,

    Did you get the solution for this problem

    Thanks,

    Raj

     

     

    in reply to: BizTalk reject Japanese or Chinese characters #24301

    What encoding is being used.
    This is specified in the xml specification at the beginning of the message:

    <? xml version=”1.0″ encoding=”utf-16″ ?>

    If the encoding is not specified, the default of utf-8 is used.

    in reply to: Need a solution on Flat files #24298

    Hi Hitu,

     

       In your BizTalk orchestration, just declare a message of type Xml.XmlDocument, which is the untyped message that does not relate to any schema. After you have GAC’ed your helper class, you can reference it in your orchestration by instantiating it, and passing that untyped message to a class method in an Expression shape.

       Assuming that your third file is returned by your helper class, you can declare another message of type Xml.XmlDocument to hold its contents, and send it to a port mapped to the FTP adapter in your Orchestration.

     

       Hope this helps,

     

       Daniel.

     

    in reply to: BAM Hotfix Event ID 14014 for X64 bit Servers #24296

    Just to close this out – I found out the issue was disabling the Antivirus, Rebooting, and then run the Hotfix.

     

    Hope this helps someone ; )

    in reply to: Byte-Order-Mark (BOM) in SOAP response message #24295

    Thanks Daniel. It doesn’t solve my problem. I’m taking my discussion to the post you referred to and hopefully someone or yourself can help me with.

     

    Cheers,

    Spike

    in reply to: Problem with bitmap on custom functoid #24294

    Close you visual studio and open again.

    in reply to: Change replyto in WCF Header #24293

    Hi,

    Thanks for your response

    Is there a way to change the replyto in the header of the message before sending it to the service from the biztalk send port.

    Thanks for your help in advance

    in reply to: BAM Hotfix Event ID 14014 for X64 bit Servers #24292

    Just put in a call to Microsoft and this hotfix is for both 32 and 64 bit machines since it’s managed code.  I’m getting “installer terminated prematurely” and still cannot get this to install. 

    Error log around the error looks like this…

    02/25/10 15:11:03 DDSet_Exit: CMsHelpObject destructor
    MSI (s) (18:44) [15:11:03:819]: Executing op: ProgressTotal(Total=2,Type=1,ByteEquivalent=1300000)
    MSI (s) (18:44) [15:11:03:819]: Executing op: ServiceControl(,Name=WinMgmt,Action=2,Wait=1,)
    MSI (s) (18:44) [15:11:04:756]: Internal Exception during install operation: 0xc00000fd at 0x0000000077EF3CB2.
    MSI (s) (18:44) [15:11:04:756]: WER report disabled for non-console install.
    MSI (s) (18:44) [15:11:04:756]: Internal MSI error. Installer terminated prematurely.

    MSI (s) (18:44) [15:11:07:256]: MainEngineThread is returning 1603
    MSI (s) (18:44) [15:11:07:256]: Destroying RemoteAPI object.
    MSI (s) (18:B0) [15:11:07:256]: Custom Action Manager thread ending.
    Installer terminated prematurely.
    MSI (c) (A4:68) [15:11:04:756]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

    MSI (c) (A4:FC) [15:11:07:272]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (A4:FC) [15:11:07:272]: MainEngineThread is returning 1603
    === Verbose logging stopped: 2/25/2010  15:11:07 ===

    [02/25/10 15:11:07] Operation succeeded.
    [02/25/10 15:11:07] Process exit code is 1603.
    [02/25/10 15:11:07] Operation failed. Error code is 1603.

    Has anyone seen this before?

    Thanks!

    Perhaps you can manipulate it, but why?  The 997 simply acknowledges that you received the EDI transmission and Biztalk handles all the details for you.  It is not intended to give any information about whether the contents of the transmission were usable.  The 824 message type exists for just that purpose.  If you intercept and modify the 997, then every Biztalk upgrade becomes much harder.  If your vendor changes their EDI software, then you might have problems.  Save yourself all these headaches and let Biztalk send the 997 and then generate and transmit the 824 in an orchestration that receives the 210.  If you use the EDI protocol the way it was intended, you will  have far fewer headaches supporting it.

    in reply to: No subscribers, or no promotion #24289

    It is very nice, it worked perfect for me too.

    I tried this one, but it still didnt help me connect to a 2006 database with 2006 R2 installed on my local computer..

Viewing 15 posts - 1,576 through 1,590 (of 9,648 total)