Where's my Smart Content? (Mac)
gw3972
Posts: 50
I installed v4.6 of DAZ Studio and then redownloaded all my products into a fresh directory using the Install Manager.
Nothing shows up under Smart Content. Clicking, or double-clicking, the All "tab" has no effect. Search finds nothing, either in the Content Library or Smart Content, either in Files or in the Database.
I have reset the database and reloaded the (copious) metadata, but still no joy.
This is a real pain. What can I do to find where the problem might be?
Comments
I don't use a Mac, but it sounds to me like your CMS (Content Management Service) is not running. DS relies on it for displaying Smart Content, Products and Categories, as well as the search function.
In Windows, CMS runs as a Process, I'm not sure how you would check on a Mac, but I think there are threads on this already.
CMS is running. I don't even see the default categories. Judging by the fact that there are others with the same problem, I think it's time or a support ticket as DS is effectively unusable currently.
Quick update. When I looked in the log file, I found this:
Definitely time for some support methinks!
Did you change the Path in DS to the new folder? Seems the only reason that no content could be loading that I know of.
EDIT: Your last post just popped for me. I agree with you now. I will point the DS Mac CV to this thread to see if they can help.
Hello,
(1) Is the DAZ Content Manager Service Running (and is the only one instance of it running)? Check using the Activity Monitor.
(2) if you go to the directory where you installed the Content Manager System usually if you didn't change it it is installed in /Library/DAZ 3D/Content Manager Service. Inside that folder is one called vlogs. Look at the latest one (just select and spacebar to quicklook it). Does it state that the CMS was started ?
I've been running 4.6 on Mac OS X for a while so the problem is most likely CMS not starting or running double. If anything doesn't work, try a reboot as if the CMS crashed in a very unlucky was (any unix server can happen to do this) the port might still be in use and it cannot start again as the OS wont let it open the listener port.
CMS is running (see prev reply).
Vlog for earlier today:
So it looks like the server started OK.
I reboot my Mac every morning, so any crash the previous day wouldn't be an issue.
ContentManagementServer is explicitly allowed to make connections on my machine - I run NetBarrier and just checked it (you never know). NetBarrier also shows CMSserver activity when Studio starts up, but none thereafter, regardless of what I do in Studio. However, as mentioned above, the Studio log does show a connection error.
A support ticket has been logged. Let's hope the gurus can figure it out.
So it looks like the server started OK.
I reboot my Mac every morning, so any crash the previous day wouldn't be an issue.
ContentManagementServer is explicitly allowed to make connections on my machine - I run NetBarrier and just checked it (you never know). NetBarrier also shows CMSserver activity when Studio starts up, but none thereafter, regardless of what I do in Studio. However, as mentioned above, the Studio log does show a connection error.
A support ticket has been logged. Let's hope the gurus can figure it out.
Connection errors most likely means Studio cannot connect.
You can in the "DAZ Content Manager Services.ini" Change the verbosity of the log. Look for a line VerboseLevel=0 and change to 3 Then restart the CMS using stop and start scripts in the utlilites folder (all in the CMS folder)
Start studio and see if you see any more log activity in the log)
OK, a lot of activity in there. Here are the first few lines:
I see an attempt to establish a connection which fails, and then one which works. Afterwards there is a ton of SQL and no errors that I can see.
I see an attempt to establish a connection which fails, and then one which works. Afterwards there is a ton of SQL and no errors that I can see.
Looks like it does establish a connection. One more thing then (if the Index file has been corrupted, thats what databases are for, corrupting things, as me I worked with my first one as an intern in 1981). In databases folder there is a file named ContentDB.ind.
If you stop the CMS (has DS shut down first too), then remove that file, then start the CMS again it will rebuild the DB indexes, might help you (and turn back verbosity to 0 or you will have a slow shystem and fill your disk in notime with logs of nonsens ;-)