Installing Casino and Admin 2.0.

2xx

Prerequisites Database Server SQL Server 2005 or higher installed in mixed mode Web Server IIS 6.0 or higher SQLXML 4.0 (make sure you get the right version 32 or 64 bit) ASP.NET 4.0

Web Server Setup

1. Copy the CasinoSolutions folder from the current casino production server. Make sure that you copy directly to the root of the drive letter so that folder permission wont get altered by actions such as copying over to the desktop.

2. Edit both web.config files with the name of the database server. If the DB server remains the same, no need for this step. These files are located in the following locations: \\CasinoRoot\Games\aspnet\web.config \\AdminRoot\Admin\web.config

3. Open IIS, create a virtual directory named Games and point it to \CasinoSolutions\CasinoRoot\Games

4. On ASPNET subfolder, go to properties and turn it into an application using ASP 4 Classic AppPool

5. At this point you may test the games by browsing these locations: Demo mode /Games/aspnet/CasinoLobby/Demo.aspx Real account mode /Games/aspnet/CasinoLobby/Lobby.aspx 6. Create a new web site named Admin preferably using an local (internal) IP address using TCP port 8080 (another port may be used based on availability). Point the site to \CasinoSolutions\AdminRoot and assing Classic .Net AppPool. Optionally you may add index.aspx as one of the default documents for this site.

7. On the Admin subfolder, edit the properties and make it an application.

Troubleshooting Games return error message Casino Closed Run this site ../Games/aspnet/support/setup.aspx This usually resolves this issue.

Blanc Demo.aspx page Loading Lobby.aspx will provide a full set of error messages which will shed light on where the problem may reside.

Page Lobby.aspx returns error that SQL server cannot be found. In this case check the following: o If the SQL used is an instance, edit the web.config file using the following format: SERVER\INSTANCE rather than just the SERVER name As a quick test, momentarily deactivate Windows Firewall on the database server to test connectivity. Should this be the cause add the following rule to Window Firewall on the database server:

While loading any ASPX page an error is returned from the main sites web.config (not ours): o If the error refers to a <httpModule> a location path may be added to the sites web.config and remove it for our Games folder:
<location path="Games"> <system.web> <httpModules> <remove name="SomeStupidHttpModule"/> </httpModules> </system.web> </location>

If thing get too complicated simply install the casino as a website on its own.

All ASPX pages return a 404 error This is common in Windows Server 2003 and usually means that Web Extensions in .NET Framework arent allowed (enabled). On IIS 7 ASP.Net 4 may not be allowed. Enable at the root of IIS.