This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 4%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
Logic. App using IBM DB2 connector to fetch data from AS400 mid-range systems with standard Logic app using VNET integration with Dot net Stack used in configuration and as runtime.
With latest deployment to the North Europe Region, we have seen that the Standard Logic app runtime has changed from node to the dotnet. With Change in runtime 4.636.0.23246 and the stack in configuration is also Dot net 8 version which is currently giving us an error.
Please find the details of the error
The type initializer for 'Microsoft.HostIntegration.Drda.Requester.Requester' threw an exception
Upon further Investigation Noticed that the System.Diagnostics.EventLog not able to find
message='Service Provider: '/serviceProviders/DB2' Operation Id: 'executeQuery' resulted in: The type initializer for 'Microsoft.HostIntegration.Drda.Requester.Requester' threw an exception.', exception='[System.IO].FileNotFoundException: Could not load file or assembly 'System.Diagnostics.EventLog, Version=8.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified. File name: 'System.Diagnostics.EventLog, Version=8.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' at Microsoft.HostIntegration.Drda.Common.Logger..cctor()
please suggest fix the above issue with IBM DB2 connector to work with standard Logic app using VNET integration while configuration is DOT NET.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 22%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESE%3C/text%3E%3C/svg%3E)
Hi @Rohit shakya ,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
The error message indicates that the System.Diagnostics.EventLog assembly is missing, which is causing the connector to fail when trying to fetch data from your AS400 systems.
Firstly, check if the System.Diagnostics.EventLog assembly is correctly referenced in your project. This assembly is needed for logging and may not be available in the current environment. If the assembly is there, try restoring the NuGet packages. This process ensures that all required libraries are included in your project.
Additionally, make sure that you have the latest version of the IBM DB2 connector. Sometimes updates include important fixes that could resolve compatibility issues.
Finally, ensure that the Logic App is properly integrated with the VNET and that there are no network restrictions preventing access to the IBM DB2 system. I hope the steps will help to resolve your issue.
hello Shireesha Eeraboina (Quadrant Resource LLC) Thank for the response!!
However, just to mentioned that this was working perfectly fine till 2 weeks ago we haven't changed anything from our end. apart from the logic app deployment which is basically the workflow deployment.
We have just noticed that there was logic app stack changed from Node to Dot net automatically, and it stopped working however, we cannot roll back to the node as seems like it is due to latest runtime.
We did try to use the latest connector but also same issue.
Also, as per error we did find the dll was missing when we did KUDU to the deployed bin folder and also tried to add in the bin manually just to make sure if that is working and also adding separate package to solution but still no luck.
Vnet and azure firewall is tested, and it is working as expected.
This is kind of blocker for us due to the sudden runtime of logic app changes as per our initial investigation, however, need support from community on insight to fix it.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(172.8, 28.000000000000004%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJK%3C/text%3E%3C/svg%3E)
We also face the same issue connecting to DB2 DB from Standard Azure logic apps. It used to work till 4 PM EST on 09/31 and it suddenly started failing and has been failing till now.
{
"code": "ServiceProviderActionFailed",
"message": "The service provider action failed with error code 'ServiceOperationFailed' and error message 'The type initializer for 'Microsoft.HostIntegration.Drda.Requester.Requester' threw an exception.'."
}
True Jeevan Kumar Ganesan it does look like an issue with the latest runtime as per my initial analysis and do post if you have found any solution which would be benefit to both of us.
hello @Logic app devloper @Logic Apps Admin @Logic App @Azure,LogicApps please help us with the suggestion related to issue with DB2 connector and looks like as per Jeevan Kumar Ganesan this is started impacted most of the IBM/DB2 connector users using standard logic apps.
We are facing below issue
Microsoft.HostIntegration.Drda.Requester.Requester' threw an exception.', exception='[System.IO].FileNotFoundException: Could not load file or assembly 'System.Diagnostics.EventLog, Version=8.0.0.0, Culture=neutral
Any insight and suggestion would be really useful to us and the community.
Thanks !!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 22%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHA%3C/text%3E%3C/svg%3E)
Agreed, this is a widespread issue.
It appears the 4.36 function extensions runtime in process is broke. We are facing the exact same issue as described and working with support to escalate.
Please let us know if someone figures out the solution for this issue.
hello Hill, Austin please do keep us posted once you have any response after escalation.
Thank You !!
This is with Microsoft's product team and they are working on a solution, I'll give an update as soon as I hear back.
This is the response from MS support team for our support ticket - "I wanted to bring to your attention that we have identified an issue affecting a significant number of our customers using the DB2 connector. Please be assured that the product team is currently dedicating their efforts to resolve this matter as swiftly as possible."
I've received a workaround from the product team. They are still working to resolve this, but for now go into your logic app environment variables and update AzureFunctionsJobHost__extensionBundle__version to [1.87.34.0]
Thanks Hill, Austin I have also received same input just now from product team.
"Could you please try to change the AzureFunctionsJobHost__extensionBundle__version to [1.87.34.0] (please copy and paste the value in Bold) in the environmental variables? After making this change, kindly perform a hard restart of the logic app"
hello Hill, Austin, Jeevan Kumar Ganesan do let me know if the above-mentioned solution works for you as it doesn't seem to be working for me.
I did change the extension bundle as mentioned but still having same error message.
Appreciate your response!! Thank You!!
Could you please try to change the AzureFunctionsJobHost__extensionBundle__version to [1.87.34.0] (please copy and paste the value in Bold) in the environmental variables? After making this change, It is working as expected now
This can be marked as closed now!!
Thanks, you all for all the support!!