You are viewing limited content. For full access, please sign in.

Question

Question

ERROR [HYT00] [Microsoft][ODBC SQL Server Driver]Login timeout expired

asked on March 6, 2015

I randomly get the error in the title in one of our scheduled workflows that runs off-hours. The workflow performs a LF search and then retrieves a set of field data from the returned entries and writes those values to a SQL table. We need this data in the SQL table to be included in daily performance reports for management (SSRS).

Sometimes, the workflow completes perfectly fine and it can go several days without an issue. Other times, it will fail with the above error. If I try to manually re-run the process, it may or may not complete. It always returns the same error when it fails. We are using Workflow 9.1.1.

I have tried modifying the custom timeout but that does not seem to make a difference.

The LF search is returning about 5,000 entries and I am retrieving 46 metadata fields from each entry and writing those to a SQL table. I truncate the table before writing the new data each day rather than trying to update since the data is very fluid and changes frequently.

The process fails at different points in the process too. Sometimes it gets about half way through writing the data and other times it gets to 90% before it fails.

I am at a loss to explain why it works one day and not another. We checked to see if there are any other process running at that time but the day it fails is not consistent so I don't think it's related to some other process. It is scheduled to run every morning (M-F) at 5:00am.

 

Thoughts?

 

Thanks in advance,

Eric

 

0 0

Replies

replied on March 6, 2015

Does it always happen around the same time?

Is the SQL instance used by WF the same SQL instance used by the LF Repository?

Do you have a backup process running before or during this time period?  If so, is it backing up the SQL databases?

Are you running a security or antivirus scan at this time?  If so, you should exclude all the LF files, folders, processes and executables.

0 0
replied on March 6, 2015

The SQL instances are the same for the LF repository and the SQL reporting table.

There could be some backup process still running when my workflow runs but even if I re-run it during business hours, it can fail. In fact, it did that today. I ran it around 9:00 this morning and it failed.

I will check on antivirus scans.

 

Thanks for the info.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.