We are trying to push data to Azure Service Bus Queue when a case is created in "Dynamics CRM Online". We have implemented it using a plugin by registering it with Plugin Registration Tool.
The error is as follows
WindowsAzurePlugin.QueueProcess: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.ServiceBus, Version=2.1.0.0, I tied changing the versions to 2.6,1.5 and 1.0 but still it is showing same type that file not found exception error
Related
I have created a worker service to consume my eventhub data and save that into cosmos db. But I want to deploy my worker service with my web app which is an .net core web application.
Can anyone help me out here to get my job done ?
What architecture I should follow for it?
UPDATE
Upgrade Visual Studio Enterprise 2019（Version 16.7.7） to the latest version, the problem still exists.
After my test (using Visual Studio Enterprise 2019 16.0.30406.217 D16.7), I found that when you add Existing Project as Azure Webjob to the webapp of the .net framework, it can be successful.
But I cannot add it to the webapp of .net core. I think this is a bug.
Suggestions can raise a support ticket to confirm and seek official help.
We are currently working on a BizTalk server migration project (from 2013R2 to 2016) and in the process need to install Azure Storage Adapter (publisher BizTalkFactory Codeplex Team) so as to fetch files from Azure blob storage into BizTalk.
This is working fine with 2013R2 version however after installing the same msi on BizTalk Server 2016 Enterprise version we are not able to see azureStorageBinding under WCF-Custom adapter bindings.
Also I tried using WCF-WebHttp adapter with azureStorageBehaviour however when I apply changes it says "Error saving properties. (System.Configuration.ConfigurationErrorsException) Configuration binding extension 'system.serviceModel/bindings/azureStorageBinding' could not be found. Verify that this binding extension is properly registered in system.serviceModel/extensions/bindingExtensions and that it is spelled correctly"
I verified the machine.config file too and azureStorageBinding is present.
Note - When I install the same msi with BizTalk Server 2016 Developer version, it works fine.
Please let me know if I'm missing something here or any probable causes for this issue.
Thanks!
I am working on upgrading a project to Windows Azure 1.3 and I am running into an issue with hosting WCF services in an Internal Web Role. I get the following exception when trying to access the services:
HTTP could not register URL http://127.0.0.1:5111/service.svc/. Your process does not have access rights to this namespace
I did have a similar issue when working with Azure 1.0 and resolved it by with the following code:
new BasicHttpBinding() { HostNameComparisonMode = HostNameComparisonMode.Exact }
With this new issue, there seem to be a few common solutions; using the above code, runing the httpcfg tool to explictly change namespace reservation, and running as Administrator.
As far as I know, the httpcfg tool will not work for an Azure Internal WebRole because the port is dynamically assigned. Running Visual Studio as Administrator and debugging the Cloud project does not fix the problem either (Visual Studio does launch the Emulator).
It seems like the Azure Compute Emulator does not inherit the permissions from the Visual Studio process. Has anyone run into a similar problem, any ideas on fixes, work-arounds?
Karl
Okay, my suspisions were proved correct. When the Azure Compute Emeulator starts, it adds the Web Role instances in IIS, but the App Pool Identity does not have permissions to register namespaces.
I found this blog article which describes how to change the identity of the app pool when a Web Role instance is started.
http://www.wadewegner.com/2011/01/programmatically-changing-the-apppool-identity-in-a-windows-azure-web-role/
This is a less than ideal solution, but works.
We have setup a .net application developed with .net framework 4.0 using MVC framework and WCF service on a Windows 2003, 32-bit server containing IIS 6 successfully.
However, when the same application is set up on a Win 2008 R2, 64-bit server, we get the following error when the application is accessing the WCF service:
No component for supporting the service was found
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Castle.MicroKernel.ComponentNotFoundException: No component for supporting the service was found
We have set the flag for Enable 32-bit apps in "Application Pool" to true on the 64-bit server.
I don't think that this is related to WCF itself. ComponentNotFound is thrown by Windsor Castle IoC container and it means that something is wrong with its configuration. So when IoC tries to resolve the type of service it doesn't find related configuration.
I have writed a primitive wcf (vs 2010) service and created proxy files by svcutil. Later I created a mobile project on vs2008 and added proxy files on project but this error occured.
Error 1 The type or namespace name 'ServiceContractAttribute' does not exist in the namespace 'System.ServiceModel' (are you missing an assembly reference?) C:\Users\Abb\Documents\Visual Studio 2008\Projects\WCF\MobileService\MobileClient\Sample.cs
the proxy files runs well on console application (vs 2008) but there is errors on mobile.
System.ServiceModel doesnot support ServiceContractAttribute.
For mobile applications you shouldn’t use SvcUtil to generate proxies since this does not generate code compatible with the subset of WCF functionality available to the .NET Compact Framework on mobile devices.
Instead, you should use NetCFSvcUtil.exe. See this link for more information: Using NetCFSvcUtil.exe to interact with ServiceContracts