Integration Stop itself mostly 33 mins after deployment starts.
Hi All,
I am new to here. We recently making a web site to allow users to input the carton info then submit to trigger new record add to the database(MS SQL server at Azure). The label prints once the integration detect new record in the table has been created. It work perfectly during test. We then deploy it. We found that it usually stop itself after 33 mins but sometimes longer. Here is the error message from the log.
- Unable to run integration 'Database Integration' while opening record set with 'select * from boxSetUp order by _timestamp desc'. Details: 'ExecuteReader requires an open and available Connection. The connection's current state is closed.'
We have tried below but doesn't work.
- Changing the Error Handling time - Max Retries 5 times and Tim Between Retries 500 seconds.
- Changing the Database Connection - Poll Time to 1 min.
How do we find out the reason? What should we do? Please help.
Please let me know if you need any kind of info details about this issues.
-
Hi Kevin,
Have you checked that there is not a (transaction) timeout in the database which is closing the connection?
Pete
0 -
Hi Peter,
First, thank you for your reply and help.
I could't find any logs, records or messages to show if there is any transaction timeout from Azure Portal.
If this is the reason it times out, would it help if we could increase the value of "DB connection timeout for full-text protocol handler (s)"?
Also, we see the status is "Starting integration 'Database Integration", is it supposed to be "Started"?
0 -
Not sure Kevin, I would suggest you drop an email through directly to Seagull's regional Tech Support team as they may have a better understanding of what is going on
0 -
Hi Kevin,
Just want to know if you find something to resolve your "Integration Stop" problem ??? I have the save problem
Let me know how you resolve it
Thanks
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
4 commentaires