Is there a particular error that you are getting back?
It could be that the directory you moved it into is not marked as an "application" within IIS -- and so the Atlas assemblies aren't being found. To fix this go into the IIS admin tool and make sure the directory the \bin directory is underneath is an application (and not just a directory or virtual directory).
Hope this helps,
Scott
There was no error. I just ran my application and nothing happened when I clicked "No" on one of my radio buttons. Normally a panel will appear with a label and textbox. Also I checked in IIS and the site is set up as a website. Nothing was changed in the website properties in IIS except for the path. The application was under the Inetpub directory and worked fine, then it stopped working when I moved it to the wwwroot directory? I moved the application to the wwwroot so that all the paths would work on both the devel machine and the server.
Did you remember to upload the Atlas .dll into the /bin directory?
That's just the thing. I did and I have not changed the contents of the Application on the server. So I'm guessing it's a problem with the way it's set up on the server. It's just strange because the application runs so it would seem like it's set up right. Another thing I use wwHoverPanels and that control is still working fine as well. Only atlas is not working right now.
These are the controls in my bin on the server.
\Bin\AtlasControlToolkit.dll
\Bin\AtlasControlToolkit.pdb
\Bin\Microsoft.AtlasControlExtender.dll
\Bin\Microsoft.Web.Atlas.dll
\Bin\wwHoverPanel.dll
\Bin\wwHoverPanel.pdb
Hmmm... I don't know. Looks like you've got everything there.
I wonder what about the mapping to the "asbx" extension that the Atlas installation does... or if the "c:\Program Files\Microsoft ASP.NET\Atlas\v2.0.50727\Atlas\ScriptLibrary" needs to exist on the remote server
I have yet to see a good and detailed explaination on folding in Atlas to an existing application and what one needs to do to the remote server for the asbx mapping and the ScriptLibrary itself
hello guys.
well, i'd also check if IIS is set to use the correct version of ASP.NET.
MorningZ, you don't need those files on the server because if you're using the server side appoach (ex.: updatepanels, scriptmanager, etc), the atlas dll already has those files embedded on them.
so, to run atlas on a server, you'll need:
1. web.config correctly set up
2. atlas dll on the bin folder
3. IIS correctly set up to ASP.NET 2.0
1. web.config correctly set up
2. atlas dll on the bin folder
3. IIS correctly set up to ASP.NET 2.0
I had Atlas working on the server on the Inetpub directory so I know the web.config was set up correctly and that the Atlas.dll was in the Bin. I've checked that the new directory under wwwroot that I moved the Application has Asp.net 2.0 set up in IIS so that's not the problem for me either.
hello.
hum...then i'd start by using fiddler to see if there's any content being exchanged between the client and server...maybe this will give you a clue on what's wrong.
I ran Fiddler and this is some of the information I got back when I clicked on the radio button if that helps-
Below is the information provided for the page URL:
TextViewScriptManager1=UpdatePanel1&__EVENTTARGET=radLicensed_In_US%241&__EVENTARGUMENT=
&__LASTFOCUS=&__VIEWSTATE=%2FwEPDwUKMTU5MDU2MTYyOQ9kFgICAw9kFggCAw9kFgJmD2QWAgI
DD2QWAgIBDxBkZBYBAgFkAgsPZBYCZg9kFgICAQ9kFgICAw8QZGQWAGQCDQ8PFgIeB1Zpc2libGVoZG
QCDw9kFgJmD2QWAgIBDw8WAh8AaGRkZExr%2BAblTGj7AwZtCZY%2BVe2yZWTF&ddlRvUse=Select&
rad150DaysUse=No&radAccess_Other_Vehicles=Yes&radClaims_3Years=No&ddlTickets_3
Years=None&radLicensed_In_US=No&__EVENTVALIDATION=%2FwEWGgLPxPXoAwLJv6f8DgLp89
axDwLsyd%2BlBALB59W9BgLlkbfiDQKNpNf%2FBwL%2Bn4b6BALY28joAwKYqfgrAvrG1sQMAojc5ro
GAsiu1vkFAqrB%2BJYJAujBmt8FAqizqpwGAsrchPMKAonQ5PwKArmRw%2BgFArbI4soGAoWEwbIDAr
jvt4wLApT%2F2YkFAtSN6coGArbix6UKArXh844KPZqmTa%2FBKTrf0o4hC%2ByHNXhZVL4%3D&
Raw
POST /Quote/Q04_Questions.aspx HTTP/1.1
Accept: */*
Accept-Language: en-us
Referer: -
che-Control: no-cache
Content-Type: application/x-www-form-urlencoded
delta: true
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Host: -
Content-Length: 706
Proxy-Connection: Keep-Alive
Pragma: no-cache
Cookie: ASP.NET_SessionId=jcuvoymc12laoq45dm21bp55
Followed by these four Url's:
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent
http://www.w3.org/TR/xhtml1/DTD/xhtml-symbol.ent
http://www.w3.org/TR/xhtml1/DTD/xhtml-special.ent
hello again.
what about the response? are you getting anything from the server?
These are the responses I get back from the server -
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent
http://www.w3.org/TR/xhtml1/DTD/xhtml-symbol.ent
http://www.w3.org/TR/xhtml1/DTD/xhtml-special.ent
This is the response I get when it's working -
GET /RvInsurance/WebResource.axd?d=QLQAXjHhrByUMUFZNrkhfw2 HTTP/1.1
And here are the responses I get on the server -
GET /TR/xhtml1/DTD/xhtml1-transitional.dtd HTTP/1.1
GET /TR/xhtml1/DTD/xhtml-lat1.ent HTTP/1.1
GET /TR/xhtml1/DTD/xhtml-symbol.ent HTTP/1.1
GET /TR/xhtml1/DTD/xhtml-special.ent HTTP/1.1
hello again...
not really what i want to see...
on fiddler, when you select a line, the right screen is divided in 2: the top represents the request and the bottom, the response.
i'd like to see the response sent by the server (headers and textview) to the atlas request. thanks.
No comments:
Post a Comment