Lost & Found - ??
Stryder87
Posts: 899
So I've been getting aquainted with the new v4.9 and running into a few weirdnesses. One, see attached. Really?? The base products are in Lost & Found??? Wow... that... wow...
Anyway, moving on, I was trying to update a number of items in my lost and found on my home machine (not the one in the attached screenshot), and was running into problems. I'm guessing that, when an item in L&F (of which I have 1000, a lot of which came out well after 4.9 hit the market) has that circle with the arrow in the top right hand corner it means there's an update or something like that, even though it doesn't show up in the Updates section. So, I 2x clicked on a few and they seemed to refresh, but some get to 99% and stop with Connecting to Daz in the bottom status bar and just stay there. One I can think of off hand is EJ Atsuko for G3F. I've tried stopping them and then uninstalling. It tells me they uninstalled successfully, but I'm not sure about that. I go to reinstall and it doesn't seem to finish properly. I looked at the log because I was getting errors on updating Metadata, and it says that there's a folder missing.
Oh, and I see a lot of this in my log file: "2016-24-01 09:24:57.368 WARNING: cloud\dzcloudtasknotifier.cpp(178): Error in metadata for product 'Full Circle for Hooded Cloak' (1319), metadata for file 'people/genesis 2 female/clothing/hooded cloak/materials/full circle/just breathe 2.duf' has no corresponding file."
What does that mean?
Since I'm not at home I can't dig out the details, but does any of this sound like something that's been dealt with?
Edit: For some reason I can't attach a picture, it's stuck on uploading.... boooo....

