Results 1 to 2 of 2

Thread: Skin Plugin Causing Unhandled Exception Error

  1. #1
    Join Date
    Feb 2008
    Location
    United States
    Posts
    49

    Skin Plugin Causing Unhandled Exception Error

    I have the latest version of GBPVR installed on both a host and client machine. I the Community SD Skin with the Glow Theme installed on both computers. When I enter "Skin" from the GBPVR menu on the host machine or via MediaMVP, everything works as expected. However, whenever I try to enter "Dkin" through GBPVR's menu on the client machine, I received the following error:

    "Unhandled exception has occurred in a component in your application..."
    "Object reference not set to an instance of an object."
    [The error details are in the "Windows Error.txt" file in the attached logs zip.]


    Following the error, the GBPVR instance will eventually become responsive again, but it does not enter the "Skin" menu.

    Both machines are running Windows 7 and are both up to date with Windows Update. Also, both installations of GBPVR are the same with the exception of the MediaMVP Position plugin on the host machine.

    EDIT: I wanted to add that when looking through the logs' errors, I am seeing a number of references to the D: drive. On my client machine, the D: drive is just a small factory installed, HP Recovery partition only. Not sure if that is an issue or not.

    Does anyone have any advice/input? The client machine seems to schedule and perform other PVR functions as needed without issue except for this "Skin" issue. Thanks in advance.

  2. #2
    Join Date
    Feb 2008
    Location
    United States
    Posts
    49
    Nevermind, finally figured out the problem. I had previously had my client computer setup as a client a year ago or so when I had an older PVR that eventually died. I evidently did not pay enough attention when I uninstalled GBPVR the first go around. Evidently, I had a leftover from the old community skin from my last install. It was a skinplugin folder in the Plugins folder. The skinplugin4 folder was there too, but the skinplugin was wreaking havoc with the newest skin plugin. Not sure why, but it was. Solution: I just deleted the skinplugin folder from the plugins folder and everything works just fine now. Go figure!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •