Print

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

[TreeFrog77]

Just downloaded .358 and when trying to upgrade, I get an error:

"Failed To Create Media Center Directory."

This happens right after I select "Express" or "Custom" installation option.  After I click okay on the error, it just tells me to reboot and try again (which I've done) or uninstall/reinstall (which I do not want to do unless last resort).

I probably would think that this isn't something with MC, but more likely my computer.  This is a new machine I just installed MC on a few weeks ago and I think this is the first time I've attempted to upgrade to a newer version on that machine (so I'm sure it's a permissions or some other funky little thing).

Question is... Is there an install log created somewhere that might help me figure out what the installer is really trying to do and at what step it is failing?

The error about failing to create the directory is not very descriptive.  I mean, MC is already installed, so the directory (at least the main program directory and everything) is already there, so I'm not sure what directory it's talking about.

Here is the system info (but not sure if it really matters):

Media Center Registered 12.0.338 -- C:\Program Files\J River\Media Center 12\

Microsoft Windows XP 5.1 Service Pack 2 (Build 2600)
AMD Athlon 2080 MHz MMX / Memory: Total - 1506 MB, Free - 1009 MB

Internet Explorer: 7.0.5730.11 / ComCtl32.dll: 5.82.2900 / Shlwapi.dll: 6.0.2900 / Shell32.dll: 6.0.2900 / wnaspi32.dll: N/A
Ripping /   Drive D:   Mode:Normal  Type:Auto  Speed:Max
  Drive E:   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 E: SONY     CD-RW  CRX215E5    Addr: 2:1:0  Speed:48  MaxSpeed:48  BurnProof:Yes
  Test mode: No /  Eject after writing: No /  Direct decoding: Yes /  Write CD-Text: No
  Use playback settings: Yes /

Portable Device Info
  Removed devices:


Interface Plugins:
  last.fm (Active)
  Library Server (Active/Enabled)
  TiVo Server (Active/Enabled)
  UPnP Server (Active/Enabled)

[JimH]

Do you have admin rights?

[TreeFrog77]

Yes, the user does.  I only have two users defined on that system and they both have admin.  The user I was under while trying to upgrade was not the same user I used when I installed it.  I tried also taking ownership of the j river directory in program files, but that didn't do anything.

I just switched to the user I used to originally install and it did it just fine.  Not really why since they are both admin, but oh well.  I hate XP Home Ed.

[Matt]

I just switched to the user I used to originally install and it did it just fine.  Not really why since they are both admin, but oh well.  I hate XP Home Ed.

Since this is a rare problem, I think it's probably permissions.  An uninstall / reinstall under the "locked" user account might fix it.

I personally find NTFS permissions vexxing -- every directory in the hierarchy can contribute rules, and it never feels very straightforward to manage.

[TreeFrog77]

Well, as an x-MSCE, I'm fully aware about NT/XPs permissions... they are just as not fun in UNIX-based systems either.  That's why I hate XP Home cause it tries to hide too much from you.  Both of the users are Admins, so I don't really see the problem (especially since I don't even know what directory the MC installer was trying to "create", since the program was already installed).

I would move that machine to XP Pro, but don't really need to nor pay even more MS tax for an already-depreciated OS (and no way Vista is going on a prod-box).

I should probably change this user that is normally logged in running MC and my home automation and such to a limited user anywho.

Just FYI... my home server just got moved to a new machine with XP a few weeks ago.  Up until then, it had been running Win 2000 with never a single crash or problem for many years.  When it comes to home automation (I include MC in that), if it ain't broke, definately do not fix it.  I've learned more and more to treat that box the same as we would a production server at work.