I'm receiving this error while opening MS SQL database tables in DataGrip.
Other solutions to the problem where related to updating Java codes but mine was related to DataGrip accessing MS SQL DB.
Solution was to update DataGrip to latest build.
I need to run several times Help - Check for updates and than Restart in Event log - or probably restarting manually should work as well.
Unless you see "You already have latest version..." when hitting Help - Check for updates than you should update again.
In my case I had to update 3 times from one build to another until reaching last one, at the time of writing 2022.1.5
This could happen when you update your DB server to latest security release and don't update DataGrip.
Related
Situation
I am running Sonarqube 5.2. Due to changes with how we run Sonarqube via CI, I needed to update my project keys. This is a Maven-based Java project (i.e., submodules). The key changed was to simply add the branch to the key for the parent and all sub-modules. After updating all the keys I ran the new CI job.
Problem
After doing so our unresolved issue count went from 223 to 883. Strangely enough, the projects dashboard still displays 223. However, if click that 223 issue count link to drill into them the number jumps to 883.
If I use the default "My Issues" filter it says I have 74. If I try to navigate/view each one of them I can't get past 11/74 (I click but the paging control just flashes yellow).
What doesn't work
Since I can't delete these mysteriously inaccessible issues I thought I'd mark them all as "Won't Fix". However, attempting this has no impact on the "Unresolved" issues/count. Viewing sonar.log the POST to make the change returns a 200.
Question
Is there anything I am missing within the web application that can address this. Or is there any SQL I can run?
FWIW
I subsequently did the same process for a Javascript project with any issue duplication
In trying to revert things I figured this one out.
The very first time we ran the CI changes we had failed to update the project keys first. In all the attempts to fix via restores/retries all we did was reimport the database backup. The culprit was the Elasticsearch cache. The duplicates only existed in the context of the ES index due to the initial failure to update the keys first.
In the end, I ended up deleting the <sonar>/data/es, restoring the database, updating the project keys, and the running the analysis via CI.
a little background, I really don't know any technical terms from Oracle. My company have a pre built machine and I'm trying not having to go there backup my files and lose a day of job because I cant.
Recently I'm learning how to use Oracle Designer (6i) to build a diagram and later a table so I can request it to be created... While using the software it requested to install some file for the repository... after doing it, It screwed up every Oracle product I was using... I couldn't connect to PLSQL or even the designer...
After fixing some registry to point to the right TNSNAME and manually adjusting PLSQL, I managed to access both. The problem in hand is in oracle Designer at the "Designer Editor", when I right click a table and select generate, the message bellow shows up
Message
-------
CDD-23564: The file "C:\ORACLE\DSG6I\BIN\cds61.dll" could not be loaded or does not exist.
Cause
-----
The specified file or one its dependent files could not be loaded.
This may be because a file has not been installed, or is not
correctly defined in the system registry.
As an example dependency, the Forms Generator files require the
Form Builder files installed as part of Developer.
Action
------
Check the registry settings for the location of the required
file. Also check the product and any required dependencies
e.g.Developer have been installed correctly.
If necessary, try reinstalling.
The dll mentioned IS and EXISTS on the mentioned folder.
Considering I don't have the Oracle Developer 6i intaller, what can I do? What registry entry should I update?
Designer 6 is long out of support. Oracle has a free tool, SQL Developer Data Model, which does not break.
Even Designer 9i was flaky and would crash at random intervals and poke along with larger schemas. Anything over hundred tables could take days to edit. Ah, good times...
I managed to fix the problem by copying and replacing the whole ORACLE_HOME\DSG6I folder (in my case c:\Oracle\DSG6I, for those confused in terms like me) and the oracle system registry (regedit > HKEY_LOCAL_MACHINE\SOFTWARE\Oracle) from a coworker machine!
I am running SQLManagementStudio_x86_2012_ENU.exe to install SQL Server 2012. I came across a problem and I was hunged on it too long.
I have seen the same problem in SO and they are give a solution for that. I also over come that problem but again stuck again in half way through. So I am going to ask this again(not a spam)
Problem: When I ran above mentioned exe it was installed fine, Then I tried to create a instance of the server. I used SQL Server Installation Center in configuration tools. then I selected new SQL Server and it asks me to select the SQL Server Installation Media. I selected C:\Program Files (x86)\Microsoft SQL Server but it was invalied.
then I figured out that it is asking for the Installation media itself. So I extracted the .exe file to a folder and selected that path. that was taken as a valid media.
I refered to this link.
some have mentioned that this was a bug here.
when I clicked next it gives the following error. so that I can not proceed and create a instance. Can some one help me on this.
thanks in advance.
I have tried lot of things to come up with a solution for this. As you can see in the picture, there are only 2 check boxes which are already checked and disabled. This is not the right .exe file to run(I was unable to create a server instance using this). I downloaded the right SQL server installation file from here.
There are several .exe files that gives different functionality enhancements. I chose SQL server with tools which is about 1GB. I did not have to uninstall the existing sql server installation. I installed this and it worked fine. I will post back if I found a way to create a SQL server form the given installation. If you have the same problem as described above, most probably you are using the wrong .exe file.
Good luck with your fix.
We use Nant to automate our builds. Everything was working fine until about a week ago when the rains caused our power to go out and the build server had to be re-booted. Now, we get the following error whenever we attempt a build:
<internalerror>
<type>System.Runtime.InteropServices.COMException</type>
<message><![CDATA[SourceSafe was unable to finish writing a file. Check your available disk space, and ask the administrator to analyze your SourceSafe database.]]></message>
<stacktrace><![CDATA[ at SourceSafeTypeLib.VSSItemClass.Get(String& Local, Int32 iFlags)
at NAnt.Contrib.Tasks.SourceSafe.GetTask.ExecuteTask()]]></stacktrace>
</internalerror>
We ran the Analyze utility on the VSS database and there appears to be plenty of room on the build server, but no luck. Any ideas? I'm at a loss.
My problem was that the current file was empty... I wrote a comment on it and everything worked ok
Ok, here is the resolution. It turns out that somehow, the version of an app.config file that was referenced in the build script was corrupted (all the previous versions, actually), which caused the VSSGet error. Updating the version to the current version fixed the errror.
I had this issue when I tried to migrate a Source Safe database to Subversion, using VSS2SVN.
This error is related to the message
There is a diff chain size mismatch in file '' (bdaaaaaa) at version (versions earlier than that version can no longer be retrieved from the database).
that may be reported by the Source Safe tool analyze.exe.
If you look into the history of the file and try to Get a version that is older than the one reported by analyze.exe, the message of this question is shown.
Microsoft provided hotfix KB927887 for cases where this was caused by XML files toggling BOM inclusion, but I did not try to apply it.
See also Message: SourceSafe was unable to finish writing a file
I created SSIS packages a while ago, today I need to re-point them to a different SQL server. I have a bunch of "Execute SQL Task" tasks, which need their Connection property changed to a different server.
I created a new connection manager, double-clicked on each of the sql tasks, changed their Connection property to the new one, ran. It failed, the error was that it could not find the old connection. I restarted the project, none of the SQL Server tasks seem to pick up the new Connection Manager. I opened up the .dtsx files, tried to find the old server name somewhere and manually change it, but I could not find the old server.
What do I have to change to get rid of the old SQL Server and make it connect to the new, correct data source.
I work in VS2005, on Windows 2008 x64 machine (I don't know if it matters or not).
Thank you.
I've seen this occur before when Package Configurations are enabled. Make sure that this is not the case, recompile, and try again.
all you had to do is change the connection string in the old connection manager
make a new one if you deleted the old one and in all the tasks select the new one, even if you create a new one with the same name as the old one it won't work because somewhere internal a guid is used
Check to see if package configuration is enabled. The package may still be getting the configuration of the old server from the package configuration.
try recompiling after making the changes.