| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
Win2k3 SP1
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 Win2k3 SP1 - Nov. 22, '04, 7:54:51 PM
|
|
|
DrPizza
Posts: 40
Joined: Mar. 27, '03,
Status: offline
|
Hi.
I downloaded the newer Win2K3 SP1 beta from MSDN the other day, and I notice that it makes psxss.exe crash on startup. Is it just me?
|
|
|
|
|
RE: Win2k3 SP1 - Nov. 23, '04, 2:13:38 AM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
I haven't tried this SP myself. But usually there is a reporting method on the Beta's
that's easier to access than with other things. What's the actual link that you picked it
up from?
|
|
|
|
|
RE: Win2k3 SP1 - Nov. 23, '04, 9:01:27 AM
|
|
|
markfunk
Posts: 673
Joined: Mar. 31, '03,
Status: offline
|
Right, there's a beta support email list setup specifically for error
reports like this.
Let Microsoft know about your problem.
It's most likely a bug in this SP1.
(either they installed a newer psxss.exe or they changed some behaviour
in the kernel that psxss depends upon )
|
|
|
|
|
RE: Win2k3 SP1 - Dec. 22, '04, 10:17:16 AM
|
|
|
DrPizza
Posts: 40
Joined: Mar. 27, '03,
Status: offline
|
quote:
What's the actual link that you picked it
up from?
I just recently grabbed the public RC1 (http://www.microsoft.com/windowsserver2003/downloads/servicepacks/sp1/default.mspx) and the same happens. I'll file a bug with SP1, but to be honest, I don't know if the problem is that SP1 has broken something, or merely /changed/ something.
|
|
|
|
|
RE: Win2k3 SP1 - Mar. 31, '05, 9:02:37 PM
|
|
|
breiter
Posts: 346
Joined: Jun. 14, '04,
From: Washington, DC
Status: offline
|
Faulting application , version 0.0.0.0, faulting module PSXSS.EXE, version 8.0.1969.1, fault address 0x0004c993.
The same problem occurrs with the gold shipping version of WIN2K3 SP1.
I'm trying the fix described in this nesgroup posting at the Microsoft SFU support forum to see if it resolves the issue for me.
The gist is that there is supposedly a 8.0.1969.2 included in the current download (unchanged version number of the installer) and that one works fine. But the MSDN subscriber ISO looks like it hasn't changed in a year, so I'm trying the download from the www.microsoft.com/windows/sfu public web site.
Offsite MS newsgroup reference.
|
|
|
|
|
2 different SFU 3.5 >> Only the new one works - Mar. 31, '05, 11:51:05 PM
|
|
|
breiter
Posts: 346
Joined: Jun. 14, '04,
From: Washington, DC
Status: offline
|
In fact, there is a difference between the ISO from MSDN library and the current download from http://www.microsoft.com/windows/sfu.
The main difference is that the original SFU 3.5 PSXSS.EXE 8.0.1969.1 (built Nov. 8 2003) crashes on boot with Windows Server 2003 SP1 (but not Windows XP SP2).
I tried simply replacing PSXSS.EXE on my test server and that didn't solve the problem. What did solve the problem was painful:
1. *UNINSTALL* SFU 3.5 (you cannot run the installer over the existing installation because it refuses).
2. Reboot.
3. Install SFU 3.5 with PSXSS.EXE 8.0.1969.2 (March 1, 2004)
4. Configure everything again and install stuff from Interopsystems.
(There is no requirement to set a DEP exclusion to make this work)
I diffed the folder trees of the two versions.
Here's the difference:
* Some changes to the EULA
* Changed psxsss.exe (the binary image is significantly different and 512 bytes smaller)
* Changed debug symbols (psxss.dbg and psxss.pdb)
* Added "/manage/W2K3/progreg.mof"
* The sfusetup.msi packages are different.
Here is the contents of progreg.mof:
#pragma namespace("\\\\.\\Root\\SFUAdmin")
#pragma autorecover
instance of __Win32Provider as $P
{
Name = "RegProv" ;
ClsId = "{fe9af5c0-d3b6-11ce-a5b6-00aa00680c3f}" ;
ImpersonationLevel = 1;
PerUserInitialization = TRUE;
Hostingmodel = "localservicehost";
};
instance of __InstanceProviderRegistration
{
Provider = $P;
SupportsPut = TRUE ;
SupportsGet = TRUE;
SupportsDelete = TRUE;
SupportsEnumeration = TRUE;
};
I ran a package diff between the two versions of sfusetup.msi. There are a lot of little differences but the main one seems to be that the moffile is used to register a class in the WMI repository. How can a Windows Managment Instrumentation repository class have anything to do with a subsystem crashing at startup?
How can I patch psxss.exe on a running server *before* installing SP1 so that the subsystem isn't broken *without* uninstalling my existing SFU installations?
|
|
|
|
|
RE: 2 different SFU 3.5 >> Only the new one works - Apr. 1, '05, 10:25:09 AM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
> In fact, there is a difference between the ISO from MSDN library and the current download from http://www.microsoft.com/windows/sfu.
Yes, it's been like that for several months now.
> How can I patch psxss.exe on a running server *before* installing SP1
The "jewels" have always been updated as a set: psxss.exe, psxdll.dll, posix,exe, psxrun.exe, etc.
So if you change out any one of these you need to do them all as a set.
There are also registry keys that record version numbers of the file ids.
> How can a Windows Managment Instrumentation repository class have anything to do with a subsystem crashing at startup?
It's linked in with the security model these days, as I understand it.
|
|
|
|
|
RE: 2 different SFU 3.5 >> Only the new one works - Apr. 1, '05, 10:33:16 AM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
You may also want to look at:
http://support.microsoft.com/default.aspx?scid=kb;en-us;838250
for the hotfix (markfunk pointed it out).
The gist of it is the SP screwed up and removed data it wasn't supposed to.
|
|
|
|
|
RE: 2 different SFU 3.5 >> Only the new one works - Apr. 1, '05, 11:01:27 AM
|
|
|
breiter
Posts: 346
Joined: Jun. 14, '04,
From: Washington, DC
Status: offline
|
Thank you Mark and Rodney.
I'm not surprised that the only "file" that changes is psxss.exe because that is the only binary difference between the two editions of SFU 3.5. The other "jewels" are identical binaries to the originals. The MSI must do something more than just replace the file, though. Because just replacing that file myself didn't work.
Can this hotfix be applied proactively *before* upgrading to SP1?
|
|
|
|
|
RE: 2 different SFU 3.5 >> Only the new one works - Apr. 1, '05, 11:28:02 AM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
> Can this hotfix be applied proactively *before* upgrading to SP1?
I have no certain information.
However, since the SP changed things and the hotfix information says to apply the hotfix
after the problem is "experienced" (ha!) its possibly just post SP install.
|
|
|
|
|
RE: 2 different SFU 3.5 >> Only the new one works - Apr. 1, '05, 4:47:44 PM
|
|
|
breiter
Posts: 346
Joined: Jun. 14, '04,
From: Washington, DC
Status: offline
|
FYI. I have an SRX registered with the product team at Microsoft. I was told that they *think* you can apply the hotfix before the SP1 install. They are going to test and confirm that for me.
Currently you have to call in to get them to email you a URL and password to download the hotfix because it isn't fully regression tested!
Apparently the product team does realize that this was a big mistake and are trying to figure out the best way to fix the situation.
|
|
|
|
|
RE: 2 different SFU 3.5 >> Only the new one works - Apr. 4, '05, 4:58:44 PM
|
|
|
jonsmi
Posts: 168
Joined: Aug. 12, '03,
From: Oslo, Norway
Status: offline
|
As far as I can see this is a pay service, handling an inciendt (bug introduced
by MS). Or have I gotten that wrong?
|
|
|
|
|
RE: 2 different SFU 3.5 >> Only the new one works - Apr. 17, '05, 11:42:29 PM
|
|
|
breiter
Posts: 346
Joined: Jun. 14, '04,
From: Washington, DC
Status: offline
|
quote:
ORIGINAL: jonsmi
As far as I can see this is a pay service, handling an inciendt (bug introduced
by MS). Or have I gotten that wrong?
No, they won't charge you. Just reference the KB number when you call in. The team was very helpful to me, but it is really annoying that hotfixes for SFU are not public downloads. The claim they made to me was that they are being double-exra careful with SFU and want to have more direct interaction with users that need patches.
According to the SFU team, you can apply the hotfix *BEFORE* installing SP1 on Win2K3 which will (er... should?) prevent the psxss.exe subsystem crash after reboot of SP1. I haven't tried it personally, yet.
Sorry for the time lag from the last post. My wife had a beautiful baby girl on 4/4/2005 and I haven't looked at a computer in 2 weeks.
|
|
|
|
|
RE: 2 different SFU 3.5 >> Only the new one works - Apr. 18, '05, 1:03:58 AM
|
|
|
jonsmi
Posts: 168
Joined: Aug. 12, '03,
From: Oslo, Norway
Status: offline
|
quote:
> No, they won't charge you. Just reference the KB number when you call in.
Yes, I made the same experience. Phone call was two minutes, the patch
downloadble a minute later. However, PSS (MS support) has had a tradition
of being quite a costly affair and not too available, reliable
and polite to just anybody.
Actually Charlie Russel - MVP - was fast to point out this fact in
microsoft.public.servicesforunix.general: "the call is free, since it's a bug."
(Has it alway been like this?  )
quote:
... but it is really annoying that hotfixes for SFU are not public downloads.
The claim they made to me was that they are being double-extra careful with
SFU and want to have more direct interaction with users that need patches.
Oh, yeah ... when I was still at HP Norway, we had all those NDA lists
of severe bugs on public Windows _highly_ recommended security patches and so on.
And UNIX admins at least used to differ in respect to applying patches,
which they hadn't thoroughly tested themselves (not common with Win admins).
(Hasn't MS encountered a single buffer overrun in Interix yet, missing
parameter checking -- SuSE and Red Hat comes with lots of new minor versions --
what about them -- or don't UNIX people don't care?)
quote:
According to the SFU team, you can apply the hotfix *BEFORE* installing SP1
on Win2K3 which will (er... should?) prevent the psxss.exe subsystem crash
after reboot of SP1. I haven't tried it personally, yet.
You can apply it *AFTER* and *BEFORE*. Doing it after will lead to a
crash of the psxss.exe -- the POSIX subsystem server. A reboot will remedy this.
I've tried all three solutions, inclusive new install (Toolsworks does wonders,
and when we have an ap-get , err pkg_update ...) 
(BTW here's a grave mistake in the man filefino: the five basic Interix files
are NOT "Win32 files that make up" that system.).
There’s another error as well. The fix says: If you change or add any
Components of SFU, you’ll need to reapply the Hotfix. At least this does'nt
hold true for the latest SFU download, which has:
$ fileinfo
/dev/fs/C/WINDOWS/system32/PSXSS.EXE 8.0.1969.2
(former was 8.0.1969.1)
quote:
My wife had a beautiful baby girl on 4/4/2005 and I haven't looked at a computer in 2 weeks
.
Very nice to hear. My two twins are five months by now, and I had to stay
away from computer for nearly three months -- a rewarding time.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
