Search Engine Hits for October

troubleshooting regular domino server 6.5.4 crashes - I don't know if any crashes are "regular"
0x0244 database semaphore - I believe Lotus has corrected this in 6.5.4 FP2 and 7.0
654 fp1 - Good fixes, but FP2 is out now
7100g screen - Plastic scratches somewhat like the Nano
acual video of janet jackson - I had to search that too - she had a "hit" from my graduation year
alias season 5 - It's been a GREAT season
always bridesmaid bride - That would be Moody
amount given to hurricane relief by southern baptists - Thanks to SBC - a good amount was donated!
b6000901 - Same answer as before - SLIP the LIC. Sorry…
b6000901' 'src' -
blackberry 7100g - It's been a good phone. Check out the 8700c!
blackberry 7280' 'speakerphone option' - N/A on 7280
blackberry version 4.1' - Looking forward to it
chris blog 'domino web access warning' - Wow, they're putting my name in the searches now. I feel special!
chris 'domino web access warning' -
chris whisonant -
cwhisonant.blogspot.com - Type that in the address bar and not the search window
cwhisonant.blogspot.com\2005_09_01_cwhisonant_archive.html - The specific page you're probably searching for on that link has been taken offline
dancing girls - It was a Lotus release thing - stop searching for that stuff here!
debug_tcp_all -
differences between updall and fixup - How much time do we have?
dltdomsem - You can call Lotus Support to get this command
domino 6.5.4 linux jvm problems - Ouch!
domino 6.5.4 system requirements' -
domino 7' 'administrator client' linux - You can use Webadmin with Firefox on 7.0 Servers - it's great
domino 7.0 comments - Personally, I think it's great! DDM and Fault Analysis…
domino fixpack 6.5.4 iseries apyptf - Remember to LOD first
domino web access warning refresh dismiss 6.5.4 - DWA errors are not fun. Hopefully my FAQ is helping
domino web access warning unable to process 7.0 -
domino web access warning' 'unable to process your request' 7 -
domino web access warning. Sorry we were unable' -
how domino transaction logging works - It's a complicated concept
illegal immigrants sued' won - Yep, they won somehow
im_show_status - Use this to disable Presence Awareness
install sametime on linux box - I haven't done this, but it's possible
installation lotus 'domino 7.0' windows hangs - Haven't tried upgrading Windows Domino server yet.
iseries 270 dst -
iseries and logs - Logging is a good thing
journal of the whills -
lost books of the bible - Again, there are none
lotus notes 6.5 easter egg - I'm still trying to figure out the webadmin egg for 7.0!
lotus notes 6.5.4 - 79% of my clients are at 6.5.4 or 7.0
lotus notes error message - Can you be more specific?
lsxodbc v5r3 - Make sure you have the latest CUME, Hiper, and DB PTFs
mozilla hostinfo.js -
nlnotes cpu time -
notes 6.5' easteregg -
notes 6.5 updates -
notes nsd - Set up Fault Analysis - blogged about it on 10/31/05
nsd error blackberry -
nsd.lotus' -
oil after katrina - It was ridiculous, huh?
originalmodtime lotus - This field has to be updated with current date via save on Policy and Settings documents
page cannot be displayed inotes lotus notes faq -
pub. l. 108-187, s877 - CAN-SPAM act, what a waste!
rock hill sc high school football - Rock Hill is good but Northwestern is not this year
sametime.ini -
scott wenzell - Whitecross! Awesome!!
script 'im_show_status' -
set config debug_capture_timeout' -
shortage of oil -
src code b6000901 - See above - SLIP the LIC
storyofnotes.wmv - Nice video, huh?
suretype t9 predictive - I like the BB 7100g SureType, but T9 is good too
upgrade to bes 4.1 - I believe you have to buy the upgrade
upgrade to lotus 6.5.4 - Go for it - FP2 is out, so get that loaded
use60htmlcode=1 -
v5r2 b6000901 -
waiting for frwsem - Should be fixed with 6.5.4 FP2 and 7.0
waiting for frwsem 0x0244 database semaphore' -
what does 'foot-in-mouth' mean? - Check wikipedia
whats your star wars name - Chrwh Prroc
workstation hardware services' - Yeah, these people kept spamming me…

Hotfix Coming for Domino 7.0.2 HTTP Issue

Cliff's Notes: I'm going to load a Domino 7.0.2 hotfix, an STLINKS hotfix, and Sametime 7.5 CF1! Talk about a patched system...

I will (hopefully) be receiving a hotfix tonight for the http issue with Domino 7.0.2. IBM was able to package a fix for the System i today and I'm awaiting an e-mail with information on how to get it.

Meanwhile, after going to 7.0.2 on my cluster and production mail servers IM from Domino Web Access "broke". A couple of weeks ago I received "Hotfix #16" for STLINKS. After upgrading Domino to 7.0.2 I have to reload those files. Basically you have to reload stlinks.jar and stlinks.js and all language files in the '/[Domino Data]/domino/html/sametime/stlinks' directory as well as the STLinksSA.jar file in the location of the executables. On the System i, it is in '/QIBM/ProdData/Lotus/Sametime' directory. The symptoms are that when you send or receive an IM the chat window is blank. I've just loaded this and it's fine.

