Tried to fix PostqreSQL error by reinstalling Daz studio twice and restarting, now can't login.
Sailoraurora17_ad2c0753ab
Posts: 52
like the title says, I tried to fix PostqreSQL error by reinstalling Daz studio twice and restarting, now can't login into Daz studio.
I still can login into DIM and on this site here, but I like to install via Daz studio instead of DIM as it shows me thumbnails and stuff of what I'm installing...
Anyways, help with both issues please? ^^;;

Comments
How are you installing Daz Studio? PostgreSQL is a seperate installation.
And what was the error from PostgreSQL?
I usually install Daz Studio and other things via DIM and then install products via Daz Studio so that I can decide if I need them or not.
as for the error message... I get this every time I open Daz:

Reinstalling daz Studio is very unlikely to fix any PostgreSQL issues - those may be the database itself, security software, settings, or the actual PostgreSQL code (in soemthing like descending order of probability)
OK, so is PostgreSQL installed? Was it working before or is this a new installation? What security software do you use?
I use Notron 360 for gamers when it comes to security software. And yes, I did try the part where I made Daz Studio show up on their allowed applications for both windows firewall and that.
no dice. and again, DIM allows my login just fine, but now Daz studio is refusing to let me login.
as for it working.... it just recently stopped working. it only started glitching out when I tried to update metadata and stuff because images were showing as broken in the smart content menu.... and then the postqreSQL thing stopped working. so that's when I tried to reinstall things to get things working again.
So you can't use Connect>:Log In to log in to your Daz account?
Nope. I'm having problems with both that and the PostgreSQL thing.
That does sound very like a firewall issue of some kind.
I checked my firewall, allowed permissions, and stuff... and it's still doing it. *sigh*
Go to Edit>Preferences and then in that open the CMS Settings tab. Make a note/copy of the current Content Cluster location, then chnage it to something else (an empty folder). Restart DS? If the error goes away it is related to the current database - folder permissions or, more alarmingly, the actual data structure. If the error remains then it is something else. If the error goes away you will justs ee an empty set of categories, because the database is not populated, but it is diagnostic.