Thanks for your reply Eric.
I have some more things about :
1) I may believe my first pb appeared because the TAP adaptor of openVPN client was not disabled.
I have several VPN servers : there is one adaptor per destination (probably related to the {dev node..} which is appended in the detailed configuration when the adaptor is being created)
When I connect/disconnect, the adaptors return to disable which seems to be the status when no VPN is active
So may be the openVPN TAP was not disabled when i launched for the first time a VPN with Viscosity and it confused about the adaptor..
Since I dont know the detailed behavior, I can't go deeper.... lets say it is probably due to something like I describe above.
2)Now A second point, not related to the previous but which makes me worry about my customer :
I had a crash of viscosity (was doing crazy telnet characters.... since I was showing viscosit to a customer, i did'nt have time to detail what led to this crash)
I tried to restart, was asked for administrator rights to create an adaptor but it failed
Restarting the computer just told me the viscosity service could'nt be contacted (again I could'nt check if the service was running but I think it was not)
so i deleted the adaptors and restarted the computer..the service went on and i could continue, the adaptor has been created
My current thinking about that is :
If Viscosity crashs, something in the adaptor remains even If I restart the computer... This prevents the viscosity service to start
All I want to do is to find a procedure for the customer if it happens.. so currently, if he finds the service has gone, i'll ask to delete the adaptors and restart the computer (he does not know how to start a service)
If It can help; here are the windows logs
First is the net run time error
second is the subsequent application error (quite obvious)
last is the service start failure (service control manager)
Hope it helps
Gilles
Code: Select allApplication: Viscosity.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ObjectDisposedException
Stack:
at DLRCachedCode.networkChangedThread$325(System.Runtime.CompilerServices.Closure, IronPython.Runtime.PythonFunction, System.Object)
at IronPython.Runtime.PythonFunction+FunctionCaller`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Call1(System.Runtime.CompilerServices.CallSite, IronPython.Runtime.CodeContext, System.Object, System.__Canon)
at DynamicClass.CallSite.Target(System.Runtime.CompilerServices.Closure, System.Runtime.CompilerServices.CallSite, System.Object)
at System.Dynamic.UpdateDelegates.UpdateAndExecute1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Runtime.CompilerServices.CallSite, System.__Canon)
at DynamicClass._Scripting_(System.Object[])
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()
second :
Code: Select allNom de l’application défaillante Viscosity.exe, version : 1.3.2.1082, horodatage : 0x4e37d4c2
Nom du module défaillant : KERNELBASE.dll, version : 6.1.7601.17651, horodatage : 0x4e2111c0
Code d’exception : 0xe0434352
Décalage d’erreur : 0x0000d36f
ID du processus défaillant : 0x1950
Heure de début de l’application défaillante : 0x01cc67b7f0b43dcf
Chemin d’accès de l’application défaillante : C:\Program Files\Viscosity\Viscosity.exe
Chemin d’accès du module défaillant: C:\Windows\system32\KERNELBASE.dll
ID de rapport : 4bcfe1df-d585-11e0-be1a-00238be0c059
last (no reply after start of viscosity service)
Code: Select allLe service Viscosity Service n’a pas pu démarrer en raison de l’erreur :
Le service n’a pas répondu assez vite à la demande de lancement ou de contrôle.