Simple uploads take forever revisited RRS feed

  • Question

  • In the thread,, I described how trying to publish just one file using EW3 took forever.  Some said they had similar problems with EW3 taking forever with the "listing files" thing.  The only real solution for me that was offered was to do a copy and paste when you wanted to transfer files--or simply use an FTP profram like FileZilla. And that is what I have been doing.

    However, I needed to use EW3 today to design a new page.  So I started it up and then sat back and waited 15 minutes for it to finish doing whatever it needed to do to load the site that would contain the page (the site is a bit over 1 GB in size).  Now this site has loaded n less than 5 seconds in the past.

    Well, once loaded, I created my page and then foolishly decided to, instead of doing a copy and paste, uploaded it to the web, I selected it and did a publish.  This file was only 300KB in size.  The program churned away for 20 minutes with me just observing and trying to figure out what was the problem.  I noted that EW3 was taking up 50% of the CPU. The Windows Task Manager said that the program was not responding.  But I let it go a total of 30 minutes before I had Task Manager kill it.

    Then I decided to look at the site in Internet Explorer.  This being one of my older sites, it is under the default IIS web site and can be accessed via http://localhost/thesite.  Well, the first thing I got was an error message which with a little work I figured out meant that ASP.Net was not functioning--and not just for this particular site--for every site under IIS.

    Somehow, the problem with EW3 had caused ASP.Net to not function for all of IIS.  I spent at least an hour getting ASP.Net back to working.

    I then went and deleted the two cache folders associated with EW3.  And when I restarted EW3, it loaded the same site in no more than 5 seconds.

    So, what is going on with EW3?  I did not have these problems with EW2.  And what happens to the Cache files so that deleting them makes the program open sites rapidly again?  Perhaps, I should just delete the cache folders each time I want to use EW3.

    There has to be a solution to this.

    Monday, April 26, 2010 1:00 AM

All replies

  • Sounds like your cache was corrupt. It happens sometime, often enough in all versions of EW (and in FP before it as well as SharePoint Designer) that Steve Easton created a little utility called FPCleaner for the purpose of clearing all the caches.

    I haven't heard of EW 3 or any other version doing anything to corrupt IIS but then I use the testing server for my previewing since I don't have any sites that use classic asp that don't have their own staging server.

    MS MVP Expression Tutorials & Help
    Monday, April 26, 2010 1:28 AM
  • You say you got back to working.  ... How?

    EW doesn't run   Preview in browser can, but that's the development server or your IIS server running, not EW.  So I'm quite puzzled about what EW could do to

    Corrupted caches can happen in any version of EW.  (And as Cheryl says, get FPCleaner in case it does.)

    Monday, April 26, 2010 2:14 AM
  • The first thing you do when ASP.Net stops working is to run aspnet_regiis -i from the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 directory at the command prompt.  But that did not solve the problem, since an attempt to access any .aspx page with http://localhost/thewebsite/pagename.aspx produced an error message.

    After a little trial and error, I added the ASP.Net Machine Account (this was on an XP machine) as a user to the root of the particular site. That got me a bit further.  Then after also adding ASP.Net Machine Account as a user of several other folders at the site that were called by the site’s default.aspx page, I got it back to working for most of the site.  However, there were several other applications at the site that also needed to have the ASP.Net account added as a user to their containing folder.

    I never said EW ran ASP.Net, but it certainly corrupted the ASP.Net setup when it hung while publishing just one file.  Below is the error message in the Event Viewer concerning EW3:

    Hanging application ExpressionWeb.exe, version 3.0.3816.0, hang module hungapp, version, hang address 0x00000000.

    After all the work I had to do in resetting individual permissions on folders, I read that a simple running of “aspnet_regiis -ga ASPNET” from the command prompt might have fixed things.  I found that information in a very long discussion of such problems at


    Monday, April 26, 2010 1:43 PM
  • Well, did EW hang because it was changing user permissions, or did it hang because the permissions were already wrong?  In that long thread you pointed to, you could see several examples of the problem occuring, unrelated to EW.   ... Just saying.
    Monday, April 26, 2010 2:53 PM
  • Everything was fine with the user permissions within an hour before I started EW that day.  I had accessed the local web sites via http://localhost.... with no problem.

    I cannot, of course, prove that EW caused the problem with ASP.Net; only observe that after it hung, the problem existed.


    Monday, April 26, 2010 4:14 PM