Input string was not in correct format - Hail Mary help request

Hello All,

Had a case open for a month already and now I am being told that they cannot replicate the error.

Any ideas?

Whenever I try to enter a sales order number, any sales order number, in order entry or order tracker I get this:

Application Error

Exception caught in: Epicor.ServiceModel

Error Detail

Message: Input string was not in a correct format.
Program: Epicor.ServiceModel.dll
Method: CallWithCommunicationFailureRetry

Client Stack Trace

at Ice.Cloud.ProxyBase1.CallWithCommunicationFailureRetry(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, RestRpcValueSerializer serializer) at Ice.Cloud.ProxyBase1.CallWithMultistepBpmHandling(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
at Ice.Cloud.ProxyBase`1.Call(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
at Erp.Proxy.BO.SalesOrderImpl.GetByID(Int32 orderNum)
at Erp.Adapters.SalesOrderAdapter.OnGetByID(Int32 ID)
at Ice.Lib.Framework.EpiBaseAdapter.GetByID(Int32 intId)
at Erp.UI.App.SalesOrderEntry.Transaction.GetOrderData(Int32 orderNum)

Looks like a BPM or something is trying to getbyid, and passing an invalid value. Can you confirm if you have any BPMs, or directives on this?

It’s a vanilla database, nothing of that sort… not even the form is customized.

Odd thing is, I can do a DMT of a new orderhed and that opens just fine.

All the rest of the order data came over from a cloud conversion and it doesn’t seem to work.

Have you traced it yet? Perhaps you can see what is going on in a trace that shows the BO methods and the parameters that are getting passed.

I’ll look at that.

The trace just shows me that it gets two method calls done and that’s that.

Doesn’t this mean it’s expecting an integer and not getting one?

We’re certain there is no customization on the form that is manipulating the SO #?

Not that I know of.

I created a new order via DMT and added an order line to that new order and it works fine, comes up just fine… All older orders won’t come up.

And yeah, it’s expecting an integer, it is one…

What format are your older jobs numbers in? Are there weird characters in there, or blanks?

See that’s where I am at Nate, I am wondering exactly what is it in the data that is causing this to happen.

I wish I could step through the actions and see where exactly it’s getting hung up.

What about trying out kinetic in browser? Then you have access to the dev tools. That might give you a little more insight. I would also be interested to know if the problem happens in Kinetic.

It happens in classic and kinetic.

I am using the swagger API to call getby ID and I get the error when I make that call (GetBYID)

I’d call SalesOrder.GetByID in Swagger as well and see if it errors.

1 Like

That’s what I did and I get the error when I call it

BWAHAHAHAHA :rofl:

1 Like

I’m don’t have a clue what’s going on but it doesn’t sound good.

Is this something you can abandon and start over, or would that be bad ?

It’s a restoration of a vantage database that was converted using Epicor’s cloud conversion tool.

That’s pretty much what they told me to do because they cannot replicate it on 2022.2.13.

I mean I just have to apply the patch is all. Users then will have to update if I am not mistaken, but it’s been a minute. I could try it, but I am skeptical at best.

Curiosity → Why are you doing that?

1 Like