Open Forum

  • 1.  Screen automation

    Posted Apr 02, 2019 10:06 AM
    ​We have a custom application that runs some screen automations.  We release orders, confirm shippers, release inventory batches, etc.  It has been running fine for years on a windows server 2008 machine for years.  We want to upgrade that machine to server 2016.  Also, I have upgraded my laptop (which I use for making any modifications on the app with Visual Studio) from Windows 7 to Windows 10.

    We now get the same problem on both my laptop and the server 2016 machine.  We get the same error when the app tries to start SL.  If SL is running and logged in under the automation user, it will "sort of" work.  It still throws errors if you are trying to shut down and restart SL within the app, but at least it will "work" once through, which is how I've been able to limp along if changes are needed.  But, now that we need to upgrade the production box it's running on, we need to get this working.  Below is the error we get.  Thanks for any input.

    System.Runtime.Remoting.RemotingException: Failed to read from an IPC Port: The pipe has been ended.

    Server stack trace:
       at System.Runtime.Remoting.Channels.Ipc.IpcPort.Read(Byte[] data, Int32 offset, Int32 length)
       at System.Runtime.Remoting.Channels.Ipc.PipeStream.Read(Byte[] buffer, Int32 offset, Int32 size)
       at System.Runtime.Remoting.Channels.SocketHandler.ReadFromSocket(Byte[] buffer, Int32 offset, Int32 count)
       at System.Runtime.Remoting.Channels.SocketHandler.BufferMoreData(Byte[] dataBuffer)
       at System.Runtime.Remoting.Channels.SocketHandler.Read(Byte[] buffer, Int32 offset, Int32 count)
       at System.Runtime.Remoting.Channels.SocketHandler.ReadAndMatchFourBytes(Byte[] buffer)
       at System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadAndMatchPreamble()
       at System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadVersionAndOperation(UInt16& operation)
       at System.Runtime.Remoting.Channels.Ipc.IpcClientHandler.ReadHeaders()
       at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.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 Microsoft.Dynamics.SL.ObjectModel.ObjectModelHelper.ReThrowParentToolbarException(Exception ex)
       at Microsoft.Dynamics.SL.ObjectModel.SIVToolbar.set_Visible(Boolean value)
       at SLBatchRelease.MainForm.Form2_Load(Object sender, EventArgs e) in C:\Projects\MLBatchReleaseWithXFR\MainForm.vb:line 18
    Error sending email: System.Net.Mail.SmtpException: Failure sending mail. ---> System.Net.WebException: The remote name could not be resolved: ''
       at System.Net.ServicePoint.GetConnection(PooledStream PooledStream, Object owner, Boolean async, IPAddress& address, Socket& abortSocket, Socket& abortSocket6)
       at System.Net.PooledStream.Activate(Object owningObject, Boolean async, GeneralAsyncDelegate asyncCallback)
       at System.Net.PooledStream.Activate(Object owningObject, GeneralAsyncDelegate asyncCallback)
       at System.Net.ConnectionPool.GetConnection(Object owningObject, GeneralAsyncDelegate asyncCallback, Int32 creationTimeout)
       at System.Net.Mail.SmtpConnection.GetConnection(ServicePoint servicePoint)
       at System.Net.Mail.SmtpTransport.GetConnection(ServicePoint servicePoint)
       at System.Net.Mail.SmtpClient.GetConnection()
       at System.Net.Mail.SmtpClient.Send(MailMessage message)
       --- End of inner exception stack trace ---
       at System.Net.Mail.SmtpClient.Send(MailMessage message)
       at SLBatchRelease.LogManager.LogError(String text) in C:\Projects\MLBatchReleaseWithXFR\LogManager.vb:line 54

    Pete Draigh
    IT Systems Manager
    Academy - Online Interactive Learning from Experts