After upgrading to the latest version of MySQL Workbench(6.3.9), I receive a Microsoft Visual C++ Runtime Library error dialog window displaying the following image:
Assert dialog window
This happens about 3-4 times a day. Any known solutions?
This bugged me so I investigated and luckily I found a solution that worked for me.
On windows:
Go to %appdata%\MySQL\Workbench\sql_history. There are files in this folder with date in yyyy-mm-dd as the format of the name.
One single file here is very large in relation to the other files, for me its the earliest date. I deleted this file and have not seen the issue since. Back it up first if you to keep your history for reference.
Related
I tried internet search on this issue and it is very common with many suggestions. The problem started with an update to VS2019 in which I paused because my projects in VSCode were breaking.I did a system restore and when I tried to start VSCode I got a message saying my installation was corrupt. So I reinstalled to the latest version and now get this error.
A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found...
I found 3 extensions that needed updating so I do so but did not fix this problem. Do not know if I need to update the .Net Core since it looks like a version mismatch. It seems these updates are wreckless since they always cause thing to go wrong.s
If you are facing this problem, it means you are using Windows.
This official microsoft live share github page explains how to fix the issue: https://github.com/MicrosoftDocs/live-share/issues/102
Especially, check out this comment: https://github.com/MicrosoftDocs/live-share/issues/102#issuecomment-366509735
make vscode is up to date
uninstall live share from vscode
close vscode completely
restart vscode as administrator
reinstall live share
I should add:
close completely vscode and restart it
I have Visual Studio Code 1.27.2 on Windows 10.
Background:
Recently there was an issue in the system not related to VS, and I had to run system repair which seems to have messed up with the settings of various programs, including VS.
Current situation:
Now when I open VS I get this:
title bar of VS with 'Unsupported' at the end
warning: "Your Code installation appears to be corrupt. Please reinstall."
According to the official FAQ, this can be due to fishy extensions. But this seems unlikely given that the last extension I installed was more than a week before this incident, and more importantly because of the system-wide settings shake-up.
Main issue:
When I try to access settings directly, I get another strange error:
warning: "Unable to open 'User Settings': e.replace is not a function (2 errors in total)."
This function didn't look familiar so I looked it up and it was in the doxygen code, which has not changed for weeks, so also don't think this is the real issue.
I tried the suggestions here but there was nothing found in my folders.
I plan on re-installing in all cases. It's not the end of the world if the settings are gone, but it would be great to ensure they are saved because I spent a lot of trial and error customizing them.
On all four of my Windows 7 x64 Pro computers with Visio Pro 2010 installed, I have had the following problem for the past several months: When I edit a Visio document that uses the UML stencil, as soon as I try to edit any object information, for example, define a table column, Visio locks up. By ‘lock up’, the program ceases to respond, Task Manager shows that the process is consuming 13% of the CPU, and the process has to be terminated via Task Manager.
In an attempt to resolve this problem, I had tried repairing the installation and uninstalling/reinstalling the program, but this has not resolved the problem.
I recently attached Visual Studio to the process to try to better understand the issue. As expected, there were numerous messages of the type ‘Cannot find or open the PDB file.’ The messages which, I sense, may be relevant were as follows:
First-chance exception at 0x7713C54F (KernelBase.dll) in VISIO.EXE: 0x80040155: Interface not registered.
In an attempt to address this issues, I tried:
C:\>regsvr32 c:\Windows\system32\KernelBase.dll
This resulted in a popup window with the following message:
The module “C:\Windows\system32\KernelBase.dll” was loaded but the entry-point DllRegisterServer was not found.
Make sure that “C:\Windows\system32\KernelBase.dll” is a valid DLL or OCX file then try again.
The version of kernelBase.cll that is currently installed is 6.1.7601.24214, dated 1 Aug 2018 with a size of 419,840 bytes.
I used MultiFind Pro to search C:\Windows for any files named KernelBase and found quite a few older version in C:\Windows\winsxs. There were also numerous folder of the type C:\Windows\winsxs\amd64_microsoft-windows-kernelbase_[identifier]. As well as other, similar folders. (What I am finding very strange is that MultiFind Pro is reporting a different file size and date than Windows Explorer or the Windows command prompt DIR command for all versions of this file.)
The last time a Visio UML file was successfully edited was Dec 2017 and based on the modified dates of the files found, the last version of KernelBase that was known to work was version 6.1.7601.23418, dated 18 Jun 2016.
I am fairly certain that my computer does not have a virus. I also know that reinstalling Windows will not resolve the issue as I have the same issue across all of my computers.
If I were to try copying Kernelbase.ddl V6.1.7601.23418 from the winsxs ‘backup’ folder, would it simply get over-written by the newer versions?
More importantly, can anyone suggest a specific course of action to resolve this problem?
Nikolay - I assume you are the MS Engineer who helped me with this issue - thanks.
Without boring everyone with the details: The problem occurs when my password manager, Sticky Password, is also running. Shut it down, and Visio works just fine. I have alerted the company and have asked them to fix the problem.
Jeez, how hard is it to get SQL Developer to work.
Last month I downloaded the latest version and kept getting the cannot find ‘msvcr100.dll’ file error.
So I reverted back to an old version I had installed.
Now I have downloaded the latest version 4.2.0.
1 The first time I tried to launch it I was asked to set the JDK path. So I set it to ‘C:\Program Files\Java\jdk1.8.0_121’. Is this correct??
2 When I launch SQL Developer I get the initial splash screen, the progress bar does not get half way, and then it vanishes.
3 I went into the folder sqldeveloper\sqldeveloper\bin and amended the file ‘sqldeveloper.conf’ i.e. SetJavaHome C:/Program Files/Java/jdk1.8.0_121
I still get the splash screen and then it vanishes.
Anyone with any ideas.
Cheers
I experienced the same problem with the version with the built-in JDK and finally got it to work by:
1) Removing all other versions of Java from the system
2) Commenting the line under the #Set our usage tracking URI line in the sqldeveloper.conf file (sqldeveloper/sqldeveloper/bin)
Not sure which one did the trick but hoping this helps someone else.
I've started building Linux installers on the 64 bit windows version of Install4j recently and am getting the error below when it the generated installers start to do their extraction.
Is this something I'm doing wrong or is unsupported? Or a bug in 5.1 of install4j. I've recently upgraded to it as well.
Extracting files ...
yxN
An error occurred:
java.lang.IllegalArgumentException: Negative time
Error log: /tmp/install4jError8217531393990762392.log
java.lang.IllegalArgumentException: Negative time
at java.io.File.setLastModified(Unknown Source)
at com.install4j.runtime.installer.helper.fileinst.FileInstaller.install(Unknown Source)
This turned out to simply be a corrupted custom JRE being included in the installer.
Had the same issue. Due to an independent reason one of the files contained in the source directory had a file date in the year 1961.
Since most calenders starts at 198ß a check of that results in a negative timestamp.
After setting a current date the build process worked fine.
So it was not denepending on any version of jdk and had nothing to do with any broken jre installations or something like that.
Hint: In the windows exploerer no file date was shown. This might be helpful for anyone having a similar source file since you won't notice a wrong date as long you don't see it.
Search for file with dates before 1980 or use a commander should help you to find that ones.