Error message in EWA

[gazoo]

I tried to go to the next day at 2:00 AM and I get this error:

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>

[psycik]

Do the same thing on your server (i.e be on the server and connect to http:\\localhost:7647\gbpvr )


and you'll get a real error message.....There is also a setting within the web.config you can change but I never know what it is...I think UJB has posted about it before.

[gazoo]

it won't do it local for some reason. I'm on a VPN, but I don't really think that's the reason since I get an IP address on that very subnet. I'll try again at home from another machine.

[psycik]

you'll need to do it on the server talking to itself, or you wont get the proper error message.

[UncleJohnsBand]

psycik is correct.....have to do it on the local machine to see the actual error being produced.

[gazoo]

That's what I meant, sorry. I did a vnc session to the actual machine and did the localhost webpage and everything worked..no errors.

[UncleJohnsBand]

That's what I meant, sorry. I did a vnc session to the actual machine and did the localhost webpage and everything worked..no errors.

Then it is something that is occuring in your VPN setup or perhaps the firewall on your local machine. Do you have the ports open on your firewall on the local machine?

[gazoo]

I'll check it out again today. I flushed the EPG and reloaded.

There really should be no problem since to the pvrx2 machine, it looks like it's talking to a machine on its own subnet. If it is related to the vpn, then it would be something having to do with smb protocol. That sometimes gets screwy over the vpn. Broadcasting nmb/smb over the vpn sometimes doesn't happen or happen real quick.

[gazoo]

Ok even weirder stuff now. No more error. I flushed the EPG on my STB pay channel source (MCE 150 s-video inputs) and reloaded. They show up fine in TV listings, but I only get half the channels on EWA. So, for example, I usually get channels 100-340 but now I only get 100-175, 244-256 and that's it!

I'm gonna reboot, let's hope it's some weird anamoly.

[UncleJohnsBand]

Ok even weirder stuff now. No more error. I flushed the EPG on my STB pay channel source (MCE 150 s-video inputs) and reloaded. They show up fine in TV listings, but I only get half the channels on EWA. So, for example, I usually get channels 100-340 but now I only get 100-175, 244-256 and that's it!

I'm gonna reboot, let's hope it's some weird anamoly.

Probably is.....EWA is mainly a web face to GBPVR.....all calls and data (except for some EWA specific settings) come from the same database the GBPVR uses.

Have you looked at the GBPVR PC client to see if you are seeing the same anomalies?