installation issue .ashx

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
9/9/2009 8:31:05 PM
Gravatar
Total Posts 4

installation issue .ashx

 

I am trying to setup Mojoportal on a new host.  They have been helpful in getting full trust and permissions set properly, but am still being plagued by a strange issue.  I have spoken to the host and they say that the .ashx extension is configured properly  but I am getting the following error in the logs:

   2009-09-09 18:22:29,937 ERROR mojoPortal.Web.Global - 173.50.150.159-af-ZA - /Data/Sites/1/skins/graformix-orange/csshandler.ashx?skin=graformix-orange System.Web.HttpException: The file '/Data/Sites/1/skins/graformix-orange/csshandler.ashx' does not exist. at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.SimpleHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) at System.Web.UI.SimpleHandlerFactory.GetHandler(HttpContext context, String requestType, String virtualPath, String path) at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 2009-09-09 18:27:37,187 INFO mojoPortal.Web.Global - Global.asax.cs Application_End

This is causing the site to show up without styles.  I am running IIS7 in Integrated mode.  MS SQL is the backend and seems to be working fine.  I checked the skins directory in the sites folder and it looks to be intact.  The other issue I am seeing is that it is taking the admin@admin.com admin login, but then saying I am not logged in.  Anything sounding familiar to anyone?  I am running with the latest posted codeplex code.

 

Thanks,

Nathan

9/9/2009 8:34:08 PM
Gravatar
Total Posts 4

Re: installation issue .ashx

FYI I do get a 404 trying to browse directly to the .ashx file.  Also This is a new install, so web.config should be OOTB.

 

Thanks for any assistance!

 

--Nathan

9/10/2009 2:12:56 AM
Gravatar
Total Posts 4

Re: installation issue .ashx

Another added note, the robots.ashx file is served properly, so it does not appear to be an extension problem.

9/10/2009 5:47:37 AM
Gravatar
Total Posts 18439

Re: installation issue .ashx

Hi Nathan,

The difference is that robots.ashx is a physical file but csshandler.ashx is not, it is declared in Web.config in 2 places, first in the system.web.handlers section which is used in IIS 6 or IIS 7 Classic mode

<add verb="*" path="*csshandler.ashx" type="mojoPortal.Web.UI.CssHandler, mojoPortal.Web" />

and also further down it is declared in the system.webserver.handlers section used in IIS 7 Integrated mode

<add name="CssHandler" verb="*" path="*csshandler.ashx" type="mojoPortal.Web.UI.CssHandler, mojoPortal.Web" preCondition="integratedMode" />

It should work out of the box unless they have it configured somehow to prevent registering handlers this way.

Hope it helps,

Joe

9/11/2009 12:53:53 AM
Gravatar
Total Posts 4

Re: installation issue .ashx

They looked at it again and figured out it was some sort of permissions issue on their side.  Thanks for the help!

You must sign in to post in the forums. This thread is closed to new posts.