Failed to execute deployed method 'DataValue' error (Promote method)

I am running version 9.0.2 with an Oracle 11 database. In the initial action of my process, I have a form that contains a dropdown field named STATE_NAME which populates with values from a lookup table (for example, a dropdown list that returns US state names). I am using the default Metastorm connection to the database (which has a successful connection) and am able to successfully deploy the process, but when I am in the web client and try to perform the initial action and bring up the form, the following error message appears:

Failed to executed deployed method 'DataValue', using entity 'STATE_NAME'. The Promote method returned an invalid value for the distributed transaction.

I've tried changing the MSDTC settings (on both the process engine and database servers) to enable user local coordinator and set the Security Configuration to enable Network DTC Access and enable Allow Inbound and Allow Outbound transactions. This results in the same error message.

Does anyone know how to resolve this?

Find more posts tagged with

BPM

Comments

Jerome_Pearce

I must say I had my reservations as to how Oracle would manage under the MSDTC. SQL Server seems to have anough of its own issues, let alone Oracle.

I'd be very interested in the results of this, and any other issues regarding version 9 on Oracle.

achopra

Have you installed Oracle Services for MSDTC per the instructions in the Installation Pre-requisites? This may be the cause of the error.

"Oracle Services for Microsoft Transaction Server must be installed on Engine machine to successfully

log into both Administration Tools and Web Client after installing of 9.0 SR2.

Oracle Services for Microsoft Transaction Server can be installed from the following location of v9.0

GA release: \Redist\Oracle\Driver\ODAC1110621.zip"

Peter__Chung

I believe Oracle Services for MSDTC have been installed because I can login to the Administration Tools and the web client without any problems. Maybe my issue stems from trying to understand how custom business objects work because I'm able to see data in the web client when using the ProcessContext default business object.

Can someone explain how a field can be created based on a business object that you create? For example, let's say my business object is named StateList and it is Query type that selects StateID, StateName from a table. I drag and drop this business object onto my form from the toolbox. In the Data Access pane, Metastorm creates a new item in the Other Business Objects section called StateList1 with two variables called StateID and StateName. I then drag and drop these two variables onto the form and click Grid from the pop-up window that Metastorm prompts. Is this correct? What else needs to be done because I always get the "Failed to execute..." error whenever I am in the web client?

Jerome_Pearce

That is the correct way. You will need to set parameters if required, and they are not set by default. You define these in your BO.

Did you test that BO itself works?

Peter__Chung

Yes, I tested the business object and it was retrieving the expected data without any problems. I didn't use any parameters since I wanted to retrieve all the records from the table (it's a very small table, i.e. 3 columns and about 10 records).

achopra

Can you please check that Oracle ODAC has been installed? It is typically not installed as part of the standard Oracle Client install, and this would only be evident when you go to use a business object at runtime rather than in the Designer. You would still be able to log in to the web client and admin tools, so the fact that you can do that does not mean that you have it installed.

Peter__Chung

Thanks for the info.

It looks like maybe not all of the required ODAC items were installed; namely the Oracle Services for Microsoft Transaction Server. This piece not being there might be what has been causing the error.

Peter__Chung

I installed the ODAC, and that fixed the problem. Specifically, it was the Oracle Services for Microsoft Transaction Server that was missing; the other components of the ODAC were already in place. Thanks for the help!