Page 1 of 1
Big problems with 5.0.9
Posted: Mon Aug 10, 2015 10:10 am
by k2R400
Hello,
I have just installed the version 5.0.9 (the pervious installed one was 5.0.8) and I have big problems:
- If y try to launcg Genie i have a HTTP 500 internal server error.
- If i try to convert DDS source i have a message : Server response is invalid
- If i try to start Atrium, i obtain : Invalid username or password
But with the link ..../profoundui/atrium/
menu i can bypass the Atrium authentification page (not the Apache authentification).
The screen shot :
https://www.dropbox.com/s/27s5uhiggwsrw ... I.pdf?dl=0
Do I have to reinstall the old version?
Re: Big problems with 5.0.9
Posted: Mon Aug 10, 2015 12:32 pm
by Scott Wagers
Patrick,
Can you tell me what is in the Apache log regarding the HTTP 500 Server error? You can check the logs under /www/profoundui/logs on the IFS. There should be a file named error_log.Q115081000 for today. If you could paste this here, or send a copy of the log file to
support@profoundlogic.com we could see what is happening when Genie is launched.
About the DDS source, we found there is a bug with European decimal formatting and version 5.0.9. I will send you a patch for this along with instructions on how to install it.
Have you confirmed the user id exists and is valid in the ATUSERSP database file? With the /profoundui/atrium/menu URL, the browser is using the last credentials entered to pass to Atrium when requested. So if the user being authenticated with the /menu URL is different and valid than the user you're trying to manually enter, this could be why it allows you access to Atrium.
Re: Big problems with 5.0.9
Posted: Mon Aug 10, 2015 3:58 pm
by k2R400
It's OK now
Re: Big problems with 5.0.9
Posted: Mon Aug 10, 2015 4:05 pm
by Scott Klement
In case anyone else runs into this:
1) The problem with DDS conversion is due to a bug in 5.0.9 on systems that use commas as decimal separators (most of Europe!) We have a patch to fix this problem, contact
support@profoundlogic.com if you need the patch. This will be fixed in the next release of Profound UI.
2) The other problems are authority problems. (We are still looking into why this happened on Patrick's system, but not on ours during testing.) This will also be fixed in the next release, but if you run into it, you can fix it yourself by running the following command:
Code: Select all
GRTOBJAUT OBJ(PROFOUNDUI/*ALL) OBJTYPE(*ALL) USER(*PUBLIC) AUT(*USE)
(replace PROFOUNDUI with the name of the library where you installed the product if you overrode the library name during installation.)