Hi Tristan,

All elements require .NET 3.5 runtime...but will run on XP/SP2+; Win Server 2003 (32 and 64); as well as Vista and Win Server 2008. The only thing you give up on XP/WIn Server 2003 is the ability in IIS 6 to host non-http/https endpoints (such as net.tcp) within an IIS-hosted service--IIS 6 can only deal with http/https schemes;...With IIS 7 (Vista/Server 2008) there is a feature called WAS Hosting; which allows IIS 7 to optionally host non-http based endpoint such as tcp/binary; and net.msmq). However, setup is smart enough not to create non-http based endpoints for IIS-hosted services when installing on Win Server 2003/XP; and all should work. You can of course still hosttcp/binary and msmq on XP and Win Server 2003 when hosting in an NT Service (or other non-IIS app); and of course Consume TCP/binary and MSMQ service endpoints from IIS 6 as a service client. But again, setup does right thing here based on OS you install on.

So I know of nothing save point above (just an incremental feature StockTrader shows when run on IIS 7) that is a difference beween the samples, cnofig service, etc on the platforms mentioned.

-Greg

Hi Tristan,

All elements require .NET 3.5 runtime...but will run on XP/SP2+; Win Server 2003 (32 and 64); as well as Vista and Win Server 2008. The only thing you give up on XP/WIn Server 2003 is the ability in IIS 6 to host non-http/https endpoints (such as net.tcp) within an IIS-hosted service--IIS 6 can only deal with http/https schemes;...With IIS 7 (Vista/Server 2008) there is a feature called WAS Hosting; which allows IIS 7 to optionally host non-http based endpoint such as tcp/binary; and net.msmq). However, setup is smart enough not to create non-http based endpoints for IIS-hosted services when installing on Win Server 2003/XP; and all should work. You can of course still hosttcp/binary and msmq on XP and Win Server 2003 when hosting in an NT Service (or other non-IIS app); and of course Consume TCP/binary and MSMQ service endpoints from IIS 6 as a service client. But again, setup does right thing here based on OS you install on.

So I know of nothing save point above (just an incremental feature StockTrader shows when run on IIS 7) that is a difference beween the samples, cnofig service, etc on the platforms mentioned.

-Greg

Hi Greg,

I tried to install .Net 3.5 runtime on anewly installedWindows 2008 Server Ent x64machine in an attempt to get the benchmark running. During the installation of Windows 2008, I added the IIS feature, complete with .Net framework 3, msmq, etc. However, installation of the 209mb dotnetfx35 package keeps repeatedly failing with an error 1603. Have you observed any peculiarities or have applied a specific install sequence in your lab when prepping a Windows 2008 machine for stocktrader? Are thereparticular windows services that need to be stopped oralready runningprior to installing dotnet 3.5 framework? At the time of installation, IIS Admin and web server services are running. I have also enabled Themes to get the Vista Aero UI feature on that same machine. Not sure if this is preventing WPF bits coming via the 3.5 runtime from being installed. I will try installing again with this feature disabled.

I've already used aaron stebner's blog (http://blogs.msdn.com/astebner/archive/2008/04/30/8445569.aspx)to try and diagnose the install issue but I haven't been able to pinpoint what is wrong so far. I will most likely have to enable verbose msi logging and pass it on to him.

Thanks in advance,
Tristan

I have installed netfx 3.5 on many x64 win server 2008 machines without issue. I would enable all the roles first with the integrated 3.0 runtime; then install .NET 3.5 runtime....I have not had this issue installing 3.5 on such machines, in that order.....I will do some further research, though... You want the app server and web server roles enabled, with all role features enabled for each...then try the net 3.5 install again....

-Greg

Thanks Greg for the prompt response. As it turns out, I was missing the Application Server role. Installing that allowed me to install the runtime succesfully.

When I try to install the latest available StockTraderSetup.msi on Windows Server 2008 Enterprise (x86), I receive the following message box immediately which prevents me:


Windows Installer
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.

This is a fairly fresh install of Win2k8. I've made to sure to enable the Application Server and Web Server (IIS) roles. Am I missing something else?

Thanks,
Jeffrey

I think the download just got corrupted. Try downloading again (saving locally and then running). It is also possible one of the download mirrored sites has a bad msi; but every time I try the install, it works fine; should be no issue on any edition of Win Server 2008.

-Greg

---

Greg Leake, Microsoft

I'm constantly getting the same issue as JLeCours.

I've tried 3 times now and each time results in the same error.

Windows Installer
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.

I'm running Windows XP Pro 32bit Service Pack 3

Any way I can access a mirrored sitethat isn't corrupted?