catapultaudio
Experienced Member
- Joined
- Mar 18, 2013
- Location
- Leeds, UK
Hi everyone,
I've been playing a little at Roxy Palace the past few days as a result of the migration of many of my other casino accounts to this casino and receiving a few freebies etc ... I played there once in the past but immediately mistrusted them a little because of the 100x WR on their new player "welcome" free chip ...
Anyway, I haven't downloaded their viper client as yet so have been playing the flash games via their website. The games are bombing out VERY regularly with casino error 0, to an ASP error page mentioning something about the "AURORA Application" ... I'll edit this post with the exact message the next time it occurs.
It's extremely annoying! Anybody else experiencing this with Roxy Palace ? I can't imagine many recreational players would stick around long if they didn't understand what this error message was all about.
EDIT: Just five minutes to next error, here is the full text - I understand some of the text contained herein as I am a developer myself, I just do not understand why the game is constantly bombing out to this page for no apparent reason.
Server Error in '/AURORA' 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>
I've been playing a little at Roxy Palace the past few days as a result of the migration of many of my other casino accounts to this casino and receiving a few freebies etc ... I played there once in the past but immediately mistrusted them a little because of the 100x WR on their new player "welcome" free chip ...
Anyway, I haven't downloaded their viper client as yet so have been playing the flash games via their website. The games are bombing out VERY regularly with casino error 0, to an ASP error page mentioning something about the "AURORA Application" ... I'll edit this post with the exact message the next time it occurs.
It's extremely annoying! Anybody else experiencing this with Roxy Palace ? I can't imagine many recreational players would stick around long if they didn't understand what this error message was all about.
EDIT: Just five minutes to next error, here is the full text - I understand some of the text contained herein as I am a developer myself, I just do not understand why the game is constantly bombing out to this page for no apparent reason.
Server Error in '/AURORA' 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>
