Functionality stopped working when upgrading from version 9.1.3.0 to 9.1.3.5

Magnus_Frost

Hi,

 

I have recently upgraded our dev environment from version 9.1.3 to 9.1.3.5. After the upgrade I noticed that some functions has stopped working. For example I use a stored procedure to search for templates. See code below:

 

SelectSql(new MetastormDefault(),"EXEC dbo.sp_nasdaqomx_search_SA_invoice @sReqID,@CustID,@CustContract,@CodaInvoiceNo,@AccountNo,@CaseStatus,@ParamStartDate,@ParamEndDate,@ResponsiblePerson,@ProjectNo SELECT 1", SQLArg("@CustID", Local.tCustomerNo), SQLArg("@sReqID", ProcessContext.FolderId), SQLArg("@CustContract", Local.txtCustContractNumber), SQLArg("@CodaInvoiceNo", Local.txtCodaInvoiceNumber), SQLArg("@AccountNo", Local.txtAccountNumber), SQLArg("@ParamStartDate", Local.dtmStartDate), SQLArg("@ParamEndDate", DBUtil.SA_CalculateSearchDate(Local.dtmEndDate)), SQLArg("@ResponsiblePerson", "%"), SQLArg("@ProjectNo", 0), SQLArg("@CaseStatus", Local.txtCaseStatus)).Integer

 

 

 

When I run this search after the upgrade I get the following error in the elog table:

 

Exception 'Object reference not set to an instance of an object.' occurred when attempting to 'Execute query'.

At he same time I receive a strange warning i the event log:
Failed to find the assembly Metastorm.Engine.Resources.resources, Version=9.0.0.0, Culture=sv, PublicKeyToken=0fa3cc64eebf4c8b.

 

 

Anyone else that have had any similar problems after applying the latest hotfixes for the 9.1.3 version?

 

 

Best regards,

 

Magnus

Robert Vignerot

We ran into a similar issue with 9.1.3.5 and instead have moved to 9.1.3.6, which resolves this.  If you move to 9.1.3.6, be aware there is an installer issue with split Web/Engine environments. If you are installing in a split environment, you may need to install and then repair to actually get the correct patch level.

Jerome_Pearce

We have this error when executing any SQL (eg UPDATE or INSERT statements) using SelectSql() in 9.1.3.6 on Oracle, We had to go back to 9.1.3.3, even though it has issues we need to have resolved.

 

Oh, and installing 9.1.3.6 over 9.1.3.3 on W2008 was an 'interesting' experience.

Magnus_Frost

Hi Rob,

 

thanks for your answer. I went to 9.1.3.6 first on my local development machine and I had the same errors. It was a single machine installation. I did not try the repair option.

 

But I will try your approach on our dev environment before I start to reinstall Metastorm BPM and goes to 9.1.3.3.

 

I will let you know how it goes.

 

Best regards,

 

Magnus

Magnus_Frost

Hi Jerome,

 

thanks for your reply. I went back to 9.1.3.3 and then it seems to work again.

 

Best regards,

 

Magnus

Magnus_Frost

Did not work for me. I will move back to 9.1.3.3.

 

 

Best regards,

 

Magnus

Jerome_Pearce

I have identified the cause. If you have any date parameter that is an empty date, it causes this exception to be thrown. It happens whether you are selecting, updating or inserting data, and works fine if the date is filled.

Kaman_Paul

I am actually having this problem after going from 9.1.2.4 to 9.2.1.3.

 

I'm referencing an assembly (that I wrote).  The assembly is bascially a .NET app that makes a call to an Oracle DB.  It worked but now stopped working... noted that the event viewer says:

 

Failed to find the assembly Metastorm.Engine.Resources.resources, Version=9.0.0.0, Culture=en, PublicKeyToken=0fa3cc64eebf4c8b.

 

This error isn't thrown until the first time the Engine tries to get the dll.  Any subsequent use of the dll just fails in the runtime but not event is logged.

 

 

Kaman_Paul

In reference to this problem I received a very important response from OT support.

 

"

Rather I think this is an issue with DTS trying to enlist the Oracle transaction by promoting the existing MSSQL connection to a distributed transaction (or something like this).  A change in 9.1.3+ to use .Net 4.0 WCF allows for transaction to be properly enlisted in a single distributed transaction where appropriate but this has often given use issues in Oracle environments.  It strikes me that this is the more simple cause to the problem as your code has not changed (and worked before) and the DLL is being invoked.  We have definitely seen the error "New transaction cannot enlist in the specified transaction coordinator" before in relation to that on Oracle deployments.

 

For a workaround could try modifying the connection string the DLL is using to include " OLEDB Services=-3" as this will stop it from being promoted to a distributed transaction and thus should prevent the "New transaction cannot enlist in the specified transaction coordinator" error. 

"

 

I made the appropriate change to a couple of dlls that connect to Oracle and this did fix the problem.