Using Umbraco 7.2.0 and 2.11 I am seeing this error during direct deploy: Could not load type 'Umbraco.Courier.UI.Pages.status'.
There is another thread about this that is mostly unresolved involving reverting to version 2.5 and changing versions of Log4net. That is not really a viable option for us.
The hotfix is the upgrade. So just copy the files from the hotfix zip to the respective locations in your instance making sure to also merge the courier.config files.
Paul, so the latest hot fix was installed. Unfortunately that did not resolve the issues and introduced several others. on Direct Deploy we still see the "Could not load type 'Umbraco.Courier.UI.Pages.status'." errors.
In addition, we are also seeing now configuration errors during transfer and extract "An invalid or incomplete configuration was used while creating a session factory" The error is referring to hard coded paths like "f:\TeamCity\buildAgent... " which seems to be part of the code and nothing related to our environment.
Could you send through repro steps, your exact configuration, and the umbraco and courier trace logs from your umbraco.com account using the courier support link?
Sounds like you have something else going on.
Also, one approach that works really well is to setup a fresh umbraco install, then install courier using all the defaults, then verify everything works - which it should. Then it's just a matter of looking at the diff between the fresh environment and your current environment. That has proven very effective on numerous troubleshooting episodes recently.
Could not load type 'Umbraco.Courier.UI.Pages.status' on Direct Deploy
Using Umbraco 7.2.0 and 2.11 I am seeing this error during direct deploy: Could not load type 'Umbraco.Courier.UI.Pages.status'.
There is another thread about this that is mostly unresolved involving reverting to version 2.5 and changing versions of Log4net. That is not really a viable option for us.
Is there no available fix for this?
Please advise with thanks!
Jamie
@Jamie -
You should definitely update to the 2.50.latest hotfix. As of today we recommend the one here (Umbraco.Courier.Hotfix.v2.50.4.187.zip):
http://nightly.umbraco.org/UmbracoCourier/Umbraco%207/Release/
It's almost identical to the 2.50.1 release on Our, but as you already have courier installed, use the hotfix archives.
Great Paul thanks! We will give this a shot. Hope all is well, its been a while since the Vegas Master Class.
Paul will that hotfix work for 2.11 or should we upgrade that?
@Jamie
The hotfix is the upgrade. So just copy the files from the hotfix zip to the respective locations in your instance making sure to also merge the courier.config files.
Paul, so the latest hot fix was installed. Unfortunately that did not resolve the issues and introduced several others. on Direct Deploy we still see the "Could not load type 'Umbraco.Courier.UI.Pages.status'." errors.
In addition, we are also seeing now configuration errors during transfer and extract "An invalid or incomplete configuration was used while creating a session factory" The error is referring to hard coded paths like "f:\TeamCity\buildAgent... " which seems to be part of the code and nothing related to our environment.
Any ideas?
Cheers,
Jamie
@Jamie
Could you send through repro steps, your exact configuration, and the umbraco and courier trace logs from your umbraco.com account using the courier support link?
Sounds like you have something else going on.
Also, one approach that works really well is to setup a fresh umbraco install, then install courier using all the defaults, then verify everything works - which it should. Then it's just a matter of looking at the diff between the fresh environment and your current environment. That has proven very effective on numerous troubleshooting episodes recently.
@Paul, the courier support link on umbraco.com 404's. It's http://umbraco.com/help-and-support/customer-area/courier-support-and-download
any idea on where I can request support directly?
Thanks,
Jamie
@Jamie -
There was a site update last night and just ironing out the kinks now. You can always submit a ticket via http://support.umbraco.com
is working on a reply...