ServiceDesk error
I have found the error in the "Altiris Workflow Designer Configuration and Logging Tool". There is one:
(WebServiceScheduleInvokeDelegate) Error triggering service at http://altirissd.vtb.com.ge//sd.accounteventlistener/ScheduleInvokeDelegateService.asmx System.Exception: exception invoking method ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.(removed by a.n.).147:11434
Server stack trace:
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(EndPoint ipEndPoint)
at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)
at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)
at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at LogicBase.Core.Messaging.Remoting.MessagingServer.GetCount(String session, String exchangeName)
at LogicBase.Core.Messaging.RemoteServerImpl.get_Count()
at LogicBase.Components.Default.Workflow.AutoStartFromExchangeComponent.StartWorkflow(IData data)
at LogicBase.Core.Models.Workflow.WorkflowManagementServiceImpl.CheckAutoStart()
at LogicBase.Core.Models.Workflow.WorkflowManagementService.CheckAutoStart()
--- End of inner exception stack trace ---
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at WorkflowManagementService.CheckAutoStart()
--- End of inner exception stack trace ---
at LogicBase.Framework.DynamicProxy.InvokeMethod(String MethodName, Object[] parameters)
at LogicBase.ServerExtensions.Core.WSInvokerDelegate.DoInvoke()
As I got, this error appeared when SD tried to ask something from NS. May anybody help me to diagnose problem more close? How to fix this?
Comments
This can safely be ignored
Common Windows Event Errors
http://www.symantec.com/docs/TECH127583
Quoting that article:
The reason for these to occur is because most of the Servicedesk components(Processes) are set to auto invoke or Pre initialize. This allows Servicedesk processes to move quicker for the users. The way Auto Invoke or Pre Initialize works in the .net world is they load into memory. Normally these processes require some sort of input to actually run. Durning Auto Invoke or Pre Initialize no data is passed as they are not running a real process.
are you sure that the sevice
are you sure that the sevice desk computer is in the admin group as computer? I hada error really close to that until I added the SErvice Desk computer to the admin group
17A. Add the ServiceDesk Computer Administrators group (pg 54 ServiceDesk 7.1 SP1 Implementation) to the Local Administrators group
1 In the Administrators Properties dialog box, click Add.
2 In the Select Users, Computers, or Groups dialog box, click Object Types, and then if you are prompted, enter your network password.
3 In the Object Types dialog box, click Computers, and then click OK.
4 In the Select Users,Computers,orGroups dialog box, in Enter object names to select, type the domain name and the name of the ServiceDesk server computer as follows:domain\host-name
5 To verify that the name resolves correctly, click Check Names.
In my environment check names removed the Domain/Host-Name format-I typed in the Domain/Host-Name
6 If the test is successful, click OK.
7 Close the Computer Management page.
Altiris user since 2001, Asset Management for 20 years
Would you like to reply?
Login or Register to post your comment.