After Uploading the Master Page the whole site is not finding any of it's pages

Discussion in 'ASP.NET / ASP.NET Core' started by dwhite, Jul 21, 2007.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. Hi All,

    Is this just me or does anyone else experience this ?

    Only after uploading a master page (which contains my aspnet menu, the one that you have in Visual Web Developer), the whole website sort of goes bonkers for a while.

    The main url loads, but the pages that the menus lead to take upwards of 20 minutes to "re-synch".
    In the meantime, they are simply not there (or can't be found anyway).

    My error is this: GenericErrorPage.htm?aspxerrorpath=/(filename).aspx ....but that's because I have a custom 404 page that DOES show with each error.

    Anyway - slowly but surely the site comes back, until the next time I re-upload a master page...

    Any ideas ?
     
  2. Well, now it's just not coming back on most of the pages..

    I took off the 404 message so I could see it, and it's just showing this...

    The system cannot find the file specified.


    But I KNOW they are up there - I can see them in VS...





    Does anyone else experience ?
    It was fine until I re-uploaded the MasterPage.master


    Thanks :-(((
     
  3. Well...they are all back now...
    But it took almost an hour this time...

    Any ideas from the DASP crew ?
    Is there something I should be aware of that I'm doing wrongthat would cause this ?

    Thanks,

    Dave
     
  4. Hard to say exactly what was going on with your web application without experiencing it first hand. Can you tell us if this is a new discountasp account?
     
  5. Hi,

    Yes , about a month old.
    Dave
     
  6. "The application may have been previously compiled and then an update was made which is not compiled."

    This is correct - that did happen - newbie error :)

    "If you have a backup of your site, try deleting everything, and reupload. Stick to one publishing method."

    My publishing method is through copy web in Visual Studio - but there is no backup, haven't done one yet..

    So, I'll guess I'll have to live with this as any backup will be of the current website.

    Thanks for the insight - I think you nailed it...

    Dave
     
  7. I've seen this weird type of behaviour before, but can't remember exactly what the cause was. Try the following:

    1. The temporary ASP.NET cache for the site somehow got corrupted. Before uploading changes, try stopping the web site and recycle (you can do this from the IIS Manager of your hosting control panel). After uploading, start the site back up.

    2. The application may have been previously compiled and then an update was made which is not compiled. If you have a backup of your site, try deleting everything, and reupload. Stick to one publishing method.







    Aristotle

    DiscountASP.NET
    www.DiscountASP.NET
     
  8. I ran a test tonight...

    Changed a menu item and uploaded the master.page as the menu is in the master page....

    Now 50 minutes since I did that - getting 404 errors randomly on pages - sometimes the same, sometimes not - those folders that require authentication (you must log in to access the pages) all work fine - every page pope right up, and the log-in name is working and visible..

    Log out, and the same pages that 404 are still doing it.

    I did restart the website both before and after the master.page was loaded. I did recycle the application pool.

    So...it appears I must update the master page very infrequently !!

    Just an FYI in case anyone else is experiencing the same.. I wouild be so curious to knwo if anyone is experiencing this .

    Dave
     
  9. Update... Over an hour later, and still the same problem...
     
  10. Well, it's been all night now--I think it's stuck..
    Maybe I need to delete the entire masterpage and then reload it rather than write over it ?


    Any ideas would be definitely appreciated
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page