DAZ Studio Crashes on Startup
mambanegra
Posts: 586
So, I was trying to be smart and broke DAZ Studio. I did submit a bug ticket, but I'm hoping someone here can help more more quickly than the ticket winding through the helpdesk.
I was running out of diskspace on the hard drive where DIM installs to, so I decided to move all of poser's runtime onto another disk. I did so, leaving only texture and textures directories behind and added the new runtime to my poser runtimes entry in the preferences/content management pane. I moved that entry to the top of the poser list of paths and then moved everything other than those two directories from that main runtime (where DS installs stuff) into the recycle bin. Now, whenever I start DS, it crashes. Inside the "cloudLog.txt", there is this error, which obviously tells of the problem:
2025-01-13T14:15:18Z Query (SELECT * FROM "customer") failed with exception: Connection to database failed
2025-01-13T14:15:18Z Unexpected exception in validateAndFixDb: Connection to database failed
Was the database inside there? If so, what is the filename. Also, are there any other required files that I should "undelete"? I haven't emptied the recycle bin, so all should still be on the drive. However, nothing looked particularly official or "database-ee". Any suggestions?
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
You should be able to see the database location in the Advanced settings for Install manager, it's the same for each application.
OK, so this is weird: The database is on my C drive, which is not, in any way, related to the location of the files I moved/deleted. Is there a preferences file for DS? Maybe that was in the runtime directory for some weird reason? That F: in the "Content Path Shortcuts" is the directory where the runtime was modified. B and C were not changed at all.
And, it works. I guess Windows decided to mess with me this morning. After a few other weird behavior issues unrelated to DS after work, I decided to restart...and...waddya know, all is right again. When in doubt, follow the obnoxious comcast help desk advice and restart, restart, restart!
In some cases, if cms services is down, you might encounter such issue ~~ Restarting PC starts cms service again, then the issue is gone. Next time you may firstly check if cms service is down or not... in DIM by checking that database icon. light grey means down.