X

Tom Clancy's Rainbow Six: Lockdown Latest News - PC

Tom Clancy's Rainbow Six: Lockdown
Game Description: In this new episode, you lead Team Rainbow, the world's most elite counter-terrorist unit, as they are called into action and unfamiliar territory to battle a bioterrorist threat. Stakes escalate as they are personally targeted by an evil terrorist organization. Used to protecting the lives of others, Team Rainbow must now embark on a mission to fight and save some of their own.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Tom Clancy's Rainbow Six: Lockdown News

Displaying 1–1 of 1 articles

  • Ubisoft Has Two New Tom Clancy Games Currently In Development

    Ubisoft might have just recently shipped Tom Clancy’s Splinter Cell: Conviction, and Tom Clancy’s Ghost Recon: Future Soldier is on the horizon, but that doesn’t mean the publisher is sitting on its Clancy-loving laurels. “At this moment I’m working on two Tom Clancy games which have just gone in...

    Posted April 28, 2010

    Ubisoft Has Two New Tom Clancy Games Currently In Development
  • The Story So Far: Rainbow Six

    Posted: March 11, 2008

    2,592 Views | 02:41 | 1 Comment

 


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>