I uninstalled the 10.1 admin console and installed the 10.0.700.4 console. I configured the app server and got it running.
I then installed the base 10.1.400.0 admin console then ran the 10.1.400.3 updater now both versions are running on my test server
I still can’t connect to the 10.0 service with the ‘new’ admin console, but at least it is running
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, February 26, 2016 1:39 PM
To: vantage
Subject: Re: [Vantage] E10.0 and E10.1 on same box
Regarding this same topic, I was trying to have 10.0 and 10.1 on the same server for testing purposes, and while I can get 10.1 to work, I can't seem to get 10.0 to work and get the following error when trying to connect to the AppServer for the first time after creation.
The requested service, 'net.tcp://epicor10/Demo100700/Ice/BO/UserFile.svc' could not be activated
Anyone seen a solution for this? I have rebuilt the Appserver 3 or 4 times but no change. I have the version as 10.0.700.4.
On Wed, Feb 24, 2016 at 5:58 PM, Bernie Walker bwalker@... [vantage] <vantage@yahoogroups.com> wrote:
Product: Server Manager
Version: 3.1.400.0
Problem:
System.ServiceModel.CommunicationException: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:05:00'. ---> System.IO.IOException: The read operation failed, see inner exception. ---> System.ServiceModel.CommunicationException: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:05:00'. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.ServiceModel.Channels.SocketConnection.ReadCore(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, Boolean closing)
--- End of inner exception stack trace ---
at System.ServiceModel.Channels.SocketConnection.ReadCore(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, Boolean closing)
at System.ServiceModel.Channels.SocketConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
at System.ServiceModel.Channels.DelegatingConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionStream.Read(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.Security.NegotiateStream.StartFrameHeader(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.NegotiateStream.ProcessRead(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
--- End of inner exception stack trace ---
at System.Net.Security.NegotiateStream.ProcessRead(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.NegotiateStream.Read(Byte[] buffer, Int32 offset, Int32 count)
at System.ServiceModel.Channels.StreamConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.Channels.StreamConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
at System.ServiceModel.Channels.SessionConnectionReader.Receive(TimeSpan timeout)
at System.ServiceModel.Channels.SynchronizedMessageSource.Receive(TimeSpan timeout)
at System.ServiceModel.Channels.TransportDuplexSessionChannel.Receive(TimeSpan timeout)
at System.ServiceModel.Channels.TransportDuplexSessionChannel.TryReceive(TimeSpan timeout, Message& message)
at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityDuplexChannel.TryReceive(TimeSpan timeout, Message& message)
at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
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 Ice.Contracts.UserFileSvcContract.IsPasswordExpired(String userID, Int32& graceCount)
at Ice.Proxy.BO.UserFileImpl.IsPasswordExpired(String userID, Int32& graceCount)
at Epicor.Mfg.Administration.ServerManagement.ApplicationServerManager.Forms.NewSessionForm.BackgroundWorker_DoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
From:
vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, February 24, 2016 5:30 PM
To: 'vantage@yahoogroups.com'
Subject: RE: [Vantage] E10.0 and E10.1 on same box
Did that – get socket timeout error trying to connect with admin console L
From:
vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, February 24, 2016 3:40 PM
To: Vantage
Subject: Re: [Vantage] E10.0 and E10.1 on same box
Sure, its trival just add the management tools for 10.x in your 10.1 Admin Console
On Wed, Feb 24, 2016 at 3:19 PM, bwalker@... [vantage] <vantage@yahoogroups.com> wrote:
Has anyone had any success getting the administration console to allow both versions on the same server?