Comments
If you are looking at the Products tab items will appear in any category that contains just one of their files - so if there's an odd file, like a link to documentation, that is in Lost and Found the product will appear there..
Another user reported a problem with EJ Atsuko - my copy is a DIM install, I will try making it a Connect install later and see if I get the same issue. In geenral metadata issues should be reported to Daz.
The no corresponding file error sounds like an installation issue - is the file actually there for you, or is it really missing?
I'll check this out after work. Most of my content is DIM installed, which would have included Atsuko, until I told Connect to uninstall it and reinstall, which still stalled at 99%. I'm thinking of trying to uninstall it through DIM and reinstall through Connect to see if that makes a difference as well.
I'll check on a few of the missing files, but there are a LOT of them listed. I cleared the log file of everything before the last program startup so I would have a clean log to look at. One question though; I checked the file path in the example I quoted and can't find the folder it references (1319). There are a number of folders in the 'cloud' folder in the path stated in the Content Directory Manager/Content Sets/Current Directories/Daz Connect Data, all of them starting with a 1_xxxx. I'm assuming that the number that replaces the xxxx refers to the Product ID? eg: EJ Atsuko = Product ID: 22838
On the missing files, did you change the Connect directory?
EJ Asuko installed without error for me - it even copied the files from the DIM install, which hadn't been working for me previously.
I didn't change any directories once I did the initial install way back in v4.5 (see attached). The one with the arrow confuses me. I seem to have a version of Reality inside another version of Reality. I suspect a newer version installed inside the older version. Never been a problem so I ignore it. I mapped everything to my biggest HDD with the most free space. I've even upgraded that drive since then, but did a straight copy so everything was in the same locations.
Ok, I just updated a few items and they went fine. Tried Atsuko and here's the error I'm getting:
2016-17-01 17:17:11.199 WARNING: cloud\dzcloudtasknotifier.cpp(178): Could not find URL for file in product EJ Atsuko for Genesis 3 Female(s) 22838
2016-17-01 17:17:11.402 WARNING: cloud\dzcloudtasknotifier.cpp(178): No DB entry for file: FIXME: Need path
2016-18-01 17:18:13.756 WARNING: cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0
2016-20-01 17:20:42.424 WARNING: cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0
And then it hangs at 99% complete.
I also ran a couple Metadata updates and I went from 1000 items in my L&F to 52, so that's progress. There are a few fails with this error (Mill Cat is just one example):
2016-16-01 17:16:11.912 WARNING: cloud\dzcloudtasknotifier.cpp(178): Query (UPDATE "product" SET name = 'Millennium Big Cat LE', default_name = 'Millennium Big Cat LE', store_id = 1, token = '3744', artists = 'DAZ 3D', description = '', guid = 'bec7b40b-a1bf-43ac-a388-28970a0f530e', meta_hash = '307e54a88ddc0150f3572938457a8a14', file_hash = 'b67ef52bdc215195ab0cdb10ab162a33', thumbnail_path = '', thumbnail_hash = '', last_update = '2013-03-05 20:32:08', date_purchased = '2014-11-29 17:25:52', date_installed = '2016-09-02 00:16:11', release_date = '2005-05-25 00:00:00', group_num = 0, hide = 'f', is_vendor = 't', has_cloud_meta_data = 't', is_installed = 'f', is_cloud_owned = 't', needs_update = 'f', normalized_name = 'millennium big cat le', normalized_name_first_letter = 'M' WHERE id = 6016) failed with exception: ERROR: duplicate key value violates unique constraint "product_guid_key"
DETAIL: Key (guid)=(bec7b40b-a1bf-43ac-a388-28970a0f530e) already exists.
Pretty much everything related to the Steam Truck add-on fails (this is just one of about 40 fails):
2016-14-01 17:14:26.563 WARNING: cloud\dzcloudtasknotifier.cpp(178): Error in metadata for product 'Delivery Service for Steam Truck Red Bizon' (15130), metadata for file 'vehicles/steampunk truck/delivery service for steam truck red bizon studiocf/!purple steam truck.dsa' has no corresponding file
And then there's this wall of fails (I have no idea what this all is related to):
2016-16-01 17:16:10.099 WARNING: cloud\dzcloudtasknotifier.cpp(178): Token "3744 " cast failed in TableProduct::loadIntoMap cast failed with exception: bad lexical cast: source type value could not be interpreted as target
2016-16-01 17:16:10.102 WARNING: cloud\dzcloudtasknotifier.cpp(178): Token "3743 " cast failed in TableProduct::loadIntoMap cast failed with exception: bad lexical cast: source type value could not be interpreted as target
2016-16-01 17:16:10.106 WARNING: cloud\dzcloudtasknotifier.cpp(178): Token "4603311601326964-1" cast failed in TableProduct::loadIntoMap cast failed with exception: bad lexical cast: source type value could not be interpreted as target
2016-16-01 17:16:10.106 WARNING: cloud\dzcloudtasknotifier.cpp(178): Token "4603311607411548-1" cast failed in TableProduct::loadIntoMap cast failed with exception: bad lexical cast: source type value could not be interpreted as target
2016-16-01 17:16:10.109 WARNING: cloud\dzcloudtasknotifier.cpp(178): Token "4603311601850025-1" cast failed in TableProduct::loadIntoMap cast failed with exception: bad lexical cast: source type value could not be interpreted as target
2016-16-01 17:16:10.111 WARNING: cloud\dzcloudtasknotifier.cpp(178): Token "4603311609458753-1" cast failed in TableProduct::loadIntoMap cast failed with exception: bad lexical cast: source type value could not be interpreted as target
2016-16-01 17:16:10.111 WARNING: cloud\dzcloudtasknotifier.cpp(178): Token "63823606355793-1" cast failed in TableProduct::loadIntoMap cast failed with exception: bad lexical cast: source type value could not be interpreted as target
2016-16-01 17:16:10.114 WARNING: cloud\dzcloudtasknotifier.cpp(178): Product "DS 4.7 Built-In Content" has no token
2016-16-01 17:16:10.115 WARNING: cloud\dzcloudtasknotifier.cpp(178): Token "4234 " cast failed in TableProduct::loadIntoMap cast failed with exception: bad lexical cast: source type value could not be interpreted as target
2016-16-01 17:16:10.116 WARNING: cloud\dzcloudtasknotifier.cpp(178): Token "5591747220402507545-1" cast failed in TableProduct::loadIntoMap cast failed with exception: bad lexical cast: source type value could not be interpreted as target
2016-16-01 17:16:10.119 WARNING: cloud\dzcloudtasknotifier.cpp(178): Token "4603311600984769-1" cast failed in TableProduct::loadIntoMap cast failed with exception: bad lexical cast: source type value could not be interpreted as target
2016-16-01 17:16:10.119 WARNING: cloud\dzcloudtasknotifier.cpp(178): Token "4603311602865367-1" cast failed in TableProduct::loadIntoMap cast failed with exception: bad lexical cast: source type value could not be interpreted as target
2016-16-01 17:16:10.119 WARNING: cloud\dzcloudtasknotifier.cpp(178): Token "4603311604581532-1" cast failed in TableProduct::loadIntoMap cast failed with exception: bad lexical cast: source type value could not be interpreted as target
2016-16-01 17:16:10.122 WARNING: cloud\dzcloudtasknotifier.cpp(178): Token "4603311605540095-1" cast failed in TableProduct::loadIntoMap cast failed with exception: bad lexical cast: source type value could not be interpreted as target
2016-16-01 17:16:10.122 WARNING: cloud\dzcloudtasknotifier.cpp(178): Product "Dynamic Nightwear for V4" has no token
2016-16-01 17:16:10.123 WARNING: cloud\dzcloudtasknotifier.cpp(178): Token "4603311607921986-1" cast failed in TableProduct::loadIntoMap cast failed with exception: bad lexical cast: source type value could not be interpreted as target
2016-16-01 17:16:10.129 WARNING: cloud\dzcloudtasknotifier.cpp(178): Token " 20499" cast failed in TableProduct::loadIntoMap cast failed with exception: bad lexical cast: source type value could not be interpreted as target
Log files are fun!
The cat and truck should certainly be reported via a ticket, I don't know what the toekn errors are from - or whether they matter.
Alright. I'll open a ticket for those two, and throw in the token ones to see if they can figure it out.
Thanks Richard.
I honestly don't know if this will help, but the "errors in metadata" when installing via Smart Content/Connect made me remember this reply from a ticket I submitted about a product: the reply stated "....we have uncovered a bigger issue then we thought. It has to do with metadata when installed through Daz Connect.". There's some sort of problem with daz connect metadata by the sounds of it - what it is, i have absolutely no idea, but thought I'd mention it so you weren't tearing your hair out thinking it was user error. :D
It looks like you may have some old zip files with old metadata lying around or some hand-built metadata.
One of the things that pops out at me is that many of the product id's are weird and invalid numbers while others either have leading or trailing spaces. This means that Daz Connect can't get a full listing of the product metadata hashes you have in your database to compare against the list it downloads of the metadata hashes that are the latest.
Other than dumping your databases and restarting from scratch, I'm not sure if there is an easy to fix this. Customer Support might have some secret magic for you, but it is not going to be an easy fix.