|
|
|
|
|
Topic: RAMIREZRACING.COM
|
Email this topic to a friend |
Subscribe to this Topic
| Report this Topic to Moderator
|
|
Page 1 of 1 of 2 replies
|
|
|
|
December 17, 2009 at
10:51:27 AM
|
|
|
Joined:
|
08/28/2009
|
|
Posts:
|
19
|
|
|
|
Our website is up! We have a few changes to make. But we're up and going now. ENJOY!
ramirezracing.com
David, if this effects you please make the needed changes. Same domain name so it shouldn't. Thanx!
Randy
Don't be jelous
|
|
|
|
|
December 17, 2009 at
11:23:09 AM
|
|
|
Joined:
|
05/29/2007
|
|
Posts:
|
369
|
|
|
|
This is what I get when I go to the website....
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>
|
Oklahoma Sports Park Photos
https://www.facebook.com/TKCRaceNightPhotos
|
|
|
|
December 17, 2009 at
11:58:27 AM
|
|
|
Joined:
|
07/23/2005
|
|
Posts:
|
7
|
|
|
|
Works fine for me
|
|
|
