|
 Posted 3/18/2008 9:39:20 AM |
| | Hi,
we are testing CRM3->CRM4 upgrade in a virtual (vmware) environment and came across an issue with Alerts fro CRM 4.
Symptoms
After a succesfull upgrade to CRM4 and installing c360.Alerts for CRM 4 an Alert can be created and it is created in the database, but when opening a window with the account the associated Alert was made on, the alert window does not show.
In Windows Event Log there is a warning event that looks like the one below.
Resolution
Do not hesitate to contact support@c360.com with this issue!
They have done a great job (again) in resolving this issue for us. 
(Thank you, Tunde!)
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 17-3-2008 16:04:18
Event time (UTC): 17-3-2008 15:04:18
Event ID: a5c013bc63f646099bb72b07e9c0a3db
Event sequence: 11
Event occurrence: 2
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/2/Root/c360-4-128502389624065000
Trust level: Full
Application Virtual Path: /c360
Application Path: C:\Program Files\c360 Solutions\V4\Web\CrmWeb\
Machine name: CRMMACHINENAME
Process information:
Process ID: 184
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: OrganizationNameNullOrEmptyException
Exception message: Request params do not contain organization name
Request information:
Request URL: http://crmmachinename:5555/c360/Alerts/ProcessAlerts.aspx
Request path: /c360/Alerts/ProcessAlerts.aspx
User host address: xxx.xxx.x.x
User: CRMDOMAIN\xxxx
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: True
Stack trace: at c360.Toolkit.MsCrm.Pages.Base.ᜀ()
at c360.Toolkit.MsCrm.Pages.Base..ctor()
at c360.Toolkit.MsCrm.Pages.Area..ctor()
at c360.Alerts.ProcessAlerts..ctor()
at ASP.alerts_processalerts_aspx..ctor()
at __ASP.FastObjectFactory_app_web_junqrtyg.Create_ASP_alerts_processalerts_aspx()
at System.Web.Compilation.BuildResultCompiledType.CreateInstance()
at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Custom event details:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
this message was posted just for documentation purposes! |
| |
|