Udostępnij za pośrednictwem

Pipeline Component Wizard for Visual Studio

  • Artykuł

Martijn has a very nice pipeline component wizard for Visual Studio .NET 2003. You can download it here .

Comments

  • Anonymous
    September 06, 2004
    The comment has been removed
  • Anonymous
    September 07, 2004
    Vincent: Pipeline.exe does not access any BizTalk database (configuration/management ...) which can sometimes be an issue while debugging a pipeline. It is very unlikely that the usage of pipeline.exe cause the problem you are seeing.

    You do not give details about your custom pipeline so I am guessing at best. Is your custom pipeline making any WMI calls by any chance? If so, you should not do this.

    Apparently, BizTalk WMI does not work anymore because WMI classes are not registered. WMI classes are registered at setup time, by running mfcomp on .mof file shipped with BizTalk. Assuming you did not install any software, it is unclear how the registration was lot. You could run the repair setup to reregister them.
  • Anonymous
    September 07, 2004
    The comment has been removed
  • Anonymous
    September 07, 2004
    Vincent: the article you point to is related to .NET 1.0. BizTak 2004 needs .NET 1.1 and this issue has been fixed.

    The error tells that you cannot access the BizTalk Management database. Did you change passwords by any chance? BizTalk needs to access databases to run properly. At configuration time, you specified usernames and passwords. If one of these changed, things won't work nd you'll need to update BizTalk configuration. This goes for SQL as well. You have remote SQL server n Windows 2000. If you tighten the security on SQL, this could happen.

    So start the enterprise manager, connect to the server uing the user/password you specified as BizTalk Administrator and see if you can connect.
  • Anonymous
    September 07, 2004
    Gilles,

    Both users btsinstancehost and ssoservice can connect to the SQL server via Windows authentication. BizTalk service is running under btsinstancehost user and is able to access the BizTalk Management database from SQL Query Analyser. SSO service is running under ssoservice user and is able to access the SSODB database.

    The users and passwords have not been changed. Is there anywhere else that I can check BizTalk's configuration? Is it worth un-configuring the whole of BizTalk and re-configuring it?

    cheers
  • Anonymous
    September 08, 2004
    Vincent: Check if the MMC console points to the right server. Fire up the MMC, right click on "Microsoft BizTalk Server 2004" and select properties. Make sure the Db connections are good and the SSO server is OK.
  • Anonymous
    September 08, 2004
    Gilles,
    Properties is not available in the right click. Is there another way to get to it?
  • Anonymous
    September 08, 2004
    Vincent: You might want to try to reconfigure the COM+ catalog:

    http://support.microsoft.com/?id=315296

    If that does not work, confirm that the remote procedure call(RPC) Locator properties is set to run under
    the Networkservice account (which is the default).

    Unconfigure Biztalk 2004 by running configframework /u and then reconfigure
    Biztalk by running configframework.

  • Anonymous
    September 16, 2004
    Gilles,

    After unconfiguring, when I try to re-configure it I get the error "Failed to load configuration data for feature: RulesEngine. Please see the log file for more details". Where is the log file? I have also deleted the BTS databases and it didn't make any difference.

    I think I will have to resort to re-installing the server.