can not get AJAX to work on sever, please help

[simon]

hello,

I have a server set up on my local (home) network and can not get an
ajax application to run on the box. it works fine on our
developement server and also works fine locally.

I copied the application to the server, setup the website, installed
the ajax extensions, also loaded/enabled front end extensions so i
could load the site in visual studio 2005. when i attempt to run the
site, either from the server or from another pc on my home network, it
barely comes up. it is insanely slow. literally will take about 5
minutes for the starting page to finish. and the page is not that big
at all. what is seems to go the slowest on are the graphics, but
everything is very very slow regardless if there are graphics or not
(but the graphics do come up last and take the longest).

i have the same site, but without ajax, and that comes up in a second.
i tried every server/web.config change i could think of and just can
not get it to change its behavior. i'm hoping there is something i'm
missing as it is impossible to work with the application.

I even tried loading a simple do-nothing ajax website to the server.
basically a page that has a time display and a button to click that
will display another time stamp in an update panel. that also takes
forever to load and the update in the panel of the new time does not
work. there is another ajax confirmaion button on the page that works
with an input text box, you enter something in the box, click the
button, ajax pop-up asks to confirm, if you answer yes it will take
your input and show it in a label on the page. that part work, but is
very slow to repost the screen. point being i have 2 simple ajax test
controls on a page and that page is incredibly slow loading/running as
well, plus the update panel isn't working

the server is windows 2003 running IIS 6. i do not know where else to
change or try anything and was hoping someone could give me some
suggestions. i do have this in the web.config as i saw these entries
mentioned in other posts,

<compilation debug="false">

<system.web.extensions>
<scripting>
<scriptResourceHandler enableCompression="true"
enableCaching="true"/>
</scripting>
</system.web.extensions>

if you have any suggestions as to why any ajax .net site is so slow
in response (as well as update panels don't seem to work at all), i
would really appreciate it. i'm out of ideas as to what to try next

thanks very much

[RhythmAddict]

On Apr 10, 5:15 pm, simon <[e-mail]:

hello,

I have a server set up on my local (home) network and can not get an
ajax application to run on the box. it works fine on our
developement server and also works fine locally.

I copied the application to the server, setup the website, installed
the ajax extensions, also loaded/enabled front end extensions so i
could load the site in visual studio 2005. when i attempt to run the
site, either from the server or from another pc on my home network, it
barely comes up. it is insanely slow. literally will take about 5
minutes for the starting page to finish. and the page is not that big
at all. what is seems to go the slowest on are the graphics, but
everything is very very slow regardless if there are graphics or not
(but the graphics do come up last and take the longest).

i have the same site, but without ajax, and that comes up in a second.
i tried every server/web.config change i could think of and just can
not get it to change its behavior. i'm hoping there is something i'm
missing as it is impossible to work with the application.

I even tried loading a simple do-nothing ajax website to the server.
basically a page that has a time display and a button to click that
will display another time stamp in an update panel. that also takes
forever to load and the update in the panel of the new time does not
work. there is another ajax confirmaion button on the page that works
with an input text box, you enter something in the box, click the
button, ajax pop-up asks to confirm, if you answer yes it will take
your input and show it in a label on the page. that part work, but is
very slow to repost the screen. point being i have 2 simple ajax test
controls on a page and that page is incredibly slow loading/running as
well, plus the update panel isn't working

the server is windows 2003 running IIS 6. i do not know where else to
change or try anything and was hoping someone could give me some
suggestions. i do have this in the web.config as i saw these entries
mentioned in other posts,

<compilation debug="false">

<system.web.extensions>
<scripting>
<scriptResourceHandler enableCompression="true"
enableCaching="true"/>
</scripting>
</system.web.extensions>

if you have any suggestions as to why any ajax .net site is so slow
in response (as well as update panels don't seem to work at all), i
would really appreciate it. i'm out of ideas as to what to try next

thanks very much

You may have tried this but...make sure you install the Ajax control
toolkit as well as the extensions, as they aren't quite the same
thing. (one is update panel and one is well...everything else. I
forgot which is which, though :) )

[simon]

thanks for taking time to reply.
i used the toolkit to build some of the apps, and have it installed on
my laptop where i do my coding, but there is nothing to install on the
server (please correct me if i'm wrong). the toolkit is a bunch of
dll's to use/reference when creating sites. those dll's are packaged
with the site source and therefore on the server.

the sites do "kinda" work, more test show the pages do render, just at
an unusablly slow rate. the simplest pages can take 1-4 minutes to
come up. and it is only the ajax enabled sites. other sites on the
box come up instantly as they should.

have no idea what or where the bottleneck could be and desperate for
some ideas.
thanks again.

On Thu, 10 Apr 2008 15:15:51 -0700 (PDT), RhythmAddict
<sa**********@gmail.comwrote:

>
You may have tried this but...make sure you install the Ajax control
toolkit as well as the extensions, as they aren't quite the same
thing. (one is update panel and one is well...everything else. I
forgot which is which, though :) )

[RhythmAddict]

On Apr 10, 11:27 pm, simon <[e-mail]:

thanks for taking time to reply.
i used the toolkit to build some of the apps, and have it installed on
my laptop where i do my coding, but there is nothing to install on the
server (please correct me if i'm wrong). the toolkit is a bunch of
dll's to use/reference when creating sites. those dll's are packaged
with the site source and therefore on the server.

the sites do "kinda" work, more test show the pages do render, just at
an unusablly slow rate. the simplest pages can take 1-4 minutes to
come up. and it is only the ajax enabled sites. other sites on the
box come up instantly as they should.

have no idea what or where the bottleneck could be and desperate for
some ideas.
thanks again.

On Thu, 10 Apr 2008 15:15:51 -0700 (PDT), RhythmAddict

<[e-mail]:

You may have tried this but...make sure you install the Ajax control
toolkit as well as the extensions, as they aren't quite the same
thing. (one is update panel and one is well...everything else. I
forgot which is which, though :) )

Simon,
Fully understand that the DLL's in the application's Bin should do
it. There is quite a lengthy thread on http://forums.asp.net/p/1054927/1745730.aspx
about the issue (working on dev but not stg/prd) The suggestion there
seems to be getting the RTM build (I'm not sure if you have this or a
diff version - it can be obtained here :
http://www.asp.net/AJAX/documentatio...RC_to_RTM.aspx)

Honestly, if it's easy enough to do, I would try installing the
current asp.net ajax version that _you're_ using on the server just
for piece of mind. If you have access to the server and don't have to
go through too many hoops...that is. Otherwise you may wanna check
out the rest of that thread.

Cheers,
S

[simon]

thanks very much for the reply and links. will be trying what they
mentioned tonight. appreciate it very much. hopefully will be able
to post back with good news.
On Fri, 11 Apr 2008 09:18:32 -0700 (PDT), RhythmAddict
<sa**********@gmail.comwrote:

>On Apr 10, 11:27 pm, simon <[e-mail]:

>thanks for taking time to reply.
i used the toolkit to build some of the apps, and have it installed on
my laptop where i do my coding, but there is nothing to install on the
server (please correct me if i'm wrong). the toolkit is a bunch of
dll's to use/reference when creating sites. those dll's are packaged
with the site source and therefore on the server.

the sites do "kinda" work, more test show the pages do render, just at
an unusablly slow rate. the simplest pages can take 1-4 minutes to
come up. and it is only the ajax enabled sites. other sites on the
box come up instantly as they should.

have no idea what or where the bottleneck could be and desperate for
some ideas.
thanks again.

On Thu, 10 Apr 2008 15:15:51 -0700 (PDT), RhythmAddict

<[e-mail]:

>You may have tried this but...make sure you install the Ajax control
toolkit as well as the extensions, as they aren't quite the same
thing. (one is update panel and one is well...everything else. I
forgot which is which, though :) )

Simon,
Fully understand that the DLL's in the application's Bin should do
it. There is quite a lengthy thread on http://forums.asp.net/p/1054927/1745730.aspx
about the issue (working on dev but not stg/prd) The suggestion there
seems to be getting the RTM build (I'm not sure if you have this or a
diff version - it can be obtained here :
http://www.asp.net/AJAX/documentatio...RC_to_RTM.aspx)

Honestly, if it's easy enough to do, I would try installing the
current asp.net ajax version that _you're_ using on the server just
for piece of mind. If you have access to the server and don't have to
go through too many hoops...that is. Otherwise you may wanna check
out the rest of that thread.

Cheers,
S

[simon]

On Fri, 11 Apr 2008 09:18:32 -0700 (PDT), RhythmAddict
<sa**********@gmail.comwrote:

>On Apr 10, 11:27 pm, simon <[e-mail]:

>thanks for taking time to reply.
i used the toolkit to build some of the apps, and have it installed on
my laptop where i do my coding, but there is nothing to install on the
server (please correct me if i'm wrong). the toolkit is a bunch of
dll's to use/reference when creating sites. those dll's are packaged
with the site source and therefore on the server.

the sites do "kinda" work, more test show the pages do render, just at
an unusablly slow rate. the simplest pages can take 1-4 minutes to
come up. and it is only the ajax enabled sites. other sites on the
box come up instantly as they should.

have no idea what or where the bottleneck could be and desperate for
some ideas.
thanks again.

On Thu, 10 Apr 2008 15:15:51 -0700 (PDT), RhythmAddict

<[e-mail]:

>You may have tried this but...make sure you install the Ajax control
toolkit as well as the extensions, as they aren't quite the same
thing. (one is update panel and one is well...everything else. I
forgot which is which, though :) )

Simon,
Fully understand that the DLL's in the application's Bin should do
it. There is quite a lengthy thread on http://forums.asp.net/p/1054927/1745730.aspx
about the issue (working on dev but not stg/prd) The suggestion there
seems to be getting the RTM build (I'm not sure if you have this or a
diff version - it can be obtained here :
http://www.asp.net/AJAX/documentatio...RC_to_RTM.aspx)

Honestly, if it's easy enough to do, I would try installing the
current asp.net ajax version that _you're_ using on the server just
for piece of mind. If you have access to the server and don't have to
go through too many hoops...that is. Otherwise you may wanna check
out the rest of that thread.

Cheers,
S

thanks again for the replies. read tru the thread over the weekend
and their issue was that they were having an error thrown when moving
their ajax site to the prod server (win 2k3), but that was an issue
with a beta release of ajax extensions.
unfortunately i'm up to date on the release and i'm not getting any
errors just very very slow processing (where it looks as if the pages
don't work).
i did get a tip from someone to install HttpWatch to monitor where the
slow down occurs (if possible) which may uncover where the issue is
(hopefully!)

back to the drawing board....