Showing posts with label debug. Show all posts
Showing posts with label debug. Show all posts

Saturday, March 24, 2012

Deployment Question- iframe executor failed ?

Just moved to a new server and Debug output is giving me.. "A web request made using the iframe executor failed. Make sure that the app's web.config registers iframecall.axd"

Of course this doesn't happen in dev/test. The server file from the root up are exactly the same (after I switched it to debug).. Is there something else to configure?

It appears that all atlas/ajax calls back to the server are failing in the new environment. There are basic service calls registered in the script manager and some toolkit controls as well.

Where to start?

Other important things I neglected to mention.. I have already added the iframecall in the http handler & theWebOperationAttribute(true,ResponseFormatMode.Json,true) setting to each of the web methods declorations.


Other important things I neglected to mention.. I have already added the iframecall in the http handler & theWebOperationAttribute(true,ResponseFormatMode.Json,true) setting to each of the web methods declorations.


I use fiddler to make sure the script manager was registering the services and everything looks good. If I point the services back at the dev server they work great?

Fiddler namespace registrations.

HTTP/1.1 200 OK
Date: Mon, 21 Aug 2006 12:32:33 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 582

Type.registerNamespace('NU.Web.ECatalog.Services');
NU.Web.ECatalog.Services.PassortUsers=new function() {
this.appPath = "http://nunettst3:8040/apps/ecatalog/";
var cm=Sys.Net.ServiceMethod.createProxyMethod;
cm(this,"SearchInvoiceApproversByName","prefixText","returnCount");
cm(this,"SearchMaterialRequestApproversByName","prefixText","returnCount");
cm(this,"SearchByName","prefixText","returnCount");
cm(this,"SearchByNameNoLimit","prefixText");
cm(this,"GetInvoiceApproverId","name");
cm(this,"GetMaterialRequestApproverId","name");
cm(this,"GetUserId","name");
}

Wednesday, March 21, 2012

Debugging Web Service/Atlas

Hello,

I'm trying to debug a problem with a biz layer class that gets called from my web service. I rtied doing System.Diagnostic.Debug.writeline but nothing gets written and also tried doing breakpoints but those don't work either. Is there anything I can do to get debug info?

Thanks,

Clank

PS - I don't the search function works for the forums either.

Yeah, debugging Ajax style applications is tough. Basically you have to put a debug line at the start of your web service and make sure it even gets there. If not, start with "alerts" in the JavaScript before your web service is called.

You can attach a debugger to both the server-side and the client-side (provided you unchecked the two relevant checkboxes in IE advanced settings).

You can also use debug.dump and debug.trace from the client-side.

You can also use Nikhil's browser helper to monitor the network traffic and get client-side stack traces:http://www.nikhilk.net/Project.WebDevHelper.aspx