Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

BlackBerry® Enterprise Service 10

Reply
Contributor
JBertok
Posts: 10
Registered: ‎05-23-2011
My Device: Q10 + Playbook + 9930

BES 10.1.1, BCS 10.1, Lync 2010 - "Cannot Sign In" The Server is unavailable. Please try again later.

Hello,

I have put in many hours this past week trying to get Collaboration Service 10.1 to work with my BES 10.1.1 and Lync 2010.  (Also running Exchange 2010 and Active Directory at 2012 level)

This has been quite a battle, I've overcome thus far the autoprovisioning problem and getting the right certificate created in the personal store, so the Collaboration service stays running now where it didn't at first.  I've also found the article referencing the incompatibility with publishing the Enterprise IM app from AppWorld and have followed the guidlines of publishing it from the local share.  (The app config has been removed and reapplied to the test user now at least 20 times.)  Collaboration Service has been reinstalled also with no difference.  I've also tried putting different Certificates into the WWW and Enterprise share folders but have not been able to find concise instruction for what the IM Client actually needs.  I've followed all the Powershell examples of verifying configuration that I could find.

 

The IM Client knows the difference between a valid and an invalid login - so communication is working and AD authetication is at least to a point.  The BBIM logs are showing an Active Directory exception:

 

<2013-07-11 23:10:33.280 PDT>:[245]:<BBIM_SERVER07_BBIM_1>:<ERROR>:<LAYER = BBIM, [OCSC] Dispatch of '{"method":"login","methodParams":"{\"sipUri\":\"sip:FIRST.LAST@MYDOMAIN.LOCAL\",\"reqId\":2,\"userName\":\"FIRST.LAST",\"userPassword\":\"...\",\"userDomain\":\"MYDOMAIN\",\"availability\":3500,\"activity\":null}"}' failed with exception: Exception has been thrown by the target of an invocation. - Unknown error (0x8000500c) at System.DirectoryServices.PropertyCollection.Contains(String propertyName)>

 

(My User and Domain names have been masked in the above example)

 

Valid SIP names on the domain for Lync are FIRST.LAST@MYDOMAIN.LOCAL

Valid username fomat is MYDOMAIN\FIRST.LAST

 

In the past few days I've followed hundreds of links, read through hundreds of posts, losing sleep late into the night, because I need so desperately to get this working. I have not been able to find a solution and do not know what to between now and the next step which is to buy a support incident.  My BES 10.1.1 deployment is still running on trial CALs, I don't have my trade-up CALs yet.  I've been focusing mostly toward Certificate and AD problems but have reached the end of the internet.  If someone has advice to offer that results in getting this working, I'll send you a gift card!

 

Thank You

Please use plain text.
Contributor
JBertok
Posts: 10
Registered: ‎05-23-2011
My Device: Q10 + Playbook + 9930

Re: BES 10.1.1, BCS 10.1, Lync 2010 - "Cannot Sign In" The Server is unavailable. Please try again later.

Update:

This could be related - not only will auto-provisioning for the Collaboration Service never work, it will not start up without intervention following a server restart.  I have to go into the BCSProvisioner tool every time, run it, and expect the following error:

 

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Runtime.InteropServices.COMException (0xC3EC7D0A)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementObject.Put(PutOptions options)
at BCSProvisioner.BCSProvisioning.AddInstanceOfTrustedAddInServiceSetting(String fqdn, Int32 port, String type, String routingPoolDN, String tlsTarget)
at BCSProvisioner.frmBCSProvisioner.btnCreate_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5472 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
BCSProvisioner
Assembly Version: 10.1.0.16
Win32 Version: 10.1.0.16
CodeBase: file:///C:/Program%20Files%20(x86)/Research%20In%20Motion/BlackBerry%20Collaboration%20Service/BBIM/bin/BCSProvisioner.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.DirectoryServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.DirectoryServices/2.0.0.0__b03f5f7f11d50a3a/System.DirectoryServices.dll
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5473 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5473 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

The dialog box gives the option to continue, so I do, but it does not actually work.  In order to get BCSProvisioner.exe to work without throwing exceptions I have the switch user, log in as the Domain "Administrator", and run it again.  (runs successfully as the Domain Admin)  After than I can switch user back to the BESAdmin user (which is in the local Administrators group) and then start the Collaboration Service manually.

It starts and stays running, but I ge t the client error in my original post when I try to actually use it.

At this point if I re-run BCSProvisioner as the BESAdmin user it will tell me the trusted service for the server is already created, rather than throw the exception.  I have to go through this excercise every time the BES Service is rebooted in order to get the Collaboration Service to start and stay running.

I have also tried promoting the BESAdmin user to a Domain Administrator - no change.

Still can't use it. Still getting "The Server is currently unavailable" on the client.

Please use plain text.