ETL and Data Integration tools - Modern ETL software for everyone

Visual Importer 7.7.8.4
Repository stored in sql server on another machine

What can cause stalling of executed packages? The execution stalls between steps regardless of what the steps are and appears random. The only cure comes in restarting the server. Packages run smoothly for a day or two then I will see a stall such as exampled in screencap. If I do not restart then the stalling progressively increases. I don't detect any increase in memory usage like would see with a memory leak. How can it eventually abandon a incomplete execution then proceed to execute a next scheduled package with execute in separate thread turned off?

Gene

How many record do you have in QUEUE_ACTIONS and QUEUE tables?

Can post a screen-shot of actual package?

Mike

Attached are all you asked for. queue counts may be small because I have taken to stopping agent then clearing logs when I restart the server in response to this issue. The package shots attached are of a larger package I have where I see this occur however it does also occur on small packages. This example has a top level package then a sub package within then a sub package within that sub package.

A2BF-PROD1

I this the only computer you where Visual importer ETL is installed or you use your own computer to check the logs?

Mike

server Prod1 is the sole installation of Visual Importer and I work with it there through rdp. The repository resides in sqlserver on server Prod2

I is s hard to tell what is wrong with that.

There is a number of possible scenarios

1 Since it is random I guess it could locking issue

Agent is trying to update the record in QUEUE_ACTIONS/QUEUE and for some mysterious reason it is locked.
so it waits forever.

It would interesting to see the locking in SQL server

2 another possible reason bug in our software or third party code.
When error happened it shows the message dialogue, since it is service user is not able to see it and press ok.

3. Memory leaks.

4. Integrity of the database some blocks are damaged. agent is not able to update records so it stalls

Try DBCC
Also delete al records from QUEUE_ACTIONS/QUEUE

5. Another thing to do is to migrate to version 8

What I can see that version 8 is much stable than version 7....and more efficient.

Mike