Loading...
> >

Daz Studio 4.9 Postgre SQL issues

ScoopeyScoopey Posts: 190
in Daz Studio Discussion

Anyone else got a problem with installing this somewhat finnicky part of Daz Studio 4.9.

I installed Daz 4.9 yesterday and everytime it boots up it tells me I do not have a valid Postgre SQL connection.
I've contacted the technical department and they recommended unintalling/reinstalling Postgre SQL from the Install manager.
This is good but two versions show up WTF?
I tried both and as soon as you install one the other is unistalled and both do not fix the error!
My firewall is not blocking the access so I can only assume that this is a problem with the program.
Out of all the Daz Studio's 4.9 is the first one I've started to take a dislike to because I'm going round in circles.

As the USS Enterprise's Mr Scott once said "the more complicated they make the plumbing the easier it is to bung it up"
 

Comments

  • Richard HaseltineRichard Haseltine Posts: 100,905

    What is your firewall?

  • Harry_2964Harry_2964 Posts: 45

    I have the same problem. I use Windows 8.1 64 bit.

     

    I have installed only SQL and DAZ to be sure nothing else interferes.

    sql.PNG
    552 x 166 - 13K
    daz.PNG
    945 x 306 - 21K
  • Richard HaseltineRichard Haseltine Posts: 100,905

    Again, what is your firewall/security software?

  • nicsttnicstt Posts: 11,715

    It can be because you need to uninstall the two SQL items - find them with DIM if you use it; delete them and re-download new ones.

  • AndySAndyS Posts: 1,438

    I had the same problem already with DAZ 4.8, which came with PostgrSQL.
    PostgrSQL has some conflicts to a lot of prefered security programs (Antivirus and Firewalls).

    You can run DAZ without PostgrSQL, but since 4.9 you don't have any content management anymore. And sometimes CM is helpful.
    It is really a pitty, but some of us requested numerous time, that the DAZ team first should look for a solution instead of forcing the new DAZ version disregarding a large number of their customers.

    So please Richard, show us a solution of these conflicts.

    Thank you

    Andy

  • Richard HaseltineRichard Haseltine Posts: 100,905

    PostgreSQL is known to conflict with ZoneAlarm, but then Valnetina proved itself prone to data corruption. Neither is ideal but there are alternatives to ZoneAlarm, while a corrupt database losing user data is more permanent.

  • namffuaknamffuak Posts: 4,146
    AndyS said:

    I had the same problem already with DAZ 4.8, which came with PostgrSQL.
    PostgrSQL has some conflicts to a lot of prefered security programs (Antivirus and Firewalls).

    You can run DAZ without PostgrSQL, but since 4.9 you don't have any content management anymore. And sometimes CM is helpful.
    It is really a pitty, but some of us requested numerous time, that the DAZ team first should look for a solution instead of forcing the new DAZ version disregarding a large number of their customers.

    So please Richard, show us a solution of these conflicts.

    Thank you

    Andy

    As far as I know, the only conflict is with all versions of Zone Alarm. This is a ZA issue, it seems to be by design, and the fix is to convert to another package. The people at ZA have known about the issue for over 5 years and done nothing to correct it.

  • mjc1016mjc1016 Posts: 15,001

    PostGreSQL is one of the top 5 database (according to some lists, it's number 2)...so it's not the problem.

  • AndySAndyS Posts: 1,438

    Sorry Guys,

    but I got the impression, that you're playing the Kindergarten game.

    I bet, if I ask ZA, they can show, that you're using unsecure mechanisms.
    Same for DAZ. Several times the virus scanner alarmed, that there were viruses with trojan signatures in the DAZ program folder. Perhaps some of your installation routines.

    And furthermore:
    On the computers of all these users there are tousands of different very complex programs. All running without any conflict against ZA. But only PostgrSQL has problems.
    So ???

  • Richard HaseltineRichard Haseltine Posts: 100,905
    AndyS said:
    Same for DAZ. Several times the virus scanner alarmed, that there were viruses with trojan signatures in the DAZ program folder. Perhaps some of your installation routines.

    or false positives.

    PostreSQL is known to have issues with ZoneAlarm, and yes each says the fault lies with the other. It has been the situation for, I believe, a number of years so it seems a resolution is unlikely.

  • mjc1016mjc1016 Posts: 15,001
    edited January 2016
    Richard Haseltine said:
    AndyS said:
    Same for DAZ. Several times the virus scanner alarmed, that there were viruses with trojan signatures in the DAZ program folder. Perhaps some of your installation routines.

    or false positives.

    PostreSQL is known to have issues with ZoneAlarm, and yes each says the fault lies with the other. It has been the situation for, I believe, a number of years so it seems a resolution is unlikely.

    At least five..l think it is going on 7 yrs now.  I believe it was back in 2009 that (yeah, March of 2009 are the earliest reports I can find) it started.

    Post edited by mjc1016 on
  • ScoopeyScoopey Posts: 190

    Sorry about the later reply....seems I stopped getting the forum notifications!
    Anyhow I used Kaspersky Security. If its does not like a "connection" it notifies you.of the "problem". In the case of DS/ Postgre it has no problem.

    I reported the problem to tech support. They told me to install via DIM (which is confusing as there is two versions....why they leave the beta in there when the main version is out does not help).
    To cut a long story short they could not fix it and it has been logged as a bug.
    I asked them what would happen if it took them a long time to fix this bug and Daz swtiched to Connect only.....
    I can either then by products that come out with a discount and not use them or I can wait till later and buy them at full price...I thought that was a tad unfair and I'm still waiting for an answer. I guess since others are having the same issue they need to fix this before chucking out the next version or switching to fully encrypted products.

  • AndySAndyS Posts: 1,438

    Hi Scoopey,

     

    did I get you right (at least the second part of your post)?
    PostgrSQL has a problem with Kaspersky, too ?

  • mrposermrposer Posts: 1,130

    I have the same minor issue as Scoopey.... I say minor because I get the message everytime I load DAZ Studio but Postgre SQL is working and I can work with Smart Content including even installing Connect products. It would be nice if could be fixed but I'm not spending any time researching it on my side.

     

  • ScoopeyScoopey Posts: 190

    I don't think PostgewSQL has a problem with Kapersky, I simply think it has a problem.
    Since I can log onto my account through Daz Studio, I'm beginning to think that I have in fact got MrPoser's problem. It may in fact be working but I get the warning all the time...either way there is a bug!

  • joeyteeljoeyteel Posts: 65

    I get the connection error sometimes when starting DS4.9 I started watching the task manager. Sometimes PostgreSQL simply doesn't get fully started before DS finishes loading and tries to connect.If that happens you'll get the error, but everything will work almost immediately that relies on it as soon as you click away the error message. Apparently DS4.9 doesn't wait for PostgreSQL to finish initializing. 

  • GLWoodardGLWoodard Posts: 3,335

    Okay, I tried uninstalling PostgreSQL, then looked for it to reappear in my downloads, not to be found anywhere! Does it eventually come up again so it can be installed?

     

  • Richard HaseltineRichard Haseltine Posts: 100,905

    If it is showing in neither Ready to Install nor Ready to Download try checking the Show Hidden box in ready to Download. If that doesn't work check the Filters, also avaialble from the Ready to Download tab.

  • ScoopeyScoopey Posts: 190

    After working for months to solve this issue I was told to perform a crow bar approach.

    Uninstall Daz Studio and then delete or rename the "Daz Studio" folder in your "Programs" folder.

    Then reinstall it - I got it running at long last. Had to reinstall all the plugins manually though. Copying and pasting it seem to reset the problem so perhaps there is an errant file in there.

  • Bluefox25Bluefox25 Posts: 21

    One thing that seemed to work was adding all associated files and folders to a list of exceptions. I bet there's a similar option for all software. I hope this helps somebody, as advice on old threads may prove relevant to a search, even years in the future. I didn't have to reinstall anything.

  • perrymevissenperrymevissen Posts: 0

    This thread is bit old so I hope someone is still reading. I have PostGre SQL issues too, but I don't think it is firewall related. When I use the DIM to uninstall and re-install  the CMS I keep getting a not working version of pgAdmin3 application. OSX says it is outdated and needs update and to contact the venor. So, at least with me, is the postgre SQL application itself. Likely I keep getting the 32 bit version which is are no longer supported by OSX 10.15.3 ( 32 bit is not supported from OSX 10.13.4 and up)

    Is there any known solution for this?

     

    Thanks,

    Perry

  • Richard HaseltineRichard Haseltine Posts: 100,905
    perrymevissen said:

    This thread is bit old so I hope someone is still reading. I have PostGre SQL issues too, but I don't think it is firewall related. When I use the DIM to uninstall and re-install  the CMS I keep getting a not working version of pgAdmin3 application. OSX says it is outdated and needs update and to contact the venor. So, at least with me, is the postgre SQL application itself. Likely I keep getting the 32 bit version which is are no longer supported by OSX 10.15.3 ( 32 bit is not supported from OSX 10.13.4 and up)

    Is there any known solution for this?

     

    Thanks,

    Perry

    As far as I am aware the pgAdmin3 is part of the footprint for PostgreSQL but is not actually used for the Daz CMS, so that should not be what is stopping the CMS from working.

  • Richard HaseltineRichard Haseltine Posts: 100,905

    You should install the 64 bit version, but be aware that the databases are not compatible across bit architectures.

  • perrymevissenperrymevissen Posts: 0
    Richard Haseltine said:
    perrymevissen said:

    This thread is bit old so I hope someone is still reading. I have PostGre SQL issues too, but I don't think it is firewall related. When I use the DIM to uninstall and re-install  the CMS I keep getting a not working version of pgAdmin3 application. OSX says it is outdated and needs update and to contact the venor. So, at least with me, is the postgre SQL application itself. Likely I keep getting the 32 bit version which is are no longer supported by OSX 10.15.3 ( 32 bit is not supported from OSX 10.13.4 and up)

    Is there any known solution for this?

     

    Thanks,

    Perry

    As far as I am aware the pgAdmin3 is part of the footprint for PostgreSQL but is not actually used for the Daz CMS, so that should not be what is stopping the CMS from working.

    Hi Richard,

     

    Thanks for your suggestions.

    CMS was running on my Mac when I checked the activiety viewer, it is another service app located somewhere else less obvious. If it were 32 bit it would not be running.

    But I found a part of the solution: https://www.daz3d.com/forums/discussion/comment/5536011/#Comment_5536011

    As described there, the ownership of the ContentCluster folder was not ok. It should not be owned by root, but by myself. When I changed it then CMS starts within DAZ. Additionally I had added the cms service as safe to my firewall list already. But I do not think that was part of the solution, because with firewall off, it didn't not work either before. It was the last change. e.g. owership of the ContentCluster folder that got CMS working.

    I'm not there yet because.... the Smart Content tab is still empty. :-(

    best regards,

    Perry

     

Sign In or Register to comment.