When i try to generate the relationship matrix in EA we are getting the "out of memory" dialog is getting show up every time.What might be the reasons for this issue.
There are too many reasons to guess and I've never encountered this. Here are a few things you can do:
Run the Project Integrity Check and see if it solves the issue.
Look into %appdata%\...sparx...\dberror.txt to find out if some DB SQL error is related.
Turn off all MDGs to see if one of them might be the cause.
Try a transfer to an empty schema and see if the copy has the same issue.
Contact Sparx support if the error persists.
I guess that "install more memory" is not really what you want to hear ;-)
I was constantly getting this error on startup. Running EA as Administrator seems to have resolved the issue.
This happened to me recently. I have 2 user accounts on the same PC and this first started to occur when I tried to open EA when both user logins were active on the machine. Even after restart and login to only one user had the same issue.
Solution: Try Shift + Right click on the EA.exe file and run as a different user
Now provide your login and it should open.
Related
We have several action console projects. But recently I could not access to one of our action console projects.
Normally I will access from list in here:
https://www.screencast.com/t/CWlbqhRFc
But now it always show error when I click to one of our projects in there.
https://www.screencast.com/t/b6DmCIcmDsec
I contact with google and ask them for helping. They said that it is caching problems and ask me clear cache on browser. I did it but error still happen. Many other members of this projects also got that error (We shared account of project with some members).
Does someone know the reason of this bug and how could I fix it?
Please check the Roles you have for the project. You need to give Viewer Role to all the members of the project who are getting this error.
Please have a look into this Stackoverflow post as well.
There are a high chance there are a problem in google server. Because after we add a new device model. We could access our project again.
When I try to run a project (Only this project and others work fine), it always stucks at the publishing(copy and paste point). It can work perfectly fine until one time I(not sure) accidentally click incrementally publish and then stop it forcefully. Then this problem persists. I try to clean the server and also try to empty the domain folder but none of them works. It is like very strange bug.
I don't want to try creating a new domain since I have add JAAS configuration and JNDI in this domain. Or can anyone tell me how to import the configuration into a new domain?
If I wait long time for it to finish, random problem occurs:
The problem is other project can be run in debug and this project also can previously. It is all just out of sudden when I forcefully stop some process in eclipse tho I am not sure whether it is because of.
This is so annoying and can anyone give some constructive advice? Thx a lot!
Anyone encountering similar situation and sharing his/her experience here will be appreciated. It does not have to be exactly same and any lead or hint are welcome, please.
Actually, I think it is definitely an eclipse bug.
Creating a new workspace and importing all the related projects and glassfish servers can solve the problems though I don't know the actual reason.
I'm new to Moodle 3.7!
I was trying to get it installed in the AMP stack that already comes with the Mac (except for the MySQL 8.0.12 which I installed separately). It all went okay so far, except for a few Issues I stumbled upon and got them fixed until I face this persistent "Error reading from database" error at the end of the installation process. If I'm not mistaken, I'm supposed to be greeted with my first admin screen to change my password and whatnot.
I've searched for an entire day so far only to find my efforts were in vain. I suspect it is some issue emerging from "dml_read_exception".
Thank you in advance for your anticipated support.
After hours of research and digging into the code, I realized that I had erased the default prefix for database set by moodle, "mdl_". Apparently, this is important.
I'm really not very well versed with databases so not very good at its terminologies.
It would be appreciative if anyone explains how it works and why it affected my installation process. Thank you.
I've seen variants of this question around, but I'm looking for a definitive answer if anyone has one...
We are running a Cloud SQL Postgres instance, and are stuck on restarting the DB after having an export crash out with an unspecified error.
For several hours now our DB has been out of action saying it's restarting.
The options to export, restart, all of that good stuff, are greyed out and unavailable.
There doesn't seem to be a way to force a restart either through the console, or via gcloud command.
Most of the replies I've seen to this question seem to end up with the poster being helped out by Google support. Don't get me wrong, I'd very much appreciate that, but I'd also like to know if there's a way of doing this myself?
Any help greatly appreciated.
Currently, the 'force restart' option is not available for 'PostgreSQL' instance.
There may be several reasons behind the 'stuck' stage of an SQL instance. Not every time, 'force restart' option wouldn't resolves the root/actual cause.
However, if you still think this option needs to be included in the 'PostgreSQL' instance, I strongly recommend opening a 'Feature Request' through the issue tracker. While opening the 'Feature Request', try to include a bit more details about your use case scenario(with or without an example) as well.
I know this question may be seen as a duplicate with this one. I even have almost the same configuration (PostgreSQL 9.1.3, pgAdmin III 1.14.3, 32 bit Windows). What is the difference and the reason I ask a new question is that my PgAdmin doesn't crash always (just mostly) and that the cause of the problem is different - in linked question the problem was with missing adminpack, but I have adminpack installed and it works well, so the answer for linked question doesn't work for me.
Do you have any ideas where the problem could be?
EDIT: PgAdmin doesn't crash at other occasions (well, unless I do someting that obviously deserves a crash), just while trying to open SQL query window. It's worse and worse as time goes on, now it's almost "always". The problem is not "connection specific" - frequence of crashing is the same for different server connections.
EDIT2: I reinstalled PgAdmin and nothing have changed. I'm starting to suspect PostgreSQL 9.1.3 or even PostGIS 2.0.1 of the problem.
Goto run and type %appdata% and go inside postgresql folder.
rename or delete pgadmin_histoqueries.xml file.
try opening the SQL query editor again.
Good luck!
PgAdmin crashes on me all of the time, but you eventually learn to be gentle with it.
Particularly, if it is waiting for a response from the PostgreSQL server, the window may freeze up until a reply is returned and parsed. When this happens, do not close the window, just wait.
Also, if you attempt to edit two different objects on the same parent, save one and click save on the other, this crashes the program.
My advice would be to only do one thing at a time, be patient, and don't be in a hurry to kill the process when it freezes up.
There can be a great many different possible reasons for crashes. Some of them have been fixed in the latest version 1.16.1, release just last week.
You could try the new version and see if that fixes your problem.
Pgadmin3 was really unstable after installation on my ubuntu 12.04 LTS. It either freezes or crashes even while doing very basic things like looking data in a table or list tables in a schema etc., I almost gave up and started using the command line psql and luckily stumbled on this blog which recommended to remove the pgadmin3 history file to solve the freezes and crashes. It worked for me.