I am trying to receive a shipment using an in-transit receipt under purchasing. I can see the items, but when I try to receive them GP freezes and never recovers, the only way to continue is to End Task GP.
I have tried several of the outstanding receipts and they all do this. I have a real problem, I have several containers that I can not receive and I can not delete the transfer.
Having Dynamics GP freezing doesn't necessarily mean that there are no processes being run, posting process might be in progress.
Freezing problem is usually hard to be diagnosed, therefore, I might have several questions in mind.
Does this happen with other inventory transaction posting like, adjustment or transfer ?
Would the receiving transaction be as slow as in-transit posting ?
What valuation method of the items being posted is ?
On the other hand, does this happen with all GP Users ? All workstations ?
Your feedback is highly appreciated.
Mahmoud M. AlSaadi
Dynamics GP Essentials | mahmoudsaadi.blogspot.com
Mahmoud thank you for getting back to me.
I have left GP running for up to 30 minutes it never recovers. In answer to your questions.
This does not happen with any other inventory or receipt transactions, it is limited to only the In-Transit receipt.
The speed would not be affected.
The valuation method is FIFO.
This problem happens on all machines with all users, including trying to post on the server.
I have run Check Links and Reconcile, no errors discovered.
I did run IV Reconcile with the Professional Tools Suite, I did receive the following error:
Allocated quantities do not match from detail to IV00102
What version of GP and what Service Pack are you on. This was experienced by a customer of mine and it was diagnosed as a problem in v2010 (but I don't remember the SP) Upgrade to the most recent SP for your version of GP. Unfortunately, the stuck ones will need to be manually deleted and re-processed.
Richard L. Whaley Author, Publisher, Consultant
Enhancing your Dynamics Knowledge!
We are using GP2013 Service Pack 2
I have been exposed to a freezing problem previously, which is definitely hard to be diagnosed. Since it is something that occurs on all workstations, with all GP users and with this transaction specifically. I ended up formatting the application server, clean GP installation solved the problem.
As for debugging, I would suggest the following; when all GP users logged out, try posting such In-transit transaction (over night would be the most suitable timing). Check whether this problem still occurs.
Following that on SQL-profiler along with the SQL activity would be a good suggestion in order to check when and what is making the posting stops. For some reason, there might be certain dead-lock, at which two processes are hanging on each other.
It's important to take into consideration that such debugging might result with further corrupted in-transit documents through posting. Therefore, having a test environment would be a relief
In this essence, if you don't think that formatting is an applicable solution, you may want to dedicate further time on debugging on this issue, until certain root-causes are revealed.
Let's hope somebody out there in the community will provide us with a better debugging criteria.
So far, hope this helps,
I have some more information. I just tried to complete a transfer with another object that does not have lot numbers. Everything worked perfectly.
I went back to my transfer that has been freezing. It still does not work. It is hanging up when I try transfer the lot.
I don't know if that information helps. It seems to be a problem with the lot information on the item.
I would still recommend profiling this issue on SQL Profiler, and post back your findings. That would make it easier to detect any potentials issues.
Start with Dex SQL Logs.
Sanjay Kumar Rajarao. ACA, MCPhttp://www.sanjaykumar.us | email@example.com
Other Microsoft Sites
I'm a Customer
I'm a Partner
Follow Microsoft Dynamics