Hello, I wrote a function to programmatically do a Courier Transfer as part of a Workflow. Everything was working fine for a while (using Courier 2.0 dlls) until recently when I recently started receiving this error (below). This still occurs when I updated my dlls to the latest hot fix 2.6.6. Does anyone know how to fix this, or what could be the root cause?
I am still receiving this error. Is there anyway to get the source code to NHiberante so I can look at line 170 and figure out what the null reference is? Per, any ideas?
Server Error in '/' Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
Line 124: Guid providerGuid = new Guid(providerGuidStr);
Line 125: ItemProvider ip = ItemProviderCollection.Instance.GetProvider(providerGuid);
Line 126: sysitem = ItemProviderCollection.Instance.GetProvider(providerGuid).FindSystemItem(itemIdStr); Line 127: PackagingManager instance = PackagingManager.Instance;
Line 128: instance.ClearQueue();
I found the root cause of this issue. Another developer thought it would be a good idea to remove the umbracoDbDSN setting in the web config file to get rid of redundant connection strings. However, NHibernate (via my Courier code), is dependent on this setting being there, which would explain the null reference error. Anyway, I figured it out, thanks anyways.
ERROR importing provider NHibernateProvider
Hello, I wrote a function to programmatically do a Courier Transfer as part of a Workflow. Everything was working fine for a while (using Courier 2.0 dlls) until recently when I recently started receiving this error (below). This still occurs when I updated my dlls to the latest hot fix 2.6.6. Does anyone know how to fix this, or what could be the root cause?
Here is the part of my code that breaks:
ERROR from log_Error.txt
3/6/2012 10:42:13 AM: Can't import provider 'Umbraco.Courier.Persistence.V4.NHibernate.NHibernateProvider'
id: e0474ca8-e73b-11df-9492-0800200c9a66:
System.NullReferenceException: Object reference not set to an instance of an object.
at Umbraco.Courier.Persistence.V4.NHibernate.NHibernateProvider.CreateSessionFactory()
in c:\Program Files (x86)\teamcity\buildAgent\work\51d185ff47ab530d\Umbraco.Courier.Persistence.NHibernate\NHibernate.cs:
line 215
at Umbraco.Courier.Core.ProviderCollection`1.(IEnumerable`1 types)
I am still receiving this error. Is there anyway to get the source code to NHiberante so I can look at line 170 and figure out what the null reference is? Per, any ideas?
Server Error in '/' Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
Line 124: Guid providerGuid = new Guid(providerGuidStr); Line 125: ItemProvider ip = ItemProviderCollection.Instance.GetProvider(providerGuid); Line 126: sysitem = ItemProviderCollection.Instance.GetProvider(providerGuid).FindSystemItem(itemIdStr); Line 127: PackagingManager instance = PackagingManager.Instance; Line 128: instance.ClearQueue();
Source File: C:\Projects\HoosierLotteryWebsite CMS - v4.5.8\HoosierLottery.CourierHelper\CourierTransfer.cs Line: 126
Stack Trace:
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272
I found the root cause of this issue. Another developer thought it would be a good idea to remove the umbracoDbDSN setting in the web config file to get rid of redundant connection strings. However, NHibernate (via my Courier code), is dependent on this setting being there, which would explain the null reference error. Anyway, I figured it out, thanks anyways.
is working on a reply...