Author Archive


January 18th, 2009 No comments

JSON (JavaScript Object Notation) looks pretty cool, basically a way to standardize data layout so JavaScript can work with it. Also like it because it uses dot notation.

AJAX (Asynchronous JavaScript and XML) is a set of extensions to JavaScript that allow it to do cool, client-side stuff that allows manipulation of the on-screen page with little or now trips back to the browser.

JQuery ( is a JavaScript library that lets you easily do all the JSON stuff in an AJAX-enabled browsers with some quick library calls.

Categories: Domino, Uncategorized Tags:

At Lotusphere

January 17th, 2009 No comments

I’ve arrived for Lotusphere 2009 in Orlando, Florida. Flight was good, but crowded (as always). Got on a shuttle pretty quickly, and got to the hotel, checked in, registered at the conference then headed to ESPN for a beer. Pretty crowded and warm in there, and I had spent the day on a crowded plane, so I headed out and got some dinner at Big River Grille on the boardwalk.

While I was there I ended up sitting next to a couple of guys from TriLog group. Before they were TriLog, they were the folks at Relavis behind their Domin0-based CRM product. We had a nice chat about the CRM market, and about how the days of dominant applications are over. Customers want to buy what they want, then used standards-based interfaces, like Web Services, to get them to all work together.

Now I’m back at the hotel room blogging, and getting unpacked.

Categories: Uncategorized Tags:

Gearing up for Lotusphere

January 12th, 2009 No comments

I’m heading off to Lotusphere 2009 this Saturday, and I’m trying to get all my ducks in a row. We’re about done with a major project, and I think I have my bases covered for my time away. I’ll have the trusty iPhone with me and a laptop, so I should be covered.

During this trip I’m hoping to learn quite a bit more about Domino 8.5 (which shipped last week), including new features like streaming cluster replication, ID vault, and AD integration (though that won’t ship until 8.5.1 or 8.5.2, there is a session on it). I’ll also poke my head in on a Portal session or two.

Since I’m staying at the Swan this year, I’m back to taking the Mears shuttle again. It will be nice to be on-site for once – first time in 7 ‘spheres!

Categories: Domino Tags:

MOSS 2007/WSS 3.0 December Cumulative Update

December 17th, 2008 No comments

The KB files aren’t up yet, but the download is available.

Categories: Uncategorized Tags:

Another upgrade!

December 11th, 2008 No comments

Not on the blog, or even at work. Just noticed today that WAS 7.0 shipped sometime last month. I only noticed this because FP1 showed up for it on WAS support recently. Guess I’ve been a bit busy, plus there’s not much I can do with it now, as all our current/future projects call for v6.1

Categories: Uncategorized Tags:

WP 2.7

December 10th, 2008 No comments

Yup, got brave and updated. Not a bad process:

Download and extract the package
Log in to my server via SSH and back up the whole wordpress directory
Remove wp-admin and wp-includes directories
Upload the files, overwriting everything
Log in, click on Site Admin then click on the Upgrade Now button.

Pretty impressive. However, this is leaps and bounds above 2.6.x – this really should be v3.

Categories: Uncategorized Tags:

WP 2.6.5

December 5th, 2008 No comments

Just upgraded from WordPress 2.6.3. Pretty painless, and seems to work fine.

Categories: Uncategorized Tags:

Step by Step, how to propagate your MOSS index

December 5th, 2008 1 comment

Quite the head-scratcher this turned out to be. In my production SharePoint 2007 install, I have search turned on and my central admin box was doing the crawling as well as being the query server. In the interest of making things a bit more robust and scalable, I thought it best to have my web front ends be query servers as well.

[Note for those of you coming from Domino-land, like me: In Domino we go to each replica of a given application and build a full-text index. Not so with MOSS, as it’s a bit smarter than that: I can designate one server to do all the crawling forĀ  a given SharePoint install (as well as external sites), then have the crawl server do a flat-file copy of the index files to designated query servers. In really big installations, you can have one or more servers doing the crawling, with one or more different servers doing the serving of those searches, or the ‘query’ function. I know, we can do that in Domino with the domain index as well, but that only really works with Notes clients. Working from a Domino-web-only perspective, I have to have this domain index created and maintained on each web server]

However, this is not as simple as just starting up Office Server Search on each WFE and checking off the query check box. This was the first problem I ran in to: If you have, as I had, a server set up both as Crawl and Query functions, the index will not propagate to the newly-designated Query servers until Query is disabled on the Crawl server. This will mean that for a time, search queries will not work if you have no other Query servers in your farm.

Once I figured out that, I apparently got bit by the proxy problem. I have a proxy server in my environment, and it is needed by us end-users to get to the Internet, but it isn’t needed by Sharepoint search, as all of the sites its crawling are internal. I had it enabled per the recommendation of one support tech, but my index files were still not propagating.

So, I had to disable it in two places: In the Central Admin GUI (Central Administration – Application Management – Search Service – Farm-Level Search Settings) and, oddly enough, I had log in to each of the servers in my farm (CA as well as all the WFE’s) and disable the proxy settings under Internet Options for the user profile associated with the MOSS service account. Seemed strange, but it sure did the trick.

So, in my case, here’s what worked:

  1. Make sure the proxy is disabled under Control Panel – Internet Options – Connections – LAN Settings for your MOSS service account on each server in the farm (though this setting on your SQL server shouldn’t matter)
  2. Make sure it is also disabled in the Farm-Level Search Settings above
  3. On your Crawl server, open the settings for Office SharePoint Server Search and make sure the box “Use this server for serving search queries” is UNchecked. If it is checked, uncheck it, then go to the Services control panel and restart the Office Server Search service. NOTE: make sure there is not a crawl going on at this time. Yes, you could use the stop/start links in the UI, but then you lose all your settings.
  4. For each of the servers you want to be a Query server, go to that server under Central Admin – Operations – Services on Server and select that server. Click on Office SharePoint Server Search and check off the ‘Use this server for serving search queries” box, then fill in the appropriate fields. Make sure the folder you designate to store the index flat files is on a volume with enough space.
  5. Back in Services on Server, click Start for Office SharePoint Server Search.
  6. Go to Shared Services Administration, SharedServices1 (where you are enabling search), click on Search Administration and check on the propagation status. You should also see files and folders under the folder you designated in Step 4, above.

That should do it. As always, YMMV, so you may need to call support

Categories: Sharepoint Tags:

Sharepoint Problems from Reboot

December 4th, 2008 No comments

Or, how I spent my Thanksgiving ‘vacation’.

In our environment, we have our Sharepoint servers using the Microsoft Rights Management Server SP2 for rights management of documents we post to certain libraries in Sharepoint. This has been working fine for months.

Last Monday night I rebooted the servers in futile attempt to get the External Collaboration Toolkit for Sharepoint installed (more on that later). This didn’t resolve that issue, but apparently caused a huge problem that ended up with me spending most of my weekend on the phone with Microsoft support. Numerous people wanted to head out of town for the Thanksgiving weekend here in the US, and had to update documents in a particular RM-enabled library; also, auditors needed to start uploading documents to a new RM-enabled library first thing Monday morning. So, Severity A ticket it is.

If you’ve called MS with a Sev A problem, you know you’re committed to being on the phone with them, or available by phone, 24×7 until the problem is resolved. Happy Thanksgiving!

Read more…

Categories: Sharepoint Tags:

iPhone update

November 21st, 2008 No comments

I am really enjoying the iPhone so far. Great interface, lots of good apps (including even one or two for business). I’ve gotten used to the keyboard pretty quick.

The first roadblock I ran in to was just activating it. AT&T did a fine job of setting me up and switching over the number, but I need to be able to connect to the iTunes store to activate the phone, which we can’t do at work because of a firewall rule. I asked a couple others about this, and they said they had to take them home to activate them. Something that will have to be addressed if we allow the widespread use of these in the company.

Apps installed so far:

Backgrounds, Coffee Finder, Constitution, Declaration of Independence, EasyWriter, Eureka, Evernote, Facebook, Free RPN Calc, Goodrec, Google Earth, Google Mobile App, i.TV, iChillout Lite, Lightsaber, Mocah Telnet Lite, Network Ping Lite, Obama Inauguration Countdown, OpenTable, Pandora Radio, PhotoWizard, Stanza, Twitterific, Urbanspoon, Weatherbug, WifiTrak, WordPress

Sadly, what is not on that list is a native Gmail client. The Google Mobile App is great, but that just comes with a screent pointing to bookmarks of the mobile versions of all their cloud apps. Nice, but the native Gmail client on the BlackBerry was pretty slick.

VPN was a little frustrating at first, but I found a workaround. Our network admin won’t let us use the Cisco VPN concentrators, so we have to use a different VPN connection that can be a bit tricky. This will be resolved when he gets new concentrators put in early next year, which will also allow users with 64-bit desktops (Vista 64, x64 Linux, future versions of OS X) to connect with a Cisco client. I still can’t believe he has to buy new hardware to allow for 64-bit client connections.

Anyway, the new phone is great, and I’ve been going to and from work with one, count ’em, just one device all week. Should be fine for day-to-day stuff, the rubber will really hit the road when I go to Lotusphere in January and spend a week away from home/work. Mind you, I will have a laptop with me, I’m not masochist.

The phone came with OS 2.0.2 on Tuesday, so I had to upgrade to 2.1 first thing, then to 2.2 this morning. Two OS upgrades in one week, yikes! However, both upgrades went quite smoothly.

Categories: Uncategorized Tags: