i've created a wcf service library with ado .net entity framework to handle the retrieving of data from the database and send it to the user.
i've been testing it in visual studio without any problems.
so, i moved the dll of the service and the xml configuration file to the bin folder of weborb, changed the web.config to add my service.
but when i invoke the service from the webconsole i get this error:
>The server was unable to process the request due to an internal
>error. For more information about the error, either turn on
>IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute
>or from the <serviceDebug> configuration behavior) on the server in
>order to send the exception information back to the client, or turn on
>tracing as per the Microsoft .NET Framework 3.0 SDK documentation and
>inspect the server trace logs"
can anyone give any help with this?
how can i get a working wcf service library using ado .net entity framework in weborb?
help would be appreciated.
thanks in advance.
Have you checked the WebORB log?
Then start off by trying the WebORB examples from here.
The WebORB log should give you more detail about the error. With that info, I would post a question on the WebORB forum.
Related
Testing the new backend discovery feature in WL6.1 used for a web service (SOAP) connection, we found a wrong import procedures from WSDL parsing. In particular, for each procedure offered by the SOAP server and exposed in the related WSDL the backend discovery service found only one input/output parameter although the procedures are composed of more than one input parameter. The problem seems to be a misinterpretation of the WSDL associated with the SOAP server.
thanks,
Here the WSDL:
https://dl.dropboxusercontent.com/u/15425546/Ws_StoreSurfer.xml
Is seems that WL v6.1 indeed has a problem with muli-parts and showing only one part of the input/output of a procedure.
Tested it with a new version of WL (not yet released) and it seems like the problem has already been addressed (see below). You will therefore get it solved in the next update of your Worklight Studio.
If you are an IBM business partner or customer you can open a PMR and request an intermittent iFix.
I am trying to deploy an application created using Breezejs and EntityFramework using the Breeze WebAPI. When I run it in my development environment it runs perfectly, but the minute I upload it to our server I get the following error "Error: Metadata query failed for: ../api/Entity/Metadata; Not Found" when I try and make a call.
In my development environment if I go to "localhost:59510/api/Entity/Metadata" I can see the xml displayed, but if I go to "www.example.com/api/Entity/Metadata" I get the error.
Am I missing a dll somewhere? Is it an error with my configuration in breezejs, web api's or with EntityFramework?
Thanks
Jeff
Sounds like you are missing something. Check the event viewer on the deployment machine. Could also be missing the breeze controller dlls
I deployed a ASP.NET MVC4 app with SQL Server CE database, but I'm getting
Sorry, an error occurred while processing your request
I am using VS2012 to publish this app to azure website. How can I solve this issue? Thanks.
To summarize and so an answer can get marked on this to help the next person that comes by.
When running into issues on azure-web-sites FTP is a handy debugging tool which enables you to:
Verify that the dll exists in your bin directory
Sometimes the .gitignore file blocks directories from being checked in
Verify that your web.config file has the proper version of the assembly configured
NuGet can help, but it's ultimately up to you to verify your dependencies
Here is a good article to follow on the subject: http://www.dotnetcurry.com/showarticle.aspx?ID=883
Unfortunately with VS 2013 Compact edition is not supported any more, so things are somewhat tricky.
I am trying to configure ASP MVC 2 Framework to run within a SharePoint 2007 install on IIS 6.0. I have managed to get the two web.config setups together, and made GAC and global.asax changes.
When I try to access the MVC application within the SharePoint domain (http://Sharepoint.com/MVCApp), I get a security exception.
**Source Error:**
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
**Stack Trace:**
[SecurityException: Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.]
System.Web.Mvc.BuildManagerWrapper.System.Web.Mvc.IBuildManager.GetReferencedAssemblies() +14
System.Web.Mvc.TypeCacheUtil.FilterTypesInAssemblies(IBuildManager buildManager, Predicate`1 predicate) +88
System.Web.Mvc.TypeCacheUtil.GetFilteredTypesFromAssemblies(String cacheName, Predicate`1 predicate, IBuildManager buildManager) +65
System.Web.Mvc.AreaRegistration.RegisterAllAreas(RouteCollection routes, IBuildManager buildManager, Object state) +80
System.Web.Mvc.AreaRegistration.RegisterAllAreas(Object state) +55
System.Web.Mvc.AreaRegistration.RegisterAllAreas() +7
CapExRequest.MvcApplication.Application_Start() in C:\Documents and Settings\Administrator\My Documents\Visual Studio 2008\Projects\CapExRequest\CapExRequest\Global.asax.cs:29
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3614
I have tried adding permissions to the MachineName\ASPNET account for the \MVCApplication as suggested in one article. No joy.
Other occurences seem to be related to accessing a remote file share. There is no remote file share in my instance.
Any thoughts, suggestions, answers??
So, here is what the setup is, and the steps taken to get it all together...
Followed basic instructions for
running an ASP.NET MVC application in SharePoint (see link below), but I put the
custom MVCHttpApplication in it's own
project and created a standalone
assembly;
Updated SharePoint to include AJAX
3.5 (ours was only referencing 1.0 standalone);
Built a signed application and
deployed to the virtual directory,
including adding the application
assembly in the GAC.
Actually pretty straight-forward so far. It just took a while to come to my senses.
"Using ASP>NET with Sharepoint Publishing" http://vspug.com/mbailey/files/2010/04/Using-ASP.NET-MVC-2-with-Sharepoint-Publishing.pdf
We developed an web application using visual studio 2008. In my development PC, the application is working fine. In production server I am getting the following exception "ASP.NET AJAX CLIENT FRAMEWORK FAILED TO LOAD". What should I do to make it work?
Thanks,
P.Gopalakrishnan.
I'd start with making sure all of the appropriate service packs are applied and that the 3.5 framework is actually installed on the box.
Also, make sure any assembly you reference that isn't part of your deployment is gac'd on the machine. Check version numbers.
All else being equal, I'd guess the server is just way out of date on it's updates.