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.
Related
I apologize if this has been answered in another post, I can't seem to find it if it has. Anyway, I have built a back end utility for a fellow streamer friend of mine but I can't seem to figure out what I'm doing wrong when it comes to deploying it. This is a project that will be expanded on in the future, and possibly have more windows form projects. So here is what I am running into (With Pictures):
Here is my solution explorer with the projects:
When I go to build the deployment I've tried making all the projects "outputs" and got this error. Thinking it was there were too many Project Outputs I changed it to where the startup project would be the output and the others would be either source or content files. Still got these errors. Here is the File System Setup:
And when I go to run the build to create the deployment, here are the errors I receive:
I don't know/don't see what I am doing wrong here and would very much appreciate a point in the right direction. Thank you all so much in advance.
Check your updates. I remember there is an option to review or check the status of latest updates.
I found this article about that issue but it looks like a general error with updates or the installation
It is not too long but maybe it does not help. I hope it helps, good luck
I've a question about the upgrade of Kentico V11 --> V12.
After the correct migration, I got these errors messages (20 times).
When I'll check the website, all design are blank. I just have the menu link without design.
I already re-sign the macro.
I've check all version of CMS.*.dll --> V12.
Do you have any idea for this blocking issue ?
Kind regards !
The error message
did you resign all the macros after the upgrade?
Typically there are a few things which can cause this. First being the hash salt changed in the web.config. If this changed, you need to resign your macros. Even if your hash salt hasn't changed the easiest thing is to go to System > Macros and check both boxes and resign all the macros.
The second thing, highly unlikely, would be you need to clear your browsers cache. Sometimes JS errors arise from the upgrade and cause problems with the system not running code.
What is the entire error message? What is the source URL and where is the code which is throwing the error? Isn't it possible it is coming from some transformation? I am asking since there were some API changes and the GetFileUrlFromAlias method was removed. See the API changes. You may want to use the Code upgrade tool to detect such changes.
I just give you a feedback.
The problem seems to be during the migration...
Due to the VPN low speed, that possible there was some timeout for many steps. (mandatory because the COVID19 =( )
I just get the database on my local computer and redone the migration, and all seems to be good now.
Thank you for your help on this subject :)
Take care of you in this period !
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 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.
When deploying a Word Add in , which publishes without error. I get the following error after the files have been copied.
I do not have much to go on. This is the stack trace.
************** Exception Text **************
System.ArgumentException: Value does not fall within the expected range.
at System.Deployment.Internal.Isolation.IActContext.ApplicationBasePath(UInt32 Flags, String& ApplicationPath)
at System.ActivationContext.get_ApplicationDirectory()
at System.AppDomainSetup..ctor(ActivationArguments activationArguments)
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.CreateAppDomainSetup(ActivationContext context, Uri deploymentManifestUri, AddInInstallationStatus installStatus)
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InstallAddIn()
here's an answer to what you are looking for:-
the problem:-
open Process Monitor during the failed update and see if Winword.exe is browsing the following registry key->
HKCU\Software\Classes\Software\Microsoft\Windows\CurrentVersion\Deployment\SideBySide\2.0\Marks\mmiw..vsto_510943deeecbc925_0002.0000_2055f5031035ea75\appid
in this someone managed to check the Compatibility Mode checkbox for Word, running it default under Windows XP SP2 (see if you can make the program compatibile with your system in short).
if this is not the issue
Then read further into this :- deploy a VS 2008 SP1 Word 2007
There is another post i have found on this topic HERE. it shows a possible work around that you could try to get a result? i'm not entirely sure but in this, the developer was using outlook 2008, i think he removed the instances of outlook within his code and re-implemented parts of it and left out others. Perhaps this could be a temporary fix or help you understand what the problem is?
(I'm sorry my answers aren't so clear, i don't have much time for stack overflow at the moment, i will clean up the answer when i have more time(it will flow)) ++ this is all i can find regarding this error, but there are people with the same issue on the Microsoft forums, maybe you could find an answer faster on there? if you follow the links I've posted you should be able to find some information that might be able to give you a decent fix.
PS. if this doesn't work, reply asap and i will search asap, i think I've found something else which might be of use, just have to understand it myself before i post.
I recently came across this problem too after messing with some dependencies. None of the noted solutions worked (either on MSDN or here).
How I fixed it:
Find an old published version that worked.
Find the .dll.manifest file.
Diff that manifest with the one that is erroring.
In my case, I saw that a .dll was incorrectly referenced there (I thus had a v2 of it and a v4). I removed this reference and, thank god, it works.