community-content

Forum Replies Created

Viewing 15 posts - 6,151 through 6,165 (of 9,652 total)
  • Author
    Posts
  • in reply to: Equal Functoid question #17150

    Nishil – check the order of the parameters, the logical must be the first parameter in the value mapper.  It is easy to get these out of order when moving and hooking things up.

     -weak architect
     

    in reply to: Custom Database Functoid #17149

    Francois,

     This is just a quick pointer for you, if you choose to go this way and need more information let me know.

    I'm usually using custom xsl and not the mapper with links and functoids (but the two boil down to the same thing in the end so this is by no means a restriction)

     I was able to write a custom function in c# that both receives and returns XPathNodeIterator (which resides in System.Xml.XPath).

    Using this class you can pass xslt node sets in and out of the helper class, there are quite a few resources on the web on how to use these classes.

    You could then write a custom class to do your lookup and return a node set whcih you could then iterate on in your xsl (but it may mean you need to re-arrange your map/xsl)

    I hope this helps 

     

     

    in reply to: An error when trying to use orchestration as a webservice #17148

    [quote user="Anonymous"]

    Hi,

    I think that I have checked everything I could but nothing help with that error. I have one "client" orchestration which try to call another one which have published as a webservice. This sample find from MS site:

    http://msdn.microsoft.com/biztalk/downloads/samples/default.aspx "Publishing and Consuming Web Services with SOAP Headers "

    I have used sample files but build and deployed it with BT 2004 cause of our client BT version. Can anyone help and offer some kind of check list for that error?

    Event Type: Warning
    Event Source: BizTalk Server 2004
    Event Category: BizTalk Server 2004
    Event ID: 5740
    Date:  18.9.2006
    Time:  15:49:11
    User:  N/A
    Computer: DEMOAPPSERVER
    Description:
    The adapter "SOAP" raised an error message. Details "System.Web.Services.Protocols.SoapException: Internal SOAP Processing Failure —> System.Runtime.InteropServices.COMException (0xC0C01666): Exception from HRESULT: 0xC0C01666.
       at Microsoft.BizTalk.WebServices.ServerProxy.ServerProxy.InternalInvoke(String functionName, Object[] parameters, ParamInfo[] inParamInfos, ParamInfo[] outParamInfos, Int32 bodyPartIndex, String bodyType, ArrayList inHeaders, ArrayList inoutHeaders, ArrayList& inoutHeaderResponses, ArrayList& outHeaderResponses, Type[] outHeaderTypes, String[] outHeaderNamespaces, SoapUnknownHeader[] unknownHeaders, SoapUnknownHeader[]& unknownHeaderResponses, Boolean oneway, Boolean spsSsoEnabled, Object cookie)
       at Microsoft.BizTalk.WebServices.ServerProxy.ServerProxy.Invoke(String functionName, Object[] parameters, ParamInfo[] inParamInfos, ParamInfo[] outParamInfos, Int32 bodyPartIndex, String bodyType, ArrayList inHeaders, ArrayList inoutHeaders, ArrayList& inoutHeaderResponses, ArrayList& outHeaderResponses, Type[] outHeaderTypes, String[] outHeaderNamespaces, SoapUnknownHeader[] unknownHeaders, SoapUnknownHeader[]& unknownHeaderResponses, Boolean oneway, Boolean spsSsoEnabled, Object cookie)
       — End of inner exception stack trace —
       at Microsoft.BizTalk.WebServices.ServerProxy.ServerProxy.Invoke(String functionName, Object[] parameters, ParamInfo[] inParamInfos, ParamInfo[] outParamInfos, Int32 bodyPartIndex, String bodyType, ArrayList inHeaders, ArrayList inoutHeaders, ArrayList& inoutHeaderResponses, ArrayList& outHeaderResponses, Type[] outHeaderTypes, String[] outHeaderNamespaces, SoapUnknownHeader[] unknownHeaders, SoapUnknownHeader[]& unknownHeaderResponses, Boolean oneway, Boolean spsSsoEnabled, Object cookie)
       at Microsoft.BizTalk.WebServices.ServerProxy.ServerProxy.Invoke(String functionName, Object[] parameters, ParamInfo[] inParamInfos, ParamInfo[] outParamInfos, Int32 bodyPartIndex, String bodyType, ArrayList inHeaders, ArrayList inoutHeaders, ArrayList& inoutHeaderResponses, ArrayList& outHeaderResponses, Type[] outHeaderTypes, String[] outHeaderNamespaces, SoapUnknownHeader[] unknownHeaders, SoapUnknownHeader[]& unknownHeaderResponses, Boolean oneway, Boolean spsSsoEnabled)
       at SoraWebService.PurchaseOrderProcessing_POProcess_WSPOPort.WSPO(PO part)".

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    [/quote]

    in reply to: 2 issues #17145

    I found a solution to my Http Post error at http://www.biztalkgurus.com/forums/thread/3806.aspx

     

    To solve this I just added IUSR_CompName and IWAM_CompName to the allowers users to modify my temp folder.  It works now. I wonder why this wasn't a problem with Biztalk 2004. 

    in reply to: Custom Database Functoid #17143

    We wrote our own for this reason.

    Always consume and pass string is correct.

    We returned a delimited string as the db result and parsed it.  we are calling sprocs to get this string.

    As far as returning array I can't help you. Also I have no idea if the string length is limited.

    -weak architect

     

    I believe the functoids always output strings, regardless of the perceived type. If you return "true" and "false" it will be the solution you were looking for.

    You can quickly prove this by evaluating the strings in the map and you'll see that a logical receiving the word "true" treats it as the appropriate boolean input.

    – weak architect

    in reply to: Installation problems #17141

    Well I don't know exactly what happened but it appears that on original configuration, I used default.  This failed and so I just did the custom configuration since I've had all the users and user groups set up from the Biztalk 2004 days (yesterday).  After I deleted all the databases and redid the configuration then it worked.

     

    So for others who may get the same problem:

    1.Undo all configurations 

    2. Delete all the Biztalk dbs

    3. Do configuration (custom worked for me).

     

    There were a few tweaks that I had to do to the sql db but it was more of the making sure that certain users can create dbs. 

    in reply to: Receive Pipeline Error #17140

    Are you using a Flat file for input or XML?

    Are you setting the "Validate Instance Input Type" correctly in the Schema General Properties?

    Are you using a Flat file disassembler when you need an XML Disassembler?

    Does this XML and schema represent the actual input file or XML generated from Validating the Flat file instance?

    in reply to: Installation problems #17139

    If you've gone through the trouble of creating a BizTalk service user and granted proper permissions on the system, then you may also need to grant DB permissions in SQL Server unless you've taken care of that with the appropriate group.

    • Are you using the Visual Studio 2005 version of SQL Express or did you install Standard or Enterprise?
    • Is this installed on Windows Server 2003 or on XP where you'll need to connect your DB to an external BizTalk Server?

    Please, describe your installation scenario if you haven't found a solution and I'm sure someone will have the answer.

     

    in reply to: how to make Biztalk point to another SQL Server? #17137

    The best way to look at this is as a deployment issue.

    If it IS production, then you should assume you are going to deploy to a NEW server and build it according to your new specs.  Then Deploy all of your applications.  The means you first need to have deployment packages and even scripts to make life easy.  Its a good process to go through anyway to be sure future maintenance will work the way you expect.

    If, However, this is a Dev environment then you can look at this as an opportunity to do the right thing since it appears as if you're outgrowing the same-server environment.  I would suggest SQL Server and BizTalk should be on separate machines, but you can also split them up on something as small as a laptop using Virtual PC, Virtual Server, or everyone's favorite VM Ware (Workstation or Server).

    I'm running an "enterprise" with a Domain Controller, SQL Server, BizTalk 2 server Cluster, and Oracle and MOSS servers as needed.  You can run what you need when you need it and test different configurations and scenarios without the time and effort to re-build a new box…especially when you don't have room, budget or you happen to be on the road.

    BizTron.

     

    in reply to: Custom Database Functoid #17136

    Have you found "DBFunktoids"?


    http://blogs.msdn.com/ebattalio/archive/2006/02/16/DBFunktoids.aspx

    DBFunktoids – SQL Server Stored Procedure Functoid / Extractor Functoids

    DBFunktoids is a collection of three functoids that enable the invocation and manipulation of SQL Server 2000 / 2005 stored procedures and their results. You can find a zip with the project and a compiled assembly at the end of this article.

    DBFunktoids were written for BizTalk 2006 and the .NET Framework 2.0. If there is enough interest, I can port the project back to BizTalk 2004 (it should pretty much be code copy with a replacement of a Dictionary Generic with a Hashtable).

    DBFunktoids are described below.

    in reply to: Installation problems #17135

    I'm not sure I understand why the user would be able to create the rest of the dbs but not this one in particular.  I'll try to log in and create a db by hand. 

    This is a new install for Biztalk 2006.  I didn't specify what version of Biztalk because wer are in Biztalk 2006 sub-forum so I didn't think it was necessary.  I'd prefer not to scratch everything but if need be, I can always start over from the Visual Studio install.

     

     

    in reply to: Installation problems #17134

    Craig,

    it sounds like a pretty fundamental problem with your access to SQL. If you log in with the same account that you specify for accessing the db, can you create a db by hand?

    Is this a new install? Can you just scratch everything and just retry?

    By the way, it's always useful to specify if this is BTS 2004 or 2006?

     John D.

    in reply to: Receive Pipeline Error #17132

    Hi Siva,

    Yes, I was able to successfully create the "Validate Instance" for the test file.  Where would I look to set the "$Dilimeted$" field, or Complexity, early termination, etc.?  I've also looked around to find where to set the "minimum" in schema and haven't seen it.  Where does that get set?  I've seen this mentioned in other posts, but never found it.

    Here is my schema and test file.  Thanks for looking at these for me.

    <?xml version="1.0" encoding="utf-16"?>
    <xs:schema xmlns:b="http://schemas.microsoft.com/BizTalk/2003&quot; xmlns="FlatFileTest.payment" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="FlatFileTest.payment" xmlns:xs="http://www.w3.org/2001/XMLSchema"&gt;
      <xs:element name="Header">
        <xs:complexType>
          <xs:sequence>
            <xs:element minOccurs="1" maxOccurs="1" name="PaymentAdjustment">
              <xs:complexType>
                <xs:attribute name="RecordType" type="xs:string" use="required" />
                <xs:attribute name="Type" type="xs:string" use="required" />
                <xs:attribute name="Date" type="xs:string" use="required" />
                <xs:attribute name="Reference" type="xs:string" use="required" />
                <xs:attribute name="Principal" type="xs:long" use="required" />
                <xs:attribute name="OtherIncome" type="xs:long" use="required" />
                <xs:attribute name="Interest" type="xs:long" use="required" />
                <xs:attribute name="Cost" type="xs:long" use="required" />
                <xs:attribute name="AgencyFeesDue" type="xs:long" use="required" />
                <xs:attribute name="AgencyCostDue" type="xs:long" use="required" />
                <xs:attribute name="AccountNumber" type="xs:string" use="required" />
              </xs:complexType>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="RecordType" type="xs:unsignedByte" use="required" />
          <xs:attribute name="Date" type="xs:date" use="required" />
          <xs:attribute name="BankName" type="xs:string" use="required" />
          <xs:attribute name="AgencyCode" type="xs:string" use="required" />
          <xs:attribute name="AgencyName" type="xs:string" use="required" />
          <xs:attribute name="ARecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="BRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="DRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="JRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="NRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="PRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="RRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="GRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="CRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="QRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="ERecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="FRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="YRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="XRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="WRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="TRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="HRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="URecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="SRecordCount" type="xs:unsignedByte" use="required" />
          <xs:attribute name="ClientControlNumber" type="xs:unsignedShort" use="required" />
          <xs:attribute name="BankId" type="xs:string" use="required" />
          <xs:attribute name="ACSInterfaceNumber" type="xs:unsignedByte" use="required" />
          <xs:attribute name="ACSImportControlNumber" type="xs:unsignedByte" use="required" />
          <xs:attribute name="ACSExportBatchNumber" type="xs:unsignedByte" use="required" />
          <xs:attribute name="AgencyCbBatch" type="xs:string" use="required" />
        </xs:complexType>
      </xs:element>
    </xs:schema>

     

    <Header
     RecordType="0"
     Date="20060122"
     BankName="FIRST BANK, NATIONAL ASSOCIATION"
     AgencyCode="C2MJH"
     AgencyName="MJH ASSOCIATES, INC"
     ARecordCount="0000000000"
     BRecordCount="0000000000"
     DRecordCount="0000000000"
     JRecordCount="0000000000"
     NRecordCount="0000000000"
     PRecordCount="0000000054"
     RRecordCount="0000000000"
     GRecordCount="0000000000"
     CRecordCount="0000000000"
     QRecordCount="0000000000"
     ERecordCount="0000000000"
     FRecordCount="0000000000"
     YRecordCount="0000000000"
     XRecordCount="0000000000"
     WRecordCount="0000000000"
     TRecordCount="0000000000"
     HRecordCount="0000000000"
     URecordCount="0000000000"
     SRecordCount="0000000000"
     ClientControlNumber="00041611"
     BankId="FUNB1"
     ACSInterfaceNumber="0000000000"
     ACSImportControlNumber="00000000000000000000"
     ACSExportBatchNumber="00000000000000000000"
     AgencyCbBatch="4">
      <PaymentAdjustment
         RecordType="P"
         Type="1"
         Date="20060119"
         Reference="376222601 HER CK"
         Principal="000000009856"
         OtherIncome="000000000000"
         Interest="000000000000"
         Cost="000000000000"
         AgencyFeesDue="000000003942"
         AgencyCostDue="000000000000"
         AccountNumber="540000159200" />
    </Header>

    Many thanks

    in reply to: Receive Pipeline Error #17131

    Hi,

    Could you create the "Validate Instance" for your test case? I think input file is missing the mandatory filed "$Dilimeter$". If it is not mandatory then you should put "0" for minimum in schema. Can you post the test input and shema structure here?

    Another reason i could think is if you select the "$Dilimeter$" as looping then you may get this kind of error. Did you set up the root propertys for "Complexity", early termination true, and so on?

    I get same kind of error when the filed is missing. I am using that case as error handling since my input must have that field.

    Siva

Viewing 15 posts - 6,151 through 6,165 (of 9,652 total)