Hello,

I've attempted to finalize my upgrade of 2.3.7.5 MSSQL on our windows server.  The site functions flawlessly on my local site, but when I move it onto the server, the site loads and shows that it has been upgraded, all the data is intact, but the stylesheets in the site skin directory and scripts in the clientscript directory are not loading.  When I look at the browser console I'm showing a 500 internal server error on those files, which I've never seen before.  I've checked the directory structure to make sure the files are there, I've checked the permissions and they are in place. The app pool also appears to be correct.

I tried upgrading to your new release 2.3.7.6 with the same results.  It appears to work locally just fine but again the 500 error on the skin files.  Has this happened to anyone before?  Hopefully it's something silly I'm overlooking but I've worked on this for two days without resolving the issue.

@Joe  Audette - I'm sorry I wasn't able to play with your source code prior to your release.  Being out of town for the holidays with my family I've barely had time to test out the sites with the upgrade I'd been working on and attempt to deploy the upgrade before returning to work on Monday.

Best,

Beth

Yeah the 500 error is generic.  I've enabled db logging but am not seeing meaningful errors.  There is this: 

Referrer(none) useragent System.NullReferenceException: Object reference not set to an instance of an object.
at Brettle.Web.NeatUpload.Internal.Module.Config.get_UseHttpModule()
at Brettle.Web.NeatUpload.UploadHttpModule.Application_EndRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

I didn't see any meaningful errors in the system logs on the server either.  I've updated the skins referencing your "Upgrading Info for skins" and all the skins are working locally.  All I did was take the working installation and move it onto the server. I think the theme.skin is loading because it's not a listed file in the Chrome Console (the errors are across Chrome, IE and FF) ... actually i guess that would be incorporated on the server ... so how would I know then?  I'll email you a screenshot of the files getting the error as there are quite a few of them.  They are the specific css files within the skin directory but there are also js files in the clientscript directory not loading.

It occurred to me that my skin wasn't in the Web->Data->skins directory so I added it just now, touched the web.config and restarted the application in IIS but that doesn't seem to have made a difference.

Any advice you have to offer would be much appreciated.

~ Beth

Hi Joe,

Happy New Year! 

I checked for runAllManagedModulesForAllRequests="true" and it is present. I don't have any custom modules. I am accessing the site by IP address (not just the styles) since I don't have an extra test domain on my server to use. I had the CombineCss value set to false in the user.config so I could test out skin changes ... I changed it to true, touched the web.config, but that hasn't helped with the files loading.

The issue is definitely somewhere in the web.config.  When I put the older web.config in place on the server (pointing to the new db in the user.config) the upgraded site loads fine.  When I switch to the web.config that shipped with the most recent version, the  stylesheets and clientscript files don't load.

Any ideas for what to look for in the web.config?  I'm comparing them line by line but quite a few things are different and I can see that you've pretty much rewritten it over time.

Thanks,

Beth

I commented out the line which caused a 500 error for the site. I uncommented it and set it to false and the site loaded but with the skins still throwing an error.

~ Beth

I commented out that line in the web.config but it didn't make a difference.  We don't have PHP installed on the server.  The app pool is running in 4.0 integrated in IIS 7 on a Windows Server 2008.

~ Beth

D'oh!  I tried using jquery-ui1 straight from the Data/skins directory and am still getting the 500 errors on the skin files.  This is a sneaky bug! ~ B