An Error Has Occurred While Consuming This Service
consuming this service. .NET Framework > Windows Communication Foundation, Serialization, and Networking General discussion 0 Sign in to vote Hello, I deploy a WCF webservice on my machine and my application can connect it normally. But when I deploy this service on production server, I had the following exception: ------------- System.ServiceModel.FaultException: An error has occurred while consuming this service. Please contact your administrator for more information. Error ID: ea1a6e8d-49ec-4372-85a3-a6428948d024 Server stack trace: at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) ------------- I guess this relates to security of WCF. Is it right? How can I fix this? Many thanks! Edited by MinhKha Thursday, July 23, 2009 8:13 AM Changed type Riquel_DongModerator Thursday, July 30, 2009 10:03 AM op didn't follow up Thursday, July 23, 2009 7:57 AM Reply | Quote All replies 0 Sign in to vote Hi MinhKha, the error you're getting is way too generic, try tracing the execution on the service side, it might give you a clue or two. Regards, John Thursday, July 23, 2009 8:11 AM Reply | Quote 0 Sign in to vote You are getting this issue due to security reason. Try to do one thing. Cre
Tips/Tricks Top Articles Beginner Articles Technical Blogs Posting/Update Guidelines Article Help Forum Article Competition Submit an article or tip Post your Blog quick answersQ&A Ask a Question View Unanswered Questions View All Questions... C# questions Linux questions ASP.NET questions SQL questions VB.NET questions discussionsforums All Message Boards... Application Lifecycle> Running a Business Sales / Marketing Collaboration / Beta Testing Work Issues Design and Architecture ASP.NET JavaScript C / C++ / MFC> ATL / WTL / STL Managed C++/CLI https://social.msdn.microsoft.com/Forums/vstudio/en-US/f9bfbc42-f42b-440c-9ac2-7dd01478d24b/systemservicemodelfaultexception-an-error-has-occurred-while-consuming-this-service?forum=wcf C# Free Tools Objective-C and Swift Database Hardware & Devices> System Admin Hosting and Servers Java .NET Framework Android iOS Mobile SharePoint Silverlight / WPF Visual Basic Web Development Site Bugs / Suggestions Spam and Abuse Watch features Competitions News The Insider Newsletter The Daily Build Newsletter Newsletter archive Surveys Product Showcase Research Library CodeProject Stuff http://www.codeproject.com/Questions/635972/Unexpected-Error-from-Exception-Handling-Block-in communitylounge Who's Who Most Valuable Professionals The Lounge The Insider News The Weird & The Wonderful The Soapbox Press Releases Non-English Language > General Indian Topics General Chinese Topics help What is 'CodeProject'? General FAQ Ask a Question Bugs and Suggestions Article Help Forum Site Map Advertise with us About our Advertising Employment Opportunities About Us Ask a Question All Questions All Unanswered FAQ Unexpected Error from Exception Handling Block in WCF for FaultExeption and FaultException Rate this: Please Sign up or sign in to vote. See more: C# ASP.NET WCF Enterprise , + Hi I am getting an unexpected error from Enterprise Library Exception Handling Block v5 in WCF. All I want to do is NotifyRethrow for FaultExeption and FaultException Please read further. Thanks in advance for any help. I am working on a project where I had to use ExceptionShielding in WCF and not try-catch as we are logging all possible exceptions. But there are cases where I just have to send inform
2012 by Nick Developing for iMIS | SOA This is http://www.imiscommunity.com/15_2_soa_product_pricing_error wilth tech support as an SMR, but have not had a response in a few days.so thought Iwould post here too incase http://dave-sampson.blogspot.com/2011/07/wcf-enterprise-library-cruise-control.html anyone has had a similar problem and has suggestions. Hello, I am getting the following error when I try to get an error product pricing information using SOA calls. The functionality is working fine on my development machine, but get this error when install on the client servers. I checked the product and there is member/nonmember pricing, the product looks similar to the set-up on the local an error has machine that works. I can add the product to the cart, but the pricing is zero, so leads me to believe the proper pricing is not being found that returns the null reference object. Let me know what I else I can provide to get this web service call working. Thanks Nick CommerceManager.GetPartyItemPrice Asi.Soa.Commerce.Persistence.V10.PartyItemPriceLinqDefinition.GetEntity() Service Error: An error has occurred while consuming this service. Please contact your administrator for more information. Error ID: e187ab14-3baf-48b2-8c6c-82e72c89bfe4 Timestamp: 3/27/2012 9:07:55 AM Message Id: e187ab14-3baf-48b2-8c6c-82e72c89bfe4 An exception of type 'NullReferenceException' occurred Type: NullReferenceException Message: Object reference not set to an instance of an object. Source: Asi.Soa.Commerce.Persistence.V10 Stack Trace: at Asi.Soa.Commerce.Persistence.V10.PartyItemPriceLinqDefinition.GetEntity() in c:\Builds\42\ScrumV3\15.2.0_Main15_Commit\Sources\imis.net\Packages\Soa\Asi.Soa\Asi.Soa.Commerce.Persistence.V10\LinqDefinitions\PartyItemPriceLinqDefinition.cs:line 274 at Asi.Soa.Core.Persistence.LinqPersistenceTranslator.PersistenceInstanceToEntity(Object persistenceInstance) in c:\Builds\42\ScrumV3\15.2.0_MainFoundation_Commit\Sources\imis.net\Packages\Soa\Asi.Soa\Asi.Soa.Core\Persistence\Linq\LinqPersistenceTranslator.cs:line 78 at Asi.Soa.Core.Persistence.LinqQuery.TranslateLinqQueryResultsToEntityIdentityMapList(Repository repository, ExtendedEntityDefinition extendedEntityDefinition, IQueryable queryable) in c:\Builds\42\ScrumV3\15.2.0_MainFoundation_Commit\Sources\imis.net\Packages\Soa\Asi.Soa\Asi.Soa.Core\Persistence\Linq\LinqQuery\LinqQuery.cs:line 104 at Asi.Soa.Core.Persistence.LinqQuery.ExecuteQuery(QueryData query) in c:\Builds\42\ScrumV3\15.2.0_MainFoundation_Commit\Sources\imis.net
be a bit out of date. Still, hopefully it might help someone sometime...] I recently had an interesting experience with Cruise Control automated builds. The scenario was this: A set of web services implemented in WCF, with the constituent parts separated out into distinct projects in the Visual Studio solution: Common, Contracts, Implementation, Host. The Exception Handling Application Block (EHAB) from the Microsoft Enterprise Library 4.1 was used for its great configurable exception handling & logging and exception shielding features. We had automated builds set up on a build server using Cruise Control. Anytime you checked in changes to the solution, the build server would rebuild a new version and make it available for deployment to the "official" dev, test, and production environments. [This has since been changed, because it was kind of overkill and led to about a million (overstating) builds per day] I was working on a local dev machine, modifying the web services, running them locally, and performing my unit tests successfully. Checked in my changes and asked for the latest build to be deployed to the "dev" web server, ran the same unit tests, the unit tests ran fine until I executed a test that was intended to produce an error that needed to be handled by the EHAB configuration. Instead of the logging and custom Fault I was expecting, I got the default "shielded" Fault and exception message produced by the EHAB "An error has occurred while consuming this service. Please contact your administrator for more information. Error ID: {handlingInstanceID}". Hmm... I double-checked that I was indeed sending in exactly the same "bad" request, that should be generating the exception I was expecting, and that the EHAB configuration should be handling it. Yes indeed. To cut a long story of