I'll add another me too. These logs lines are there right before it crashes:
20111109211957.478201 Network Connect[p376.t519] DSSignalProxy.panic caught signal 10 (DSSignalProxy.m:205)20111109211957.478225 Network Connect[p376.t519] DSSignalProxy.panic relaunching /Applications/Network Connect.app/Contents/MacOS/Network Connect for crash reporting (DSSignalProxy.m:228)20111109211957.569315 Network Connect[p451.t2307] NCController.info -applicationDidFinishLaunching: Network Connect 7.0.0 (16007)/Version 10.6.8 (Build 10K549) starting (NCController.m:98
)20111109211957.584125 Network Connect[p451.t2307] DSLoginWindowController.info -windowDidLoad setting user-agent to Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/6534.51.22 (KH
TML, like Gecko) Network Connect (like Safari)/16007 (DSLoginWindowController.m:105)
Time Machine saved me this time.
Open the Time Machine.
Pick a date before the update.
Find everything Java related. For me the main folders were System/Library/CoreServices, PrivateFrameworks, FrameWorks, /usr/share and Applications/Utilities.
Restore to the same folders.
If everything went ok Network Connect should work again and Software Update wants to install the update again. Something you shouldn't do, obviously.
Same here. I have tried it all. It is related to the Java update 1 for sure. Apple says its junipers issue to resolve since they are doing something that shouldnt with code.
Same here. Updated OS X Lion (10.7.2) with the Java update from Apple via Apple's network update tool. It broke the Juniper Network Connect client application. Behavior is:
Network Connect starts up and is able to contact the remote server. It accepts my login credentials and passes the host check that our servers do, but instead of then providing our usual prompts/links window to select VPN, etc., the Network Connect window gets put behind other windows and returns to the prompts for login credentials. I don't have the log with me now, but I can confirm that my log is showing the " DSSignalProxy.panic caught signal 10" message as well. But, I thought mine shows signal 11, not 10...but that could be my faulty memory.
I can also confirm that launching from the web portal rather than the local installed Network Connect client works, So, I have a workaround, but the Network Connect functionality is currently broken by the Java update.
Here's my log snippet:
2011-11-09 18:55:53.204 Network Connect[p674.t6915] DSLoginWindowController.info -webView:didStartProvisionalLoadForFrame: loading https://remote.foo.com/dana-na/auth/url_default/welcome.cgi?p=preauth&id=state_e8f5dc100eb174658565a... (DSLoginWindowController.m:256)
2011-11-09 18:55:53.205 Network Connect[p674.t6915] DSLoginWindowController.info -webView:didStartProvisionalLoadForFrame: setting cookie <NSHTTPCookie version:0 name:"DSUserAgent" value:"NcWin32" expiresDatenull) created:2011-11-10 01:55:53 +0000 (3.42583e+08) sessionOnly:TRUE domain:"remote.foo.com" path:"/" isSecure:FALSE> (DSLoginWindowController.m:269)
2011-11-09 18:55:53.806 Network Connect[p674.t6915] DSSignalProxy.panic caught signal 11 (DSSignalProxy.m:205)
2011-11-09 18:55:53.806 Network Connect[p674.t6915] DSSignalProxy.panic relaunching /Applications/Network Connect.app/Contents/MacOS/Network Connect for crash reporting (DSSignalProxy.m:228)
2011-11-09 18:55:53.964 Network Connect[p725.t6915] NCController.info -applicationDidFinishLaunching: Network Connect 7.0.0 (16899)/Version 10.7.2 (Build 11C74) starting (NCController.m:98)