Avatar of dl_ee
dl_eeFlag for United Kingdom of Great Britain and Northern Ireland asked on

Blackberry Manager on XP - to assign users to devices. Get DIspatcher Service Error RPC when assigning device.

Hello I am required to do wired activation of Blackberry by my customer for security reasons. We have a BES on the network aand a BES Database running on MSDE.

I am trying to install ONLY Blackberry Manager on a Windows XP machine from the 4.1.6 BES Source. This is allowed.

Everything installs correctly and I get connection to the Database and Exchange server.

I can run Blackberry Manager fine and see everything.

WHen I try to assign a device I get the Dispatcher Service error. RPC?

Please help someone!
Cell PhonesBlackBerry ProgrammingBlackBerry

Avatar of undefined
Last Comment
dl_ee

8/22/2022 - Mon
Rob Knight

Hi,

Make sure that your PC can get to the BlackBerry Router using Desktop SRP (4101) - you may want to add a custom router config in the BlackBerry Device Manager - you'll see it running in the system tray.

Regards,


RobMobility.
ASKER
dl_ee

Hi RobMobility:

Thanks for respone. Yes I can see the Device Manager running in System Tray.

BUT I don't understand why the Router is involved here for device assignment/activation.?

All I want to do right now is wired activation of the user to phone.

and 4101 is probably not open on our firewalls - is that also required - if so client initiated only or both ways?
Rob Knight

Hi,

When you do a wired activation, the BES will still communicate out with the RIM NOC (this might not be the case with WLAN activation but I have not tried that).

For a desktop activation to occur, the device needs to talk directly to the BlackBerry Router via 4101 which in turn will talk to the RIM NOC via 3101.

If this cannot happen, then activation will not take place.

Unless you have a separate BlackBerry router, then your device will need to communicate via 4101 to the BES. If you have a separate Router, then it will need to get to that via 4101 TCP.

Regards,


RobMobility.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
Rob Knight

Hi,

Make sure your SRP status is connected in Blackberry Manager when looking at BES statistics as well.

Regards,


RobMobility.
ASKER
dl_ee

Firstly my SRP Status for my main BES Server (not the local XP device with BB Manager on it) is showing as UNKNOWN? Is this the problem?

We have separate Router but this is sitting in a separate isolated VLAN from the BES and Database servers.

I can confirm via telnet command that port 4101 to the BES is working to connect.

Still get the Dispatcher error message. Should I add the custom router config in Blackberry Device Manager as advised first?
Rob Knight

Hi,

Presumably if you go to the BlackBerry Router page on the BlackBerry Configuration manager on the BES, this is pointing to the BlackBerry router, not SRP.eu.blackberry.net/srp.gb.blackberry.net?

If you do a test connection, does this work OK?

The Unknown status indicates that your BES cannot talk to the RIM NOC (BBI) so you should be seeing lots of other problems.

Regards,


RobMobility.

Are you UK based on a non-commercial organisation with GSI access? I can email you directly if you like.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER
dl_ee

We have no reported problems with status on the BES to the router - I am not the regular BES administrator but the admin says the Status is fine on his BB Manager.

I believe I have tried your Blackberry Device Mgr - add router config. Added IP address of our router server. And pressed OK to see a port 4101 router setup. However its status in "Statisitcs" screen is showing as connecting...not Connected.

Yet Telnet <BESServer> 4101 command seems to work fine.

I can give gsi email address but can't get at it easily today so we can maybe talk on phone - 07867 831290 is my number although the reception is bad here. Could I ring you maybe?
Rob Knight

Hi,

If you leave the router setup as default, do you see a connection to the BES or is this also showing 'connecting'?

Regards,


RobMobility.
ASKER
dl_ee

Sorry could you expand on what you mean - do you mean delete all router entries?
so nothing is setup in Device Manager?

Where should I see the connection to the BES showing connecting?

(Sorry I am not an experienced BES administrator)
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
Rob Knight

Hi,

Apologies - if you delete any custome router entries, you should default to the BES - therefore when in that configuration, do you see any statistics to the BES?

Regards,


RobMobility.
ASKER
dl_ee

Currently I am reading that as TCP port 1433 needs to be open both ways on our firewall for Blackberry Manager to talk to the database server.

We have only implemented one-way from client side.

So having the network engineer change this.

I will update result on this exercise.

Thanks for you help in meantime ROBMobility...
Rob Knight

Hi,

Client initiated should be the rule - this usually permits a response by default as it will be treated as Stateful.

1433 assumes that you are using default port so worth checking. MSDE, like SQL Server Express usually only allows local TCP connections not remote ones - might be worth checking that these are permitted as well?

If there were serious issues with your SQL communication, I would expect you to have more serious problems!

Regards,


