community-content

Forum Replies Created

Viewing 15 posts - 9,076 through 9,090 (of 9,648 total)
  • Author
    Posts
  • in reply to: BizTalk Installation #12652

    Thanks–I was planning to use the standalone BizTalk Explorer tool instead. Sounds like I can do that.

    in reply to: Consuming Sharepoint Webservices #12585

    Hi Stephen,

    Yes, adding reference to any other .NET project perfectly works but not for Biztalk Projects

    Error Information – Failed to add a web reference

    I found this reply from other groups -‘ BizTalk doesnt support Array types’

    -Regards,

    in reply to: Biztalk and web services on virtual pc #12741

    I also use virtual PC for my BizTalk development projects and as Ken said I had to change the WSS settings to let IIS manage the root.

    Ron Davis

    in reply to: Pain Re-deploying Assemblies to Biztalk 2004 #12701

    Jon has lots of insight into deployment issues, but one of my favorite entries has to be this one:

    http://www.masteringbiztalk.com/blogs/jon/PermaLink,guid,628aecb9-4eaa-4044-88c9-92cb53f81bdf.aspx

    If you look at his grid for when you must undeploy/redeploy you can see that if you make changes to an orchestration, without changing/adding/removing ports, then its a simple matter of just deploying your fixed assembly to the GAC and recycling the biztalk service. Most of my orchestration issues center on not writing good xpath expressions, so I’m constantly changing one or two message assignment shapes and then redeploying. This trick has saved me tons of time.

    in reply to: Biztalk and web services on virtual pc #12740

    Do you have WSS (Windows Sharepoint Services) Adapter installed on the virtual PC? If yes, was it installed on the root folder?

    If yes, read the follg. otherwise ignore the rest:
    By default, WSS adapter will try to manage the web service – You need to make a setup change to indicate that the webservice should be handled by IIS and not by WSS.

    This may be one of the issues…

    Howver, if the Webservice resides outside the virtual PC, the above problem will not apply here.

    Thanks,
    Ken

    in reply to: Pain Re-deploying Assemblies to Biztalk 2004 #12700

    Chenue…

    It is a bit more than just unenlist/stopping and restarting things.

    For instance, if you have a port with map attached, you cannot redeploy the project (containing the map) without removing the map from the port. Similarly, if you have the custom pipeline attached to the map, it will be removed automagically (I think this happens if the pipeline is used by only one port) and if you redeploy the project containing pipeline, you will have to reconfigure the port properly.

    I agree that these ports need not be deleted everytime the solution is (re)deployed. But, some changes are required.

    The best thing is to go with binding xml files with scripts as some of the earlier posts suggested.

    Thanks,
    Ken

    in reply to: Error with BizTalk Base EDI Adapter #12743

    Hi,
    I am converting files from EDI to xml format. Since this was throwing errors I am just workin on the example found in htttp://www.msdn.microsoft.com/library I have followed all the steps accurately and still the error persist. It would be great if someone could post a solution for the same.
    Error Message in the Even Viewer:
    Error encountered: ERROR (41), interchangenr 10003 :
    The sender of the document is not recognized. Contact the system administrator.
    sender: [][] [7654321][ZZ][7654321], (msgnr:0 segnr:0)(line:3 pos:40 filepos:445)
    Error Message from HAT:
    While i run the Query under EDI Reports Recieve Messages
    Error Code: 41
    Error Description: The sender of the document is not recognized. please contact the System Administrator.

    Thanks

    in reply to: Biztalk and web services on virtual pc #12739

    I use virtual pc for my lab enviroment without any problems

    in reply to: Pain Re-deploying Assemblies to Biztalk 2004 #12699

    If I am not mistaken, rightclick on your project(not the solution) and go to properties. On the left pane go to configuration properties then to deployment. On the right pane now, set redeploy to true.
    when that is done all u have to do is to unlist the project orchestrations before and checking all boxes to get rid of existing instances before deploying. U do not have to delete any ports or anything of the sort.

    Chenue

    in reply to: Need to use BizTalk #12737

    hi all,

    can anybody please suggest me what all 10 scenarios(reasons) where i can convince myself to implement BizTalk.

    cheers
    vikas

    in reply to: Using an old organization name when create a channel #12735

    Just for saying that I’m registered in this forum.

    in reply to: Another Correlation Question #12728

    We basically determined that this is either a bug or a \”design feature\”.
    We will proably do a work around for now, and maybe open a support issue with Microsoft.

    I created a small project with 3 orchestrations to reproduce the error on demand. It is definitely related to trying to correlate on property fields that are not in the message body – i.e. SOAP Headers (and may also be tied to the use of ports with direct binding).

    Neal Walters
    http://Biztalk-Training.com

    in reply to: Correlation Internals #12733

    Sometimes you think you understand this stuff, then you realize you really don’t!

    Given that a Correlation Type is a C# class, and a Correlation Set must be a C# object, what does \”initialize correlation\” really do? Does it basically instantiate the object? And that is why you can’t do it more than once?

    Then what does following do – just change the value of the properties in the correlation set based on the current value of the promoted fields?

    What can cause this message for a non-activation receive?
    1. You must specify at least one already-initialized correlation for a non-activation receive that is on a non-selfcorrelating port.

    Why can’t you initialize correlation in a loop?
    Is it like I said above, you would be reinstantiating the same object over and over? Apparently, if your loop is in a scope, you can do it.

    Is there anyway to initialize correlation besides doing a send or receive?
    Could you do it in an expression or message assignment – I might try this later tonight?

    When would you select multiple correlation sets when you send a message?

    What if you have 4 sends in different branches of an if statement.
    You want them to all correlate on the same property field.
    It looks like we either have to create four correlation sets so each one can be initialized in each branch, or we have to somehow initialize earlier, then use following in each branch.

    Sorry, this is the brain dump of what I have been thinking about today.

    Neal Walters
    http://Biztalk-Training.com – Will probably be doing a correlation video in the near future! I’ve got to get this nailed first.

    in reply to: Another Correlation Question #12727

    It turns out the issue has something to do with the correlating on the SOAP headers. I built another two orchestrations that were basically identical – except I correlated on an element in the message, not on a SoapHeader.

    Neal

    in reply to: Another Correlation Question #12726

    This is an existing system, and we have to work with their existing framework.

    Here is the exact error I’m getting. Instead of just getting the \”not able to find subscriber\” that you normally get, I get 3 exceptions:
    1) PersistenceException
    2) PersistenceItemException
    3) PublishMessageException.

    Several posts have suggested that the PeristenceItemException can be caused by an unenlisted orch, but my Orch-A and Orch-B are both enlisted, and Orch-B finishes – even though the exception below is from Orch-B (whose real name is Compassion.BizTalk.BusinessProcesses.Constituent.orchServiceAgentSim).

    Event Type: Error
    Event Source: XLANG/s
    Event Category: None
    Event ID: 10034
    Date: 1/24/2006
    Time: 11:23:26 AM
    User: N/A
    Computer: USGDPWV81NB
    Description:
    Uncaught exception terminated service Compassion.BizTalk.BusinessProcesses.Constituent.orchServiceAgentSim(86e37f34-27f9-4cc5-469d-296639ae7331), instance 56ce3b91-599c-4762-92c1-6e1643eb7970

    Exception occurred when persisting state to the database.

    Exception type: PersistenceException
    Source: Microsoft.XLANGs.BizTalk.Engine
    Target Site: Void Commit()
    Help Link:
    Additional error information:

    A batch item failed persistence Item-ID 227b434c-ef4b-4ed4-8d53-9fb5634faa8b OperationType MAIO_CommitBatch Status -1061151998 ErrorInfo The published message could not be routed because no subscribers were found. Please use the Health and Activity Monitoring (HAT) tool to diagnose this situation. .

    Exception type: PersistenceItemException
    Source:
    Target Site:
    Help Link:
    Additional error information:

    Failed to publish (send) a message in the batch. [b:5cad729eb8]This is usually because there is no one expecting to receive this message. The error was The published message could not be routed because no subscribers were found. [/b:5cad729eb8] Please use the Health and Activity Monitoring (HAT) tool to diagnose this situation. with status -1061151998.

    Exception type: PublishMessageException
    Source:
    Target Site:
    Help Link:
    Additional error information:

    Exception occurred when persisting state to the database.

    Exception type: PersistenceException
    Source: Microsoft.XLANGs.BizTalk.Engine
    Target Site: Void Commit(Microsoft.BizTalk.Agent.Interop.IBTMessageBatchEx[], Microsoft.XLANGs.Core.Segment, Microsoft.BizTalk.Agent.Interop.IBTOperationStatus ByRef)
    Help Link:
    Additional error information:

    A batch item failed persistence Item-ID 227b434c-ef4b-4ed4-8d53-9fb5634faa8b OperationType MAIO_CommitBatch Status -1061151998 ErrorInfo [b:5cad729eb8]The published message could not be routed because no subscribers were found[/b:5cad729eb8]. Please use the Health and Activity Monitoring (HAT) tool to diagnose this situation. .

    Exception type: PersistenceItemException
    Source:
    Target Site:
    Help Link:
    Additional error information:

    Failed to publish (send) a message in the batch.[b:5cad729eb8] This is usually because there is no one expecting to receive this message. The error was The published message could not be routed because no subscribers were found. [/b:5cad729eb8] Please use the Health and Activity Monitoring (HAT) tool to diagnose this situation. with status -1061151998.

    Exception type: PublishMessageException
    Source:
    Target Site:
    Help Link:
    Additional error information:

    Neal

Viewing 15 posts - 9,076 through 9,090 (of 9,648 total)