Is WIF 4.5 supported in a partial-trust environment? I have a WCF service that uses it and when deployed to a medium-trust environment the following error is occurring:
An error occurred creating the configuration section handler for system.identityModel: Attempt by method 'System.Configuration.ConfigurationElement.ApplyInstanceAttributes(System.Object)' to access method 'System.IdentityModel.Configuration.IdentityConfigurationElement.get_ApplicationService()' failed.
No WIF only runs in full trust.
Related
I'm building a WCF service that on startup (not first invocation) needs to monitor the filesystem for files to be updated. I have the service working however, I'm running into a problem where I can't get the WCF service to "warm up" on deployment and start doing its job. The only way I've been able to get the service to start is by directly poking it via one of its web methods.
I've followed the instructions in the following articles to no avail:
IIS 8 Application Initialization - warming up WCF services
http://www.codeproject.com/Articles/508713/Custom-WCF-web-service-warm-up
The only difference between what I'm doing and the samples appears to be that I'm using IISExpress. Has anyone had any success with WCF Service warm starts in IISExpress?
Dev Env: Visual Studio 2012 Sp2
When we install an NServiceBus 3.3.6 endpoint as a Windows service using the /install flag, it is automatically configured with a windows service dependency on Message Queuing.
However, even though our NServiceBus endpoints use RavenDb for persistence, the installer does not configure a service dependency on RavenDb. This means that when our server restarts most of our NServiceBus endpoints fail to start up due to the following exception:
System.InvalidOperationException:
The database {name} is currently being loaded, but after 30 seconds,
this request has been aborted. Please try again later, database loading continues.
Is there any way to tell NServiceBus to set up a dependency on RavenDb or is this something we have to configure manually, perhaps using INeedToInstallSomething<T>?
You can pass a dependencies list eg:
NServiceBus.Host.exe /install /dependsOn:"MSMQ,RavenDB"
The list needs to be comma delimmited.
In v4 the command line args are a bit different:
NServiceBus.Host.exe -install -dependsOn=MSMQ -dependsOn=RavenDB
Whenever I attempt to consume WCF Data Service (version 5.0 of WCF Data Services), the proxy generation fails with the error message:
The operation could not be completed
Any ideas? The Data Service is built using VS2012, Entity Framework 5.0 and WCF Data Services 5.0. Client is Windows 8 built using VS2012.
I have also tried installing WCF Data service 5.3 installer but faces same issue.
So basically I was facing issues on the entities which had a timespan datatype and throwed a "Operation cannot be completed" error while consuming the WCF data service in a Windows Store Client Library.
So the solution to the issue whilst consuming the WCF Data service to Windows Store app is to install the "WCF Data Services 5.6.0 Alpha Tools Installer" available here
Installing this resolved the issues faced while consuming the service.
I am new to Biztalk (Stack Overflow as well) I want to receive an xml schema file containing 2 digits and send it to WCF service which will do some arithematic operation on them and give me answer in a file as well. I have tried a lot but unfortunately couldn't succeeded.
What I have done...
I created a service and host it to IIS. It is running fine. I have tested it through (WCFTestClient.exe). Then I have created a biztalk project and Consume WCF Service from generated items. Then I deployed the project. And configured Receive and Send ports accordingly but have no luck.....
I have solved problem myself. Actually I read error message in suspended service messages in Biztalk Administration Console and after some google I was able to solve the issue.
I've written up a server in VB.NET that consumes a providers WSDL for functionality and then hosts my own WSDL so that they can communicate with me. In testing it's been working as expect; I can consume my hosted service using SOAP-UI and WCFTestClient effortlessly.
But when our provider attempts to connect to it he received this error:
Yadadada cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher
They're not entirely helpful in resolving this issue and I'm not sure where to start.
After toiling away at this on and off again I realized that the provider, who was trying to access my service, was using an ASMX web service as opposed to the WCF service I had written up. Still having been a little raw to WCF I chose to just redo the work as an ASMX service and thus my problems are solved.
Trials and tribulations of an intern.