![]() _ at .OnAsyncReceiveComplete(IAsyncResult result)_ _ at .AsyncMessagePump(IAsyncResult result)_ _ at .HandleRequest(RequestContext request, OperationContext currentOperationContext)_ _ at .DispatchAndReleasePump(RequestContext request, Boolean cleanThread, OperationContext currentOperationContext)_ _ at .Process(Boolean isOperationContextSet)_ _ at .Invoke(Object instance, Object inputs, Object& outputs) in c: Releases\ICE\3.1.400.20\source\Framework\Epicor.System\Hosting\Wcf\EpiOperationInvoker.cs:line 23 _ at (Object instance, Func 2 func) in c:\_Releases\ICE\3.1.400.20\source\Framework\Epicor.System\Hosting\OperationBoundInvoker.cs:line 59_ _ at (Object instance, Func 2 func) in c: Releases\ICE\3.1.400.20\source\Framework\Epicor.System\Hosting\OperationBoundInvoker.cs:line 28 _ at .Invoke(Object instance, Object inputs, Object& outputs)_ _ at SyncInvokeRunTask(Object, Object, Object )_ _ at .RunTask(Int64 ipTaskNum) in c: Releases\ICE\3.1.400.20\source\Server\Services\Lib\RunTask\RunTaskSvcFacade.cs:line 97 _ at .InnerRunTask(Int64 ipTaskNum, Boolean suppressTransaction) in c: Releases\ICE\3.1.400.20\source\Server\Services\Lib\RunTask\RunTask.cs:line 502 ![]() _ at .Run(String sessionIdPrefix, IceContext db, Action taskRunner) in c: Releases\ICE\3.1.400.20\source\Server\Services\Lib\RunTask\BpmFriendlyTaskLauncher.cs:line 63 _ at (Boolean suppressTransaction) in c: Releases\ICE\3.1.400.20\source\Framework\Epicor.Ice\Hosting\TaskCaller\TaskCaller.cs:line 31 _ at (IceDataContext newContext) in c: Releases\ICE\3.1.400.20\source\Framework\Epicor.Ice\Hosting\TaskCaller\TaskCaller.cs:line 78 _ at .VerifyGLBals.VerifyBalanceByBook(Int64 InstanceTaskNum) in c: Releases\ERP\RL10.1.400.0\Source\Server\Internal\GL\VerifyGLBals\VerifyGLBals.cs:line 659 _ at 1.MoveNext()_ _ at (IEnumerable 1 source)_ _ at .VerifyGLBals.b_b(GLBookPer ttFiscalPer_Row) in c: Releases\ERP\RL10.1.400.0\Source\Server\Internal\GL\VerifyGLBals\VerifyGLBals.cs:line 660 Program raised an unexpected exception with the following message: RunTask: Nullable object must have a value. The datafix is supposed to address this error that generates when trying to run verify balances process: I do hope with all my heart that this datafix is indeed going to address the original problem we have, which is verifying balances so that we can roll over year. I don’t know what the free burger equivalent is to a data fix from an ERP company other than knowing that one may have helped someone else down the road avoid an issue instead of just correcting an issue myself when the issue presents… which is a good enough reason to do anything in my if you haven’t done so already, please update your support case and the analyst will work with the developer that wrote the fix to determine what the issue is, and make it right. This is why I ended up with a free burger at BWW last week when they put the wrong cheese on the one they brought me (I just asked for a piece of the correct cheese :/). Speaking for myself (and in the most generic sense possible), I find letting the resource that provided the less than ideal experience know the issue is the most effective way of getting the issue resolved–and, hopefully in the process, prevent another person from running into the same experience. If there is an issue with any given data fix or it isn’t quite right, Support commits to working with the team that creates the data fixes to get it right–we just need to be made aware. There is a reason why one should never blindly do anything anyone says in production, ever, even if that person is a representative of your ERP software vendor, without knowing how it will actually impact production–best way to know how it will work is to test it somewhere that is as close to a production environment that isn’t actually one’s production environment. When any of the previous variables are not true (for whatever reason, right, wrong, or indifferent), the initial success rate of any given data fix is obviously going to be less as all those involved with the data fixes have to make some inferences and educated guesses along the way–nature of less than perfect sight into an issue. When an issue is clearly defined and when Support has the customer’s database in-house where the issue can be duplicated,and where the analyst can test the data fix before it is sent out to a customer the success rate of data fixes is very high. ![]() It’s not you, Epicor support is very bad at providing data fixes that actually work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |