Archive for November, 2005

Building IBM Bladecenters – A foto journal

Thursday, November 24th, 2005

2 x xSeries 366 Servers, unpacked, and ready to recieve options

So much stuff to build, so much to unpack!!

Over 100.000 dollar worth of components on the table here. Extra CPU’s, Harddisks, Option cards, even

Acoustic Attenuation Modules .. all to be built into our Blades, Bladecenters, and xSeries 366’s

21 HS20 Blade Servers, still in Box.

One of the 2 IBM 366 servers, they will be running Windows 2003 and SQL 2000.

The 2 Bladecenter Chassis waiting to be unpacked.

Way way waaaaaay to many boxes to unpack. Thank goed we got these 2 guys to do it ūüôā¬† And to actually put the stuff together!

Pile o’ Blades.¬† IBM HS20’s to be exact, each has 2 2.8Ghz Xeon’s and 2 x 36gb scsi 3.5″ Disks, and 2gb of memory.

These two guys from BPSolutions are helping us putting it all together.  Here they are working on equiping 2 IBM xSeries 366 servers that will function as database servers.

Placing 3 additional CPU’s, 2.8Ghz Xeons

Figuring out how to move 280kg of IBM Enterprise Rack into the server room

An IBM HS20 Bladeserver. 14 of these go into a single chassis. Notice the slots of 2 x 3.5″ SCSI harddrives. Click here for a closeup

View more pictures of cool server hardware here.

Installing Windows Update client error 0x8007041d

Monday, November 14th, 2005

When installing the latest version of the Windows Update Client, you may recieve an error that references this code: 0x8007041d

0x8007041d simply refers to not being able to stop, restart or manipulate in some way, the Windows Update service.

With a recent version of the Windows Update agent installed, the C:windowsWindowsUpdate.log file will produce and error similair to the following:

Windows Update Client standalone setup : eula file path is d:72535cf0e694fc12f4c5a4eneula.rtf
2005-11-14 12:26:23 23248 68f8 Setup *************
2005-11-14 12:26:23 23248 68f8 Setup ** START **  Setup: Installing client binaries
2005-11-14 12:26:23 23248 68f8 Setup *********
2005-11-14 12:26:23 23248 68f8 Setup   * Download directory: d:72535cf0e694fc12f4c5a4
2005-11-14 12:26:23 23248 68f8 Setup   * Stop and start service: Yes
2005-11-14 12:26:53 23248 68f8 Setup FATAL: SelfUpdate: Failed to stop service wuauserv, error = 0x8007041D
2005-11-14 12:26:53 23248 68f8 Setup   * WARNING: Exit code = 0x8007041D
2005-11-14 12:26:53 23248 68f8 Setup *********
2005-11-14 12:26:53 23248 68f8 Setup **  END  **  Setup: Installing client binaries
2005-11-14 12:26:53 23248 68f8 Setup *************
2005-11-14 12:26:53 23248 68f8 Setup FATAL: InstallUpdatedBinaries failed with error 0x8007041d

This can occur with the Standalone Installer, as in the example above, but also when updating your Windows Update client though the Windows Update homepage.

