WL7 is restarting at the same time as WLD 6.9 is running its data update, this causes WLD 6.9 data update stop working. Its Strategy Monitor also could not update data. The error message was Socket Error Time Out. I would appreciate any suggestions.

Removing and reinstalling WLD 6.9 seems to work for now. The problem has been intermittent so hopefully this will solve it.

I'm at a loss how a reinstall would fix this. Most likely it's a conflict of the two programs (WL6 and WL7) trying to share the same IQFeed subscription. I'd say try leaving just one and see how it goes.

There is only one subscription for IQFeed and I have been running data update on both programs at the same time since the introduction of WL7 and there are no problems. However, as I observed when WL7 restarting when WLD 6.9 is running it's data update, the update stop with the error message Socket Error time out.

Restarting WLD a couple times won't help. I then try to delete the "IQFeedStaticProvider.txt" file at

QUOTE:
C:\Users\XX\AppData\Roaming\Fidelity Investments\WealthLabDev\1.0.0.0\Data

. This seems to get the data update working but not all the time. The reason I did this is because based on my experience, delete this file helps with the data update when it is running very slow.

I agree it seems like there is a conflict of sharing when WL7 restarting while WLD6.9 is running its data update.

It seems that re-installing WLD6.9 won't fix the data update, I still getting

QUOTE:
SOCKET ERROR! TimedOut

when trying to run data update. What can I do to get the data update running again? Thanks.

Don't restart WL7 while WLD6.9 is running its data update?

I restarted WL7 while WLD 6.9 runs its data update on accident- and that was the only time. Now with WLD 6.9 runs its data update independent from WL7, it still not working properly. Every few days or so it stop working and outputs the SOCKET ERROR TIMEOUT. Is it that some file got corrupted?

It's not a file issue. The socket connection (a link set up by the adapter for 2-way communications with a server) had an error for whatever undetermined reason and didn't recover. If you can come up with a procedure to make it happen consistently, we could try to duplicate what you're doing and possibly work around it.

As of last night, I am unable to complete a SM scan since about 1/2 the names are returning "Socket connect error: XLV; Message E,Could not connect to History socket.,"

I've contacted IQFeed and installed their 6.2.0.23. Prior to that install their SnapQuote app was not returning some names but afterword returned all i put in by hand ok.

Attached is the WL last update log of a couple minutes ago which took about 30 min to complete. As two nights ago, the scans were good and time to complete was under 10 min.

I am running WL v 6.9.24.1.

Please advise.

As of this morning, the problem has disappeared.

If mine was the only complaint then my guess would be a network switch.

Thanks