A new issue recently popped up where users signing on with the Kinetic menu see an error message “Business Layer Exception - undefined”. There are zero details provided so I have no idea what it is related to. The error message does not display in Classic menu. One can just click OK to bypass the error but it comes up again at next logon.
This sever is running v10.2.700.40 and recently had the 11.2.200.38 DemoDB added to it. That is the only recent change so I assume it is maybe somehow related.
Any ideas on how to troubleshoot this given that there is no error detail?
The error that shows in the event viewer when logging on is below. This issue seems to be that Epicor isn’t looking for the valid FQDN of the server. It should be MYSERVER.MYDOMAIN.com but is pointing to MYSERVER.MYDOMAIN.local Any idea where that setting would be? I checked the AppServer Config and the config file on the client, but none of them reference MYSERVER.MYDOMAIN.local Seems like an easy fix if I can just locate the config that is pointing to the invalid FQDN.
Ice.Common.EpicorServerException: One or more errors occurred. —> System.AggregateException: One or more errors occurred. —> System.AggregateException: One or more errors occurred. —> System.Net.Http.HttpRequestException: An error occurred while sending the request. —> System.Net.WebException: The remote name could not be resolved: ‘MYSERVER.MYDOMAIN.local’
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
— End of inner exception stack trace —
— End of inner exception stack trace —
at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification) at Ice.Services.BO.DataDiscoverySvc.<>c__DisplayClass5_0.<requestSysconfigAsync>b__0() in C:\_releases\ICE\ICE3.2.700.40\Source\Server\Services\BO\DataDiscovery\DataDiscovery.cs:line 131 at System.Threading.Tasks.Task1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Ice.Services.BO.DataDiscoverySvc.<>c__DisplayClass4_0.<b__0>d.MoveNext() in C:_releases\ICE\ICE3.2.700.40\Source\Server\Services\BO\DataDiscovery\DataDiscovery.cs:line 111
— End of inner exception stack trace —
at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification) at Ice.Services.BO.DataDiscoverySvc.GetDataDiscoveryUrl() in C:\_releases\ICE\ICE3.2.700.40\Source\Server\Services\BO\DataDiscovery\DataDiscovery.cs:line 98 at Ice.Services.BO.DataDiscoverySvcFacade.GetDataDiscoveryUrl() in C:\_releases\ICE\ICE3.2.700.40\Source\Server\Services\BO\DataDiscovery\DataDiscoverySvcFacade.cs:line 153 at SyncInvokeGetDataDiscoveryUrl(Object , Object[] , Object[] ) at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) at Epicor.Hosting.OperationBoundInvoker.InnerInvoke(Object instance, Func2 func) in C:_releases\ICE\ICE3.2.700.40\Source\Framework\Epicor.System\Hosting\OperationBoundInvoker.cs:line 59
at Epicor.Hosting.OperationBoundInvoker.Invoke(Object instance, Func`2 func) in C:_releases\ICE\ICE3.2.700.40\Source\Framework\Epicor.System\Hosting\OperationBoundInvoker.cs:line 28
— End of inner exception stack trace —
I was not able resolve this. However I did eventually realize that this started happening on the day that I made changes to the Epicor server required to install 2022.2 (both 10.2 and 2022.2 are on the same server now). That same error does not occur in an upgraded version of the database in 2022.2 so we’re just going to live with it until we move to 2022.2
