Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[dasymington]

Whenever I try to switch to a Mini-Me skin, I get:

JScript Error.
Code = 80070057
Code meaning = The parameter is incorrect.
Source - ScriptControl
Description - The object cannot be nothing.

This is since upgrading to 11.0.297.

Anyone have any ideas?

[dasymington]

I've installed 299 and the problem seems to have gone away.

[dasymington]

I take that back: after rebooting the PC the JScript problem is occurring again and I can't switch to the Mini-Me Skins.

[dasymington]

I've gone back to build 270 as it's the only way I can get the Mini View to work. Is anyone else having this problem? 

[dcwebman]

I use a Mini Me skin everyday and haven't had a problem with it in a long time, and I've been upgrading to every build that comes out.

[dasymington]

I use a Mini Me skin everyday and haven't had a problem with it in a long time, and I've been upgrading to every build that comes out.

When you upgrade, do you just apply the new build over the old, or do you uninstall first?

[dcwebman]

Just install over the old.

[dasymington]

It doesn't matter whether I install a later version over 270 or uninstall and then install from scratch, I still get the error and can't use Mini View with versions after 270.

Am I stuck with version 270 forever? Can anyone tell me what the JScript error is and what might be causing it?

[dasymington]

Hello, I realise that this issue might not seem very important compared to some, but it's been on the board now for two weeks and, as there doesn't seem to be any other way to obtain support for this purchased software, I'd appreciate a response from J River.

[dasymington]

I wasn't too concerned about this error because I could get MC to work without the error by going back to version 270; however, MC has now automatically updated to the latest version and I'm getting the error again:

When I switch to a Mini-Me skin, I get:

JScript Error.
Code = 80070057
Code meaning = The parameter is incorrect.
Source - ScriptControl
Description - The object cannot be nothing.

Could someone from JRiver tell me what this error means and how to get the latest version of Media Center working properly, please.

[JimH]

I don't think MC uses jscript so I don't know why you'd get that error.

Any mini-skin?

What else are you running with MC?  Any third party plug-ins?

[<°)))))><]

There's an "main.js" file inherent in every mini skin...

[JimH]

I stand corrected.  Thanks.

Can anyone else duplicate this problem?

[dasymington]

Cover Art Finder and Lyrics Finder are installed. I'm also using NetRemote MediaBridge, but I've tried it without that and I still get the error.

I'm using the LowerRight Mini-Me skin mainly, but the error happens no matter which one I use.

[JimH]

Uninstall all third party software and reboot to eliminate it as a factor.

[dasymington]

I uninstalled the third party plug-ins, rebooted and updated MC11 to the latest version. It worked OK initially but after a reboot I get the same error message when I use a Mini-Me skin.

Can you suggest anything else?

[JimH]

The fact that it worked initially may provide a clue.  Can you get it to do that again?

[dasymington]

The fact that it worked initially may provide a clue.  Can you get it to do that again?

Only by re-installing version 270 and then updating to the latest version again.

[GHammer]

Have you tried enabling MC debug logging?
It might catch something useful.

I'd try General & Skinning.

[dasymington]

Below is what it shows when I start up MC then switch to Mini-Me. It doesn't catch anything about the error. That's with General and Skinning enabled. I tried it with everything enabled but it still didn't catch the error.

19:15:39: General: CMCPlayerApp::InitInstance: Start
19:15:39: General: CMCPlayerApp::InitInstance: Loading file types
19:15:39: General: CMCPlayerApp::InitInstance: Loading options helper
19:15:39: General: CMCPlayerApp::InitInstance: Registering objects
19:15:39: General: CMCPlayerApp::InitInstance: Initializing automation SDK
19:15:39: General: CMCPlayerApp::InitInstance: Checking for proper installation
19:15:39: General: CMCPlayerApp::InitInstance: Creating MC core
19:15:39: General: CMCPlayerApp::InitInstance: Creating database core
19:15:39: General: CMCPlayerApp::InitInstance: Creating skinning
19:15:39: General: CMCPlayerApp::InitInstance: Creating tools core
19:15:39: General: CMCPlayerApp::InitInstance: Setting up ASPI
19:15:39: General: CMCPlayerApp::InitInstance: Loading global settings
19:15:40: General: CMCPlayerApp::InitInstance: Cleaning up any previous intalls
19:15:40: General: CMCPlayerApp::InitInstance: Processing command line:
19:15:40: General: CMCPlayerApp::InitInstance: Initializing components
19:15:40: General: CMCPlayerApp::InitInstance: Loading skin
19:15:40: General: CMCPlayerApp::InitInstance: Creating player core
19:15:40: General: CMCPlayerApp::InitInstance: Processing startup settings
19:15:40: General: CPropertiesFileAssocDlg::CPropertiesFileAssocDlg: Start
19:15:40: General: CPropertiesFileAssocDlg::CPropertiesFileAssocDlg: Finish (0 ms)
19:15:40: General: CMCPlayerApp::InitInstance: Creating resource helper
19:15:40: General: CMCPlayerApp::InitInstance: Loading library
19:15:40: General: CMCPlayerApp::InitInstance: Creating main UI
19:15:41: General: CMCPlayerApp::InitInstance: Initializing services
19:15:41: General: CMCPlayerApp::InitInstance: Updating after database load
19:15:42: General: CMCPlayerApp::InitInstance: Updating and showing UI
19:15:42: General: CMCPlayerApp::InitInstance: Updated window positioning
19:15:42: General: CMCPlayerApp::InitInstance: Updating startup settings
19:15:42: General: CMCPlayerApp::InitInstance: Checking for handheld devices
19:15:45: General: CMCPlayerApp::InitInstance: Version: JRiver Media Center 11.0.309 (registered)
19:15:45: General: CMCPlayerApp::InitInstance: Finish (5890 ms)

