none
837_P v/s 837_I RRS feed

  • Question

  • I have the following first lines for the two different 837's in my xml message as follows.

    <ns0:X12_00401_837_I xmlns:ns0="http://schemas.microsoft.com/BizTalk/EDI/X12/2006">

    <ns0:X12_00401_837_P xmlns:ns0="http://schemas.microsoft.com/BizTalk/EDI/X12/2006">

    The 837_I is for Institutional and 837_P is for Professional.

    Here is the problem I am having. The outgoing message always take the default GS values from the EDI Party setup. In Party setup:

    1. I have selected the ST1 from the drop down 837_I and 837_P respectively.
    2. I have version as 00401 for both lines in party setup
    3. The namespace is "http://schemas.microsoft.com/BizTalk/EDI/X12/2006"
    4. Other values are same as it is the same destination party except the GS08 values are "004010X098A1" for Professional and "004010X096A1" for Institutional

    Problem Statement -- Both 837's process fine but the GS values of the default are taken. Which means the GS8 values comes out the same for both transactions. So Professional is also treated as Instituitnal :(

    Any suggestions. I have tried lot of things but to no avail.

    Regards,
    -amit
    amit kumar
    Tuesday, March 3, 2009 11:43 PM

Answers

  • HI,
         I tried the same scenario. scenario is:

    1- I used Xmlreceive receive pipeline and edisend send pipeline.
    2- I have selected the ST1 from the drop down 837_I and 837_P respectively.
    3- I have version as 00401 for both lines in party setup
    4- The namespace is "http://schemas.microsoft.com/BizTalk/EDI/X12/2006"
    5- Other values are same as it is the same destination party except the GS08 values are "004010X098A1" for Professional and "004010X096A1" for Institutional
    6- I selected 837_I grid in both grids as default.
    7- droped a 837_P message. having following lines :

    <ns0:X12_00401_837_P xmlns:ns0="http://schemas.microsoft.com/BizTalk/EDI/X12/2006">

    8- Got a edi message having following GS header:

    GS*HC*354*65*20090304*113652*9*X*004010X098A1~




    So I am not able to repro the scenario. Can you tell me are you doing some extra things like mapping or batching or any other processing . such that I can repro the fault here?



    Thanks
    Gyan
    Wednesday, March 4, 2009 6:14 AM
  • Please ask to your Microsoft support team for getting this patch. Using KB article number 951760.



    Thanks
    Gyan
    • Marked as answer by technoamit Friday, June 19, 2009 3:07 PM
    Monday, March 16, 2009 2:04 PM

All replies

  • HI,
         I tried the same scenario. scenario is:

    1- I used Xmlreceive receive pipeline and edisend send pipeline.
    2- I have selected the ST1 from the drop down 837_I and 837_P respectively.
    3- I have version as 00401 for both lines in party setup
    4- The namespace is "http://schemas.microsoft.com/BizTalk/EDI/X12/2006"
    5- Other values are same as it is the same destination party except the GS08 values are "004010X098A1" for Professional and "004010X096A1" for Institutional
    6- I selected 837_I grid in both grids as default.
    7- droped a 837_P message. having following lines :

    <ns0:X12_00401_837_P xmlns:ns0="http://schemas.microsoft.com/BizTalk/EDI/X12/2006">

    8- Got a edi message having following GS header:

    GS*HC*354*65*20090304*113652*9*X*004010X098A1~




    So I am not able to repro the scenario. Can you tell me are you doing some extra things like mapping or batching or any other processing . such that I can repro the fault here?



    Thanks
    Gyan
    Wednesday, March 4, 2009 6:14 AM
  • It is pretty much the same scenario you reproduced. I have a 837 in and I am looking up certain values etc..and routing it to respective mailboxes. The messages is as is. I did have to apply a patch. The KB for that is "KB939080" I had to install this to get new schemas to fix REF looping issues.

    You think i am missing something?

    -a
    amit kumar
    Wednesday, March 4, 2009 2:04 PM
  • Can you send your binding xml file? Such that I can repro this scenario.

    May be this will help in resolving your problem.


    Thanks
    Gyan
    Wednesday, March 4, 2009 5:20 PM
  • the binding file is too big and cannot send as attachment.....here is a snippet..hope this will help...

    <Party Name="TPA_LOB1_BATCH">
          <Aliases>
            <PartyAlias Name="Organization" Qualifier="OrganizationName" Value="TPA_LOB1_BATCH" IsAutoCreated="true" />
          </Aliases>
          <SendPorts>
            <SendPortRef Name="SP_LOB_01_TPA" />
          </SendPorts>
          <SignatureCert xsi:nil="true" />
          <EdiData>
            <PartyEDIProperties PartyName="TPA_LOB1_BATCH">
              <PartnerAgreement xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                <IsSender>false</IsSender>
                <PartyName>TPA_LOB1_BATCH</PartyName>
                <Contacts />
                <AgreementStartDate xsi:nil="true" />
                <AgreementEndDate xsi:nil="true" />
                <ActivateStatusReporting>false</ActivateStatusReporting>
                <StoreTransactionSet>false</StoreTransactionSet>
              </PartnerAgreement>
              <PartnerEdifact xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                <IsSender>true</IsSender>
                <PartyName>TPA_LOB1_BATCH</PartyName>
                <PartnerEdifactReceiverGroups />
                <PartnerEdifactSenderGroups>
                  <anyType xsi:type="PartnerEdifactSenderGroupUpdatable">
                    <IsSender>true</IsSender>
                    <PartyName>TPA_LOB1_BATCH</PartyName>
                    <TargetNamespace>http://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006</TargetNamespace>
                    <UngDefaultSetting>true</UngDefaultSetting>
                  </anyType>
                </PartnerEdifactSenderGroups>
                <UnaGenerateSegment>true</UnaGenerateSegment>
                <Una1>:</Una1>
                <Una2>+</Una2>
                <Una3>,</Una3>
                <Una4>?</Una4>
                <Una5>*</Una5>
                <Una6>'</Una6>
                <Una6Suffix>None</Una6Suffix>
                <Unb1Id>UNOB</Unb1Id>
                <Unb1Version>1</Unb1Version>
                <Unb5CheckDup>true</Unb5CheckDup>
                <Unb5DupValidity>30</Unb5DupValidity>
                <Unb5>1</Unb5>
                <Unb9>0</Unb9>
                <Unb11>false</Unb11>
                <UngCreateSegments>false</UngCreateSegments>
                <Ung5>1</Ung5>
                <Ung5CheckDup>false</Ung5CheckDup>
                <UnhApplyNewId>true</UnhApplyNewId>
                <UnhCheckDup>false</UnhCheckDup>
                <UnhRefNumber>1</UnhRefNumber>
                <SetSequenceNumberFlag>None</SetSequenceNumberFlag>
              </PartnerEdifact>
              <PartnerAckValidation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                <IsSender>true</IsSender>
                <PartyName>TPA_LOB1_BATCH</PartyName>
                <RouteAcktoSendPipeline>true</RouteAcktoSendPipeline>
                <SendTechnicalAck>false</SendTechnicalAck>
                <DontBatchTechnicalAck>false</DontBatchTechnicalAck>
                <SendFunctionalAck>false</SendFunctionalAck>
                <ExpectFunctionalAck>false</ExpectFunctionalAck>
                <DontBatchFunctionalAck>false</DontBatchFunctionalAck>
                <GenerateLoopForValidMessagesInAck>false</GenerateLoopForValidMessagesInAck>
                <ValidateEdiType>true</ValidateEdiType>
                <IgnoreInvalidChars>false</IgnoreInvalidChars>
                <ValidateExtended>false</ValidateExtended>
                <AllowTrailingDelimiters>false</AllowTrailingDelimiters>
                <GenerateTrailingDelimiters>false</GenerateTrailingDelimiters>
                <CreateEmptyXmlTagsForTrailingSeparators>true</CreateEmptyXmlTagsForTrailingSeparators>
                <MaskSecurityInfo>true</MaskSecurityInfo>
                <ConvertImpliedDecimal>false</ConvertImpliedDecimal>
                <PreserveBatch>TransactionSetXML</PreserveBatch>
                <EdiEncoding>Edifact</EdiEncoding>
              </PartnerAckValidation>
              <PartnerEdifact xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                <IsSender>false</IsSender>
                <PartyName>TPA_LOB1_BATCH</PartyName>
                <PartnerEdifactReceiverGroups />
                <PartnerEdifactSenderGroups />
                <UnaGenerateSegment>true</UnaGenerateSegment>
                <Una1>:</Una1>
                <Una2>+</Una2>
                <Una3>,</Una3>
                <Una4>?</Una4>
                <Una5>*</Una5>
                <Una6>'</Una6>
                <Una6Suffix>None</Una6Suffix>
                <Unb1Id>UNOB</Unb1Id>
                <Unb1Version>1</Unb1Version>
                <Unb5CheckDup>true</Unb5CheckDup>
                <Unb5DupValidity>30</Unb5DupValidity>
                <Unb5>1</Unb5>
                <Unb9>0</Unb9>
                <Unb11>false</Unb11>
                <UngCreateSegments>false</UngCreateSegments>
                <Ung5>1</Ung5>
                <Ung5CheckDup>false</Ung5CheckDup>
                <UnhApplyNewId>true</UnhApplyNewId>
                <UnhCheckDup>false</UnhCheckDup>
                <UnhRefNumber>1</UnhRefNumber>
                <SetSequenceNumberFlag>None</SetSequenceNumberFlag>
              </PartnerEdifact>
              <PartnerAckValidation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                <IsSender>false</IsSender>
                <PartyName>TPA_LOB1_BATCH</PartyName>
                <RouteAcktoSendPipeline>true</RouteAcktoSendPipeline>
                <SendTechnicalAck>false</SendTechnicalAck>
                <DontBatchTechnicalAck>false</DontBatchTechnicalAck>
                <SendFunctionalAck>false</SendFunctionalAck>
                <ExpectFunctionalAck>false</ExpectFunctionalAck>
                <DontBatchFunctionalAck>false</DontBatchFunctionalAck>
                <GenerateLoopForValidMessagesInAck>false</GenerateLoopForValidMessagesInAck>
                <ValidateEdiType>true</ValidateEdiType>
                <IgnoreInvalidChars>false</IgnoreInvalidChars>
                <ValidateExtended>false</ValidateExtended>
                <AllowTrailingDelimiters>false</AllowTrailingDelimiters>
                <GenerateTrailingDelimiters>false</GenerateTrailingDelimiters>
                <CreateEmptyXmlTagsForTrailingSeparators>true</CreateEmptyXmlTagsForTrailingSeparators>
                <MaskSecurityInfo>true</MaskSecurityInfo>
                <ConvertImpliedDecimal>false</ConvertImpliedDecimal>
                <PreserveBatch>TransactionSetXML</PreserveBatch>
                <EdiEncoding>Edifact</EdiEncoding>
              </PartnerAckValidation>
              <PartnerX12 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                <IsSender>true</IsSender>
                <PartyName>TPA_LOB1_BATCH</PartyName>
                <PartnerX12ReceiverGroups />
                <PartnerX12SenderGroups>
                  <anyType xsi:type="PartnerX12SenderGroupUpdatable">
                    <IsSender>true</IsSender>
                    <PartyName>TPA_LOB1_BATCH</PartyName>
                    <GSTargetNamespace>http://schemas.microsoft.com/BizTalk/EDI/X12/2006</GSTargetNamespace>
                    <GSDefaultSetting>true</GSDefaultSetting>
                  </anyType>
                </PartnerX12SenderGroups>
                <Isa5>ZZ</Isa5>
                <Isa6>MERTPA</Isa6>
                <Isa7>ZZ</Isa7>
                <Isa8>MERITAIN1</Isa8>
                <Isa11UseAsRepSep>false</Isa11UseAsRepSep>
                <Isa11>U</Isa11>
                <Isa12>00401</Isa12>
                <Isa13>1</Isa13>
                <Isa13CheckDup>false</Isa13CheckDup>
                <Isa13DupValidity>30</Isa13DupValidity>
                <Isa14>false</Isa14>
                <Isa15>T</Isa15>
                <DESeparator>*</DESeparator>
                <CESeparator>:</CESeparator>
                <SegmentTerminator>~</SegmentTerminator>
                <SegmentTerminatorSuffix>None</SegmentTerminatorSuffix>
                <GS6CheckDup>false</GS6CheckDup>
                <GS6>1</GS6>
                <TSCheckDup>false</TSCheckDup>
                <TSApplyNewId>true</TSApplyNewId>
                <TSControlNumber>1</TSControlNumber>
                <X12CharSet>UTF8</X12CharSet>
                <SetSequenceNumberFlag>None</SetSequenceNumberFlag>
              </PartnerX12>
              <PartnerAckValidation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                <IsSender>true</IsSender>
                <PartyName>TPA_LOB1_BATCH</PartyName>
                <RouteAcktoSendPipeline>true</RouteAcktoSendPipeline>
                <SendTechnicalAck>false</SendTechnicalAck>
                <DontBatchTechnicalAck>false</DontBatchTechnicalAck>
                <SendFunctionalAck>false</SendFunctionalAck>
                <ExpectFunctionalAck>false</ExpectFunctionalAck>
                <DontBatchFunctionalAck>false</DontBatchFunctionalAck>
                <GenerateLoopForValidMessagesInAck>false</GenerateLoopForValidMessagesInAck>
                <ValidateEdiType>false</ValidateEdiType>
                <IgnoreInvalidChars>false</IgnoreInvalidChars>
                <ValidateExtended>false</ValidateExtended>
                <AllowTrailingDelimiters>false</AllowTrailingDelimiters>
                <GenerateTrailingDelimiters>false</GenerateTrailingDelimiters>
                <CreateEmptyXmlTagsForTrailingSeparators>true</CreateEmptyXmlTagsForTrailingSeparators>
                <MaskSecurityInfo>true</MaskSecurityInfo>
                <ConvertImpliedDecimal>false</ConvertImpliedDecimal>
                <PreserveBatch>TransactionSetXML</PreserveBatch>
                <EdiEncoding>X12</EdiEncoding>
              </PartnerAckValidation>
              <PartnerX12 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                <IsSender>false</IsSender>
                <PartyName>TPA_LOB1_BATCH</PartyName>
                <PartnerX12ReceiverGroups>
                  <anyType xsi:type="PartnerX12ReceiverGroupUpdatable">
                    <IsSender>false</IsSender>
                    <PartyName>TPA_LOB1_BATCH</PartyName>
                    <GSTransactionId>837_P</GSTransactionId>
                    <GSVersion>00401</GSVersion>
                    <GSTargetNamespace>http://schemas.microsoft.com/BizTalk/EDI/X12/2006</GSTargetNamespace>
                    <GS1>HC</GS1>
                    <GS2>MERITAIN1</GS2>
                    <GS3>MERTPA</GS3>
                    <GS4>CCYYMMDD</GS4>
                    <GS5>HHMM</GS5>
                    <GS7>X</GS7>
                    <GS8>004010X098A1</GS8>
                    <GSDefaultSetting>true</GSDefaultSetting>
                  </anyType>
                  <anyType xsi:type="PartnerX12ReceiverGroupUpdatable">
                    <IsSender>false</IsSender>
                    <PartyName>TPA_LOB1_BATCH</PartyName>
                    <GSTransactionId>837_I</GSTransactionId>
                    <GSVersion>00401</GSVersion>
                    <GSTargetNamespace>http://schemas.microsoft.com/BizTalk/EDI/X12/2006</GSTargetNamespace>
                    <GS1>HC</GS1>
                    <GS2>MERITAIN1</GS2>
                    <GS3>MERTPA</GS3>
                    <GS4>CCYYMMDD</GS4>
                    <GS5>HHMM</GS5>
                    <GS7>X</GS7>
                    <GS8>004010X096A1</GS8>
                    <GSDefaultSetting>false</GSDefaultSetting>
                  </anyType>
                  <anyType xsi:type="PartnerX12ReceiverGroupUpdatable">
                    <IsSender>false</IsSender>
                    <PartyName>TPA_LOB1_BATCH</PartyName>
                    <GSTransactionId>837_D</GSTransactionId>
                    <GSVersion>00401</GSVersion>
                    <GSTargetNamespace>http://schemas.microsoft.com/BizTalk/EDI/X12/2006</GSTargetNamespace>
                    <GS1>HC</GS1>
                    <GS2>MERITAIN1</GS2>
                    <GS3>MERTPA</GS3>
                    <GS4>CCYYMMDD</GS4>
                    <GS5>HHMM</GS5>
                    <GS7>X</GS7>
                    <GS8>004010X097A1</GS8>
                    <GSDefaultSetting>false</GSDefaultSetting>
                  </anyType>
                </PartnerX12ReceiverGroups>
                <PartnerX12SenderGroups />
                <Isa5>ZZ</Isa5>
                <Isa6>MERITAIN1</Isa6>
                <Isa7>ZZ</Isa7>
                <Isa8>MERTPA</Isa8>
                <Isa11UseAsRepSep>false</Isa11UseAsRepSep>
                <Isa11>U</Isa11>
                <Isa12>00401</Isa12>
                <Isa13>49</Isa13>
                <Isa13CheckDup>true</Isa13CheckDup>
                <Isa13DupValidity>30</Isa13DupValidity>
                <Isa14>false</Isa14>
                <Isa15>T</Isa15>
                <DESeparator>*</DESeparator>
                <CESeparator>:</CESeparator>
                <SegmentTerminator>~</SegmentTerminator>
                <SegmentTerminatorSuffix>Crlf</SegmentTerminatorSuffix>
                <GS6CheckDup>false</GS6CheckDup>
                <GS6>253</GS6>
                <TSCheckDup>false</TSCheckDup>
                <TSApplyNewId>true</TSApplyNewId>
                <TSControlNumber>317</TSControlNumber>
                <X12CharSet>UTF8</X12CharSet>
                <SetSequenceNumberFlag>None</SetSequenceNumberFlag>
              </PartnerX12>
              <PartnerAckValidation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                <IsSender>false</IsSender>
                <PartyName>TPA_LOB1_BATCH</PartyName>
                <RouteAcktoSendPipeline>true</RouteAcktoSendPipeline>
                <SendTechnicalAck>false</SendTechnicalAck>
                <DontBatchTechnicalAck>false</DontBatchTechnicalAck>
                <SendFunctionalAck>false</SendFunctionalAck>
                <ExpectFunctionalAck>false</ExpectFunctionalAck>
                <DontBatchFunctionalAck>false</DontBatchFunctionalAck>
                <GenerateLoopForValidMessagesInAck>false</GenerateLoopForValidMessagesInAck>
                <ValidateEdiType>false</ValidateEdiType>
                <IgnoreInvalidChars>false</IgnoreInvalidChars>
                <ValidateExtended>false</ValidateExtended>
                <AllowTrailingDelimiters>false</AllowTrailingDelimiters>
                <GenerateTrailingDelimiters>false</GenerateTrailingDelimiters>
                <CreateEmptyXmlTagsForTrailingSeparators>true</CreateEmptyXmlTagsForTrailingSeparators>
                <MaskSecurityInfo>true</MaskSecurityInfo>
                <ConvertImpliedDecimal>false</ConvertImpliedDecimal>
                <PreserveBatch>TransactionSetXML</PreserveBatch>
                <EdiEncoding>X12</EdiEncoding>
              </PartnerAckValidation>
              <PartnerBatchUpdatable xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                <IsSender>false</IsSender>
                <PartyName>TPA_LOB1_BATCH</PartyName>


    amit kumar
    Wednesday, March 4, 2009 5:43 PM
  • Actually, I am using batching. I told you before I was not. i wish I can send you a screen capture of my GS settings. I am thinking this is a bug of some sort.


    amit kumar
    Wednesday, March 4, 2009 8:10 PM
  • Can you explain your total scenario ( including batching). Such that I can repro in my machine.



    Thanks
    Gyan
    Thursday, March 5, 2009 4:05 PM
  • Here is the scenario. i have removed Batching from the scenario to make it simple.

    1. EDI837 Pro. and Ins. is received. (pure EDI)
    2. The Files are read in a ODX (1 for each 837 type which means I have 2 ODX) and several business rules are performed. The message integrity is maintained all the way.
    3. the 837's are written out via Send Ports which are selected in Party setup.
    4. The party setup is simple. Under Party as Receiver---under GSandST settings....2 GS lines for the party as they can receive both 837's only difference is ST1 is 837_I and 837_P and GS08 - values are unique as per the 837 type. Rest all the information is same for both GS
    5. The default GS checked is what gets picked up. For some reason my message is not getting matched or resolved with this Party Setup.

    Here is the first line from my xml.


    <ns0:X12_00401_837_P xmlns:ns0="http://schemas.microsoft.com/BizTalk/EDI/X12/2006">

    <ns0:X12_00401_837_I xmlns:ns0="http://schemas.microsoft.com/BizTalk/EDI/X12/2006">


    Let me know if I can give more information.
    amit kumar
    Thursday, March 5, 2009 4:27 PM
  • Hi Prakash,
    My issue is still not resolved. I did the setup on a different machine with no luck.

    Although I have questions on Points "2" and "6" in your solution/secnario

    A. Question on your Point # 2 is do you have just "837_I" and "837_P" in your drop down as my drop down has the following
     
    837_I - Health Care Claim: Institutional
    837_P - Health Care Claim: Professional

    B. Question on your Point # 6 is that which "both grids" you have this checked. Is that one at a time or some other place you set GS items which I am missing. I can select only one box as defualt at a time.

    Also, I have a prolog before my file. I never had issue with that before. I removed the prolog and still it would not work.

    I think the last issue is the encoding of the file as I am splitting these files in ODX before EDI engine picks up the XML. So my ODX might be gnerating a encoded message that the EDI engine cannot understand or the Party setup needs to be setup specifically to handle this Encoding. May be if it encoding issue then I might have to do something in my ODX to switch the encoding to the requried one for EDI engine

    Let me know.

    Thanks.
    -a
    amit kumar
    Wednesday, March 11, 2009 10:52 PM
  • one more thing I did notice is that the XML that is created by the XMLTransmit Pipeline for my pure EDI File has some special characters right at the beginging of the file...some thing like the following. I open the file in WINVI and saw this. Now I know why my xml's would never open in IE browser.

    <ns0:X12_00401_837_P xmlns:ns0="837000000">http://schemas.microsoft.com/BizTalk/EDI/X12/2006"><ST><ST01>837</ST01><ST02>000000

    I wonder there is some bug I am dealing with here and has something to do with Encoding indeed.

    My current setup.

    1. A Rec. Port - EDIReceive (received core 837_I or P EDI doc)
    2. A Send port - XML Transmit - Filtered on the 2 message types.  (this is where I get those special characters)
    3. Another Rec. Port - XML Receive
    4. Another Send Port - EDISend 
    5. I have 2 Parties one set as Sending the EDI document inbound and another party which is Sending the EDI 837's outbound.

    The Second party I have for outbound has the 2 GS settings and I am still not able to get the correct GS08 on them. It always takes the defualt.

    Hope you can shed some more light on this.

    -amit
    amit kumar
    Thursday, March 12, 2009 12:12 AM
  • Are you still getting this problem? Asking you because you marked this thread as "Answered".



    Thanks
    Gyan
    Thursday, March 12, 2009 11:06 AM
  • i still have the issue. Looks like your post helped someone else and they marked it as Answered!
    amit kumar
    Thursday, March 12, 2009 2:07 PM
  • Hi,
         It worked on my machine. May be you were doing some small mistake. Suggest me any other way that I can help you.

    You can send your Binding files and input files to me at gyancse08@gmail.com. I will try to repro it.



    Thanks
    Gyan
    Friday, March 13, 2009 1:37 PM
  • Hi,
        Sorry for late answer. But I reoslved this problem. Actually you need to Apply a patch in which we fixed this bug.
    The KB article for this Patch
    Monday, March 16, 2009 7:47 AM
  • can you send me a link to the patch download? i dont seem to find it anywhere.
    amit kumar
    Monday, March 16, 2009 11:17 AM
  • Please ask to your Microsoft support team for getting this patch. Using KB article number 951760.



    Thanks
    Gyan
    • Marked as answer by technoamit Friday, June 19, 2009 3:07 PM
    Monday, March 16, 2009 2:04 PM
  • is this a new patch you created or it already exisits? Why cant I get it from msdn or technet account?
    amit kumar
    Monday, March 16, 2009 3:42 PM
  • Actually this hotfix is not public. And it was already fixed. So you need to ask to yuor support team for this.


    Thanks
    Gyan
    Monday, March 16, 2009 4:44 PM
  • Hello Gyan,
    I am in a similar situation as described in the http://support.microsoft.com/default.aspx/kb/951760 article. I contacted the support team and applied the hotfix. The hotfix doesn't seem to fix the problem. I have tried this in three different environments.

    I have noticed that the timestamp for the DLLs mentioned in the KB article are 18th April 2008 with version# 3.6.1450.2. Whereas, the DLLs that I have are all latest ones dated 23rd July 2008 with version# 3.6.1481.2. I would expect the fix to be carried over to this, but that doesn't seem to be the case. Can you please help us?

    Thanks
    Monday, September 21, 2009 10:35 PM