I recently moved a number of sites from Server 2003 to 2008 and started experiencing the "Image Processor: No component detected" issue that others have had.

I've read a number of thread from developers having similar issues with the new Windows Server 2008 security structure but haven't been able to solve this issue:

www.dmxzone.com/support/12607/topic/48329/
www.dmxzone.com/forum/topic/44029/
www.dmxzone.com/forum/topic/41453/
www.dmxzone.com/support/12064/topic/54533/

...and I read this page as well and tried some of the suggestions:

www.iis.net/learn/manage/configuring-security/application-pool-identities

...but I'm either not following the instructions correctly or it isn't working.

I've included debug information below and I'm hoping to get a few suggestions on things to try before I give up and move to a different architecture.

Thanks for your help.

Jeff

-----------------------------

Server Information
Info Value
Server Name www.<snip>.com
Server IP Address <snip>
Server Port 80
Server Software Microsoft-IIS/7.5
Operating System
Script Engine VBScript (version: 5.8.17910)
Response Object
Attribute Value
Response.Buffer True
Response.CacheControl private
Response.Charset
Response.ContentType text/html
Response.Expires
Response.ExpiresAbsolute 12:00:00 AM
Response.isClientConnected True
Response.Status 200 OK
Server Object
Attribute Value
Server.ScriptTimeout 90
Session Object
Attribute Value
Session.CodePage 1252
Session.LCID 1033
Session.SessionID 830091621
Session.TimeOut 20
Installed Components
Component Version Resize Crop RotateLeft RotateRight Sharpen Blur GrayScale AddText AddWatermark AddTiledWatermark AddStretchedWatermark FlipHorizontal FlipVertical
Image Processor 2.5.6 debug
Url to ASP.NET service www.<snip>:80/portal/admin/../../ScriptLibrary/sip_service.asmx
Error
Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

Error creating object Msxml2.ServerXMLHTTP.5.0 006~ASP 0177~Server.CreateObject Failed~800401f3
Error creating object Msxml2.ServerXMLHTTP.4.0 006~ASP 0177~Server.CreateObject Failed~800401f3
Error
Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

Error
Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

Error
Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

Error
Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

Error creating object AspNet
Error creating object GraphicsMill 006~ASP 0177~Server.CreateObject Failed~800401f3
Error creating objectImageX 006~ASP 0177~Server.CreateObject Failed~800401f3
Error creating object ShotGraph 006~ASP 0177~Server.CreateObject Failed~800401f3
Error creating object ImgWriter
Error creating object Persits AspJpeg 006~ASP 0177~Server.CreateObject Failed~800401f3
Error creating object AspImage 006~ASP 0177~Server.CreateObject Failed~800401f3
Error creating object SmartImage 006~ASP 0177~Server.CreateObject Failed~800401f3
Error creating object PictureProcessor 006~ASP 0177~Server.CreateObject Failed~800401f3
Error creating object AspThumb 006~ASP 0177~Server.CreateObject Failed~800401f3
Image Processor: No component detected
There is no supported component detected.

...and here's my detect.asp output:

Smart Image Processor Components

Detecting Components:

NOT FOUND: Smart Image Processor Own component
NOT FOUND: ASPJpeg Server Component
NOT FOUND: ASPImage Server Component
NOT FOUND: ASPSmartImage Server Component
NOT FOUND: ImgWriter Server Component
NOT FOUND: AspThumb Server Component
Object Msxml2.ServerXMLHTTP.6.0 created
FOUND: ASP.NET Msxml2.ServerXMLHTTP.6.0
Smart Image Processor can be fully used on this server!


-------------------

My /bin has exec privs.

Thoughts?

Hi Jeff,

check this topic for common causes of the problem - is usually IIS permissions issue:

forums.iis.net/t/1164511.aspx?Can+t+Create+Object+MSXML2+ServerXMLHTTP

Greetings,
George

Thanks for the link George, but it didn't help.

I followed the guidance in that article (I'm not sure that MSXML2.ServerXMLHTTP is the issue--but tried anyway). I found teh CLSID valuein my registry, looked up the associated file (in this case msxml3.dll) and gave it permissions but it didn't help in any way. I even tried giving it everyone/full permissions, but that didn't work either, so I returned the permissions to their original values.

If detect.asp says that "Smart Image Processor can be fully used on this server!" and debug says "Image Processor: No component detected There is no supported component detected." where does the problem lie?

Are there insufficient privledges on /Bin/DMXzone.ImageProcessor.dll?

Should there be a different image processing tool installed on the server?

Is there an issue with the default file permissions on Server2008 R2?

Is this an IIS config issue?

Can you give me a little more direction?

I'm willing to do the work--but I'm not sure the link that was provided is related to the issue (or if it is, I'm not sure how to tie it back to a permission issue with ImageProcessor.dll).

Can I pay for support? I can't seem to solve this via the forums.

Anybody?

I spent months trying to solve this and ultimately discovered that adding the following line to the web.config (in the website's root dir) fixed it:

<system.web>
<customErrors mode="Off"/>

<webServices>
<protocols>
<add name="HttpGet"/>
<add name="HttpPost"/>
</protocols>
</webServices>

</system.web>