Port 1352

Here's an example of a fun error that you might encounter in AdminP when attempting to process administration requests across domains:

In this example
*  A request was submitted to create a replica of database "towelie.nsf".
*  The database "towelie.nsf" is currently on server "MyServer/MyDomain" and the replica needs to be created on "YourServer/YourDomain"

So, after dutifully creating the corresponding Cross Domain Configurations on either side (see your Admin guide for how to do that), you submit the request on the MyDomain side.

But...

You find in MyDomain's Administration Requests database that the request failed, listing the following error as the reason:

Title: Administration Requests (6) File name: admin4.nsf; Name: YourServer/YourDomain; Error: Cannot determine the destination server's domain based on Server Documents in the Domino Directory and Cross Domain Configuration documents in the Administration Requ <sic>

(The error text ends rather abruptly probably due to a character limitation in the field or error message output.)  No matter; it's enough information to match the problem with the solution.

Solution:
Copy the "YourServer/YourDomain" server document from YourDomain's Domino Directory and paste it into MyDomain's Domino Directory.

Tip:  Change the "Server Title" for the copy of the server doc for YourServer's in MyDomains Directory to something like, "Needed for Cross Domain AdminP requests," so you'll have a visual reminder in the "All Server Documents" view as to why that server doc copy is there.

Rock over London, Rock on Chicago;  Diet Pepsi - Uh-Huh

Selected some text in a message I was composing to check the properties and...



Now I have two Text menu links.  (The one on the left is the real menu.)

Thanks for playing Freaky Friday.  We have some nice parting gifts for you (like restarting your Notes client to get rid of the bogus menu option).

I recently blogged about how to manually urge BES along in processing certain pending actions.

Along those same lines, it's a little known fact that there is a service, called "SQLSERVERAGENT," available to automatically run pre-configured SQL maintenance jobs for BES versions 4.0 and 4.1 (except those configured to use Microsoft SQL Server 2005 Express Edition).  See this if you use Express Edition.

By default, the Startup type for the SQLSERVERAGENT service is set to Manual. If the Startup type is set to Automatic, all BlackBerry Enterprise Server maintenance jobs execute regularly on a pre-set schedule.

Here's a link to the details:
How to run Microsoft SQL Server maintenance jobs for the BlackBerry Configuration Database

...and, while you at it, don't forget to tweak your "Debug log maximum daily file age" settings!

"Rock Over London, Rock on Chicago;   Wheaties, the breakfast of champions!