My Daz has majorly crashed.
dannavy85_6336e4e4
Posts: 53
So I was working on DAZ afew hours ago and everything was fine. Now when I tried to used it, I can't load any of my characters from Genesis to Gen 8.1. It seems it can't find Data files? I checked all my directory paths and they are as they should be for the external drive that I use. I've tried re-starting and re-booting several times.
problem 3.jpg
826 x 751 - 101K
problem 1.jpg
901 x 778 - 104K
problem 2.jpg
880 x 780 - 99K
problem 4.jpg
928 x 400 - 69K
problem 5.jpg
892 x 655 - 79K
Comments
Update: So these furry characters load with no problems, I guess because they are Hiro 3 and Aiko 3 base.
How are you installing?
And what is the full error text from the log (Help > Troubleshooting > View Log File) for one of the missing files?
This is part of the TS log.
2024-10-30 12:16:23.137 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in categoryGetRoot: Unable to connect to the database
2024-10-30 12:16:24.736 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in categoryGetRoot: Unable to connect to the database
2024-10-30 12:16:24.741 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in categoryGetRoot: Unable to connect to the database
2024-10-30 12:16:24.773 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in categoryGetRoot: Unable to connect to the database
2024-10-30 12:16:24.777 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in categoryGetRoot: Unable to connect to the database
2024-10-30 12:16:24.789 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in categoryGetRoot: Unable to connect to the database
2024-10-30 12:16:24.819 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in categoryGetRoot: Unable to connect to the database
2024-10-30 12:16:24.836 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in categoryGetRoot: Unable to connect to the database
2024-10-30 12:16:25.082 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in categoryGetRoot: Unable to connect to the database
2024-10-30 12:16:25.113 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in categoryGetRoot: Unable to connect to the database
2024-10-30 12:16:25.474 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in CloudFIle::lookupFromDb: Unable to connect to the database
2024-10-30 12:16:26.534 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in contentGetBySubdir: Unable to connect to the database, can not quote
2024-10-30 12:16:26.536 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in contentGetBySubdir: Unable to connect to the database, can not quote
2024-10-30 12:16:26.554 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in contentGetBySubdir: Unable to connect to the database, can not quote
2024-10-30 12:16:27.621 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in contentGetByRelativePath: Unable to connect to the database, can not quote
2024-10-30 12:16:35.606 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in CloudFIle::lookupFromDb: Unable to connect to the database
2024-10-30 12:16:36.029 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in needMigrate: Unable to connect to the database, can not quote
2024-10-30 12:16:36.107 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Unexpected exception in runNextTask-runTask: Unable to connect to the database
2024-10-30 12:16:36.177 Migration failed.
mostly, I've installed products manually.
Is the F: drive still connected, and still connected as F:?
Ok....now I see something confusing.
So I have two externals connected to the computer and both are showing F: drive.
no....excuse me on that previous post. I have two externals and F: is showing twice?
sorry....Am I misreading the previous?
Seriously though.....what if I clean out all of this and redo it from scratch?
Can you access files on the F: drive? For example, try opening a texture file from somewhere in /Runtime/Textures/ in an image editor.
Yes.....Using "Paint" I was able to open six files from Runtime / Textures
OK, so it isn't that the drive is failing at least. Are you sure that the content loaded OK initially - that is, if you work with Daz Studio online has it shown signs of downloading files when you try to open a newly installed product?
Are you sure that the content loaded OK initially - that is, if you work with Daz Studio online has it shown signs of downloading files when you try to open a newly installed product?
So far, I haven't had or seen any downloading of files when I opened a new installed product to the point this morning when this issue started. It was working fine until I turned the laptop off to go to work and when I started DAZ then....I got the CMS alert and the problems started.
I have had a problem though for the last month where Genesis 8 and 8.1 figures won't load properly.
could it be my firewall or virus protection blocking access to data?
What about DSON cashe? Could the port number be wrong?
Wow.....I just re-started DAZ a few minutes ago and it works again. Now I'm just having to re-map textures when the figures load up and show a missing textures box. I don't know how it re-set itself.
Thank you Richard for your trying to help me with this issue.
What I might have done which could have solved this issue was this....
On my external F: Drive there's two folders....
1. USER
2. USERS
both contain CMS / DOSON files.
So I switched the CMS from the current setting of USERS to USER and of course DAZ replied that it would not work well with that setting. I backed out of DAZ, re-started the lap top, went back into DAZ and selected CMS back to the USER folder.
and things returned to normal.
I would recommend everyone using external files to have saved back up folders for all their DAZ settings just in case you have this happen to yourself.