Saturday, April 8, 2017

MissingMethodException - Method Not found

Below error was encountered after deploying the application and doing a smoke test on newly configured BizTalk server


method not found

The error says there was some exception while doing a transformation in orchestration- method not found: 'Void Microsoft.BizTalk.ScalableTransformation.BTSXslTransform.set_MapUseXSLTransform(Int32)'.

But this gets overruled by the fact that same application runs fine on other environment with same data used for testing, so there is no problem with the constructing of message.

It is reported on one of the forum thread that this issue is related to assemblies not deployed correctly. Following to this, redeployed the assemblies - didn't help. Another probable reason, is the deployed assembly latest - this doesn't apply here as no changes were made in the assemblies. 

Why it happened

We had try tried to apply CU 5 on this server(Note: Same CU5 is applied on other servers successfully and are running fine.), but post that the server started behaving weird and numerous error related to DB started to pop out - like few Stored procedures are missing and so on. 



So we decided to reconfigure the BizTalk server thus creating fresh BizTalk DB's (we didn't had Backup else restoring it would have been the choice).

The reconfiguration went successful with little surprise - last post about it

What to do


Although the configuration was successful, we are getting error - assembly redeploying not helping, so it was certain that the effect of CU5 still exists thus asking to go for reinstalling the BizTalk server, but before doing that thought of repairing - and it did solve the issue.

Still, the main problem remains unanswered why on few servers CU5 was successful and on this server it caused issue(same steps followed on all). Will try to dig into this issue and if found something will share it.




Friday, April 7, 2017

System.EnterpriseServices.TransactionProxyException

A little background - we were provisioned with new database server and a new database instance against which we have to configure the BizTalk server (which was configured against the old one).



It is no complex tasks, you run the configuration wizard and provide the details and you are done :) . But sometimes simple task blow your mind with some surprises, this is what happened to us.  The configuration wizard was not happy and it threw an error


Transaction Proxy Exception

MS DTC service is configured incorrectly
MS DTC Ports are not allowed in the Firewall rules

On BizTalk sever it was all good (as it was already configured with old database). So the doubt was on new database server, we checked on it too and there too all was good.

Now this was annoying and ate lot of our time. After lot of thought and trying various thing, we disabled the MSDTC settings and enabled again followed by restarting the server - and the trick worked.


Why it happened

The only deduction I can think of is - that while re-configuring the MSDTC settings were disabled and were not refreshed on GUI . 

If anyone knows the real reason, please share your views in comment. 


What to Do

First is to check the MSDTC settings and firewall setting , if that doesn't work then do as I did.

Another interesting post around this error, I read after resolving the above issue is by Kent  - msdtc adventures 


.

Sunday, April 2, 2017

Routing Failure Report

Recently we have started getting Routing Failure Report error(non resumable instances) as can be seen below:


routing failure report error message

routing failure report




But when cross verified by going through the tracked service instance, all looked good as all the instances of the interface for which we got error was completed successfully.

completed instances
No, it is not related to the bug reported with SP1 of BizTalk 2006 R2 , so why suddenly we started getting this error in spite of the instances getting completed (BizTalk 2013 R2) 


Why it happened


There were some errors in the event log at the same time when there was Routing Failure report generated in admin console. 


Orchestration xlang exception


The error says that there was exception raised in orchestration while processing the request, still the question persists - why Routing Failure Report for this?

There is one more thing pointed in error, service xxxx terminated without responding to the operation xxxx, thanks to my colleague Pravin Shinde for pointing out the reason. 

Let me explain the interface

As can be seen from the diagram, interface receives a request and using the information from it, it invokes the target webservice and collects the response. If there is any exception in the process, it is caught by exception block and in it the respective stake holders are notified about it.

But why Routing failure report? - It was because there was exception raised before the step 4 (Send response to caller) and that was over passed,as on exception control goes to exception block. Thus the operation of sending response was not completed although the Orchestration instance completed by sending email to stakeholder.


What to do

Then there might be question what to do with the error -- Terminate it. And yes, connect with stakeholders and let them know or understand yourself what data was incorrect, with a fix on it to avoid unnecessary error in admin console.