Frequent "Error triggering service" messages on SSL based ServiceDesk 7.1 installations
| Article:TECH174932 | | | Created: 2011-11-21 | | | Updated: 2012-07-28 | | | Article URL http://www.symantec.com/docs/TECH174932 |
Problem
In SSL based ServiceDesk 7.1 and 7.1 SP1 installations there are "Error triggering service" messages thrown in the logs every minute.
The functionality impact includes the SD.Email.Monitor schedule not being triggered properly and chat invitation emails not being sent.
Error
(WebServiceScheduleInvokeDelegate)Error triggering service at https://serverFQDN//sd.documenteventlistener/ScheduleInvokeDelegateService.asmx System.Exception: exception invoking method ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at LogicBase.Core.Messaging.MessageExchangeFactory.CreateRemoteTarget(String name, NetworkCredential credential)
at LogicBase.Core.Messaging.MessageExchangeFactory.GetExchangeTarget(String name, Boolean internalRequest, NetworkCredential credential)
at LogicBase.Core.Messaging.MessageExchangeFactory.GetExchange(String name, Boolean internalRequest, NetworkCredential credential)
at LogicBase.Core.Messaging.MessageExchangeFactory.GetExchange(String name, Boolean internalRequest)
at LogicBase.Core.Messaging.MessageExchangeFactory.GetExchange(String name)
at LogicBase.Components.Default.Workflow.AutoStartFromExchangeComponent.StartWorkflow(IData data) in c:\build\projects\MP1_KB54090\components\LogicBase.Components.Default\Workflow\AutoStartFromExchangeWorkflowComponent.cs:line 151
at LogicBase.Core.Models.Workflow.WorkflowServices.CheckAutoStart()
at LogicBase.Core.Models.Workflow.WorkflowManagementService.CheckAutoStart() in c:\build\projects\MP1_KB54090\core\LogicBase.Core.WebServices\WorkflowManagementService.cs:line 133
--- End of inner exception stack trace ---
(WebServiceScheduleInvokeDelegate)Error triggering service at https://serverFQDN//sd.chatinvitationeventlistener/ScheduleInvokeDelegateService.asmx System.Exception: exception invoking method ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at LogicBase.Core.Messaging.MessageExchangeFactory.CreateRemoteTarget(String name, NetworkCredential credential)
at LogicBase.Core.Messaging.MessageExchangeFactory.GetExchangeTarget(String name, Boolean internalRequest, NetworkCredential credential)
at LogicBase.Core.Messaging.MessageExchangeFactory.GetExchange(String name, Boolean internalRequest, NetworkCredential credential)
at LogicBase.Core.Messaging.MessageExchangeFactory.GetExchange(String name, Boolean internalRequest)
at LogicBase.Core.Messaging.MessageExchangeFactory.GetExchange(String name)
at LogicBase.Components.Default.Workflow.AutoStartFromExchangeComponent.StartWorkflow(IData data) in c:\build\projects\MP1_KB54090\components\LogicBase.Components.Default\Workflow\AutoStartFromExchangeWorkflowComponent.cs:line 151
at LogicBase.Core.Models.Workflow.WorkflowServices.CheckAutoStart()
at LogicBase.Core.Models.Workflow.WorkflowManagementService.CheckAutoStart() in c:\build\projects\MP1_KB54090\core\LogicBase.Core.WebServices\WorkflowManagementService.cs:line 133
--- End of inner exception stack trace ---
(WebServiceScheduleInvokeDelegate) Error triggering service at https://serverFQDN//sd.discussioneventlistener/ScheduleInvokeDelegateService.asmx System.Exception: exception invoking method ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at LogicBase.Core.Messaging.MessageExchangeFactory.CreateRemoteTarget(String name, NetworkCredential credential)
at LogicBase.Core.Messaging.MessageExchangeFactory.GetExchangeTarget(String name, Boolean internalRequest, NetworkCredential credential)
at LogicBase.Core.Messaging.MessageExchangeFactory.GetExchange(String name, Boolean internalRequest, NetworkCredential credential)
at LogicBase.Core.Messaging.MessageExchangeFactory.GetExchange(String name, Boolean internalRequest)
at LogicBase.Core.Messaging.MessageExchangeFactory.GetExchange(String name)
at LogicBase.Components.Default.Workflow.AutoStartFromExchangeComponent.StartWorkflow(IData data) in c:\build\projects\MP1_KB54090\components\LogicBase.Components.Default\Workflow\AutoStartFromExchangeWorkflowComponent.cs:line 151
at LogicBase.Core.Models.Workflow.WorkflowServices.CheckAutoStart()
at LogicBase.Core.Models.Workflow.WorkflowManagementService.CheckAutoStart() in c:\build\projects\MP1_KB54090\core\LogicBase.Core.WebServices\WorkflowManagementService.cs:line 133
--- End of inner exception stack trace ---
Environment
ServiceDesk 7.1
Cause
The problem with monitoring project scheduling as well as chat invitations not being sent is caused by the ServiceDesk PostInstallWizard. When installing with SSL, the ServerFQDNWithoutPrefix property in ServiceDeskSettings incorrectly contains the https:// prefix. This defect has been logged with development and is fixed for ServiceDesk 7.1 SP2 release.
Solution
Removing https:// prefix from the ServerFQDNWithoutPrefix property in ServiceDeskSettings (Admin > Data > Application Properties) and restarting the services enables proper scheduling of the Email Monitoring project and chat invitation emails being sent.
Article URL http://www.symantec.com/docs/TECH174932
Terms of use for this information are found in Legal Notices
Thank you.