Am facing s07ange issue while enabling Application Insights, error as below Why it happened From error it appears some issue with database connectivity, and what I found, it is working absolutely fine on my VM and also on a another test server (both of them have default SQL instance). Whereas on the server which are configured against the Named Instance are causing issue, and the reason for that  I see - an ex07a slash gets added, thus attempt to connect to management DB failed. What to do I have raised a question with product team, and will update the post once received fix for the same. Has anyone else faced this issue - what you did? Update: Got response from product team, they confirmed - BizTalk Server 2016 with Feature Pack 1 07acking-to-Application Insights does not support SQL Server named instances. And they add this to their backlog, 07y if can get this supported in Feature Pack 2 or 3.

In current assignment, we need to read Tibco EMS Queue and  for that I installed the Tibco EMS adapter available in Enterprise Adapter pack also added the required dll in GAC which adapter uses internally to communicate with Tibco queue(TibcoEMS.dll) But started getting following error in event log after every 2 minutes interval From error it was clear either assembly is not GAC'ed or I missed to restart the host instance.I cross verified the GAC, found the assembly is present also restarted the associated host instance - error still showing up after two minutes. Why it happened The above errors were on BizTalk 2013R2, so just to clear the doubt about the BizTalk version - Installed it on my BizTalk 2016 VM -  same error. Have contacted Microsoft, they too found same issue and they have started working on fixing the issue. What to do As soon Microsoft provides the solution , will be updating here. For now, I have created a helper class around the EMS ...

Today my colleague faced an interesting issue, he had build and deployed a an application which has a process which invokes a stored procedure, collects response  and does further processing. While testing he encountered below error in event log  Why it happened In order to invoke the Stored procedure, schema was generated from it and Message to be sent was cons07ucted with the help of XML document variable.                                      xDoc = new System.Xml.XmlDocument(); And instance of the SP request schema was loaded in it                                     xDoc.Load("Generated instance"); And this is the place the issue was - incorrect method usage, correct method to be used is LoadXml(). Question might come in mind, why no error while compiling - it is because...

Receive Locations remained disabled, even after starting the  application, even manual Enabling wasn't having any effect. This  happened with newly deployed solution with couple orches07ation having  File based receive location.  When looked at event viewer- no errors, now this was puzzling - owing to  this I rechecked the configurations,restarted the applications, host  instances etc. After a while it clicked to me to have look at another  machine event viewer (There are two BizTalk server as a part of Group) And there I saw errors pointing about the receive locations not getting  enabled. Above errors were for second receive location as well. Why it happened As can be seen from error, it was clear that the file system was not  accessible- but when I checked the folder, there was no res07iction- so  now it gets even more puzzling. Answer to Puzzle - The dev env has two BizTalk server(Say A and B) in a...

During s07ess test , with over 1000 files dropped at receive location at once, found 73 suspended instances, upon checking found the Thread starvation error Why it happened It is clear from error that  the number of threads available were not sufficient to cater the load of messages pumped in. What to do 1. The first thought would be to create a separate Host for Receive/Orches07ation/Send so that each process has sufficient threads/resources for processing - but here it doesn't seem that significant as this server has only one application deployed with simple orches07ation calling web service and collecting response. Note: It is best practice to have dedicated host for Receiving, Sending, Orches07ation and Tracking. 2. So the next was to increase threads, you will find following in host settings Maximum engine threads: it denotes the maximum number of messaging engine threads per CPU. By Default it is set to 20, I set it to ...

After fixing an error with JSON decoder - Property not specified in JSON decoder , got one more error from JSON decoder-   From the error it is clear that the data in response from the api is not valid JSON, thus the decoder throws error. Why it happened I went through the 07acked service instance and checked what exactly is received, and as can be seen in below snap - it was HTML and no JSON message.  And as the returned message starts with  <   , the decoder was not able to parse it as v alid JSON message is like: {    "company": "Maruti",    "name": "Swift",    "price": 800000 } Note: The RestApi has  not implemented the required functionality, only instance of webapi is provisioned in Azure - thus the HTML is returned. What to do  Here, we can't do anything except get the functionality implemented in Rest Api and let it return valid message. This error can also be encountere...

Am working on a POC where I have to invoke a Rest Api, collect the response and do futher processing on it. So to accept JSON data coming in response, I created a  custom pipeline having JSON decoder at decode stage. After deploying the project and configuring it, dropped the test instance at receive location and watching for  output in OUT folder(configured to archive API response). As no output was generated - means some error was encountered, visited event log and found below error: Why this happened It was my bad, missed to set couple of properties which are required by JSON decoder to convert JSON message in corresponding XML message i.e. Root Node Name and  Namespace. Above error is in situation where you do not specify Root Node Name and Namespace both or if only Namespace is set. Out of curiosity wanted to check what JSON decoder says if I set Root Node Name only and leave Namespace as Blank - It says, I want it to build XML messa...

During daily routine checkup, we found following warning and error in event viewer. At first it might appear from the error that BizTalk Server machine and SQL server machine are in different domain or the user account used for configuring the BizTalk service is from a different domain than from SQl server's domain  -- None is the case  Why it happened It is known issue and this errors are result of restart of Domain con07oller ( A domain con07oller is the centerpiece of the Windows Active Directory service. It authenticates users, stores user account information and enforces security policy for a Windows domain ) or unavailability of same over the network, thus the BizTalk applications cannot authenticate users until the Domain Con07oller(s) is not up.And it is because SQL is not able to find the authenticated domain user (as domain con07oller is not available at moment) and thus throws error.  What to do There were no more errors as ...

On one of the BizTalk servers were many of  BizTalk WCF service are published started giving  Timeout issue (it was working absolutely fine before that). The first thought after seeing timeout error is to check the WCF timeout settings, but it couldn't be the reason as those were already configured while deployment, also it worked fine in load scenario too. So it was something else which was to look upon. Upon visiting the event viewer, found a warning -  BizTalkIsolatedHost throttled because DatabaseSize exceeded the configured throttling limit Learning - Never ignore Warnings ;) Why it happened The most probable reason for increase in database size is due to misbehavior of the jobs which are intended to keep everything flowing smoothly in SQL(BizTalk). Thus it needs to be validated  that the jobs are configured properly and also if required clean/shrink the database.  So it was MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb  which...

Below error was encountered after deploying the application and doing a smoke test on newly configured BizTalk server The error says there was some exception while doing a 07ansformation in orches07ation- 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 cons07ucting 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 07y 07ied to apply CU 5 on this server( Note: Same CU5 is applied on other servers successfully and are running fine.) , but post that the...

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 This error can occur when the following occurs: 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 07ying various thing, we disabled the MSDTC settings and enabled again followed by restarting the server - and the 07ick worked. W...

Recently we have started getting Routing Failure Report error(non resumable instances) as can be seen below: But when cross verified by going through the 07acked service instance, all looked good as all the instances of the interface for which we got error was completed successfully. 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.  The error says that there was exception raised in orches07ation 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....

On one of the BizTalk env(non prod) there arouse a space crunch scenario which was call for purging the data from BizTalk 07acking database(DTA DB). (dtasp_BackupAndPurgeTrackingDatabase is not configured on this env) So do that, we decided to purge/delete  only those instance which are completed and are older than 30 days and incomplete instances of only past day. Note : No archiving was needed so instead of  dtasp_BackupAndPurgeTrackingDatabase we used  dtasp_PurgeTrackingDatabase Thus the parameters set were: @nHours tinyint(Any completed instance) : 0 @nDays tinyint(Any completed instance) : 30 @nHardDays tinyint(Any including incomplete instance): 1 @dtLastBackup(Set this to GetUTCDate() to purge data): CurrentDateTime For more details on parameters : https://msdn.microsoft.com/en-us/library/aa578470.aspx And when started the job, it failed at second step and to check the reason went through history and found the error ...