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!

From time to time I've encountered the following error for a BES account that refuses to purge:
User "user's name" is in delete pending state on server "CN=user's server name", please recover the user before adding user to server.



It's tempting to just switch to the "User's Pending Delete" tab and manually complete the process, but BES Manager then gives you a warning that basically indicates that you probably don't want to do that...



No love from the BlackBerry Technical Solution Center for this error in Domino (just something for Groupwise), but I found a solution here that might very well do the same thing as manually following through on the Users Pending Delete tab, but it "feels" like a better solution.

Here's the solution posted in the link above:

1. Open command prompt
2. Type "osql -E"
3. 1>use BESMgmt
4. 2>go
5. 1>delete from userconfig where mailboxsmtpaddr=''<email address>''
6. 2>go

If your command was successful, you'll get the response "(1 row affected)".
Checking the "Users Pending Delete" tab will now confirm the account is fully purged.

I'm sorry, but you forgot to phrase your question in the form of a question.

...does the pilot get radioed, "TK-421, why aren't you at your post?"

I took a support call recently from a user that was suddenly missing the column headers in their Inbox.  My first thought was that something went awry in the "Customize this view" option, but resetting to the defaults didn't resolve the issue.

A quick search at the forum introduced me to the 8.x feature called "narrow mode."  You developer types probably already have this article bookmarked, but for those that don't already know about it...

Turns out that when, for instance, the Inbox view width is reduced below a certain threshold, the columns are prioritized, reduced, and reformatted in a way that the usual column headers don't apply;  thus they are hidden.

"Normal mode" - now you see the Header

"Narrow mode" - now you don't


The squished Inbox view actually looks a lot like Ultralite mode.

I know that this probably isn't news to everyone.  I was just particularly obtuse about this feature until recently.

Post Blog Ponder:
I wonder if this feature were around in '06 and the soccer football soccer pitch were narrowed in the World Cup final if that would have eliminated the headbutt, too. 

Had a user with a funny looking mail rule.  Trying to enable or disable it yields the ever-so-helpful pop-up:

When creating and configuring your shiny new ID Vault, make sure you do not include a space in the "Notes ID vault name."



As the config tool's help text mentions, Domino uses the ID vault name to create the file name.  So, any space included in the ID Vault's name will translate into a space in the filename, too.

Otherwise, I've found that person deletions for ID Vault participants generate "File not found" errors;  exactly as Notesboy mentions here.

Most Firefox users probably already know that you can move tabs around in the Firefox window.  That is to say, tabs are displayed in the order you open them, which may not always be what you want, so Firefox allows you to drag and drop tabs in order to change a tab's location.  Yes, I know Notes lets you do that, too, and thankfully so.  Too bad XP doesn't offer a similar function for the taskbar.

Anyway, the neat trick I've just discovered for Firefox expands on the tab reordering feature.  You can actually drag and drop tabs from one Firefox window to another.  That's just cool (and handy when you need to see the content of two tabs simultaneously).

Not sure I want to take collaborative strategy lessons from someone that retracts salutations.

After recently reformatting an old laptop I use to access the home network, I needed to install the drivers for my tried and true HP LaserJet 4050.  Yes, it's named Barney; in honor of the Simpson's character, not the dinosaur.  Anyway, after a quick search of the HP support site for drivers, I was provided with a host of options, including the specific driver for the printer (last updated Dec 2003) or the shiny new "Universal Print Driver" (updated Nov 2008).  I second guessed my gut instinct and installed the shiny new all encompassing driver of all drivers.

And...

The catch with using the file transfer feature in Sametime is that there are two types of file transfers:  "client-to-client" and "through the Sametime server."  The default policy causes the client to use the client-to-client method and will not fail over to the other method if the latter does not succeed (and doesn't give the indication to the user if the file isn't going to route; leaving them with the opposite of the warm-fuzzy feeling).

Here's how IBM explains it:  If you enable "Allow client-to-client file transfer" and two users are unable to transfer files client-to-client, the file transfer does not automatically change to file transfer through the Sametime server. The file does not get transferred.

Too bad the client can't attempt to send a test packet and quickly warn a user that their client-to-client file transfer isn't going to work... or fail over to the alternative method... or present them with some other indication of what's going on... or...

Even if client-to-client transfer works in your environment, you might consider changing your policy to use the other method.  Your local paid-paranoid IT security manager will probably flip with the realization that files passed client-to-client are not logged.  (I know, neither are transfers via usb drives, and CDs, and...)

So, without further ado, here's how to prevent client-to-client transfers (destined for failure or not) and enable transfers through the server (set the other related settings you'll see in the following menus to match your needs):

1. Log in to your Sametime web site as an administrator.
2. Click "Administer the server."
3. Click Policies.
4. Click the user policy whose members you want to allow file transfers.  For this example, I'm editing the "Sametime Default Policy."
5. In the "Community Services" section, verify the "Allow file transfer" box is checked.
6. In the same section, verify the "Allow client-to-client file transfer" box is unchecked.
7. Click OK.
   
8. Click Configuration > Community Services.
9. On the "Community Services" tab, "Server Features" section, verify that "Allow users to transfer files to each other" has been enabled.
10. If you made changes to the Community Services settings, click Update and restart the Sametime server for the changes to take effect.

Sure this is pretty much straight out of the Lotus Sametime Info Center, but it isn't the easiest thing to find and solve if you don't know what you are looking for and how the client behaves by default.

Technote 1329103 (published yesterday) indicates that copy-style compacting in 8.0.2 can cause database corruption.

Thankfully, I haven't (knowingly) had the pleasure of encountering said situation, but there is a heck of a good chance I could have considering the number of ODS upgrades I've performed after upgrading servers to 8.0.2.

Hopefully the hot fix (only acquired after contacting IBM) will be included in the upcoming 8.0.2 FP1 (Estimated release date: January 2009).  The r5fixlist doesn't show anything, yet, regarding 8.0.3 or SPR# WTUZ7EEL85.

If you've encountered the following error message:

"You cannot enable your out-of-office notification because your mailbox has exceeded its quota.  Choose Tools > Quota Information for quota details and tips on decreasing your mailbox size."

...and you don't have a quota set on the database that is complaining of the problem...

It's an ACL issue.

-

Credit to Obinna for posting the answer in the ND8 Forum.

Technote 1266681 explains the issue and resolution, but it does not list the speciffic error message, so I was only able to find the technote after learning the solution.

-

Note that this problem only occurs when Out of Office runs as an agent; yet another good reason to configure Out of Office to run as a Service.