Hello, we are running Umbraco 4.7 and have migrated to a new server. I rechecked permissions on the server and everything is good. Both the new/old were the same IIS (7.5) and .NET 4.
After copying the site, everything looks fine from the user-end. However, when we create a new page and save/publish it shows a 404 error. If we save and preview, also a 404 error. The page will show up in the menu via macros, but it is not viewable. This error persists after republishing the entire site. This error can only be circumvented by copying an existing page and changing the content.
I'm not sure what else is safe to try. Can I delete everything inside App_Data?
It could be a permissions problem?, maybe the new server won't let the code write/modify to the umbraco.config file in app_data? Check the file permissions and see if they're OK.
Finally figured this out. For some reason after the migration, templates were not being associated with a certain doctype. If you run into a 404 error in the future, take note that it may not be loading the proper template. Manually reassigning the template to the doctype then existing content pages fixed the issue.
404 errors after migration
Hello, we are running Umbraco 4.7 and have migrated to a new server. I rechecked permissions on the server and everything is good. Both the new/old were the same IIS (7.5) and .NET 4.
After copying the site, everything looks fine from the user-end. However, when we create a new page and save/publish it shows a 404 error. If we save and preview, also a 404 error. The page will show up in the menu via macros, but it is not viewable. This error persists after republishing the entire site. This error can only be circumvented by copying an existing page and changing the content.
I'm not sure what else is safe to try. Can I delete everything inside App_Data?
Hi Mike
How about the DB permissions? Did you also recheck those?
/Jan
Hi Mike,
It could be a permissions problem?, maybe the new server won't let the code write/modify to the umbraco.config file in app_data? Check the file permissions and see if they're OK.
Finally figured this out. For some reason after the migration, templates were not being associated with a certain doctype. If you run into a 404 error in the future, take note that it may not be loading the proper template. Manually reassigning the template to the doctype then existing content pages fixed the issue.
@Mike,
Nice one! Glad you got it sorted :)
is working on a reply...