A customer of ours with the following spec server can't get the X\IO driver to install. They're using the v10.01 install. The spec of the server is as follows: -

Processor 2 x 3.00GHZ Quad Core

There is an entry in the install log as follows: -

Action 10:14:17: pvswCA_CallCheckXioReqsMet. Determining XIO compatibility...
Action start 10:14:17: pvswCA_CallCheckXioReqsMet.
MSI (s) (D4:70) [10:14:17:406]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI7.tmp, Entrypoint: CheckXioReqsMet
Action: CheckXioReqsMet Description: Entering function.
Action: CheckXioReqsMet Description: Verify RDTSC is available.
Action: CheckXioReqsMet Description: Verify running on supported Window's OS.
Action: CheckXioReqsMet Description: Invalid Windows OS.
Action: CheckXioReqsMet Description: Setting property pvswXioReqsMet to '0'.
Action: CheckXioReqsMet Description: Exiting function.
Action ended 10:14:17: pvswCA_CallCheckXioReqsMet. Return value 1.
MSI (s) (D4:50) [10:14:17:421]: Skipping action: pvswCA_SetpvswAllXioChecksPassed (condition is false)

The server meets the requirements to install the X\IO driver. If they use the v10.10 BETA version it installs fine.

Why is it failing to see the server as a valid OS? Is there any way to force the install of X\IO?

Is it possible the system is running Windows Server 2003 x64 and not x86?  Can you post the lines from the end of the installation log that begin "Property (S): ..."?  That will give us more information on the system configuration.  Thanks

This is the only bit at the bottom of the log thats got anything to do with OS: -

Property(S): Intel = 6
Property(S): MsiNTProductType = 2
Property(S): PhysicalMemory = 16379
Property(S): RemoteAdminTS = 1
Property(S): ServicePackLevelMinor = 0
Property(S): SystemLanguageID = 1033
Property(S): VersionDatabase = 301
Property(S): VirtualMemory = 17918
Property(S): WindowsBuild = 3790

I've also checked with the customer and it is x86.

Please zip up and send me the entire MSI log file.  I've left you a PM with my email address.  Thanks

It turns out I didn't need the whole log file after all - the snippit you sent shows the system is configured as a Domain Controller ("Property(S): MsiNTProductType = 2").

There's a [currently not documented] known issue with the v10.00 PSQL 32-bit Server installation (FCS) that prevents XIO from being installed on a Windows Server 2003 SP2 system that is set up as a Domain Controller.  The issue was fixed in a subsequent PSQL v10 FTF release (update 10.10.55 or later).  Unfortunately, there isn't a way to apply the fix to the earlier FCS installation itself.  However, the steps outlined below should work. 

Steps:

1. Install v10.00 FCS 32-bit Server installation on the system.
2. Install v10 FTF update for 32-bit Server (10.01.055 or later - 10.01.070 is available here).
3. Run the 'Modify' option for the installation from the Add/Remove Programs control panel.  The modify installation process should now show XIO as one of the optional installation features.
4. Enable the XIO feature and complete the installation.

Please note that I don't have that configuration set up right now so I can't verify that the modify installation process properly interprets the fix (the change is to a library file embedded in the MSI patch package itself rather than any of the files that are updated on the system).  Please reply to this post and let us know if the steps above resolve the issue and I will ask our support team to issue a tech bulletin with the work around.  If not, there is a more technically involved solution that involves editing the cached version of the MSI database itself.  I'd prefer not to go there unless it's absolutely necessary.

Thanks

Just to let you know, your suggestion worked fine.

Thanks for your help.