Moss Version Numbers

To find your SharePoint version (The version that you currently have), you need to enter the Site Setting. In the middle of the screen you can see the version No’.

Note that if you have more than one server in the farm, you need to match the version number on all the servers. Every service pack, update or hotfix that you install mast be applied on all the farms.

Moss/WSS 3.0 version numbers:
MOSS 2007 or WSS 3.0 SP2 12.0.0.6421
MOSS 2007 or WSS 3.0 Cumulative update (KB956056 & KB956057) 12.0.0.6327
MOSS 2007 or WSS 3.0 Infrastructure Update (KB951695 & KB951297) 12.0.0.6318
MOSS 2007 or WSS 3.0 post-SP1 hotfix (KB948945) 12.0.0.6303
MOSS 2007 or WSS 3.0 post-SP1 hotfix (KB941274) 12.0.0.6301
MOSS 2007 or WSS 3.0 post-SP1 hotfix (KB941422) 12.0.0.6300
MOSS 2007 or WSS 3.0 SP1 12.0.0.6219
MOSS 2007 or WSS 3.0 October 08 public update 12.0.0.6039
MOSS 2007 or WSS 3.0 August 24, 2007 hotfix package 12.0.0.6036
MOSS 2007 or WSS 3.0 RTM 12.0.0.4518

Beta versions:

MOSS 2007 or WSS 3.0 Beta 2 TR: 12.0.0.4407
MOSS 2007 or WSS 3.0 Beta 2: 12.0.0.4017

LoadBalancer.RegisterLauncher failed

Here's an irritating error that I bump into lately:

Event Source: Office SharePoint Server Event

Category: Launcher Service

Event ID: 6102

User: N/A

Description: LoadBalancer.RegisterLauncher failed: Unable to connect to the remote server.

This error usually happens when Document Conversions Load Balancer Service is using a wrong service account.
To resolve this error Try the following steps:

1. Configuring the proper Service Accounts

- Central Administration -> Operations.
- Security Configuration -> Service account.
- Click the Windows Service radio button -> select Document Conversions Load Balancer Service.
- Fill in the proper service account.

2. restarting the services.

- Central Administration -> Operations -> Services on Server.
- Click Stop on the Document Conversions Load Balance Service. …And stop the Document Conversions Launcher Service too.
- Start the services and the error will not appear again.

After this procedure the error will disappear.

Infrastructure Update

About a two months, Microsoft has released a significant update: Infrastructure Update.

One of the problems that the Following updates fix’s, is addresses that are not available when exposed by AAM(Alternate Access Mapping in conjunction with reverse proxy or NLB solution.

This KB fix the Bugs - KB951695

Here’s a link Http://support.microsoft.com/kb/956248

Folders that may want to excluded from antivirus

If you have seeing the error “Access Denied” when you are trying to upload new documents, it’s likely that you have antivirus Vs Moss problems. Ther are some folders that may want to exclude from antivirus scanning on system with MOSS 2007. most of the time it solved the problem.

If you don't have antivirus agent for MOSS on your system, you may want to leave out those folders. Scanning them will cause errors and weird behavior when files are uploaded.

I recommend excluding the “Microsoft Office Servers” folder. Located in: %drive%\Program Files\Microsoft Office Servers

If you - for some reason - don’t want to exclude this folder you may want to exclude the Following folders:

%drive%\\Program Files\Microsoft Office Servers\12.0\Data. (or different folder that holds the Index files)

%drive%\\Program Files\Microsoft Office Servers\12.0\Logs

%drive%\\Program Files\Microsoft Office Servers\12.0\Bin

More on this topics in Microsoft KB952167.

link to KB952167: http://support.microsoft.com/kb/952167