SP1 woes

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

SP1 woes

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> SP1 woes

Page: [1]

Message

<< Older Topic Newer Topic >>

SP1 woes - 6/23/2008 10:52:54 AM

MhermanNBME

Posts: 62
Score: 3
Joined: 4/4/2007
Status: offline

Last week I prepared to do the SP1 upgrade by taking care of all the warnings and errors in the prereq checker which went pretty well. I left the WIAK (untill right before the upgrade) and the warning about SA security.

FYI, double check your hard drive space on your server, i was just under the 5gb minimum, and the prereq checker aparently doesn't check that.

After that was taken care of, I started installing the sp. It got about 3 items down, and there an error message about writing a file popped up for 3 seconds and the server rebooted. Tried installing locally rather than a network share with no luck, and some other attemps all with the same result. Luckilly it's an ESX virtual server so I was just reverting to snapshots before I ran the installer. When I would revert, the RTM console seemed to be running OK, so the DB stuff that it had done didn't seem to be affecting it so i didn't do any database restores. Here is the entry from the log file on failed setups:
<06-21-2008 11:13:09> Failed to run Windows Automated Installation Kit installation file. Error code: 1641. Check log file at C:\DOCUME~1\sccmsvc\LOCALS~1\Temp\1\waik_install.log

And of course, that waik_install.log did not exist.

Finally I got it to work by uninstalling waik 1.0, installing 1.1 manually from the subfolder in the SP1 download. Then I ran the sp1 installer. According to the logs, it looked like it tried to install waik again, but this time it succeded, and now my site seems pretty healty.

I have a realatively small site with just 1 primary server, so painfull as it was, it turned out ok. i couldn't imagine dealing with this if i had multiple sites and servers...

Hopefully this helps someone else save some time, good luck.

Post #: 1

RE: SP1 woes - 6/23/2008 11:05:01 AM

wbracken

Posts: 1006
Score: 22
Joined: 4/12/2002
From: St. Louis
Status: offline

Thanks for the follow up!

_____________________________

William Bracken

http://www.clientarchitect.com

(in reply to MhermanNBME)

Post #: 2

RE: SP1 woes - 6/23/2008 1:55:46 PM

palle

Posts: 22
Score: 0
Joined: 8/29/2007
Status: offline

This has come up to me a couple of times, not here, but in real life. I'm just wondering one thing: Why do folks install WAIK separately on a SCCM server? Even on clean SCCM installs on W2K3 SP2, which comes with WDS by nature. I know that if you need a WDS server on a W2K3 SP1 server you need that, but I've seen already two different installs, where for some unknown reason somebody installed WAIK separately before SCCM (without SP1). Of course they run into trouble with sp1 update (just as described above), and then they call for help.

I don't mean that you MhermanNBME did this, but I know at least two different admins who did (and I can prove it

), I'm speaking just in general.

I'm just wondering, am I missing something, is there some reason I am not aware of, on a server which comes with SP2/WDS already to install WAIK separately? As far as I am concerned, needed parts come with SCCM, and that's all you need, but as always, I might be wrong.

Just wondering...

< Message edited by palle -- 6/23/2008 1:58:37 PM >

(in reply to wbracken)

Post #: 3

RE: SP1 woes - 6/23/2008 2:45:41 PM

MhermanNBME

Posts: 62
Score: 3
Joined: 4/4/2007
Status: offline

I thought that it installed with the RTM version of SCCM. And now that I look at it, according to my event logs WAIK was reported installed about 7 minutes before SCCM. I don't remember doing it manually, and it's not on my checklist that I ran through when doing the initial setup.

(in reply to palle)

Post #: 4

RE: SP1 woes - 6/24/2008 11:05:33 AM

dreames

Posts: 26
Score: 0
Joined: 10/20/2003
Status: offline

I had a similar problem with my SP1 upgrade yesterday. As it was upgrading, all of a sudden, it rebooted. I wasn't watching the screen, but had it up and the screen changing caught my eye. After the server came back up, I checked the event log and found that the WIAK caused the reboot. Not knowing if the update was completed, I started the console and found that the version in Help-About was RTM and the version in the Site Settings was SP1.

I figured I would run the update again (bad move) to see if that would fix it. Now the Executive service won't start and ConfigMgr is down for the count. I've submitted a Request with MS Support and I'm waiting for their call. This is a small site with a single Primary server with every piece of SCCM on it.

Wish I would have read this post before starting!!

(in reply to MhermanNBME)

Post #: 5

RE: SP1 woes - 6/24/2008 1:45:55 PM

palle

Posts: 22
Score: 0
Joined: 8/29/2007
Status: offline

quote:

ORIGINAL: MhermanNBME

I thought that it installed with the RTM version of SCCM. And now that I look at it, according to my event logs WAIK was reported installed about 7 minutes before SCCM. I don't remember doing it manually, and it's not on my checklist that I ran through when doing the initial setup.

OK, so this can probably happen even without a separate WAIK installation - maybe. It's good to know this. The two problem cases I ran into were due to separate WAIK installation, so I figured that's the reason, but maybe it's not totally so.

(in reply to MhermanNBME)

Post #: 6

RE: SP1 woes - 6/24/2008 1:51:06 PM

MhermanNBME

Posts: 62
Score: 3
Joined: 4/4/2007
Status: offline

dreames:

What kind of backup did you do before starting the upgrade?

(in reply to palle)

Post #: 7

RE: SP1 woes - 6/26/2008 1:49:33 AM

palle

Posts: 22
Score: 0
Joined: 8/29/2007
Status: offline

On VMWare it's easy to just take a snapshot

Just need to remember to delete the snapshot afterwards before the disks fill up.

Otherwise I've used just normal SCCM backup by its own task (of course on VMWare this as well). As far as I understand that shoud be enough to do a successful recovery, nevere needed it though.

(in reply to MhermanNBME)

Post #: 8

RE: SP1 woes - 7/22/2008 2:53:22 PM

jgilbert442

Posts: 10
Score: 1
Joined: 9/19/2003
Status: offline

WAIK is installed on the SMS Provider computer during Configuration Manager Setup. RTM used WAIK 1.0 and SP1 requires WAIK 1.1:
http://technet.microsoft.com/en-us/library/bb680613(TechNet.10).aspx (section starting with Windows Automated Installation Kit Requirements).

This issue (unexpected reboots) is caused by SP1 Setup attempting to upgrade WAIK 1.0 to WAIK 1.1 during the upgrade process and a file used by the WDS Server service (wimgapi.dll) is in use and locked. To complete the upgrade of that file, a system restart is required and so WAIK just reboots the server.

To avoid this situation/or troubleshoot the after effects, check out my blog post about it:
http://blogs.technet.com/wemd_ua_-_sms_writing_team/archive/2008/07/22/upgrading-the-windows-aik-for-configuration-manager-2007-sp1.aspx

Hope this helps,

~Jeff

This posting is provided "AS IS" with no warranties and confers no rights.

< Message edited by jgilbert442 -- 7/22/2008 4:00:12 PM >

(in reply to palle)

Post #: 9