I am a hobbyist-programmer and build a few nice working solutions on NetDuino Plus 2 in C#. Recently I acquired the new Netduino 3 Ethernet. My problem is that the debugger does not work. When I load my C# application I get an error message:
STM32F4Discovery, VS2013 Debugger engine init fails (every next start debug) when Thread.Sleep(Timeout.Infinite) in Main procedure. VS output window: Looking for a device on transport 'USB' Found device port 'USB' with ID '8a381d09-b2d4. Android device reboots occasionally. We are testing our Android app on real-world devices and notice some of them reboot occasionally after 2-3 hours of app running. Logcat did not help, as we did not see any important messages before the device reboots. Sometimes the device even does not start, only battery removal helps to start it again.
The debugging target and the debugger engine failed to initialize because of unspecified device errors. The debugger engine thread has terminated unexpectedly with error 'Could not reconnect to the debugging target after rebooting it.'.
I have been looking on the web for a solution for a number of days now and I found a few people with the same problem but without solutions. Some people had the problem only on specific PC's. It worked fine on one PC, the other threw the error above. Other people had the problem in VS2012 but not in VS2013. One solution pointed at modifying the debugger SW but that goes beyond my knowledge. It seems there is some sensitivity in the debugger which has not been grasped yet..... Everything works fine with Netduino Plus 2, debugger always attaches. I have posted the problem also on the Netduino forum but without result.
Can someone point me in the right direction for a solution ?
Thanks in advance,
Arno
ArnoArno
Browse other questions tagged c#debuggingvisual-studio-2013netduino or ask your own question.
I have a server with Win2008R2 and a synology NAS. On the Nas there are 6 iSCSI partitions which are mounted on the windows server. The windows server is virtualized under Hyper-V.
After rebooting the client machine, two of the 6 partitions do not remount and I have to manually remount them... every time.
Each one has a similar configuration and has been configured with CHAP authentication. All 6 appear in the favourites list.
Event log shows no errors regarding iSCSI.The other 4 partitions mount without problems.
Any suggestions for further debugging?
EDIT: After speaking with synology they suggested disabling chap authentication and enabling something called masking, which is basically a filter to block which nodes can connec to each LUN. This made a huge difference to the problem. It still occurs every now and again after power outages or similar, but after reboots I can be pretty much certain that the luns will remount. I guess its an issue between the windows iscsi initiator and the target in authentication negotiation.
Ian Murphy
Ian MurphyIan Murphy
3 Answers
Apart from Favourites list have you checked if the volumes are listed in Volumes and Devices tab in iSCSI initiator properties? And are they set to Auto Configure?
This should (in theory) make sure that all volumes are initialized.
LukePLukeP
Make sure add to favorites and enable muilti-path is selected when you connect to targets:
When you discover portal, click advanced, don’t use defaults click “Microsoft iSCSI Intiator” and you’re NIC IP for Initiator IP.
whathefoxwhathefox
Rather old thread, but running into the same problem these days with Windows Server 2008 R2 SP1 and a Synology RS18017xs+ with DSM 6.1.5-15254.Checked the above 'auto configure' suggestion, but it does not work for me. The solution from this guy worked for me:
- Remove the auto configured device
- Click 'Add...', and manually specify the drive letter or mount point - 'F:' in my case
Just for the records.
Thomas PThomas P