.Net 2.0 Bug when starting PVRX2

[jusbo]

Ok Scenario:

GBPVR Happily working on my server (MediaBox) I wrote a batch that turns off VMC and turns on the GBPVR recording service. Verified that it works I can watch TV on the server, get guide data the whole enchalata.
(Sorry...version of both programs is 1.0.21.3)

Laptop (the client)
I installed the same program and set it up as Sharing instead of streaming everything configured great.
I have .Net 2 and directX 9.0c so everything should be peachy. When I right click on the g in the tray and start PVRx2 it takes a minute then I get an "Unhandled exception in a component in your application"

I click continue and the PVRx2 box comes up with a white background and a thin "X"....like the program didn't get called or something.I have a screenshot available and more info if anyone needs it to see whats going on. Im lost.
thanks for any help in advance!

[McBainUK]

Best thing would be to zip and attach the log files from the gbpvr/Logs/ folder. Best one to start with is pvrx2.exe.log

[gEd]

I had this problem on my laptop. A repair of .NET 2.0 fixed it. (via add/remove programs, change option IIRC)

[jusbo]

Ok here are the logs:

.Net log when error occurs
PVRx2 log: nothing seems out of the ordinary...but then again I don't know what should be there.
PVRx2-native log: Not sure...but there it is.

I have tried that gED....still same thing...I have also completely uninstalled every .net frame work I had installed (1 2 & now 3) and d/l it seems like every friggin' HOTFIX under the sun, no avail so far.

[Dracmarcz]

Just wanted to add that I'm having the same problem with 1.2.13.

I have .Net2.0 and the Updated C++ Runtime installed. My log files finish at the same point as jusbo.

If I turn off "Configure this machine to act as a client" then it starts ok.

[jusbo]

Didn't think anyone would have a clue either. Perhaps it will work on XPe fresh install. Good luck !

[Dracmarcz]

Just wanted to add that I fixed it by correcting some connectivity problems between the server and client.

The problems I had were:

• Wrong IP address being used by the client for the server due to VMware Sever being installed on the server - the VMware IP address was being used
  
• Windows Firewall configuration
  

Generally I kept looking at the client log to see what it was trying to do.

[whurlston]

I click continue and the PVRx2 box comes up with a white background and a thin "X"....like the program didn't get called or something.I have a screenshot available and more info if anyone needs it to see whats going on. Im lost.
thanks for any help in advance!

I had the same issue with my Netflix plugin when I set the data drive to a mapped drive on another machine. It was a Seagate FreeAgent drive and it turned out that the drive was going to sleep after 15 mins of inactivity and when GBPVR went to access it, the drive did not spin up quick enough. Preventing the drive from going to sleep solved the issue. To test if this is the problem, access the drive through Windows Explorer to spin it up and then try running GBPVR from the client.

[eeknz]

I've had this same issue since I rebuilt the server machine.
The server machine has windows firewall disabled and from any of 3 clients, I can read and write to all shared directories. I've reset permissions on existing files to give users full control as there was a run where access to config.xml on the server machine was denied.
I'm running 2.1.13.
The server machine is XP Pro with Nvidia 6200, 2 PVR150s and a Nova-S.

The clients are XP Pro SP2 or Vista SP1. I've removed .net 2 completley and reinstalled .net 2 without the SP1. I've installed the patch to correct a similar issue I found on the forum.
I've removed everything from an XP client and reinstalled 1.0.15 and upgraded it to 2.1.113 to be sure the skin directory being missing problem isn't the cause.

The logs just stop without any mention of an error

The client machines are running mostly ordinary on board video to CRT's except one which is running NVidia 5200 to a TV. It was all just fine before I rebuilt the server machine where I changed from Intel P4 to an AMD XP2100. The Intel was crashing a lot and the XP2100 was lying about.

The AMD based server machine works great. Records everything it should and plays everything it shoud, but was nearly the only thing to change.
The other thing that changed was dropping the W2K3 server with a domain and going to Windows Home server, so there is no common users database and DHCP runs from the router.
The server is wide open and guests and change files over the wire. The access denied to config.xml has gone, so I don't believe it's permissions.
The name \\tvpc can be resolved and pings so I don't think it's name resolution. That was the other thing that changed though so it may be relevant.

Is there something more you would need to do on the server with an old AMD CPU that you wouldn't need to do on an Intel? It was a fresh install with MP10 and the C and .net dependencies. Added WinDVD, CCCP codec pack and GBPVR and that's all.

XP Client's machine had the name changed in the client mode config to the name of the new server and it's been .net unhandled exception hell ever since. If they worked before, I don't quite get why they don't now. The server is working better than ever. The network appears functional. I've run out of ideas.

Thanks

[sub]

Zip and attach the logs and I'll take a look.