Loading...
> >

Content Manager Keeps shutting down.

deleted userdeleted user Posts: 1,204
edited December 1969 in New Users

Anybody else having this issue? I've tried everything I can think of.
Firewalls, reinstalling Daz, firing up Content manger Before Daz, Firing it up after opening Daz. I've tried everything I can think of.
I'm fresh out of idea's.

Comments

  • fixmypcmikefixmypcmike Posts: 19,583
    edited December 1969

    Do you have custom content folders? If not, uninstall CMS, delete the database files, then reinstall DS.

  • SpottedKittySpottedKitty Posts: 7,232
    edited December 1969

    The CMS just plain won't work on some systems. In my case — and I'm not alone — I can't run D|S if I leave the CMS installed. (I don't want or need to use it, so I don't mind.) You might turn out to be just unlucky, although if the uninstall/reinstall doesn't work a bug report might get you somewhere.

  • Dino GrampsDino Gramps Posts: 0
    edited December 1969

    If it was working before and stopped, it is a database issue. There are several threads on how to fix it. Do a search for content manager in these forums. If it never worked then maybe a bug report is in order.

  • TotteTotte Posts: 13,977
    edited December 1969

    Check the CMS log (vlog). If it's a corrupt index, just stop CMS delete the .ind file and then start the CMS again and it will rebuild the index.

  • JStryderJStryder Posts: 168
    edited December 1969

    Yes I've had this problem a lot lately. CMS keeps stopping without warning or reason. It can be restarted, but eventually (e.g., maybe only a few sessions or not so many hours of work) it stops at a bad time and corrupts the database, which then has to be rebuilt by uninstalling everything. CMS is really not usable unless it is stable and always running. Have not heard any clues as to why CMS keeps stopping or how to keep it running stable.

  • TotteTotte Posts: 13,977
    edited December 1969

    Check the log (vlog), and depending on your OS, check the crash logs if any. If you're on Mac OS X, post last lines of vlog and first 100 line of the crashlog here and I can probably find something out.

  • JaderailJaderail Posts: 0
    edited December 1969

    You do not NEED to re-install to rebuild the Database. Just Delete the old one and use the DataBase Management function in DS to re-import and build a new one. You can Also export one and then Import it back. Re-install is the LONG way to do it.

  • JStryderJStryder Posts: 168
    edited December 1969

    Thanks, I will try that next time. This time, I had to move the CMS database from my e:drive to the c: drive default location, so I did a complete uninstall/reinstall. Will see if that works any better.

Sign In or Register to comment.