The old Empty Smart Content Tab ploy – and how to fix it

- by

One morning I woke up and my entire Smart Content tab in DAZ Studio was empty. Nothing had happened since the day before when it was working perfectly fine. It just stopped working overnight.

What I had done shortly before going to bed was to install the latest service release of Poser Game Dev (SR5). If this was the cause of the problem or not will forever remain a mystery. In this article I’ll explain how I fixed this issue on my Mac.

Screen Shot 2014-11-09 at 15.06.54

Content Management Services you say?

DAZ now offer two types of metadata management. They both rely on  a database server to run which can manage which content belongs to which figure, what type of content an item is, and so forth. Those are background services, also known as daemons: little always-on apps on your system.

For many years this was Valentia DB, but as the demands for more metadata has risen over the years, users have on and off experienced problems with database corruption – which is why DAZ Studio 4.6 now supports PostgreSQL. Now DAZ Studio users can choose to use a different database server for their metadata if they wish, or stick with Valentia DB.

CAVEAT: If you’re using Carrara 8.5 then PostgreSQL is not going to work because Carrara does not currently support it. Hence, I’m sticking with Valentia DB for now – and it looks like that’s what I have a problem with on my Mac.


Is  the Database Server running?

A few hours of research revealed that the DAZ Content Management Server (Valentia DB) was not running on my Mac. I never had a problem with it until today.

To check if the service is up, head over to Applications – Utilities – Activity Monitor. This will bring up a nice GUI akin to the command line tool top and allows you to see everything that’s running on your Mac right now. To narrow it down, type “daz” into the top right search box.

In an ideal world we’re expecting to see DAZ Content Management here, but that wasn’t the case for me. You may also see the DIM (install manager) and DAZ Studio if those are running:


On Windows there’s a similar tool called the Task Manager – it’s probably easiest to search for it rather than figure out where they’ve hidden it in Windows 8.1 Check out this link for details.

If a service isn’t running, it’s probably best to start it and see if this fixes our problem.


Manually starting the DAZ Content Management Service

Thankfully DAZ have provided two small scripts that let us start and stop Valentia DB. On Mac those are in /Mac HD/Library/DAZ 3D/Content Management Service/Utilities and are aptly named

  • Start DAZ Content Management Service
  • Stop DAZ Content Management Service

Both will prompt for your admin password. If all goes well, the service should start and it should show itself in the Activity Monitor – and of course that Smart Content Tab in DAZ Studio should now be populated as it was yesterday.

Naturally this wasn’t the case for me: the service simply didn’t want to start anymore. Poor thing. Perhaps he was sick and tired of serving content, or something else was preventing it from doing so.


Checking the Error Logs

Every system admin knows that if things fail, it’s best to check the error logs to see why and how something has failed. I always forget that this is less painful than it sounds.

On Mac those logs are best investigated via Applications – Utilities – Console. This will display literally every system log message, so simply filter out anything by typing “daz” into the top right search box again. Here’s what mine looked like:


Here are the highlights:

09/11/2014 11:13:13.384 launchservicesd[108]: Application App:"Start DAZ Content Management Service" asn:0x0-40040 pid:655 refs=7 @ 0x7f84bad05180 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x41041 pid=658 "SecurityAgent"")), so denying. : LASSession.cp #1481 SetFrontApplication() q=LSSession 100005/0x186a5 queue
09/11/2014 11:13:13.384 WindowServer[121]: [cps/setfront] Failed setting the front application to Start DAZ Content Management Service, psn 0x0-0x40040, securitySessionID=0x186a5, err=-13066
09/11/2014 11:13:13.517[1]: (com.daz3d.content_management_service) Throttling respawn: Will start in 10 seconds

According to this it appears that the service is trying to start, but isn’t allowed anymore. God only knows why, because it sure as hell was less than 12 hours ago. Are the Poser people trying to jeopardise DAZ Studio users? Or were my 3D characters not happy with the morphs I keep drawing onto their faces? Was it Revenge of the Runtime?


How can we fix this, Cap’m?

According to this forum thread we should be able to

  • uninstall DAZ Studio
  • uninstall the Content Management Service
  • re-install DAZ Studio
  • which in turn should also re-install and perhaps fix the CMS

