Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Strange web service (AJAX) errorStrange web service (AJAX) error
Previous
 
Next
New Post
2/11/2009 9:43 AM
 

I have a webservice that I'm calling from AJAX (mapped the web service using the ScriptManager so it'd load the javascript proxy for me) and it works great on my dev machine all the time.  I deploy it to the live server and it works in FireFox but not in IE7, it gives the error: "Invalid web service call, missing value for parameter: 'timeFrame'."  Now here's the really weird part -- if I turn on Fiddler to try and see what is going on IT WORKS.  The second I disable Fiddler it stops working again.  How the freaking heck am I supposed to debug it if the debugger causes it to work?

Has anybody ever seen anything like this happen and, if so, know what I can do to fix it? 

I can't provide a link for other people to test it because it is internal (company Intranet).  My next step is to try it in IE6 and/or another computer altogether... might be an isolated problem on my development machine.  Ideas greatly appreciated.

*EDIT: I checked IE6, same problem.  Checked IE8 (beta, with Windows 7 beta) and it works.  It did give me the error once after I had just tested it in my IE6 instance (different virtual machine) but I refreshed the page and tried again and it worked.  Refreshing the page over and over in IE6 and IE7 doesn't make a difference though.


-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com
 
New Post
2/11/2009 12:53 PM
 

Some follow up on this.  First off I'll say I don't know *how* it was working with FireFox but not IE... seemed like a strange happening.

Anyway, this is where I went to solve it:

  1. I have a staging server so I deployed my changes to the staging server (yeah, I actually had done a straight release from dev to production in this case as it was only a very minor change... I should have gone to staging first).  Everything worked just peachy on the staging server in both IE and FireFox.  Must be a server issue?
  2. Started comparing server configurations and save having Frontpage Extensions enabled on the production server (dunno how that got there, so I turned it off) the configuration looked the same.  One thing triggered in my mind though -- this is an Intranet so both servers are set to use Integrated Windows Authentication and Anonymous Authentication is disabled.  What if, for some weird reason, the AJAX request isn't authenticating?  Still doesn't explain why it worked on the staging server but it was a straw to grasp at.
  3. I go back to the production server and find my service files (.asmx) in the appropriate module folder and through IIS manager I mark those files so they can be accessed Anonymously.  *voila!*, it works.  Just to be clear on this -- staging server is set up exactly the same with exception of marking those ASMX files as accessible anonymously.  WTF?

At this point I don't care why it works now I'm just happy it does.  If anybody has any ideas about it though I'd be more than glad to hear them.


-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com
 
New Post
2/11/2009 5:26 PM
 

Could be caching by the web browser. USing Fiddler probably ignores the browser cache.



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
2/12/2009 9:16 AM
 

Michael Washington wrote

Could be caching by the web browser. USing Fiddler probably ignores the browser cache.

I thought that might have been the case as well and tried forcing a browser refresh (CTRL+F5) but I didn't try manually clearing the cache.  On the other hand I did try this on another computer that had never connected to the tab containing the module and they could replicate the issue.  I'm just happy that using IIS to mark those service files as "Anonymous" worked and I'm not terribly concerned about not having the Windows authentication on it since I'm using an authentication scheme on my webservices similar to the one you (Michael) presented in IWeb and your "Secure AJAX Web Services" tutorials.


-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com
 
New Post
2/12/2009 9:51 AM
 

Hmm I guess it it could be explained that only IE was able to pass authentication through an AJAX call when IIS was not set to allow "Anonymous".

Perhaps it would explain why most people have not run into this issue. Most usually have IIS set to "Anonymous" and when they don't they are usually using IE.



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Strange web service (AJAX) errorStrange web service (AJAX) error


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out