Strange Error in Receipt Entry

Still using the classic version of Receipt entry. One user noted a strange error we have never seen before. “You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels.” Image and text below. This happened after he performed these steps.

  1. Create a new receipt entry, enter PO and Packing slip.
  2. Correct the arrival date, press tab
  3. Error pops
    This is not repeatable, only some are generating this error. We ignore it by clicking the X, and the rest of the receipt entry goes fine.

## System Information ##
==================

AppServer Connection: MYLIVESERVER
Form Name: Receipt Entry
Customization Name: 
Menu ID: SRGO1001
Software Version: 11.3.200.0

============

Application Error

Exception caught in: Epicor.ServiceModel

## Error Detail ##
============
##!Message:##! You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels.
##!Program:##! Epicor.ServiceModel.dll
##!Method:##! CallWithCommunicationFailureRetry

## Client Stack Trace ##
==================
   at Epicor.ServiceModel.Channels.ImplBase.CallWithCommunicationFailureRetry(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, RestRpcValueSerializer serializer)
   at Epicor.ServiceModel.Channels.ImplBase.CallWithMultistepBpmHandling(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
   at Epicor.ServiceModel.Channels.ImplBase.Call(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
   at Erp.Proxy.BO.ReceiptImpl.ValidateMRPONum(Int32 poNum, Int32 vendorNum, String& errorMsg)
   at Erp.Adapters.ReceiptAdapter.ValidateMRPONum(Int32 poNum, Int32 vendorNum, String& errorMsg)

I think this is more an SQL server error than it is an Epicor error.

READPAST tells SQL to ignore rows that are locked by other transactions.

Do you have any BPMs tied to Receipt Entry?

Nothing on receipt entry, but on POForm, I have this Post proc method directive:


This just saves a line in UD11 to show that the PO has been printed. This is used elsewhere, and still seems to work fine.
Also confirmed no customizations on Receipt Entry. :thinking:

So… no BPMs that would be locking rows…

… maybe request to have your app server restarted?

I guess the issue was only popping up a few times, and it didnt happen again after he showed me. If it comes up again, we will try to get more information.
Thanks!

Maybe the compatibility level is wrong on your database.