Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

ComponentArtScript.axd not being served
tgillet1
#1 Posted : Wednesday, 21 December 2011 10:03:56 AM(UTC)
Rank: Newbie

Joined: 21/12/2011(UTC)
Posts: 2

I just transfered my website to a new host and everything appeared to be working fine. However when going to make additions to the GalleryServerPro gallery I found that the buttons for making changes to the gallery weren't showing up. It turns out that ComponentArtScript.axd wasn't be served, which prevented the buttons from appearing. Not being intimately familiar with the namespaces and objects of GSP and other asp libraries I don't know where to look next. Could anyone provide a suggestion?

One questionably related issue has to do with a module called Subgurim Chat. I did not put this site together originally (hoping to hear back from the original designer) so I don't know what it's for, but below the httphandler definition for CopmonentArtScript.ad was one for subgurim_chat/*aspx with type Subgurim.Chat.Procesador. This line simply prevented the site from working so I commented it out and I saw no clear problems from doing so. Its proximity to ComponentArtScript.axd made me wonder if the two might be related though.
Roger Martin
#2 Posted : Wednesday, 21 December 2011 11:46:24 AM(UTC)
Roger Martin

Rank: Administration

Joined: 3/08/2007(UTC)
Posts: 3,300
Location: Fort Atkinson, WI

There are three things I would check:

1. Verify the ComponentArt handlers and modules in web.config are present. Refer to the web.config in the download for a reference.

2. Verify the application pool is running in Integrated Mode (applies only to IIS7+).

3. Investigate whether other handlers or modules might be interfering with ComponentArt. Temporarily disable any 3rd party items in web.config to see if it makes a difference.
Roger Martin
Creator and Lead Developer of Gallery Server Pro
tgillet1
#3 Posted : Friday, 23 December 2011 2:14:59 AM(UTC)
Rank: Newbie

Joined: 21/12/2011(UTC)
Posts: 2

Roger Martin;8097 wrote:
There are three things I would check:

1. Verify the ComponentArt handlers and modules in web.config are present. Refer to the web.config in the download for a reference.

2. Verify the application pool is running in Integrated Mode (applies only to IIS7+).

3. Investigate whether other handlers or modules might be interfering with ComponentArt. Temporarily disable any 3rd party items in web.config to see if it makes a difference.


Thank you very much for responding.

I tried a few of the things you suggested, but I haven't yet found the original web.config to ensure everything is correct. The web.config that I'm using is the same as the one that works perfectly on the old host, so I'm fairly confident the problem is not specifically in web.config. If I were to guess, I would imagine that some file did not get transfered or was corrupted on transfer. I did change the server settings to show complete details for a 500 error (which is what I was getting when trying to reach ComponentArtScript.axd). The error is:
Handler "ComponentArtScriptHandler" has a bad module "ManagedPipelineHandler" in its module list

Does that suggest anything useful to you? I don't see any mention of "ManagedPipelineHandler" in web.config.

Also, I did try commenting out all other handlers and modules to no avail.
Rss Feed  Atom Feed
Users browsing this topic
Guest
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.