Content Management Server stopped working after install of 4.8
I always installed everything manually in Daz until now. I resisted for a long time, waited and waited for the 4.8 Public Beta with Iray to come available but at last I downloaded the dreaded Download manager and installed it. And right enough both my new and old DS stopped working, that is the Content Management Server stopped working. Whenever it runs or not it do not connect to any of two my 2 Daz installations. Smart content do not work and more important for me as a vendor I can not set content type and compatible with when I save.
Post edited by vintorix on
Comments
Are you using Windows?
When you run DAZ Studio, look in the Task Manager and see if the CMS is running, or are there several versions of PostgreSQL running?
There is an option available in DIM to change to the newer (and more stable) PostgreSQL, did you install that?
You can also start CMS from the Start menu in Windows, All Programs > DAZ 3D, have you tried that? You can also reimport Metadata from the Content Library drop-down menu.
I doubt if installing DS4.8 had anything to do with CMS not running. The Beta installs to a completely different location than the normal version.
"Are you using Windows?"
Yes. Windows 8.1 64bit
"When you run DAZ Studio, look in the Task Manager and see if the CMS is running, or are there several versions of PostgreSQL running?"
I can not see CMS or PostgreSQL in the Task Manager. Not even after I start CMS from Start menu in Windows (which seem to go well I get no error messages)
"There is an option available in DIM to change to the newer (and more stable) PostgreSQL, did you install that?"
Yes, I did
"You can also start CMS from the Start menu in Windows, All Programs > DAZ 3D, have you tried that?"
Yes, as I mention above
"You can also reimport Metadata from the Content Library drop-down menu."
I have done that and everything seems ok but nothing shows up
There is the old Daz Content Management Service in Services but it is stopped and will not start, but I don't need this one anymore right?
"I doubt if installing DS4.8 had anything to do with CMS not running.
But I assumes that both programs (4.7 and 4.8) use the same CMS there is never TWO versions of CMS running? Or is it?
By the way can I uninstall the old 4.7 and its content Manager?
JimmyC_2009,
When I saw a lot of PostgresSQL error messages in the event manager I deleted PostgresSQL in the download manager and also the Daz 4.7 along with the Daz Content Managment Service. Then reinstalled Daz 4.7 and the Content Management Service. Now it works.
That is okay. After all it is Beta software.
When you first install Postgresql, you need to manually run a transfer script, which will fill the content of the old CMS database into the new database. The script is a separate download.
I fuess that something went wrong during the conversion of data from one system to the other?
"I fuss that something went wrong during the conversion of data from one system to the other?"
No, I don't care about Smart Content and never use it. Having worked with databases all my life I have no confidence in them. I have my own system of organization. The fault was that progress did not install correctly and in spite of that ordered both applications to use the new faulty database.
That is quite normal all in a days work. A database must be nursed like a baby all then time. But I have other things to do!
You aren't running ZoneAlarm by any chance?
No I use windows intrinsic firewall.
Smart Content and whatever organization system you use aren't really relevant to the process, as such. Even if you use your own system of organization, as long as you use the DAZ Studio database tools, you need to follow that process to get things to work properly.
Did you run the conversion script? If you didn't, then there is nothing for the database to import. You effectively have no metadata, as far as PostgreSQL is concerned. Valentina and PostgreSQL have different database formats, different database locations, different everything.
Also, if you're switching from the old pre 4.6 Valentina database system to PostgreSQL, you need to make sure that Studio actually knows where your new database is. The default location will be something like C:\users\username\Appdata\Roaming\DAZ 3D\cms\ContentCluster - you should be able to see where the location is in your Preferences. (I'm assuming that paths are more or less the same between Windows 7 and Windows 8.1; if they're not, then you'll need to figure out where everything is on your own.)
Did you change the location of your content or any programs? If so, you'll need to go into C:\users\username\Appdata\Roaming\DAZ 3D\ then delete dzinstall.ini, then reinstall Studio and PostgreSQL then try running the import script again. Reinstalling Studio this way will make sure that everything knows where everything else is.
vwrangler,
Thank you for the information I will remember that to next time. But when was this information when I needed it? I why can't the installer draw this information from the register as SQL Server should have done? Two possibilities exist, either I did something wrong or the beta program did something wrong. Assuming that I did something wrong is not Daz Studio primarily a program for hobbyists? I handle a dozen program every day including C4D, Zbrush, Marvelous Designer, Poser Pro, WrapX etc etc and have previously over 20 years experience as Programer/Consultant inclusive SQL Server and MySQL, But Daz Studio became my nemesis? Please.
(edit): Nota bene, I have been a member of this forum for several years and have never complained before! In case you should think I am only a cranky guy)
Well, I expect the information doesn't actually exist in the registry, so the installer can't pull it out. That's more or less what the dzinstall.ini file is for, and the installer IS looking at that file, unfortunately. The installer seems to be set not to touch dzinstall.ini if it exists, so any incorrect paths will be retained. (THAT information doesn't exist anywhere that I know of; I found that out through painful experience.) It would be nice if the installers had more auto-detection, or at least more steps where it confirmed all the paths, and not just the program and content paths. According to the release notes for RC3, they've finally dropped the Valentina installer and put the PostgreSQL installer into the Studio installer, so maybe it will be better set up to figure out where things are.
Since 4.7 has been around for several months, and the need for converting databases came with that version, I suspect DAZ has been assuming that most people are going to upgrade from 4.7 to 4.8, and not from a version that uses Valentina, so they would have converted the database already; there were instructions all over the forum about converting from Valentina to PostgreSQL at the time, and lots of people getting confused when the process went weird. And the beta program is, in fact, a beta program, not a full release, so it's entirely probable that something went wrong. Having both a beta and a production version on the same system at the same time is just difficult enough to manage that I haven't wanted to bother, myself; I'm perfectly happy NOT to be the canary in the coal mine for this one.
It would probably be a good idea, when 4.8 goes final, for DAZ to link to instructions for converting the database, for those people who didn't upgrade from 4.5/6 until now. There may be a fair number of people who haven't wanted the difficulty of backing up databases and converting and whatnot, but who might want to do so now.
And, of course, none of that helps you now. That said, if you haven't done anything to your databases -- and maybe even if you have, as long as you haven't deleted anything -- if you run the conversion script NOW, then run the metadata import tools, it should still work. Worth a try, in any event.