Finance | Project Operations, Human Resources, ...

SQL connection error in Sandbox environment

(0) Share

Report

Posted on by migi111

485

Hello,

We started to experience problems with the connection to the dabase when running batches in Sandbox environment. Earlier, in onebox azure environment there wasn't such problems. The exact messages are:

"Cannot execute a stored procedure. There is a temporary problem with the connection to the database. Please retry later."

"Cannot select a record in Dimension code combination, There is a temporary problem with the connection to the database. Please retry later."

And eventually this results to a failed batch task.

I have tried to google the problem, but couldn't find any other suggestion than "Try again later". It's not a good answer to our customer who expects more reliability from the system and it's been happening from time to time lately.

Thanks,

Migi

I have the same question (0)

All responses (17)

Answers (0)

Sergei Minozhenko 23,093 on at

Like (0)

Report

Hi migi111,

Do you run custom or standard operations in a batch? Is it related to a specific batch job or to all batch jobs? How long does it usually take to run it in batch?

Was this reply helpful? Yes No
migi111 485 on at

Like (0)

Report

It's been happening when running a customized feature in batch mode. When the batch run was restarted, it worked. But this has occured quite often lately.

Was this reply helpful? Yes No
Sergei Minozhenko 23,093 on at

Like (0)

Report

Hi migi111,

How long usually does it take to finish custom job in batch? Do you have long open transaction during custom job processing? Which PU version are you using?

Was this reply helpful? Yes No
migi111 485 on at

Like (0)

Report

This time it took nearly 1,5 hours and we're running on PU 34.

Was this reply helpful? Yes No
Suggested answer

Rahul Mohta 21,032 on at

Like (0)

Report

check your SQL connection timeout settings

Was this reply helpful? Yes No
Sergei Minozhenko 23,093 on at

Like (0)

Report

Hi migi111,

Have you enabled the feature "Batch framework contention reduction"? If not, would you mind to try it?

docs.microsoft.com/.../whats-new-platform-update-31

Was this reply helpful? Yes No
Sukrut Parab 71,710 Moderator on at

Like (0)

Report

If its a custom batch job, are you connecting with some external DB using store proc ?

Was this reply helpful? Yes No
Leo Chen on at

Like (0)

Report

If searching LCS telemetry with keyword like batch job id doesn't help to get more specific error info, would recommend you to raise a support request to get Microsoft support team engaged.

Was this reply helpful? Yes No
Suggested answer

Rahul Mohta 21,032 on at

Like (0)

Report

also check the function the batch is doing

if errors are accumulating due to dimension code validation then also it could take more time

you could probably run in the dev box with trace and analyze for contentions

Was this reply helpful? Yes No
migi111 485 on at

Like (0)

Report

Checked the parameter for connection timeout and it's timeout is set to 600 (default) - that's 10 minutes and I guess it should be enough.

Was this reply helpful? Yes No