Share
Report
29Hello,
We've been having this issue for the last 2 months in our company. We also upgraded to 10.0.37 at the beginning of February, but can't say it's relevant or not.
Summary is below:
- During January close, we ran the depreciation proposal batch job just as every other month. It usually takes 5-7 hours. This one didn't complete after 15 hours. At the same time, we ran it in a sandbox environment after refreshing the data from Prod and which is also identical with the production code-wise. It ended in 5 hours successfully.
- During February close, which is also the first month close after replaced Revenue Recognition with Subscription billing, the recognition batch job threw an SQL related error twice. Then the third attempt ended successfuly but in 28 hours. We ran the same batch job in the sandbox environment (again identical to prod data&code-wise) and it ended in 12 hours successfully. Btw - This batch job tested multiple times in real life data in a Tier-2 sandbox before go-live and the batch jobs were completed in min 5 max 8 hours successfuly. We were obviously expecting a similar situation after the go-live but here we are.
We have contacted Microsoft support but infortunately no help. They -as most of you are aware- usually take these things case by case and whenever they see a customization they stop supporting. We tried to explain this under multiple incidents that this issue is bigger as we don't have a reliable production environment and also we can't rely on any tests we run in sandbox as after the deployment the results may be different in production.
We can't start to work on an improvement given the fact that we can't trust the test results we'll get in sandbox environments.
I thought it would be a good idea to share this here and i'm looking for a reason why the sandbox all over sudden stop representing production. Is there something that's related to version 10.0.37? Or anything else specific to production environments that we're not aware of? Any idea would be much appreciated.
Thanks,
Nagehan
All responses (
Answers (
