Open GoogleCodeExporter opened 9 years ago
[deleted comment]
Dear Paul
Thanks a lot for your description and the attached recording of the error. And
sorry for my late reply, I was quite busy the last days and I also realized
that it will not be that easy to track down the problem with the named pipe
exception.
The named pipe allows the GUI to communicate with the service that applies the
IP settings. This way the GUI is not required to run as administrator to change
the adapter settings. It looks like applying the IP settings throws an
exception and therefore also the pipe server stops, causing the exception in
the GUI when trying to read from the pipe. If something goes wrong when
applying the profile, the service does currently not write anything to the
eventlog (one of the reasons a 1.0 version is not released yet). My suspicion
is however that the network adapter driver does not properly support WMI,
causing the error when applying the IP settings. That WMI has its disadvantages
is already reported in issue 58. To track down the problem you can run the pipe
server tester GUI application that is part of this project. It can be run in
place of the service and should display a more useful exception message if
something fails. I’ll compile it and attach it to this ticket.
Regards
Urs
Original comment by u...@urx.ch
on 11 May 2014 at 6:18
It turned out that the proposed pipe server tester application would not
display a different exception exception message. Instead I prepared and
attached a new installer based on revision b4a7e8d8cbd3 that now displays
exception messages if the service fails applying IP settings or if the named
pipe connection fails in the main application.
Please make sure to uninstall the original 0.2.3 version before installing this
test release. Since the version information is unchanged in the installer, it
would not update the executables.
Unfortunately this will not solve the issue you reported, but it should allow
you to report a different error message that might help to solve the problem.
Original comment by u...@urx.ch
on 20 May 2014 at 9:01
Attachments:
Original issue reported on code.google.com by
prb1...@gmail.com
on 28 Apr 2014 at 5:33Attachments: