Daz Studio says it is updating metadata but some items fail
![Kev914](https://secure.gravatar.com/avatar/2b53132ca2c46b74c73515416a70b152?&r=pg&s=100&d=https%3A%2F%2Fvanillicon.com%2F2b53132ca2c46b74c73515416a70b152_100.png)
I keep seeing the message that Daz Studio is updating metadata for 72 items but then 68 fail. Next time it was 68 items but 66 failed. Maybe eventually it will be down to zero.
Not sure if it could have anything to do with this. But I was in the product library yesterday and I was looking around. There was an icon for M4 that had an exclamation on it. I was trying to figure out what it mean. I right clicked on it and I chose update metadata. Maybe that caused this?
Yesterday when I was doing a test render, it would put information about this into the little panel that registers information about the render and displays the progress bar. It must have shown four attempts to install the metadata. Not sure about what the numbers were for fail or success. The numbers given about were what I saw today.
So is there anything I should do? Why do some items keep failing. I thought maybe it was because I was rendering and possibly using some of the items. But today I wasn't doing anything when it happened. Just opened Studio.
Comments
Yes,, actually it is annoying, and un-reliable. I have no reason to use DAZ connect, if it miss up-date meta-data again and again.
I can see, same message. as for me, now,, everytime, DS say, "Metadata update failed: 1 items succeeded, 37 items failed"
I felt,, at least,, DS up-date 1 items meta data of 38.
but it is funny, because if I log-off, then start daz coonnect again,, there were same message.
"Metadata update failed: 1 items succeeded, 37 items failed."
about this 38 or 37? items,, DS always say same thing,, today.
everytime try to up-date 38 meta-data, then say me,, they succeed 1 items. it is terrible joking me![devil devil](http://www.daz3d.com/forums/plugins/ckeditor/js/ckeditor/plugins/smiley/images/devil_smile.png)
then I chekced log file,, almost of them are new product,, then I do not make user-data or product -data about these.
and it show same 37items,, which Daz connect miss up-date meta-data..
then I really hope to know,, which 1 item actually DS could up-date ?? I do not believe,, ds success it..
because there is no disribe product ID which DS succeed to up-date meta data. it seems cheat number for me.
Is DAZ connect really stable, and easy way, to up-date meta-data?
I've seen this a few times. We've been told that this is supposed to go on in the background but a few times I've had Studio become very sluggish when the metadata is being updated. Yesterday Studio locked up completly when I tried to apply a material setting and the metadata progress bar was there.
Has anyone else had lockups or slowdowns during metadata updates?
So far, the public build hasn't given me failed metadata updates. \o/
Yesterday when I opened Daz Studio, it said it was updating 64 items. I waited and when it finished it said 63 succeeded and 1 failed. The first day that this happened, it kept retrying over and over. Since then it only seems to try it once...when I first open the program. Hopefully if they all succeed then it will stop.
Same here. 2 items succeded 684 (all remaining) failed. Tried reinstalling the PostgreSQL (sku::18869) but no luck yet. Already tried all relevant options from here: https://helpdaz.zendesk.com/hc/en-us . Windows 10 with latest Norton Internet Security running.
It's more a connection/server side issue...
It has to download the metadata updates first and if something fails there (drop out, slow server, etc) then the local updates will fail. Some people are affected more than others.
Check to make sure that Norton isn't doing something to slow it down.
mrinal...you don't have to reinstall Postgre, it's not the problem. It's the data going IN that's the problem.
may be worth putting in a support ticket to bring it to their attention.
Yes...they can make sure that there isn't something messing up on that side, too. Or if there is enough...add more servers (or maybe replace the gerbils).
There's the problem, most servers are driven by hamsters not gerbils.
I think you have this problem because at least one of the files are broken.