Works in debug, not in production (localhost)

I just put together my first Atlas page just to test out a couple components. I've just got a 4-pane accordion control and one collapsible pane control. Both work flawlessly when in debug mode using the built-in web server in VS 2005. But when I try to load the page using just localhost (not deployed, just the same page I am editing in debug) the page loads fine, no errors, it's just that the accordion has the first pane expanded and when I click on the other pane headers nothing happens. The collapsible pane is expanded and doesn't do anything (collapse) when I click on the header div for that. Basically, the page loads but none of the special Atlas functionality is there... I added an .axd mapping to the webapp in IIS, but that didn't fix it. Anything else I can try?

Thanks!

eddie

Hmmm... Still can't get this to work. It's too bad, I'd like to be able to use Atlas stuff in my current projects - doesn't anyone have ANY idea about what might be causing this? I'd be happy to try anything you can think of, just don't know what to do at this point...

Thanks!

eddie

hello.

start by checking the configuration of the application you've configured in IIS. it must be set to asp.net 2.0.

Hi Luis,

Thank you for responding, I was beginning to think I wouldn't get any help with this. I do appreciate it...

I checked and the webapp is set to use ASP.NET 2.0, as are all of the webapps I have on my system right now. It looks like the javascript stuff isn't working, but I get no js errors so I have no idea where to begin debugging this...

Anything else I can try?

Thanks again!

eddie

A little more info I've discovered:

I loaded the site in Firefox, since I have a really nice Javascript debugger in that browser, and I get the following error on EVERY Atlas page, including the AtlasSampleWebsite webapp:

WebForm_InitCallback is not defined

This is the same problem discussed inthis thread, but was never resolved. I haven't been able to find a mention of it anywhere else, but I'm stumped. This is just running on my local IIS instance, so I KNOW the webapps are configured to use asp.net 2.0 (in fact, it's 2.0.5027) but none of the Atlas components I'm using work and this is the only error I'm getting. Anyone know why this function wouldn't be included?

Thanks!

eddie

http://forums.asp.net/thread/1309775.aspx

hello again.

if you can, please do the following:

* open fiddler

* open your page on a browser

* you should see several entries in fiddler. see what's going on with the webresource.axd?... handler request. can you see the jsfiles that should be sent from the server? if you can't then there's something wrong with your configuration. in the past, i've seen this happen due to a.) incorrect version of asp.net (in this case, it's correctly configured) b.) having put an asp.net 2.0 app inside another folder which is configured as a 1.1 asp.net app and c.) are using any anti-viruses or similar programs? I think i've heard someone mention that they couldn't get the js file returned by the webresource.axd handler because those requests (axd extensions) were being blocked by those kind of apps...

Hmmm... could be "c"... I know we have a pretty strict proxy here. They even use Surf Control. I'd be shocked if that was it, but the other two you mentioned aren't the cause in this case.

In Fiddler I get a 404 error for WebResource.axd:

TERSE SUMMARY:GET http://localhost/AtlasSampleWebSite/WebResource.axd?d=qdMG4SiwmEiK1Z5jwwY0sQ2&t=632901232309638044
404 Object Not Found

FULL SUMMARY: # Result Protocol Host URL Body Caching Content-Type User-defined
67 404 HTTP localhost /AtlasSampleWebSite/WebResource.axd?d=qdMG4SiwmEiK1Z5jwwY0sQ2&t=632901232309638044 4,040 text/html

Seems strange that I would get a 404 - usually when the proxy is involved you get a access denied, not a file not found... I guess I'll try uninstalling Atlas and reinstallng from scratch to see if that fixes it...

Eddie

hello.

well, in my experience, if you're getting a 404, that means that the extension is blocked or the app is not using asp.net 2.0. btw, webresource.axd is introduced by asp.net 2.0 (not atlas), so you shouldn't need to reinstall atlas.

Yeah, that didn't help at all. Well, let me ask you this: if I can run the sample website from VS 2005, wouldn't that indicate that the axd entension is not being blocked, but rather there's something not configured properly in my IIS or webapp configuration? I can browse other atlas sites, so it's not like our proxy is blocking axd files. I would think I have something configured incorrectly somewhere, just don't know where else to look...

eddie

hello.

well, if you're using the internal server that comes with vs, then it doesn't count because it serves everythign (even those extensions that aren't configured and that normally would result in error). btw, there's been several posts about similar errors...maybe one of the posts has the correct answer...

Yeah, I finally found the answer inthis post. What a relief... This was driving me nuts. Just turning off the "Verify that file exists" for axd files fixed all my problems.

Thanks for trying to help, I do appreciate it!

eddie

hello.

cool!

btw, have you any idea on how that option got checked?

No, no idea, but I'll be looking for it from now on when I get similar errors!