community-content

Forum Replies Created

Viewing 15 posts - 2,431 through 2,445 (of 9,648 total)
  • Author
    Posts
  • in reply to: Flat file as email-attachment #23016

    Ok.

    Now It`s plain to me why I allways get the unmapped xml in my attachment.

    Because the FlatFile-Pipe is never called, when sending the mail instead of create a file in the file-system.

    I think I have two options:

    1. Call the pipeline inside of the orchestration.

       I have tried this without success.

    2. Allways reate the file in the file-system, remember the filename and then set this file as the email-attachment.

       Here I don`t know how to do this 2 steps…

    in reply to: Can I map this problem #23012

    I would probably use some Xpath queries inside the Orchestration.  First one would determine if you had rows of data or not.  Next would xpath out the data you are looking for.  You could use this data to build a custom, more friendly response / error message. 

    Hope this helps.

    Stephen W. Thomas

    in reply to: Functoid Issue #23011

    I’ve actually never written a custom Functoid… but have you tried testing it though a Receive / Send Port?  The context of testing a map inside Visual Studios might be messing it up. 

    Probably will not help – but never know.

     

    in reply to: Passing Xml Document whill calling Orchestration to BizTalk #23010

    Sorry I’m a little confused as to what you are trying to do.  You need to call a Rules Engine Policy or a Pipeline? 

    in reply to: Error in RFC Call #23008

    Check you ports

    in reply to: Error in RFC Call #23007

    Please ignore this post. I set the port up wrong

    in reply to: WCF-custom error with SQL adapter #23004

    Hi,

    Did you suceeded to resolve the issue?

    in reply to: SCOM Management Pack for BizTalk 2009?? WHERE?? #23003

    Got my answer from Microsoft. Looks like we won’t have this until Oct – Nov timeframe. Bummer.

    in reply to: Access denied during deployment #22997

    You’ve probably resolved your problem in BizTalk 2009 by now, but I have had to tackle it myself and discovered a fix that might work for others.

    Normal
    0

    false
    false
    false

    EN-US
    X-NONE
    X-NONE

    MicrosoftInternetExplorer4

    <!–
    /* Font Definitions */
    @font-face
    {font-family:”Cambria Math”;
    panose-1:2 4 5 3 5 4 6 3 2 4;
    mso-font-charset:1;
    mso-generic-font-family:roman;
    mso-font-format:other;
    mso-font-pitch:variable;
    mso-font-signature:0 0 0 0 0 0;}
    @font-face
    {font-family:Calibri;
    panose-1:2 15 5 2 2 2 4 3 2 4;
    mso-font-charset:0;
    mso-generic-font-family:swiss;
    mso-font-pitch:variable;
    mso-font-signature:-1610611985 1073750139 0 0 159 0;}
    /* Style Definitions */
    p.MsoNormal, li.MsoNormal, div.MsoNormal
    {mso-style-unhide:no;
    mso-style-qformat:yes;
    mso-style-parent:””;
    margin-top:0in;
    margin-right:0in;
    margin-bottom:10.0pt;
    margin-left:0in;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:”Calibri”,”sans-serif”;
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:Calibri;
    mso-fareast-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:”Times New Roman”;
    mso-bidi-theme-font:minor-bidi;}
    span.MsoIntenseEmphasis
    {mso-style-priority:21;
    mso-style-unhide:no;
    mso-style-qformat:yes;
    color:#4F81BD;
    mso-themecolor:accent1;
    font-weight:bold;
    font-style:italic;}
    .MsoChpDefault
    {mso-style-type:export-only;
    mso-default-props:yes;
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:Calibri;
    mso-fareast-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:”Times New Roman”;
    mso-bidi-theme-font:minor-bidi;}
    .MsoPapDefault
    {mso-style-type:export-only;
    margin-bottom:10.0pt;
    line-height:115%;}
    @page Section1
    {size:8.5in 11.0in;
    margin:1.0in 1.0in 1.0in 1.0in;
    mso-header-margin:.5in;
    mso-footer-margin:.5in;
    mso-paper-source:0;}
    div.Section1
    {page:Section1;}
    –>

    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:”Table Normal”;
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:””;
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin-top:0in;
    mso-para-margin-right:0in;
    mso-para-margin-bottom:10.0pt;
    mso-para-margin-left:0in;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:”Calibri”,”sans-serif”;
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:”Times New Roman”;
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;}

    Inspecting the AssemblyInfo.cs of a project that deploys successfully and one that does not, I found that the highlighted piece of the quoted portion of a standard AssemblyInfo.cs existed in a working project, but not in a project that would not deploy.  Adding the highlighted text to the AssemblyInfo.cs file of a project that would not deploy resolved the issue.

    [assembly:
    AssemblyVersion(“1.0.0.0”)]

    [assembly:
    AssemblyFileVersion(“1.0.0.0”)]

    [assembly: AssemblyInformationalVersion(“1.0.0.0”)]

     

    [assembly:
    Microsoft.XLANGs.BaseTypes.BizTalkAssembly(typeof(Microsoft.BizTalk.XLANGs.BTXEngine.BTXService))]

    in reply to: Biztalk dropping/hanging on messages. #22996

    April,

    I’m sure that you have checked this, but do you have any warning or error events in the Event Log, or suspended (resumable or non-resumable) messages in BizTalk?

    This could also be a edge-case bug that only manifests itself in the 64-bit version. Alternatively, are there any logs you can use in the Summit package that might shed any light on this?

    Nick.

    I think your easiest approach is to deploy it to your local machine.  Then from the Biztalk administration console, export the application to an .MSI.  You can then take this .MSI to another Biztalk group and install it there. 

    Also, you will need to export the bindings as well if you need your send/receive ports and orchestration bindings.

    Please see this link for a basic walk through of deploying an application in Biztalk

    http://msdn.microsoft.com/en-us/library/aa559168(BTS.10).aspx

    -Ben

    Solved.

    “exec MyStoreProcedureName” from receive location polling statment does it’s work.

     

    in reply to: Login failed for user ‘NT AUTHORITY\NETWORK SERVICE’. #22983

    Yes! it worked!

    Thank you very much.

    in reply to: Error while generating schema using SQL stored Proc #22980

    I hava the  same problem. =(

    Besides, everytime i try to configure location in the BT administration console (SQL command in SQL transport properties), when i selec schema from assembly i get the error: “This is not valis schema generated by SQL Schema generator”

    I have set Full control permisions to user account adapter is running. on C:\Windows\Temp folder, but it doesnt fix the issue.

Viewing 15 posts - 2,431 through 2,445 (of 9,648 total)