moved database from SQL 2005 to SQL 2008 - BPM engine crashes frequently

JD Freeman
JD Freeman
in AppWorks #1

As the title says, we have an installation of Metastorm BPM 9.0.3 which was currently running with a database located on a SQL Server 2005 cluster. We copied the DEV db to a SQL Server 2008 cluster and changed all the connection strings accordingly. We're running on a SQL Server 2008 Standard edition virtual environment. The application runs, but from time to time the engine sems to quit on us, generating an error on the front end that looks like this:

 

72de8672-da50-451f-becf-b01326607b66

 

 

We inherited this highly customized app and would love some pointers as to where to look and if anyone else had experienced similar problems due moving from SQL 2005 to SQL 2008.

 

Tagged:

Comments

  • Paul Lawrence
    Paul Lawrence
    #2

    If you've moved to 2008 and are in a clustered environment I would start looking at the clustter and MSDTC in particular. Microsoft have changed the way you configure MSDTC in 2008 clusters and it sounds like you may have some issues around this setup.

  • JD Freeman
    JD Freeman
    #3

    Paul wrote:

    If you've moved to 2008 and are in a clustered environment I would start looking at the clustter and MSDTC in particular. Microsoft have changed the way you configure MSDTC in 2008 clusters and it sounds like you may have some issues around this setup.

    That was my initial thought, as well. The DBA's told me the MSDTC settings were the same as before but they did not go into great detail.

  • Paul Lawrence
    Paul Lawrence
    #4

    The changes with 2008 are more about the design of the MSDTC components on the cluster. My suggestion would be do some failover testing of the cluster and try to reproduce the issue. There's also a DTCPing tool you may like to use to test various failover configurations of your cluster.

Categories

image
OpenText CE Products
AppWorks
Gateway & Platform