[GHammer]

Below is what it shows when I start up MC then switch to Mini-Me. It doesn't catch anything about the error. That's with General and Skinning enabled. I tried it with everything enabled but it still didn't catch the error.

Anything in your Application or System event logs?

[dasymington]

Yes, each time it errors the event log shows:

Event Type:   Error
Event Source:   Application Error
Event Category:   None
Event ID:   1000
Date:      31/07/2005
Time:      19:19:17
User:      N/A
Computer:   DAS
Description:
Faulting application media center.exe, version 11.0.309.0, faulting module media center.exe, version 11.0.309.0, fault address 0x0028f274.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 6d 65 64   ure  med
0018: 69 61 20 63 65 6e 74 65   ia cente
0020: 72 2e 65 78 65 20 31 31   r.exe 11
0028: 2e 30 2e 33 30 39 2e 30   .0.309.0
0030: 20 69 6e 20 6d 65 64 69    in medi
0038: 61 20 63 65 6e 74 65 72   a center
0040: 2e 65 78 65 20 31 31 2e   .exe 11.
0048: 30 2e 33 30 39 2e 30 20   0.309.0
0050: 61 74 20 6f 66 66 73 65   at offse
0058: 74 20 30 30 32 38 66 32   t 0028f2
0060: 37 34 0d 0a               74..   

[GHammer]

That may be a clue.

[dasymington]

It might be significant that if MC11 is playing a song it continues to play even when the error message appears and you click OK, and then when the Windows problem pop-up appears, and only stops playing when you click the latter dialogue.

Something's definitely changed between version 270 and the latest one to cause this behaviour. What could it be?

[dasymington]

Thanks for all your help. I didn't realise that NetRemote installed anything into MC11. I've uninstalled it and upgraded MC11 to version 309 and the mini-me skin now works; however, when I install NetRemote again I get the same jScript error.

I guess I should look on the NetRemote forum for further clues, unless you can suggest anything.

[dasymington]

Proximis have said:

Is it possible that for their new Mini-Me they're using COM, and MediaBridge already has the COM object?

I hate to pass the buck, but if this worked previous to their new release, I'm hesitant to accept that it's a NetRemote/MediaBridge issue. What did they change?

and that does seem reasonable. Anyone have any suggestions as to why the Mini-Me skins would work in MC11 version 207 with MediaBridge installed but only in MC11 version 309 when MediaBridge is not installed?

Is anyone else using NetRemote Music/MediaBridge with MC11?

[lambert282]

Yes I'm using it.  I get the same error with mini-me.  I suspect there is something broken in the com side of things.  I think there are other issues that promixis have reported in connection with the com interface and AFAIK these are still outstanding problems.

[JimH]

Please copy your system info from MC Help and paste it here.

We talked about this error and couldn't come up with much.  The only thing that was suggested was that it could be a java engine problem on the PC.

Can you provide a link to a thread on the Promixis forum?

[lambert282]

http://www.promixis.com/phpBB2/viewtopic.php?t=12201

[dasymington]

Here's my system information:

Media Center Registered 11.0.309 -- C:\Program Files\J River\Media Center 11\

Microsoft Windows XP 5.1 Service Pack 2 (Build 2600)
Intel Pentium 4 3198 MHz MMX / Memory: Total - 1047 MB, Free - 586 MB

Internet Explorer: 6.0.2900.2180 / ComCtl32.dll: 5.82 (xpsp_sp2_rtm.040803-2158) / Shlwapi.dll: 6.00.2900.2668 (xpsp_sp2_gdr.050430-1553) / Shell32.dll: 6.00.2900.2620 (xpsp_sp2_gdr.050225-1820) / wnaspi32.dll: N/A
Ripping /   Drive F:   Mode:Normal  Type:Auto  Speed:Max
  Drive I: HP      DVD Writer 400c   Mode:Normal  Type:Auto  Speed:Max
  Digital playback: Yes /  Use YADB: Yes /  Get cover art: No /  Calc replay gain: Yes /  Copy volume: 32767
  Eject after ripping: Yes /  Play sound after ripping: No 

Burning /  Drive I: HP       DVD Writer 400c    Addr: 3:0:0  Speed:24  MaxSpeed:24  BurnProof:Yes
  Test mode: No /  Eject after writing: Yes /  Direct decoding: Yes /  Write CD-Text: Yes
  Use playback settings: No /  Normalization: None