Also, I will be loading Sametime 7.5 CF1 onto my production IM server. It was fine on my test server (but so was Domino 7.0.2...). At least I can back out of CF1 more easily than 7.0.2! I'm applying it as I post this.

Now Playing: "Shout To The Lord" by Ruben Studdard (Hey, it was in LAUNCHCast's station)

I'm Not Sure What To Hate - Lotus, Spam, or Stupid Politicians

Please forgive me for the rant that is about to take place - I'm really going to be civil about it. But I'm really having issues dealing with the myriad of Domino Web Access and/or HTTP problems that have been introduced with every Lotus release in the past couple of years. The latest is dealt with in SPR BRIS5TXQJU and is occurring in Domino 7.0.2 FP1. Basically, a user gets a spam email with an image and they try to forward it or reply to it. OK, the replying is just lunacy, but I can see how it's possible that one would forward a junk message to an administrator to show them the junk that got through. Reading the spam is OK by the Domino http task, but when you reply to or forward it, the image is placed in the server's memory and this is where the entire server is halted! Who cares if Domino is secure and can escape viral outbreaks if you can't access the server. And this didn't even start happening with a major "dot zero" release. It happens in a fixpack. And it's happened to my server 5 times today!

I can deal with a couple of crashes every now and again, but we're talking about multiple crashes per day! And it's not just me. And it's not just this latest Fixpack. If you've read my blog long enough, you'll know that the major Domino problems I see are related to the HTTP task and/or DWA. I have posted about HTTP crashes (sometimes 8-10 per day) with Domino 7.0, 7.0.1, 7.0.2, and now 7.0.2 FP1 with a hotfix that was made to keep my prior 7.0.2 issue fixed. And I did go to 7.0.2 FP1 knowing that this could happen and that reverting would be easy. So tonight I will be reverting back to 7.0.2 and loading my stable hotfix. Lotus Development is working on a fix for this that I will probably load another night this week or this weekend.

And I wouldn't have even been so trigger happy to load FP1 had it not been for this whole DST fiasco that our wonderful politicians have gotten us into! Even Al Gore's home energy usage is 20x the usage of the average household (actually 15x more than my household)! And he's calling us to be green and is going to make us change our DST! Sorry, I digress...

So I've listed 3 things to "dislike" right now. Lotus http because of bad dealings with spam due to a rushed apply of a fix (per Lotus support - it's all over their websites!) to aid in the transition to new DST rules because of a ludicrous energy bill. What's even more ludicrous is that it would appear that I agree with Senator Clinton on the fact that the bill will be a failure!! What's happening to me?!?

Well, in 20 minutes I will be watching 24. My cable better not go out!!

HTTP 1.0 and Domino 7.0.2 (New notes.ini Setting)

Lotus has re-worked the caching for HTTP 1.0 in Domino 7.0.2. So, if you have DWA users who have HTTP 1.0 enabled, keep an eye out for issues. To determine if this updated cache mechanism is the issue, you can enable a new setting in your Domino 7.0.2 server's notes.ini:

iNotes_WA_PreferWebEngineCacheControl=1 - This will revert the HTTP 1.0 cache behavior back to that of Domino 7.0.1.

Now Playing: "Some Things Never Change" by Bride

Technorati: Lotus Domino

A Sampling of Notes Domino 7.0.2 Fixes

Looks like it should be out in September. Here are some fixes that we may have seen at my site or could benefit from.

http://www-10.lotus.com/ldd/r5fixlist.nsf/Public?OpenView

SPR# RWAH6HPQ8B - This iSeries specific fix allows daylight savings time and standard time changes without recycling the Domino server. (Me: It's about time for this one - I always have to end and restart the Domino servers on iSeries because they will lock up when the time changes.)

SPR# MHOL6J7QYH - Failover did not work when the primary server was down. This regression was introduced in 6.5.5.

SPR# KYOE6M37ES - Fixed a Microsoft Internet Explorer freeze when trying to download an attachment which contained '?' in the file name.

SPR# FMWI6MBM6M - Fixed a problem that an attachment could not be downloaded if it contained a backslash in its name."

SPR# DWHR6PQCT4 - When choosing not to install the DWA 7 Control (ActiveX), the user was constantly presented with a warning of this. This change of behavior occurred due to the new ActiveX block support in IE 6 SP2. Without offering a way to continue to use the ActiveX on a subsequent page, there is now no way to ever install the ActiveX. Answering affirmatively that you want to continue to try to use the ActiveX allowed the user to then click the blocked ActiveX bar and install the ActiveX (which refreshes the page).

A new Notes.ini, iNotes_WA_ConfirmBlockedActiveX=0, has been added in 7.0.2 to disable this confirmation box. This setting results in the inability to install the DWA Control from normal DWA view and document pages. However, the DWA control may now be installed from the DWA Preferences page, within the Basics panel!!

