Scripting Driver 3.6.1.12 - the version from IDM 4.0.2b install ISO
(not yet tried the latest 4.5 one)

Windows 2008 R2

Configured to use the scripting service.

Event recieved from engine, sent to script service
(bin\scriptclient.exe)

The trace log shows that the event fails with the typically useless
error 1

However the windows application event log (listed at the end of this
post) shows something more interesting (in that I've never seen this
before with the scripting driver).

The port 8200 is the one configured in scriptservice.conf

-address localhost:8200


And yes WSE 3.0 is installed as per the documentation.

Ideas?? How does one troubleshoot this interop between driver shim and
script client?



Microsoft.Web.Services3.AsynchronousOperationExcep tion: W...
Microsoft.Web.Services3.AsynchronousOperationExcep tion: WSE101: An
asynchronous operation raised an exception. --->
System.Net.Sockets.SocketException: No connection could be made because
the target machine actively refused it [::1]:8200

Server stack trace:
at Microsoft.Web.Services3.Messaging.SoapTcpConnectio n.Connect()
at Microsoft.Web.Services3.Messaging.SoapTcpConnectio n..ctor(Uri
remoteEndpoint, SoapTcpTransportOptions options, ISoapFormatter
formatter)
at
Microsoft.Web.Services3.Messaging.SoapTcpTransport .CreateConnection(Uri
transportAddress)
at
Microsoft.Web.Services3.Messaging.SoapTcpTransport .GetConnection(Uri
destination)
at
Microsoft.Web.Services3.Messaging.SoapTcpTransport .Send(SoapEnvelope
envelope, EndpointReference destination)
at
System.Runtime.Remoting.Messaging.StackBuilderSink ._PrivateProcessMessag
e(IntPtr md, Object[] args, Object server, Object[]& outArgs)
at
System.Runtime.Remoting.Messaging.StackBuilderSink .AsyncProcessMessage(I
Message msg, IMessageSink replySink)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvok eHelper(Message
reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invo ke(Object
NotUsed, MessageData& msgData)
at
Microsoft.Web.Services3.Messaging.SoapOutputChanne l.SendDelegate.EndInvo
ke(IAsyncResult result)
at
Microsoft.Web.Services3.WebServicesClientAsyncResu lt.OnSendComplete(IAsy
ncResult result)
--- End of inner exception stack trace ---
at Microsoft.Web.Services3.AsyncResult.End(IAsyncResu lt result)
at
Microsoft.Web.Services3.Xml.SoapEnvelopeReaderWrap per..ctor(SoapClientMe
ssage message, String messageContentType)
at
Microsoft.Web.Services3.WebServicesClientProtocol. GetReaderForMessage(So
apClientMessage message, Int32 bufferSize)
at
System.Web.Services.Protocols.SoapHttpClientProtoc ol.ReadResponse(SoapCl
ientMessage message, WebResponse response, Stream responseStream,
Boolean asyncCall)
at
System.Web.Services.Protocols.SoapHttpClientProtoc ol.Invoke(String
methodName, Object[] parameters)
at WebServiceClientDispatcher.ExecuteScript(String sScriptPath,
String sArg0, String sArg1, String sArg2, String sArg3, String sArg4,
String sArg5, String sArg6, String sArg7, String sArg8, String sArg9)
at Novell.IDM.WSD.ScriptService.ScriptClientMain.Main (String[] args)