2008 sp2 32 bit

[bedowyn]

Hi.  I am trying to re-purpose my home file server to be a little more robust, and I thought I would install DrivePool to help.  But I can not get the installation to launch.  Instead, I get an error saying that I require a (newer?) version of the "kernel-mode driver framework."  For the record, the server is a 32 bit instance of 2008 server.  If I recall correctly, there is no R2 release for the 32 bit version of windows server 2008, so this is as far as I can go.

 

When I try to find an installation of MS update 970158, I find it no longer available; I presume it was superceded. 

 

When I try to manually install the update for 2685811, which appears to be the current 1.11 framework, I have an error saying something like "this update is not for your system."  To be sure, I have tried the "all x86" update, and the other 2008 and win 7 64 updates, for good measure.

 

So... am I doomed?  Any help is very welcome!

 

Thanks

-AA

[Christopher (Drashna)]

You are correct that Windows Server 2008 is last Windows Server OS that supports 32-bit.

Though, out of curiosity, why not use Windows 7 32-bit or Windows 8 32-bit?

 

Could you go to "%temp%" on the system and grab the "StableBit DrivePool" logs from there and either attach them here, or open a ticket at https://stablebit.com/Contact ?

 

In theory, there should be no issue with StableBit DrivePool installing on the system. 

 

 

Also, is this a clean image from Microsoft? If not.. that could be why. Either way, running "sfc /scannow" may be a good idea here.

[bedowyn]

It was an old 2003 file server, 32 bit, running on some relatively low end hardware.  I did an in place upgrade to 2008, simply because it seemed like the path of least resistance going forward.

At this point, I am considering rebuilding the box.  Windows 7 as a file server had never occurred to me, but since all I am doing is sharing the folders, it might very well be an option. 

 

Interesting.

[Christopher (Drashna)]

Considering how old the box may be.... rebuilding it from the ground up may be a good idea. May use a lot less power, at least. Which isn't a bad thing at all.

 

And yeah, you can definitely use Windows 7 as a file server (and even Windows 8). Actually, I was using Windows XP as a file and web server before I found Windows Home Server v1. And it works well. And is a viable option.

If you want any help or suggests for that, don't hesitate to ask.

 

 

And just to let you know, I'm currently re-installing my Server 2008 x86 VM, as it apparently get damaged ..... Once that's up, I'm going to see if I can reproduce your issue.

[Christopher (Drashna)]

Could you make sure that Service Pack 2 is installed on the system? And that all available updates (even optional ones) are installed?

[bedowyn]

Right, I patched this right through SP2 last night, trying the application and the framework installations at each step.  

 

The application log at time of fail is showing below.

 

[0C1C:0E54][2014-06-16T17:39:21]i001: Burn v3.7.1224.0, Windows v6.0 (Build 6002: Service Pack 2), path: D:\Archive\Temp\StableBit.DrivePool_2.0.0.420_x86_Release.exe, cmdline: ''

[0C1C:0E54][2014-06-16T17:39:22]i000: Initializing string variable 'InstallFolder' to value '[PlatformProgramFilesFolder]\StableBit\DrivePool'

[0C1C:0E54][2014-06-16T17:39:22]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\jester\AppData\Local\Temp\StableBit_DrivePool_(32_bit)_20140616173922.log'

[0C1C:0E54][2014-06-16T17:39:22]i000: Setting string variable 'WixBundleOriginalSource' to value 'D:\Archive\Temp\StableBit.DrivePool_2.0.0.420_x86_Release.exe'

[0C1C:0E54][2014-06-16T17:39:22]i000: Setting string variable 'WixBundleName' to value 'StableBit DrivePool (32 bit)'

[0C1C:0E54][2014-06-16T17:39:22]i100: Detect begin, 2 packages

[0C1C:0E54][2014-06-16T17:39:22]i000: Setting string variable 'NETFRAMEWORK40CLIENT' to value '1'

[0C1C:0E54][2014-06-16T17:39:22]i052: Condition 'NOT VersionNT64' evaluates to true.

[0C1C:0E54][2014-06-16T17:39:22]i000: Setting string variable 'PlatformProgramFilesFolder' to value 'C:\Program Files'

[0C1C:0E54][2014-06-16T17:39:22]i052: Condition 'VersionNT64' evaluates to false.

[0C1C:0E54][2014-06-16T17:39:22]i000: Registry key not found. Key = 'SOFTWARE\StableBit\DrivePool'

[0C1C:0E54][2014-06-16T17:39:22]i000: Setting version variable 'KmdfVersion' to value '1.7.6001.0'

[0C1C:0E54][2014-06-16T17:39:22]i000: Product not found: {1AB7D699-E19A-45E6-992C-2FB2DC1730C7}

[0C1C:0E54][2014-06-16T17:39:22]i000: Setting version variable 'DrivePool1Version' to value '0.0.0.0'

[0C1C:0E54][2014-06-16T17:39:22]i052: Condition 'NETFRAMEWORK40CLIENT' evaluates to true.

[0C1C:0E54][2014-06-16T17:39:22]i101: Detected package: NetFx40ClientWeb, state: Present, cached: None

[0C1C:0E54][2014-06-16T17:39:22]i101: Detected package: DrivePoolApplication, state: Absent, cached: None

[0C1C:0E54][2014-06-16T17:39:22]i052: Condition '(VersionNT >= v6.0)' evaluates to true.

[0C1C:0E54][2014-06-16T17:39:22]i052: Condition '(KmdfVersion >= v1.9)' evaluates to false.

[0C1C:0E54][2014-06-16T17:39:22]e000: Error 0x81f40001: Bundle condition evaluated to false: (KmdfVersion >= v1.9)

[0C1C:0E54][2014-06-16T17:39:22]i199: Detect complete, result: 0x0

 

 

[bedowyn]

And so I went back after being nudged to check my SP2 installment, and found that there were more updates pending.  And after installing these, something corrected itself.  

 

So it appears that we are in business.

[Christopher (Drashna)]

Okay, I'm glad to hear that.

 

ANd yeah, the log indicates the same thing that the error above was giving.

 

And in theory, SP2 includes the "Kernal Mode Driver Framework" for the system. Though I suspect that one of the updates fixed an issue with it. You can always verify that by looking at the update history, and looking at what the updates AFTER SP2 was installed contain (any "wdf" files that are updated, specifically)

 

Either way, I'm glad to hear that it does seem to work properly now! And I'd recommend making a backup of the system disk, just in case (Install the "Windows Server Backup" role, at least).