SPR# DPOL6LMEBW - A scheduled agent running on AS400, which entered an infinite loop, would not terminate when the "Max LotusScript/Java execution time" limit was reached. The agent would continue to run indefinitely. This problem has been fixed in 7.0.2.

SPR# MKAA677PAK - Updated the Rooms and Resource Manager task (RnRMgr) to take a new command line parameter of "-?" (or "/?"). This paramter will cause RnRMgr to print out a description of all of its supported console commands and a brief description of what they do.

SPR# LMEF6MXLXZ - Open collection always reads from server - does not make use of cache.ndk. This problem was a regression introduced in 6.5.5 and 7.0, and fixed in 7.0.2. (Me: This could be why view performance has been seeming really slow - opening the views wasn't making use of local cache apparently!(

SPR# TKIE3ZA457 - This fix resolves the issue of replication problems when a user sends a message to themselves from a mail file replica which is not on their home server and keeps a copy in the Sent folder.

SPR# GPKS63AGBN - Fixed a problem where performing a Design Replace, always disabled the Out of Office Agent. This regression was introduced in 6.5.2.

SPR# MPAA6JZKAZ - "Contact","Of" and "Phone" fields are blank in Phone Message when "To" field is not filled first and "," is pressed. This problem has been fixed in 6.5.6 and 7.0.2.

SPR# EHET5TDP2U - Fixed a crash on the Macintosh client with over 1000 fonts installed. This regression was introduced in 6.0.

SPR# BSPR67HN6W - Using a server based, Notes.ini variable (ADMINP_EXCHANGE_ALL_UNREAD_MARKS = 1), this fix will allow the exchange of unread marks when the Administration Process based replication is used to create and populate a replica between servers. Please note that the amount of time to perform the initial replication by the administration process will increase due to the additional work required to exchange all the unread marks.

SPR# EFEN6LVQMD - @Error was returned if @DBLookup returned data more than 64K bytes long. Prior to this regression, @DBLookup was allowed to return data that long, but the result of the formula couldn't be longer then 64KB. This fix repairs the problem, which was a regression introduced in 7.0.1.

Note: "A fix for this SPR has been developed but is currently undergoing testing. IBM reserves the right to remove this fix from the targeted release if it does not pass quality assurance tests. Please consider this information to be provisional. Do not base irreversible business decisions on this information until this notice has been removed."

Now Playing: "The Great Nothing" by Spock's Beard

Technorati: Lotus Notes, Lotus Domino

My 2006 In Review

2006 was mostly a great year for me. One of the major highlights was in January when I was able to speak at Lotusphere 2006 on "Domino for iSeries Administration Best Practices" My other speaking engagement came in September at the COMMON User Group Conference on Domino Domain Monitoring. Both of these times I co-presented with Kim Greene - a true Domino Diva! I went to one other conference in March, but it wasn't tech-related. It was "Thirsty" - an awesome Christian worship conference. We are planning on going again in May and I just found out last night that a guy who lived in my house in college will be going too. We, unexpectedly, got to hang out some last night - so that was great since it's been a while since I saw him.

Anyway, I will try to put together some coherent thoughts together below related to what I've blogged about this year. There has been a lot of things happen that I haven't blogged. For instance we have some great friends from church (I actually went to college with them before they were "them") who are now a military family. He signed up at the end of 2005 and is now a Lieutenant. They'll be moving later this year and will be sorely missed, but they have a higher calling both nationally and spiritually!

I could probably ramble some more about some of the great friendships I cultivated at Lotusphere. All of you bloggers are great and I'll miss you later this month - have fun at Kimono's!! But, here we go...

Things I Received
- On May 2, I got to enjoy a great family trip to Disney and received the joy of taking a 2 1/2 year old to Disney! It was awesome!!!
- On May 29 I finally got a Gibson Les Paul! I'm still loving it! I just need a tube amp now...
- The next day I became an uncle! He's such a cute kid and is (sort-of) crawling around now.
- Then on June 21 we found out that we are having another child! And it's a boy - Oliver Thomas

Things I Lost
- Starting in February I set out to lose some weight. By June I had lost 14 pounds. But I've fell off the wagon since then and gained about 6 of it back. So I'm lighter than I was last year, but plan on going back to the cross-trainer. I did go Saturday.
- On November 5 I lost my Aunt Cassie and then on December 19 I lost my "Nanny". It has definitely been a long couple of months for my Dad's side of the family since he and his 6 remaining siblings have lost a sister and their mother. I just want to thank all of you again who have offered your encouragement and support through these times.

Sports
- I'm not a huge sports fan, but I love Gamecocks football!! This year we beat our arch-rival Clemson and also won our first December game since 1960! We've won some January bowls since then, though, so that helped out with that number in our minds.

General Lotus Stuff
- At Lotusphere I passed my first Lotus Development exam (623). At COMMON I passed the Domino for iSeries Technical Solutions exam. Then in October I updated my 6/6.5 Domino Administration certification to 7.0. I still have one more exam to take for the "Advanced" certification (PCLP).
- In August, I posted about how to drive site traffic in the Lotus community. I plan on trying to keep that up this year with end-user/administrator perspectives on new technologies from Lotus that affect me. The graph in that post shows up through July - I posted in June about the Sametime 7.5 client being (prematurely) available in Beta 2 and the next month I was the first to post some screen shots and thoughts about the newly available Notes Client for Linux. What the graph doesn't show is the affect of my lengthy post the last day of September on Lotus Notes NOMAD. That one actually increased my October site traffic about 33% over the previous high in June.
- As an aside, my most popular Google search is for my Domino Web Access Warning post. I would like to see that number decline due to Lotus working harder to prevent that error. Looking at my post, though, you can see that a ton of things can potentially cause this.
- Also, I have been working on reviving the Charlotte Lotus Notes User group with Susan Bulloch, Brian Good, and Mike Robinson. We didn't have a meeting in 2006, but I'm hoping that we get one in 1Q 2007!
- For Show-n-Tell Thursdays I posted 17 times! It was a mixed bag of development and administration.
- I have upgraded to some of the latest releases as well. We moved our Domino servers to 7.0.1 and then to 7.0.2. We had some major issues with 7.0.2 - see here. But it's all good now. I still have 3 servers to move to 7.0.2 and will probably do that really soon. I also upgraded to Sametime 7.5 - that was a breeze!! All of our Notes Clients are at 7.0.1 or higher. I will probably get Chris Moody to push out 7.0.2 quickly this month.

Domino 7.0.2 on iSeries and Time Changes

As I briefly mentioned in the past, there was supposed to be a fix for the Domino software to allow for OS time changes without hanging the Domino server(s). This fix is in SPR# RWAH6HPQ8B for Domino 7.0.2- This iSeries specific fix allows daylight savings time and standard time changes without recycling the Domino server.

I just want to say a huge thank you to IBM for this. I have upgraded 3 of my cluster iSeries Domino partitions to 7.0.2 and they didn't have any problems with the time change this weekend. Now to get to my production partitions...

Now Playing: "Solid As The Sun" by Neal Morse

Technorati: Lotus Domino, iSeries

Notes 7.x Smart Upgrade Changes

I am now starting our Notes 7.0.1 upgrades. There was an option in the Smart Upgrade kit that I did not have selected properly. This is new for the Domino 7.0 Smart Upgrade template.

In the kit there is now a yes/no field titled "Release 6.5.4/6.0.5 or previous?" If the source Notes version is in the 6.x range, this must be "Yes." Likewise, if the source Notes version is in the 7.x range this must be "No."

On top of this, if the source version is 7.x, you must also choose the "Install Type" of "Notes client only" or "All Client (Notes client, Admin client, Designer)".

Another update: It also appears that the issue with the client configuration wizard prompt for multi-user installs may be technically resolved. It appears that going from 6.x to 7.0.1 will work. Upgrading from 6.x to 7.0 gives the configuration wizard prompt. Then, subsequent upgrades from 7.0 to 7.0.1 will cause the prompt as well.

The issue is with a registry key that 7.0 doesn't delete. From my understanding, the key will be properly deleted going from 6.5.x to 7.0.1, but if you had upgraded from 6.5.x to 7.0 and later upgrade to 7.0.1 the key will still not be deleted.

Now Playing: "Entrance" by Neal Morse

What To Choose For New Sametime Installations?

On a Domino for iSeries List to which I subscribe, the question was asked if one would recommend going to 7.0.3. Is it stable on i5 V5R4 yet? The question was asked in relation to running Sametime 7.5.1 CF1 and not having to use the 7.0.1 jvm with the 7.0.2 server code. I hope you find my reply amusing...

7.0.3 is a major bug fix release. If you're planning on a Sametime upgrade or install, I would load up 7.0.3 just so I don't have the hodgepodge of Fixpacks, Hotfixes, Hacked older versions of Java, and convoluted template installs (for DWA/DST/IE7) that are necessary to run Sametime 7.5.1 with Domino 7.0.2 FP2 HF145-9er (10-4?).

Come to think of it, 7.0.2 FP2 seems to have been an extremely crippled piece of software - with all of the hacks and fixes you have to apply to make it "stable"...

I sure hope IBM doesn't get into the 7.0.2 situation again with all of the patches eventually necessary for it to be stable.

Anyway, since I brought up i5/OS - are you planning for your V6R1 upgrades yet?

Domino 7.0.2 for System i - New WRKDOMSVR Options

For you System i folks out there, there are 3 new options under F23 for the WRKDOMSVR command. I have only loaded the release - I have not upgraded any servers to 7.0.2 yet. The new options are:

14 - Work with support files - This opens the IBM_TECHNICAL_SUPPORT directory.
15 - Work with NSDs - This opens the IBM_TECHNICAL_SUPPORT directory and only displays nsd* files.
16 - Dump server call stacks - This will create spooled files for each job running in the particular Domino partition.

It's great to have these options right from the server management screen! I just have to remember the numbers now...

As a side note, before you load the QNOTESRL savf, make sure that nobody is using the WRKDOMSVR command. The panel group objects may not get updated correctly. I had to redo my install of the Domino release files because I was receiving an error when doing WRKDOMSVR. This is not something specific to Domino 7.0.2, though, as others have had it happen on previous versions.

Now Playing: "Be The Quiet" by Disciple

Technorati: Lotus Domino

Lotus Notes and Domino 7.0 Beta 4

I have a test mule PC (600 MHz PIII) running RedHat Linux 9 (Shrike) and Domino 6.5.4. I downloaded the 7.0 Beta 4 today and attempted a straight upgrade (didn't read instructions...). It went fairly well, and I noticed that the installer now has a text-based "status bar" showing the completion percent - which was a pretty handy addition.

I was told by the installer that Domino does not support Shrike. Guess I'll have to peruse the readme and see what distro I need. Hopefully it's at LinuxISO.org.

As a side note, I had G Simmons (not gene!) upgrade from Notes 6.5.4 to 7.0 Beta 4. He instantly noticed a performance improvement in navigating his 6.5.4 mail file. Hopefully we'll see others giving the same feedback. I'm considering SmartUpgrading our IT department although I can't personally upgrade because of Development. I'm curious to see if I get any more positive feedback. Just today our PC Support manager was asking me if there had been improvements made to the DWA client in 6.5.4. I told him that there were many improvements and he said that he could definitely tell when accessing via his cable modem.

Scalability and ROI is what we've been seeing with the latest releases of Notes and Domino. There are supposed to be some performance enhancements with the 7.0 Domino iSeries code as well. I love a product that will allow you to leverage current hardware and software investments. I won't mention Exchange upgrades (they call it Exchange because you exchange out your current server and OS platforms for a newer investment...)

BES 4.1 Upgrade (and Downgrade)

Judging by the title, you can probably tell that my upgrade was unsuccessful. Let me do a recap (as much for me when I call RIM tomorrow as for the readers).

First of all, I thought I would just upgrade Domino from 6.5.4 to 7.0.1. No problems with the Domino upgrade (as usual). So then I got out my BES upgrade checklist. I should have stopped when the configuration database could not be backed up using the BlackBerryDBBackup.exe command. I was getting a C++ error. I pressed on since we are using a SQL backend and it is backed up regularly. So I proceeded with the BES setup.exe.

I chose to install the full package of BES plus MDS. None of the documentation stated that TWO additional SQL databases would be created (MDSS and MDSS_DIR). This is in addition to having to update the current BESMgmt database. I was able to successfully update the BESMgmt database and then it was to the point of rebooting. After coming back up, the setup program continues.

It was at this point that the two new MDS databases would be created. My SQL user account already had the required SA (Server Administrator) and DB Creator authority as noted in the upgrade manual. After successfully creating the MDSS database, I received an error stating that the database could not be updated. In the BES logs folder, there is an Install sub-folder with installation logs. Looking at this I could see that the problem was that the SQL DB_VERSION table in the MDSS database could not be updated with an INSERT of the new version data. So I paged our Network/SQL admin group and got someone to look at the database. Come to find out, the DB_VERSION table didn't even exist! I'm glad the install program created it properly... Back to the story, I had the SQL admin manually create the table AND give me owner access to all of the other tables. It seems that the install program didn't grant that authority either! Then I was able to INSERT the records for the version and proceed with the setup.

After this, I get to the next to final option. Two more clicks and I'm home free and should be able to get Sametime working (since we have a need for that, hence the upgrade). So I'm at the point where the install program is going to need the location of the Microsoft SQL Server 2000 (or 2005) Driver. I didn't have the driver installed, but the installer gives you the location for download. After downloading and installing the driver, the installer cannot find the DLL. I think that possibly a restart would be in order, so I do that and come back to the installer. It still cannot find the file. I uninstall the SQL driver and reinstall it to the D: drive where my BES is installed. It's a no-go! The installer apparently cannot find a file that exists on the system!!

So after this, I was basically dead in the water. I would have to downgrade to get it working because for some reason I don't have weekend support (the things done to save a buck...). So I uninstalled BES 4.1 and was going to load BES 4.0. Can anyone guess what happened? I didn't have (nor could I find) a full installer for BES 4.0 SP3 that supports Domino 7. So after loading BES 4.0 I got an error stating that the notes.ini could not be located. So I just installed Domino 6.5.4 over 7.0.1 and then ran the BES installer again. During this install, it found that the BESMgmt database was at a "Pre-4.0 level" and could not proceed. So I call my SQL guy again and he sees that in the BESMgmt database there is a ServerDBVersion table that has a record for 4.0 and 4.1. So he just removes the 4.1 record and the installer was happy. Things came up fine and I loaded SP3 for BES to be fairly up-to-date. Now my BES is active but still at 4.0...

To do this week:
- Find a full installer for BES 4.0 SP3 so I can load Domino 7.0.1 and not have to downgrade Domino later.
- Find out why in the world the BES 4.1 installer couldn't find the SQL driver!! Not happy about that!
- Find out where my SQL guy wants to go to lunch because I owe him!

Search Engine Hits for August (So Far...)

6.5.2 'insufficient memory' 'index pool is full' on Google
6.5.4 domino web access warning sorry we were unable to process" on Google - get a lot of these, hopefully my little FAQ is helpful!
'6.5.4 fix pack 1'" on Google - Not here but IBM has it somewhere...
b6000901 on Google/MSN - Get several of these hits too - hope people aren't mad that they have to slip the LIC
blackberry '7100 g' ringtones on MSN - Love this smartphone - way to go RIM!
blackberry 7100g 7290 on Yahoo - 7100g is better
blackberry pros cons on MSN - pros - it's not running Windows! =)
can-spam act of 2003 (pub. l. 108-187, s877) on Google - what a joke...
'chris moody' mensa" on Google - see above - lol sorry Moody!
country song/'do you want fries with that' on MSN - get a lot of these hits too - prompted by Ed mentioning the phrase on his site
coworker on vacation office on MSN - I don't condone doing anything to coworkers offices! ;)
debug_tcp_all on Google - Sorry you're having to debug too...
debug_threadid on Google Again, see above
desktop6.ndk on MSN - Just delete it
dltdomsem on Google - A command that only shows up at my blog - not even on IBM's sites...
do you want fries with that on MSN - many iterations of this below too
do you want fries with that? on MSN
domino 6.5.3 - nsd dump set up on Google - I wish I could read NSD files better, but getting there
'domino 6.5.4' and 'lotus instant messaging' and 'iseries'" on Google - You've found the spot - I'll help where I can
domino 6.5.4 fixpack 1 on Google - Works well for me and fixed my Domino 6.5.4 issues so far!
domino stmux on Google - Lotus Support says they've been getting more calls about this - you better check with them.
domino web access warning sorry we were unable on MSN - Many more iterations of this
domino web access warning on MSN/Yahoo
'domino web access warning. sorry we were unable to process your request at this time.' on Yahoo
domino web access warning. Sorry, we were unable to process your request at this time. if you are unable to continue working in your mail file, please dismiss this warning and then select view, refresh from your browser's menu on Google - WOW, they searched the whole string...
download sametime 651 fp1 on Google - I believe it was finally ready for prime time!
im_show_status on Google - Nice hack here to change this globally with Desktop Settings documents.
'index pool is full' on Google - That's not good
inotes 'domino web access warning'" on Google
iseries b6000901 on Google
lotus domino 6.5.4 fixpack 1 (fp1) linux install on Google - Yeah, I installed this and it was OK. I'm running 7.0B4 on my Linux box now
lotus domino iseries delete semaphores on Google - I have you covered!
'lotus notes domino 6.5.4' system requirements on Google - Better check with IBM
nif global pool on Google - I think there were some issues with this and 6.5.4
'nif global pool'" on Google
originalmodtime on Google
passing the mensa test on MSN - Don't ask me! I haven't passed it (yet...) LOL
performance notes lotus 'cache.ndk' symantec on Google - Make sure your Symantec AV isn't scanning Notes b/c it makes everything SLOW...
prohibit running activex controls sametime on Google
'sametime 6.5.1 fp1' on Google - Still hasn't fixed my STMUX issues. IBM is making an STMUX trace fixpack for me
sametime 6.5.1 video .wmv on Google
server error: insufficient memory 6.5.4 iseries on Google - Better buy some more memory from IBM! Or just use the DLTDOMSMEM and DLTDOMSEM commands
song do you want fries with that? on Yahoo
stmux crash on Google - Still crashing
stmux debug on Google - Still de
the song-do you want fries with that on MSN
use60htmlcode on Google - This is a notes.ini entry apparently reverts the html fixes in 6.5.4 to the older code.
user inotes warning sorry we were unable to process your request on Google
zzyzx on MSN - Hope Zzyzx hasn't seen my post - I was a little livid that day...
song do you want fries with that? on Yahoo

71% of Servers and 97% of Clients at ND 7.0.1

I (finally) upgraded our production application and mail partitions to Domino 7.0.1 on Saturday night. All but 2 of our Domino servers are at 7.0.1 now. I'm holding off on upgrading the Sametime partition to 7.x since we only use it for chat and there are no major benefits at Sametime 7.0 for us. I may even hold off until Sametime 7.5. And I'm still holding off on our BES 7.0.1 upgrade because of the fiasco I had last time I tried upgrading the BES from 4.0 to 4.1. But so far, so good!

Now Playing: "Blindside" by Precious Death

Technorati: Lotus Domino

Server Update

Sametime 6.5.1 FP1 for iSeries - I'm still having my STMUX crashes. Development is seeing that an exponentially growing large number of connections is causing the STMUX task to go over the bounds of an array. This is what's causing the STMUX task to crash (thus causing the server to hang).

Domino 7.0 for iSeries - I have scheduled to upgrade our production iSeries this Friday evening to Domino 7.0 from 6.5.4 FP2. My cluster iSeries has been at 7.0 since September 29 without a problem. I have 3 DPARs and will be upgrading 2 of them to 7.0. The third is my IM server which will stay at 6.5.4 FP2 until we resolve our STMUX issue.

Snappshot - I got an email today from Rob Novak stating that Snappshot 7 is available. Snappshot is an application that collects IM logs. We tested this last year and it worked well. But we decided not to persue the Big Brother route. It was a great product that works on the iSeries. If you need a chat logging application, I highly recommend this!

Domino 8: 101 - Server OS Upgrades

In planning for Domino 8, it may be possible that you will have to upgrade the Operating System that your Domino 7 (or 6 or earlier) servers are running. For more information, see the detailed system requirements here.

In some of these cases, such as Windows 2000, this is because the Operating System is no longer supported by the vendor. However, there is currently no set EOS date for i5/OS V5R3. However, this is not a supported OS for Domino 8.

The following operating systems are not supported for Domino 8. If you are running one of these with any prior version of Domino, you will need to upgrade the OS to be in a supported configuration for Domino 8. Please note that the latest release levels of all of these platforms are still supported and that it is generally recommended to stay fairly recent on the Operating Systems in your environment. There is also no rip-and-replace involved (as with other messaging platforms) - the most current OS levels were supported for Domino 7.0. So, if you are current on your OS and current on your Domino installation, you will have no issues upgrading to Domino 8. Also, I'm in no way criticizing IBM for this move to only support the latest OS release levels - just making you aware of it for your planning purposes.

OS Platforms Not Supported For Domino 8.0:

Microsoft Windows
Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server
IBM AIX
IBM AIX 5.2(4) (64-bit kernel)
Linux
Novell SUSE Linux Enterprise Server (SLES) 8
Novell SUSE Linux Enterprise Server (SLES) 9
RHEL 4
Sun Solaris
Sun Solaris 9 (64-bit kernel)
IBM System i
IBM i5/OS, V5R3
IBM System z
IBM z/OS Version 1, Release 5 or later
Linux on System z
SLES 8 & 9
RHEL 4

Domino 7.0.2 HTTP Hotfixed

As of Friday we have been running with no problems on Domino 7.0.2 for our production mail server. Lotus worked on a hotfix and delivered it Friday for my company and "other customers clamoring for the fix." I discussed the issue here. We were getting an "HTTP crash on Locking handle when creating NMemBlock". I did test a hotfix that didn't work.

After further investigation, it was discovered that the issue was with the HTTP UserCache and how it was working with LTPA tokens in an SSO environment. Since we use LTPA we were receiving the error. It's been almost a week now and it's working well. Whew...

I don't really want to start a rant here, but the last major Domino server issues we had were when we went to 7.0 this time last year and revolved around the HTTP task. Thankfully this time the fix took a week instead of 2.5 months!!

Upgraded to Sametime 7.5 on iSeries (SnTT)

Last Friday night I upgraded our internal Sametime server to 7.5. As part of that process, I had to upgrade the the 6.5.4FP1 Domino server to Domino 7.0.1 and then upgrade ST 6.5.1FP1 to 7.5. This worked like a champ and we haven't had any issues with the server this week. It was a very smooth upgrade.

One thing that we have been waiting on to be "fixed" was the poor screen sharing capabilities of ST 7.0 and earlier. It's one reason I didn't worry about taking the server to 7.0. After testing the screen sharing of ST 7.5 on my test server, I was very pleased with what I saw. So, this was a good reason for us to upgrade. We may be able to get rid of a WebEx account. Speaking of screen sharing, we did have one ST server crash this week while holding a test meeting. I've worked with Lotus a bit on that and it may be related to the Meeting Room preference to optimize screen sharing for performance. This basically drops the color depth to 8 bit and looks pretty bad. The NSD showed a crash due to some type of conversion. I'm thinking it may be the 8 bit conversion, but neither Lotus or I could reproduce this.

Another "gotcha" that we ran into is with the DWA integration with chat. There were actually 2 gotchas. First of all, if you are upgrading the Sametime server and you have chosen to have your DWA server set to load STLinks from the DWA server, you will need to delete the domino/html/sametime/stlinks directory on the DWA server and copy over the stlinks directory from the IM server. Then restart the DWA server's HTTP task and it works! Since I could see the java console error in IE about a StartIM{} function call, I figured it was something with the stlinks jar file. I think this may be the case if you have a 7.0 or earlier stlinks folder on your DWA server.

The second gotcha is also with DWA and I haven't actually "confirmed" it. We are almost complete with an MS XP migration from Windows 2000 in our company. Since going to ST 7.5, I have actually seen that a Win2K user without the Sun JVM worked for a day with the MS VM but then their DWA chat failed and I had to load the Sun JVM. That's really odd that it would work and then fail. It appears that only Sun JVM is supported, though.

Now Playing: "Taking Notes Podcast #34" by Bruce & Julian

Technorati: Show-n-tell thursday

Potential DoS Vulnerability in Domino LDAP Server Task

I had someone forward this to me. I don't recall seeing it in the blogs, but the IBM technote was updated on 2/10/2006:

Potential Denial of Service Vulnerability in Domino LDAP Server Task

Problem:
A specially crafted bind request sent to the LDAP server port can result in a Lotus Domino server crash. If successfully exploited, this vulnerability allows an unauthenticated remote attacker to crash the LDAP service preventing legitimate usage.

This issue was reported to IBM Lotus by iDEFENSE. The advisory address is as follows:

IDEF 1173: Lotus Domino LDAP Server Bind Command DoS
http://www.idefense.com/intelligence/vulnerabilities/display.php?id=389

Solution:
This issue was reported to IBM Lotus Quality Engineering as SPR# JBUD6FMQST and fixed in Domino 6.5.4 FP2, Domino 6.5.5, and Domino 7.0.1.
Refer to the Upgrade Central site for details on upgrading Notes/Domino.

A workaround for previous releases is to limit access to TCP port 389 on the LDAP server to only allow trusted hosts to connect.

Note: This issue does not affect Domino servers that are not running the LDAP server task.

Now Playing: "12" by Neal Morse

Domino Web Access Warning

I first posted this as a help file from my internal FAQ. The most recent update is for a specific DWA 7 error. This post generally ranks high on my search engine hits, so I like to keep it updated from time to time. Hopefully it's helping people get these issues resolved. If you know of a resolution that's not listed, please let me know! This first entry is one that happens pretty frequently. An alternate title could be "iNotes Warning" from previous versions. This document contains two sections. One is a general information section and the other is a section on steps to correct the error(hopefully). Please see the bottom for a change log.

General Information:

The full error message is:
"Microsoft Internet Explorer Domino Web Access Warning. Sorry, we were unable to process your request at this time. If you are unable to continue working in your mail file, please dismiss this warning and then select View, Refresh from your browser's menu."

In Domino Web Access (DWA) 7.0 and higher, I have been seeing a new error message that reads "The installation of Domino Web Access 7 Control has been blocked or declined by the user. Do you want to use this on subsequent Domino Web Access pages?" A specific correction for this can be to ensure that the user has at least Power-User authority. Another possible correction is to simply add the DWA server to Internet Explorer's Trusted sites zone.

IBM has recently updated two technotes regarding this:

Prompt: 'Installation of Domino Web Access 7 Control has been blocked by the user. Do you want to use Subsequent Domino Web Access Pages?'. This alludes to the DWA7w.cab file being moved or corrupted on the DWA server or even that the default HTML directory has been changed from domino\html. I have notified them that in my experience, this may come up when the DWA server isn't in the trusted sites zone for IE.

Can the Domino Web Access ActiveX Upload Control (iNotes Class) be manually placed on a workstation? While not directly related to the error message, this contains a table of the behaviour of DWA with and without the ActiveX control installed.

Corrective Actions:

Recently, the top two on the following list have been what we have seen internally to cause more issues. If the computers are external (employees' home PC), then I would definitely bank on them having spyware.

- Disable Pop-Up blocker
- Clean up spyware (use application such as Spybot and/or AdAware)
- Add DWA server to Internet Explorer's Trusted Sites zone (this may be a good idea for any other intranet servers or via an Active Directory policy)
- Clear out Java Cache by running C:\Program Files\Java\jre1.5.0_0X\bin\javacpl.exe
---Click “Delete Files” then click “OK”.
---*if there are different versions, do this for each version or uninstall older versions and leave only the newest copy.
- Clear out Windows temp folders.
--- C:\Temp--- C:\Documents and Settings\USER PROFILE\Local Settings\Temp
--- C:\Documents and Settings\USER PROFILE\Local Settings\Temporary Internet Files
--- C:\Winnt\Temp
--- *Clear out the Temp/Temp. Internet Files for each user listed in the Documents and Settings folder.
- Reset IE to default settings.
--- Right Click on the Internet Explorer icon on the desktop or go to Control Panel and open Internet Options.
--- Click on the Programs Tab. Then click the Reset Web Settings button. Uncheck
“Also reset my home page” then click “OK”.
- Tools > Internet Options > Advanced > Disable "Use HTTP 1.1" (you may need to enable it because sometimes IE just doesn't like the setting. I have actually seen it start working by enabling this option.)
- Tools > Internet Options > Advanced > Disable "Do not save encrypted pages to disk"
- Download the MSXML 4.0 SP2. This link will get you to the download. I selected the msxml.msi.
- Clear Browser Cache
- Delete iNotes or Domino Web Access class file
- If one is currently installed, upgrade to the latest Sun JVM
- Windows Update (also verify that a recent Windows Update has not broken this!)
- Load Convert, Fixup, Updall, and Compact against the mailfile
- Reboot
- Defrag
- Run a tool such as Symantec/Norton WinDoctor

Change Log:
08/14/2006: Added information regarding Java Cache, Temp Folders, and Resetting IE defaults.
04/14/2006: Added information regarding technotes 1228480 and 1161877.
Added comment to Windows Update line to state that a recent update may be causing the problem. I have personally seen this in 2004 and the link in the text above is from April 2006.