On the web you will find references to Norton virusscanner possibly causing this, but its not the only reason this can happen. ( http://www.kbalertz.com/kbNamed_902322/902322.aspx ) In fact there are any number of reasons a Windows server can fail to unload.

The Windows Update service is launched by the system, under system account credentials, and with the following command line: C:windowssystem32svchost.exe -k wugroup

If the service is trapped in the ‚Äústopping‚ÄĚ state, you may wanna kill the process manually, however, you can only do this on a Windows 2000 machine! As I will show below‚Ķ

But because the service is launced via cvchost, you might have a hard time recognising which instance of cvchost to kill.

Wu_service_stopping

Process Explorer has an option to show the command line with which all system processes have been started. This is simply a column you have to turn on in the main view.

Wu_service_px

The Windows XP / W2K3 command tasklist.exe will give you much the same data:

On a Windows 2000 Server:

tasklist /FI “IMAGENAME eq SVCHOST.EXE” /SVC

Image Name                   PID Services
========================= ====== =============================================
svchost.exe                  636 RpcSs
svchost.exe                  780 EventSystem, Netman, NtmsSvc, RasMan, SENS
svchost.exe                 2512 TapiSrv
svchost.exe                26864 BITS
svchost.exe                30912 wuauserv

A Windows Server 2003 machine:

Image Name                   PID Services
========================= ====== ============================================
svchost.exe                 1504 DcomLaunch
svchost.exe                 1580 RpcSs
svchost.exe                 1636 Dhcp, Dnscache
svchost.exe                 1780 LmHosts, W32Time
svchost.exe                 1820 AeLookupSvc, BITS, CryptSvc, dmserver,
EventSystem, helpsvc, lanmanserver,
lanmanworkstation, Netman, Nla, sacsvr,
Schedule, seclogon, SENS, SharedAccess,
ShellHWDetection, TrkWks, winmgmt, wuauserv
svchost.exe                  692 ERSvc
svchost.exe                 1120 RemoteRegistry
svchost.exe                 2824 W3SVC
svchost.exe                 2948 TermService



A Windows XP machine:

Image Name                   PID Services
========================= ====== ============================================
SVCHOST.EXE                  940 DcomLaunch, TermService
SVCHOST.EXE                 1008 RpcSs
SVCHOST.EXE                 1104 AudioSrv, BITS, Browser, CryptSvc, Dhcp,
dmserver, ERSvc, EventSystem, helpsvc,
lanmanserver, lanmanworkstation, Netman,
Nla, RasMan, Schedule, seclogon, SENS,
SharedAccess, ShellHWDetection, srservice,
TapiSrv, Themes, TrkWks, w32time, winmgmt,
Wmi, wuauserv, WZCSVC
SVCHOST.EXE                 1196 Dnscache
SVCHOST.EXE                 1308 LmHosts, RemoteRegistry, SSDPSRV, WebClient
SVCHOST.EXE                 3320 stisvc

A funny thing to note here is the difference between Windows 2000 and Windows XP / W2K3. On Windows 2000 Server, the wuauserv service is run as a completely seperate process, with its own ID.
This means you can kill it seperatly.

But on Windows XP / W2K3, it is launched as part of the Network Services group. This is reflected in the command line in which it is launched:
C:WINDOWSsystem32svchost.exe -k netsvcs

You cant simply kill svchost.exe in this case, it will crash the system.
Recommended is to disable the service, reboot, and after reboot install the standalone Windows Update Agent.

How long will the MDA Pro pen last?

Thursday, November 10th, 2005

(pic taken using the small camera on the Mda)

Dont really know how I need to tall this thing for the sake of the blog. MDA Pro? HTC Universal?

Anyway.. my primary MSN works again, now at jemimus@hotmail.com..  its so stupid really. Just needed to add everyone again so they could authorise my new adress.. and there I was thinking the process was automatic or something… whatever.

Had a look at setting up mobile sync on my Exchange server, but the first attemps seem to reveal that WM05 is rather picky about certificates, so I will have to figure that stuff out first.

Another issue I need to look at, is why MWV9 movies from Channel9 wont play fullscreen, even though they play really well! I need to go buy myself a 1gb SD card, so I can start treating those vids as really large podcasts, and listen to them on the train.  I sent Scoble a mail about having the sound for those vids brought out as seperate podcasts, but never got a reply.

A case for the MDA Pro

Monday, November 7th, 2005

Now I have my cool phone, I will need a cool case.

since I got a Piel Frama case for my previous phone, and was so impressed by the quality, I will remain brand-loyal and order with them again.

These really are great cow-leather cases. I used my XDA one for 3 years and there was hardly any wear at all. The belt-clip they use is also very sturdy and will last long, though I will likely order a few spare.

Got me new phone! Mda Pro!

Sunday, November 6th, 2005

A.k.a. The HTC Universal!

I have been pining for this thing for the last year or so. Isn’t she a beauty!
Got the bluetooth sync working great, now to set up Exchange for mobilesync.


Still cant use my Primairy MSN account though, I am currently using jemi_test@hotmail.com
I hope they fix it soon so I can try it out on Pocket MSN.