RobMobility.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Sudhakar Kumar

Normally this support doc is helpfull, when you install Blackberry Manager on a non BES server/machine.

Server Routing Protocol or Server status shows "Unknown" in BlackBerry Manager or BlackBerry Administration Service
Article ID: KB10063

Type: Support Content

Last Modified: 08-03-2010

PrintEmail Document Bookmark  
Product(s) Affected:

BlackBerry® Enterprise Server

Search the knowledge base:


Visit BlackBerry Community Support Forums
Follow us on Twitter® @BlackBerryHelp
Collapse all | Expand all
Jump to: Overview | Environment | Cause | Resolution | Additional Information
Overview

In a remote BlackBerry Manager or BlackBerry Administration Service installation, the Server Routing Protocol (SRP) status shows as Unknown. The status cannot be updated from BlackBerry Manager or BlackBerry Administration Service.

Back to top
Environment

BlackBerry® Enterprise Server 4.0 to 5.0 SP1
Back to top
Cause

This issue may be caused by one of the following:

A remote procedure call (RPC) session has not been established with the remote BlackBerry Enterprise Server. An RPC session is required when BlackBerry Manager is administering a BlackBerry Enterprise Server installed on a different computer.
The BlackBerry Dispatcher service is not started.
The remote BlackBerry Administration Service console is running under a different service account than the BlackBerry Enterprise Server service account.
Back to top
Resolution

Cause 1

A remote procedure call (RPC) session has not been established with the remote BlacKBerry Enterprise Server. An RPC session is required when BlackBerry Manager is administering a BlackBerry Enterprise Server installed on a different computer.

Resolution 1


To verify this issue, complete the following steps:

Verify that file sharing is configured on the BlackBerry Enterprise Server and establish an authenticated session. It is possible to set up a local account on the BlackBerry Enterprise Server that has the credentials of the BlackBerry smartphone user on the remote computer, or establish an authenticated session using the following command prompt:

net use \\<servername>\<pipe > /user:<DOMAIN>\<username>

Where

<servername> is the Windows® name of the computer hosting the BlackBerry Enterprise Server.
<pipe> is the pipe where the file sharing is configured on the computer hosting the BlackBerry Enterprise Server. For example, C$.
<DOMAIN> is the Windows Domain of the computer hosting the BlackBerry Enterprise Server or the computer name of the BlackBerry Enterprise Server.
<username> is the name of the Windows user account on the domain of the BlackBerry Enterprise Server or the local system account on the BlackBerry Enterprise Server.
After using the above command, a prompt will be made for the password for the <username> account that is logged in. If this is completed correctly, the The command completed successfully message is displayed.

Example:
The following is an example of the command executed successfully using the computer name:

C:\>net use \\<machinename>\c$ /user:<machinename>\localsystemadmin

The password or user name is invalid for \\<machinename>\c$.

Enter the password for '<machinename>\localsystemadmin' to connect to '<machinename>':

The command completed successfully.

If a connection cannot be established using the BlackBerry Enterprise Server computer name, the computer may not be able to resolve the computer name. To make this connection successful, confirm the following settings:

Ensure that Windows firewall is not set to block RPC connections
Make sure the Windows Server® and Computer Browser service is running
Make sure file and print sharing is enabled
After these steps have been completed, verify the issue again using the net view command:

net view \\<computername>

If the command is successful, restart the BlackBerry services on all servers containing BlackBerry components.

Cause 2

The BlackBerry Dispatcher service is not started.

Resolution 2

Start the BlackBerry Dispatcher service.

Important: Restarting certain BlackBerry Enterprise Server services delays email message delivery to BlackBerry smartphones. For more information, see KB04789.

Cause 3

The remote BlackBerry Administration Service console is running under a different service account than the BlackBerry Enterprise Server service account.

Resolution 3

Ensure the BlackBerry Administration Service service account has local administrative permissions on the BlackBerry Enterprise Server.

Back to top
Additional Information

This issue does not occur when BlackBerry Manager is installed on the same computer as the BlackBerry Dispatcher, because all communication stays within the same computer unless the BlackBerry Dispatcher service is stopped.

However, in a network setting, where BlackBerry Manager or BlackBerry Administration Service exists on a different computer than the BlackBerry Dispatcher, the RPC communication between the two has an additional dependency on authentication between the two computers. The Windows Server that the BlackBerry Enterprise Server is installed on needs to validate the authenticity of the BlackBerry smartphone user logged in to BlackBerry Manager to establish an RPC session. A failure in this authentication will terminate the RPC session.

ASKER CERTIFIED SOLUTION
dl_ee

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Rob Knight

Fine with me.
ASKER
dl_ee

We had to open our firewall fully and then see what traffic was being observed. My Network Engineer identified what was being sent/received.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck