Windows SharePoint Services 3.0 SP1 on Vista x64/x86

This is some great news, one of my biggest criticism of SharePoint has always been the fact that you need a Server to run it on, even just for development. I’ve managed to work around this with lots of ram a collection of VPC’s with diff disks. But it looks like it’s been solved here. I’m going to be trying this out this afternoon. The next question will be if the Visual Studio WSS Extensions work with it, as they won’t install on a machine where it doesn’t detect SharePoint installed.

Advertisements

Virtual PC 2007 Service Pack 1 Released

VPC 2007 SP1 has been released, the main changes are that Vista SP1, XP SP3 are now support host and guest Operating Systems while Server 2008 is supported as a guest operating system. Download both the 64 & 32 bit versions from here, and the release notes are here.

A quick warning make sure that you shut down your host operating systems before you upgrade as the installer warns there could be problems restoring images suspended prior to SP1 being installed. There also appears to be a new version of the Virtual Machine additions which you will need to install inside your guest machine.

MOSS on Server 2003 SP2 with SQL 2000

It appears that SQL 2000, MOSS and Windows Server 2003 Service Pack 2 don’t play too nicely together. During the config the MOSS Shared Service provider there are Authentication issue’s in SQL. The good news is by dropping Windows Server 2003 Service Pack 1 appears to be tolerant in this configuration with a couple of caveats.

  1. Make all the MOSS Service Accounts Administrators on the SQL Box. These privileges should be able to pruned at a later date, but there does seem to be issues with the installation and configuration of MOSS.
  2. The MOSS configuration tool that is usually run from Start Menu will not complete the installation. To get around this run the tool from the command line using “psconfig.exe” located under the “%COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\bin” folder.
  3. After running the MOSS Hotfixes following re-run the config tool after each upgrades completes, using the “psconfig.exe” command line tool. Again the Start Menu Option will not work. Here are the hotfixes :-
    • Windows SharePoint Services 3.0 hotfix package: May 8, 2007 – KB936867
    • SharePoint Server 2007 hotfix package for SharePoint Server 2007 and for SharePoint Server
      2007 for Search: May 8, 2007 – KB936877
    • SharePoint Server 2007 hotfix package: May 15, 2007 – KB937207

I’d be interested to work out what in SP2 actually stops SQL 2000 from working with MOSS, but then again I’m not in a rush to do another MOSS job with SQL 2000.

Fixing DCOM Issues after MOSS SP1 Installation

I’ve recently done a couple of MOSS installations on clients sites, both of which have been used SP1. As usual after each installation and configuration I do my testing while checking the event long. You will notice there are several DCOM Errors that occur in the event log, similar to this one.

The application-specific permission settings do not grant Local Activation permission
for the COM Server application with CLSID
{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}
 to the user DOMAIN\Username SID (S-X-X-XX-XXXXXXXXX-XXXXXXXXX-XXXXXXXXX-XXXXX).
This security permission can be modified using the Component Services administrative tool.

From feedback I’d gotten from a few people I was expecting, and a few months ago I’d found a quick fix related to the “IIS_WAMREG” component. Simply after the install is done by going to Administrative Tools / Component Services, then expand Component Services / Computers / My Computer / DCOM Config. Scroll down until you find “IIS_WAMREG“, then right click and select “Properties” then Select the “Security“. Ensure the account that your MOSS service and the SQL Identity for MOSS are in here and they have “Local Activation” and “Local Launch” permissions (I also think that they may need Remote if you are running in other Farm configurations, but I haven’t come across these but if you find this required please leave a comment here). I found today that you also have to make the same change to the “OSearch” component.

I thought I’d throw in a hint on exactly how to work out which is the component is annoying you. Each of the Component’s is referred to as a GUID, so all you need to do is open regedit (Start -> Run -> Regedit) and then from the root of the tree search for the GUID of the issue that’s appearing in Event Log. Once the search finds your GUID you should see an application name in the right hand pane. Simply follow the steps above for the particular Component name and you should quickly resolve the DCOM issues that keep appearing in the event log.

Once I’ve made these changes I usually reboot, I’m not 100% whether the reboot is required but I guess it doesn’t hurt, at worst it should confirm that your MOSS Box will come up after a component change.

Vista 64 Bit Up and Running

I’m now running a complete 64 bit Vista system on a Dell Latitude D830. Overall it was relatively painless, as it was about 6 months ago the last time I tried. The only problem last time was the ZTE MF322 Telstra NextG Card, as you can see from this site, is unsupported on any 64 Bit Systems which forced me back to 32 Bit Vista. Now I’ve bypassed the need for a dedicated wireless card by just using my trusty Dopod 838 either over the usb cable or bluetooth. Talking of Bluetooth, this almost was a problem, but it appears that there are some fixes in Vista SP1 that dealt with this seamlessly.

The most frustrating part was trying to get the touchpad mouse working correctly. By default the mouse worked in simple mode, with a default driver. If you’re like me and used to the added functionality such as scrolling etc this is really painful. The good news is that although Dell won’t display a driver when you enter either your model or service tag, there is a driver on their website which I found accidentally here.

Microsoft SharePoint Products and Technologies Team Blog : Announcing the First Release of the Microsoft SharePoint Administration Toolkit

Seem Like where going to start getting some great new and very welcome update tools in Sharepoint. Microsoft SharePoint Products and Technologies Team Blog : Announcing the First Release of the Microsoft SharePoint Administration Toolkit has just been announced. The good news is there are going to several updates a year, so there should be a nice collection of useful tools before we know it. The first two tools that have come out the Batch Site Manager tool and the Update Alert addition to the “stsadm” command.

Download Links are below.

x64: http://www.microsoft.com/downloads/details.aspx?FamilyId=F8EEA8F0-FA30-4C10-ABC9-217EEACEC9CE&displaylang=en

x86: http://www.microsoft.com/downloads/details.aspx?FamilyId=263CD480-F6EB-4FA3-9F2E-2D47618505F2&displaylang=en

Finally Back on Deck

I’ve finally got around to getting back to my blog. I ended up having the first two weeks of April off after having Renal Colic, better known as kidney stones. Let me tell you the pain was awful. In the 2 weeks I had 4 stays in hospital, 2 procedures, surviving on 4 hourly doses of pain killers.

I actually had 2 stones, the one that was causing all the pain was stuck in my left Ureter and was only 3mm, or around the size of a small piece of fish tank gravel (I know I have it in jar here). This little sucker wasn’t moving at all, the first operation I had was where the surgeon was meant to remove it but for one reason or another couldn’t find it (although I think this had more to do with fact that he did the procedure at 5.30 on Friday afternoon and probably had some dinner reservations, ALLEGEDLY!!!). He instead put in an ureteral stent and the pain from this thing was excruciating. If these things haven’t been outlawed by the Geneva Convention they should be, I ended up insisting that the surgeon remove it or I’d do it myself. This ended up happening on the Tuesday, at the same time as I decided that it was probably time for a second opinion, as this “Urologist” that had been treating me was to put it bluntly a “Cowboy”. I’d managed to get into see another Urologist and he was great. Within a few minutes of seeing him, we’d worked out a proper treatment plan for firstly this initial stone that was close to becoming critical to get removed, but also to stop this happening with the second stone which was still stuck in the kidneys. Funny enough after taking his advice within 2 hours the stone had come out and I was feeling great.

As to what happened with the other stone, well I went in a week ago to have a Lithotripsy done. I was out in 2 hours and other than the effects of the anaesthetics, all went well. Finally a month after this had all started, it was all finally over, funny this was what they should have done in the first place.

If you have to see a Urologist in Melbourne, feel free to ping me to ask who you should see, so you don’t have to go through the circus of un-needed surgery. Stay tuned as I’m going through and I’ve got a lot of post’s that need to be published.