06-07-2011 08:25 AM - edited 06-08-2011 04:59 AM
Bridge has been working fine with a 9700 until this afternoon. It crashed when the handset temporarily lost phone signal. This has happened before and the Playbook seems to recover, After a while Bridge started working again.
This evening, an OS update went through. Now every time I attempt to connect to a Bridge app I get Error Code: 13
I have tried the knowedge base workaround (KB26643). Have tried deleting Bridge from the phone and reloading everything a number of times. I suspect it has something to do with the OS update. Evrything worked okay until this went through.
What can I do? Bridge is the app I use most and pretty much the reason why I have the playbook.
Solved! Go to Solution.
06-07-2011 09:20 AM
06-07-2011 10:23 AM
What bridge and pPlaybook version are you on?
BESAdmin's, please make a signature with your BES environment info.
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V
06-07-2011 06:46 PM
Thanks for the tip. I have tried this and I still have the problem. Bridge does seem to be connecting becuase I get notifications on the Playbook. The problem occurs when I attempt to open a Bridge application.
I notice the Bluetooth connection has been working differently as well, since I updated the OS on the Playbook.
When I checked the connection status, it used to say "Connected to Bold 9700" , now it doesn't say that, even thought the bridge connection is up.
06-09-2011 07:09 AM
I resolved the problem by performing a security reset. After trying every other bridge delete and re install combination, this was the only way to fix the problem.
Overall, this seems to have resolved a lot of issues with the tablet.
Only thing I lost was the 7 digital store shortcut so if anyone knows how to get this back, I'm open to suggestions.
06-10-2011 03:00 PM
i too have tried everything including the "dance of the Playbook" in E minor. Last resort is to do the security wipe but have about 50 pictures and videos I have to get off first but no USB cable available so will have to wait. Anyone know the source of this problem. Mine happened 1 day after the 05 update and 1 hour after the bridge update....hmmm.