This approach works – but because the DAZ Installation Manager (DIM) gets involved it may not work as expected.

I had installed DAZ Studio 4.6 via DIM, so I uninstalled it via DIM too. But re-installing it via DIM does not re-install the Content Management Service – it’s only installed when the manual installer is used (they don’t tell you this in the tourist brochure).

So here’s what worked for me, step by step, on Mac OS X 10.9.5 (Mavericks):

  • uninstall DAZ Studio via DIM
  • uninstall DAZ Content Management Service (under /Mac HD/Library/DAZ 3D/Content Management Service/ Utilities/Uninstallers/ RemoveDAZContentManagementService
  • remove all files from /MacHD/Library/DAZ3D
  • remove /MacHD/Library/LaunchDaemons/ com.daz3d.content_management_service.plist
  • download the DAZ Studio installer from (under My Account – Product Library – DAZ Studio 4.6 Pro)
  • use the blue download button, don’t use the green one because this will open DIM which will not re-install the CMS
  • once downloaded, double-click the file to unZIP it
  • double-click the installer and follow the instructions

Make sure to point to your existing DAZ 3D Library during the installation. When it’s finished, launch DAZ Studio and notice that your Smart Content pane is still empty.

Find that little disclosure triangle and select Content DB Maintenance.

Screen Shot 2014-11-09 at 13.00.09

This will present you with a modal window. Select Re-Import Metadata and you’ll see a list of all your products in the associated directories. All should be selected by default, so click Accept and grab a coffee.

After a while you’ll have your Smart Content pane repopulated.


Further Reading

If you enjoy my content, please consider supporting me on Ko-fi. In return you can browse this whole site without any pesky ads! More details here.

11 thoughts on “The old Empty Smart Content Tab ploy – and how to fix it”

  1. Thank you for instructions that are straightforward yet detailed enough to get the job done. I am running DS 4.7.12 on a Mac 10.7.5. I believe I have all of my files correctly deployed, but I am not getting Gen 2 Male Base coming up in Smart Content. I have looked, at the DSX files (pretty closely, I thought,) and it seems all files are where they need to be. I have reloaded Metadata several times. The G2Male Base is in Content Library, just not Smart Library. Gripes me.

    Hope you can help . . .

    Many thanks!

    • Hi Jim,

      that’s a tricky one. I’m on a Mac too and Genesis 2 Male shows up in Smart Content. Does Genesis 2 Female show up in your Smart Content tab, or other content? I would probably uninstall the Genesis 2 Male Starter Essentials and then re-install it via the Install Manager. Good luck!

      • I found the problem after I went through the G2M Base Essentials DSX files to confirm all the paths. I set up Daz to load G2F Base at start up. So in the Files/Products Editor, guess what would I see? Female material only. I would not see any Male stuff. When I deleted the G2F figure, I would see G2M in the DAZ Figures folder. Duh . . . .

        I hope I can pick your brain in the future about actual operating info . . .

          • I think I have seen link for the manual, but I appreciate the remark that not much has changed from 4.6 to 4.7. I couldn’t find anyone to tell me that!

            Candidly, I am not a big fan of manuals, for any software. They show the functions, but usually miss explaining what I want to do, if that makes sense.

            Thanks again!

          • The biggest change I can remember in 4.7 was the addition of an aux viewport. This lets you preview a render in a small window without having to wait for the “real” render. It’s good to get an impression of overall lighting. You can access it via Window – Aux Viewport.

            4.8 will introduce a new default render engine (NVIDIA Iray instead of 3Delight). That change will be more dramatic as lights and materials will start to behave very differently – plus render times will increase by 500% or more.

            Happy rendering 😉

  2. Hey, Jay. I’ve been encountering a somewhat related problem with DS 4.9 and OSX 10.12. I wrote to Daz support about it, and while I was waiting to hear back from them, I figured out what was going wrong.

    The symptoms were essentially what’s described here, in their support site:

    None of their fixes were even slightly practicable for me (delete and reinstall? Such a typically Windows answer), so I didn’t try them. Here’s what was happening, and why.


    I have DS installed on two Macs, a portable (for composing) and a desktop (for rendering). The desktop Mac has all the Daz content — models, materials, user files, everything. I connect to it via network with the portable.

    Here’s what was going wrong. The logfile on the portable Mac indicated that the CMS could not connect to the remote volume’s content; it was throwing a ‘permission denied’ error.

    The trouble is that it doesn’t do that consistently. It only happens sometimes with the remote volume, and never happens at all with the desktop (which has the files resident on its hard drive; it’s not remotely connecting at all).

    This appears to actually be a fault in OSX and the way it behaves with network volumes; or actually, the way it misbehaves. It’s also relatively novel; the problem began surfacing only after I installed 10.12.x, but didn’t happen with 10.11.x or anything previous.

    What I discovered is this. All media is mounted by OSX in a hidden root level directory, /Volumes. So if you have a hard disk called ‘Harddisk’, it appears on this path:


    It mounts on the desktop with the name ‘Harddisk’, as you’d expect.

    Remote volumes or folders mount in a similar fashion. If you connect to a networked folder called ‘foldername’, it appears under /Volumes like this:


    …and mounts on the desktop as ‘foldername’. So far, so good, right?

    So when I connect to the remote folder, I’ve told Daz on my portable that its content is located in foldername:Daz. This SHOULD also be accessible as


    …and under normal circumstances, it is. The CMS has no trouble locating any of the remote content, reading it, working with it, etc.


    OSX occasionally, and silently, fails to properly purge the content of the /Volumes directory. I have no idea why. But when that happens, the foldername item remains in /Volumes, but it’s been flagged by OSX as being unreadable. You’re not allowed to access or open it. And it still appears there:


    …And when you look at it in Terminal, you see its permissions are set so access to it is blocked.

    Where this becomes a problem is twofold. For one, you need to know that item is there in the first place, and that it hasn’t been purged; and you need to be willing to force Finder to delete the locked folder. (You also have to know how to get to /Volumes in the first place.)

    The other way it’s a problem is that the next time you mount the remote volume, Finder tries to behave as though there are no problems. It still mounts the item to the desktop as ‘foldername’, and it still displays in /Volumes as ‘foldername’.

    But the *actual* name is different; its path is given as ‘foldername-1’. OSX hides this rather important fact from you.

    So what you see in /Volumes is something like this:


    …But one of those foldername items is marked as unreadable. In icon view, it shows as a folder with a red circle and line over it, indicating your access is locked out.

    The other foldername item is actually called foldername-1, but there is no way to know that short of actually traversing the path in an open-file dialog and reading the results; or by cd’ing in through Terminal and doing a pwd to find out what the path actually is.

    The solution is to unmount the remote volume, navigate to the /Volumes directory, and force Finder to delete the locked ‘foldername’ icon.

    After that, remounting ‘foldername’ before loading Daz allows the CMS to connect properly to its contents.

    • Warren! Thank you so much for sharing this in so much detail. It’s exactly those tips of tips that usually nobody tells us, and when we have to do it again, we’ve all forgotten because there’s no documentation. Great work, and well done for persevering 🙂

      Just in case mounting and unmounting is unfamiliar to any passing reader: dragging an external volume to the trash unmount the drive. Plugging it in again usually re-mounts it. You can also do this from the command line as explained in this article:

      • Quite welcome. I thought it was worth retaining *somewhere*, and this seemed a pretty good place for it.

        I think I’ve narrowed it further. The portable uses a remote disk for Time Machine, and whenever TM fires up to run a backup, it silently creates a temp volume called [username] in /Volumes to do it.

        So what?

        So if your Daz content is located on another remote volume, and you connect via the standard way through file sharing, and you’re using the same username there as well, it means your Daz content is going to be loading from a networked folder also called [username].

        TM does its mojo once an hour. If it’s quietly backing up to [username] at the same time you try to mount the other [username], you bet there’s gonna be a pathname conflict. Rather than deal with that, Finder calls the second mount point [username-1] … and doesn’t bother to tell you. Daz doesn’t seem to like that.

        So if I weren’t using TM to do a remote-disk backup, I’d probably never, ever see this problem at all.


Leave a Comment