CNVCreateBufferedWriter - Could not complete operation in specified time

[vix]

I added your code immediately after InitCVIRTE() at the beginning of my application, and I'll let you know.

Not deleting the process when it already exists didn't completely solve the problem, but the situation is better: the Variable engines now hangs twice or three times a day (an not 20 times!!)

[vix]

OK. I can confirm that the problem is not completely solved.

How can I further debug the issue?

[vix]

I have one additional information:

• when the Variable Engine is properly working, if I open NI Distributed System Manager 2011, under "Network Items" are automatically listed all the PCs in the LAN that have NI Variable Engine (or other NI components, I don't know)without having to manually register them
• when the Variable Engine is not working, all the other PCs disappear from Distributed System Manager 2011 "Network Items". Only the localhost name is still listed.

I hope this helps.

[D_Biel]

Do the two conditions you mentioned above happen as a result of the CVI application, or do they both occur even if you do not run your application on startup?

[vix]

As I said in one of my previous messages: it's not a problem of running my application on startup!!!!

While developing m applications, sometimes I'm able to successfully launch the application itself several times, then at some moments it doesn't work anymore and I must restart my PC.

After some empirical test I found out that if I launch my application the first time immediately after system bottom (and then I stop it, starting writing some modifications to the source code), I'll able to develop for some hours before the engine hangs.

If I don't launch the application immediately after the bottom, the first or the second time I launch it (inside CVI or as standalone executable, it doesn't matter) the engine hangs.

And sometimes the engine hangs even re-launching the application without any modification to the source code!

So the question is: how can I debug why the engine hangs (and I see this at least 2 or 3 times a day)?

After having applied the workaround you proposed (basically not to delete the variables if they already exist) I see an engine hang 2 or 3 times a day. Without this workaround I saw an engine hang 25-30 times a day. And every time I must reboot the PC.

I think the problem is in some race condition or concurrent access to some network resource done from Variable Engine and some other application and/or Windows service...

[D_Biel]

Vix,

I have sent you a private message with an attachment for advanced troubleshooting. This should allow us to create a log of the MXS service. Please follow the directions and send me the logs back.

[vix]

I can't find any private message yet. Have you already sent it?

[vix]

My mistake. I haven't seen the private message. I've just answered

[djac91]

Hi Vix,

Have you found a reliable solution to this issue already. If so, could you share how you solved it

[vix]

The topic is quite old and so I had to search into the old email to find the answer.

I don't know if what happened to me 8 years ago (with WinXP and Win7) can be related to what happens now, but I try to summarize what we found.

The issue came from the PC of one of my colleague, who had installed a Microsoft Loopback Adapter on hi WinXP PC.

When he joined the corporate domain with the Loopback Adapter enabled, my PC crashed immediately.

This post on NI forum is related to some issue with Loopback Adapter, but I wasn't able to find if this is related to my issue.

After some weeks, @D_Biel found a similar issue on his own PC, generated by MS Loopback Adapter on Win7.

In his case, a couple of settings helped:

• disable Internet Protocol Version 4 (TCP/IPv4) for the Loopback Adapter
• change the binding order of network connections on the PC, moving the Loopback Adapter to the bottom

This issue had been highly prioritized by NI team and (probably) a newer relase of some NI services could have fixed the issue (I can't say).

I haven't received any update since 2012, but I asked my colleague to uninstall the MS Loopback Adapter and I solved my issue.

In the meanwhile, I and the collegue changed our PCs  and I didn't see the issue anymore.