Content Management lost
![AndyS](https://secure.gravatar.com/avatar/1aad5c42261a939232ac0da72b530cb8?&r=pg&s=100&d=https%3A%2F%2Fvanillicon.com%2F1aad5c42261a939232ac0da72b530cb8_100.png)
Help!
As I started DAZ today, I ad once saw, that the "New" marks on a lot of the entries in the Content Library Pane were missing.
But worse:
- the smart content is completely gone,
- in the content library pane the entrie to list all installed product (A-Z) is missing
- the categorisation of the entries (prop, scene, materials, ...) are gone.
What can I do to rebuild the CMS again?
Version: DAZ 4.8, used the old Valentina (or how it is called) - no PostgrSQL
Post edited by AndyS on
Comments
First check and make sure that Valentina is running as a service...if it isn't then nothing else will matter.
How / where?
P.S.
OK, found it in the Windows Task manager.
I could start it manually. Afterwards CMS was active again.
But why didn't it start together with the startup of DAZ?
Not sure...
But when everything disappears like that, the first thing to check is if CMS is actually running, because most of the time, that's why nothing is poplulated.
The second common reason is database corruption.
Yes, you're right.
But shouldn't it be synchronized with DAZ? Don't know, how it was before.
The situation now:
CMS is started when the computer starts. It is still running even long after closing of DAZ.
Shutting down Windows now takes way more time.
That's the way Valentina has always been.
Even the stand alone Valentina runs as a service, from boot up to shutdown.
Ah OK,
thank you.
Note that you might have been bitten by one of the reasons DAZ changed to using the PostgreSQL database, and D|S4.9 doesn't even use Valentina any more — the old CMS was just too unstable and fragile, and sometimes corrupted the database or decided not to work at the least excuse.
No, don't think.
It was only an odd incident, that stopped the valentina service. And on the following startup, Windows didn't start the service again, although it was flagged "automatic".
I never experienced any problems with it. No corruptions, no slow respond times.
As already stated:
After once manually restarting the service, now it runs without any problem every session.