Forum Widgets
Latest Discussions
Problems installing Biztalk2020 CU1
Just yesterday we tried to upgrade our new BTS2020 dev environment to CU1. Installation went through without problems, but after the installation Biztalk Admin Tool mmc-plugin fails to load with error below. Same happens if the MMC is opened separately and they trying to add the Biztalk Server add-in. The problem started when installing CU1 with VS plugin, all changes were removed and it was fixed. Reinstalling the CU1 only made it happen again and removing it fixed the situation again. Has anyone else faced anything like this? We are also receiving this error when trying to start Biztalk hosts. : Error code: 0x80131534 Error source: Microsoft.BizTalk.CommonSettings Error description: The type initializer for 'Microsoft.BizTalk.CommonSettings.CBizTalkSettingsLookup' threw an exception. Also this problem is fixed as soon as CU1 is removed. We were trying to install this to fix a problem with BTS2020 jobs, one fails with the error message Invalid column name 'uidServiceInstanceId', where it seemed it could be a collation issue in our database - something similar was fixed in Biztalk 2016 CU7-upgrade. Error text for MMC: Faulting application name: mmc.exe, version: 10.0.17763.1282, time stamp: 0x9eae7180 Faulting module name: KERNELBASE.dll, version: 10.0.17763.1369, time stamp: 0xb99aaceb Exception code: 0xe0434352 Fault offset: 0x00122452 Faulting process id: 0x14cc Faulting application start time: 0x01d69275d6dd21c4 Faulting application path: C:\Windows\SysWOW64\mmc.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 41426be9-6006-4a1b-8e75-52cae7d62349 Faulting package full name: Faulting package-relative application ID:
BizTalk 2020 WCF-OracleDB adapter Error
I am trying to create a WCF-Oracle DB send port and I get this error. I have Installed both ODP.NETUnmanaged19.10Xcopy32bit and ODP.NETUnmanaged19.10Xcopyx64 and used the command OraProvCfg.exe /action:gac /providerpath:"Oracle.DataAccess.dll" to Gac the Dlls. Also I have changed the machine config on both Framework and Framework64 to point to this version. <runtime> <assemblyBinding xmlns="urn: schemas-microsoft-com: asm.v1"> <dependentAssembly> <assemblyIdentity name="Oracle.DataAccess" publicKeyToken="89b483f429c47342" /> <bindingRedirect oldVersion="4.122.18.3" newVersion="4.122.19.1" /> </dependentAssembly> </assemblyBinding> </runtime> I am running out of ideas here. Any body encountered the same issue?
Known issues with BizTalk Server 2020 RosettaNet accelerator (Part 1)
As we all know, BizTalk Server 2020 thoroughly removed old native SQL adapter and replaced it with WCF-SQL adapter. This change has resulted in several known issues with some existing components like RosettaNet accelerator(BTARN) that used old SQL adapter previously. Before Microsoft releases official fix of the BTARN problems, you can also follow the steps below to work around them by yourself. Steps: First of all, you need to correct the binding of receive locations: LOB_To_PrivateInitiator and LOB_To_PrivateResponder. Use XmlPolling Set Xml SP Root Node Name to: LOBMessage Set Xml SP Namespace to: http://schemas.microsoft.com/biztalk/btarn/2004/LOBMessage PolledDataAvailableStatement to: Select 1 See the screenshots below: After that, you also need to correct binding of Send ports: PrivateInitiator_To_LOB and PrivateResponder_To_LOB. Especially pay attention to the SOAP Action header: A further problem was that PrivateInitiator_To_LOB port uses an outbound map to transform LOBMessage into the schema of native SQL adapter(SQLSCMessageOut) before being inserted into MessagesToLOB table. In this case, we also need to generate new Wcf-Sql based schema and create corresponding map to transform LOBMessage Into Wcf-Sql Insert message: The generated schema and map files I use are in attachment. The script functoid in the map is quite simple that converts string type Delivered value("0" or "1") to boolean. public bool getDelivered(string delivered) { if(delivered == "1") return true; return false; } The same changes need to be applied to PrivateResponder_To_LOB port as well. After all the above changes, the BTARN Loopback sample should be back to work fine. Next, let's move on and continue to resolve issues with DoubleAction scenario: Known issues with BizTalk Server 2020 RosettaNet accelerator (Part 2)BizTalk Server 2016 Standard Edition CU7 not available in german language?
Hello, on a system of one of our customers we have an BizTalk Server 2016 Standard Edition installation in german language. Because of advanced security requirements we want to configure TLS1.2 explicitly. BizTalk Server 2016 TLS1.2 is supported with CU5 and above. But there is no german download of these CUs on the download pages. We tried to install CU7 in english (BTS2016-KB4528776-ENU.exe) but the installer reports, that the programm to patch is not installed or the patch used is a wrong one. Please tell me, when or where the CU7 in german langugage for BizTalk Server 2016 will be available? Is there another way to patch our BizTalk installation to work with TLS1.2? Thank you very much in advance. Best regards Jan GorkowBizTalk TMS does not start after BizTalk Server 2020 configuration
The problem has two causes: The first start of BizTalk TMS requires higher permissions than specified in the documentation. According to the documentation, the account under which the service runs must be in the SSO Administrators group. However, the service creates an event source the first time it is started, and this operation requires computer administrator privileges. The workaround is to add the service account to the computer administrators group before the first startup and then remove it from this group. The permanent solution from Microsoft should be to create this event source during configuration by the BizTalk Server Configuration tool. BizTalk TMS starts before the Enterprise SSO service usually. According to the documentation, the service depends on the Enterprise SSO service, however the BizTalk Server Configuration tool this service dependency does not configure. The workaround is to create this dependency manually by running command: sc config BizTalkServerTMS depend=ENTSSO The permanent solution from Microsoft should be to create this service dependency during configuration by the BizTalk Server Configuration tool.
BizTalk process Host is not releasing memory until Hosts are manually restarted
The BizTalk process Host is not releasing memory until Hosts are manually restarted (Ideally it should release the memory that is not in use) We tried terminating all running/suspended instances, still memory occupied by Host was stagnant. We tried processing small feed files, however still the memory was not changed. Memory keeps increasing during high load and is not getting freed up. The memory slowly piles up and each of the service calls (WCF Web Service calls) starts getting delayed, taking around 10 mins to proceed (even when we clearly see on WCF Web Service Servers that response from service was sent on time within a minute) Everything goes back to normal and speeds up as soon as we manually restart process host instanceIssue with Custom Domain on APIM and Cloudflare Proxying
Dear all, Last week, we attempted to configure a custom domain name for our Azure API Management (APIM) instance. We use Cloudflare as our DNS provider. The required CNAME record was created with the proxied attribute enabled. However, when configuring the custom hostname in Azure, we encountered the following error: Invalid parameter: CustomHostnameOwnershipCheckFailed. A CNAME record pointing from apim.ourowndomain.net to apim.azure-api.net was not found. As a workaround, we disabled the proxied attribute in Cloudflare, retried the configuration, and it worked successfully. We then re-enabled the proxied attribute, and the custom domain continued to function correctly. However, yesterday, we discovered that the custom domain was no longer working and returned a "404 Web site not found" error page. After extensive troubleshooting—including disabling the proxied attribute on the CNAME record—we were unable to resolve the issue. To restore functionality, we removed and reconfigured the custom domain by following the same steps: Disable the proxied attribute on the CNAME record. Configure the custom domain in APIM. Re-enable the proxied attribute. This resolved the issue again. We suspect that Azure initially validates the CNAME record during the custom domain configuration process when the proxied attribute is disabled. However, after a few days, Azure appears to revalidate the CNAME record and expects it to resolve to *.azure-api.net. Since Cloudflare returns its own IPs when proxying is enabled, Azure may reject the custom domain configuration, leading to the issue. Can anyone confirm whether our assumption is correct? Additionally, is there a recommended workaround for this issue? We are considering deploying a reverse proxy (Application Gateway) to handle Cloudflare requests and forward them to the APIM instance. Thank you in advance for your help. Best regards,
Site from Azure VM to web
Newbie here, have a vm on azure running Windows server 2016 with IIS. Have installed a ticketing application to be hosted on IIS. I can access the application using http://localhost:portno from the azure vm itself. I want to access this site from the internet from anywhere. Are there any materials i could read up for this to be done. Thanks
