libsqlite3-0.dll was not found error when launching shp2pgsql-gui on Windows (PostGIS) - postgresql

I recently installed PostgreSQL 13 on windows 10 and the PostGIS extension via the stack builder. However, when trying to launch the shp2pgsql-gui application to import a shapefile, I get a "libsqlite3-0.dll was not found" error. I can see the file under the bin folder, so I'm not sure where the problem is and googling did not help very much. I wonder what the problem may be because the installation seemed pretty straightforward to have done something wrong.

Copying the "libsqlite3-0.dll" file from \PostgreSQL\13\bin to PostgreSQL\13\bin\postgisgui and then running the shp2pgsql-gui application seemed to fix this issue for me.

This problem can occur for different reasons, but I recommend that you download that .dll from the following link (https://es.dll-files.com/libsqlite3-0.dll.html). Then replace the file in the installation folder.

Related

Eclipse save error when trying to open the design view of a synapse config file in WS02 Developer Studio

I'm following the tutorials and samples of the official WSO2 ESB documentation. When I create (or load) a synapse configuration in the WSO2 Developer Studio I'm getting the error as shown below:
Save problems
Save could not be completed.
Reason:
resources\sunErrorHandler.esb_diagram (The system cannot find the path specified)
This error shows up when I want to open anything in the Design view. Even when I'm not trying to save anything.
So far I have tried to add the path specified in the error, but without success. I already found a workaround to be able to save and deploy my ESB configurations. By using "Save as" I'm able to keep the changes I made in the XML files. However the error stills shows up when I open the new version of the file.
Does anyone know a better solution to permanently resolve this error message?
I had this problem as well, running eclipse.exe as administrator fixed it.
Issue remains unresolved for my Eclipse + DevStudio 3.8.0 install on a Windows 10 environment. However since I was experiencing some other issues with the WSO2 ESB I decided to migrate to a Linux (Ubuntu) environment. This seems to work much better, the eclipse does not seem to have this issue on Linux.
Eclipse want to write in C:\Program Files\eclipse\resources. I solve problem by adding full permissions to group users on folder C:\Program Files\eclipse
If this happens in Mac you can provide the required permission to the "/Applications/IntegrationStudio.app/Contents/MacOS/resources" folder.

Getting "Error: Failed to connect to OmniSharp"

I'm trying to get VSCode working with my Unity projects, and every time I select the Project icon (the little fire at the bottom) I get the following error:
Error: Failed to connect to OmniSharp
Is anyone else getting this?
You need to download the most recent version of "mono". Open up terminal and pass in brew install mono. Then "Pick a project" and select the ..-csharp.sln file and you should be up and running.
Ok, made some progress and gotten a few Unity projects working. It seems that you need some prerequisites installed, a clean up of your Unity project folder, and possibly some hand editing of your .sln and .csproj files.
I posted a (possibly) better answer over on Reddit. Hope that's not breaking stack etiquitte.
http://www.reddit.com/r/Unity3D/comments/34d6gc/visual_studio_for_mac_help_us_vote_for_unity/
i get this on windows when my project directory has a space in it
i removed the space and removed the error
i expect it will be fixed soom
I have a completely different answer: it's the runtime that VSCode is using. It doesn't match up with what it thinks it needs. I have to remember that we're still in beta and that things are changing rapidly. I had my dnvm running beta 7, but VSCode (and OmniSharp, by extension) is looking for beta 6, so it was failing. I updated my runtime using this this post as a clue. Now I have VSCode 0.7.0 using the beta 6 runtime. I have no idea how to tell what it's looking for...I just guessed based on when they were both released. HTH

sql developer hangs on startup - what can I do?

At present I cannot run it (SQL Developer 4.1) because it hangs on "Restoring Editors" while starting. I suppose I've done it by exiting it before by killing sql developer process because it was hanged on fetching objects to Schema Browser so long...
Maybe I would clean some temporary files but can't find any.
Any ideas?
Deleting files from c:\Users\MY_USER\AppData\Roaming\SQL Developer\SQL History
and c:\Users\MY_USER\AppData\Roaming\SQL Developer\System...
Really helped me to resolve the connection issues
Basing on this thread https://community.oracle.com/thread/2564842 I've created own solution.
Extract installation of current version SQL Developer (4.1.0.17.29)
At "c:\Users\MY_USER\AppData\Roaming\SQL Developer\"
I've changed directory name system4.1.0.17.29 to system4.1.0.17.28.
After running newly extracted SQL Developer (4.1.0.17.29) I was prompted to let copy configuration from version 4.1.0.17.28 to 4.1.0.17.29 ;)
Everything works great now. I suppose that running the same (broken) installation after decreasing version could also help.
Remove folders c:\Users\USERNAME\AppData\Roaming\SQL Developer\system4.1.3.20.78\system_cache*. SQLDeveloper will recreate it after launching.
Just execute sqldeveloper as administrator. It works fine!
In my case the problem was because of windows compatibility issue. So I've selected my windows version and it's stop from randomly crash after startup
Our setup:
Windows 10
Sqldeveloper Versions <= 20.4.0
We observed this problem as well. Even worse while working over a VPN connection. I followed a couple of hints with more or less no effect.
To move
C:\Users\<USER>\AppData\Roaming\SQL Developer
to a local directory by adding this line
AddVMOption -Dide.user.dir=c:\temp\sqldev-conf
in the \sqldeveloper\bin\sqldeveloper.conf file gave us some improvement, but the “IndexPreferencesTask” still got stuck several times on startup.
After some more hours on unsuccessful research, we moved back from JDK 11 to JDK 8.
This solved 99% of the problem. The “IndexPreferencesTask” still hangs on startup but for less than a second.
Sounds to me like a problem with JDK 11.
In my case when i changed Tools --> Preferences --> Environment -> Look and Feel to Windows it is solved.
Delete the History files from C:\Users\User\AppData\Roaming\sqldeveloper
Restart the PC
In my case, the solution was kind of weird. After battling to resolve this for 2 days, no luck. Suddenly, on my mac, I searched for sql developer, not sqldeveloper. It popped up a sqldeveloper application (not sure how that is different from what I have been trying to open ), clicked it and boom, it opened. My guess is that there is a copy of that app on my system that I should have been opening rather than trying to open the reinstalled app. Note: I reinstalled the app after it started misbehaving though.
Operating System: Windows 10
Oracle Sqldeveloper Ver: 17.4.0
The problem has been noticed sometime when any network security
patch was installed on your machine. Looks like the patch impacts
your cached data under your user profile folder.
As above Lakh, rtbf and others answered. Removing below folders
will resolve the issue.
C:\Users\<userId>\AppData\Roaming\SQL Developer\SqlHistory
C:\Users\<userId>\AppData\Roaming\SQL Developer\system17.4.0.355.2349
If any one find more approriate reason please feel free to
disagree with my answer.

error while trying to run MapReduce job using eclipse Indigo

I am trying to run MapReduce jobs using hadoop-eclipse plugin with Eclipse Indigo, but I am getting the following error:
Error: failure to login
While looking for some help, I found there is a problem with Hadoop-0.20.203.0, so I tried Hadoop-0.20.205.0 as the issues are fixed in this version.
I am still facing the same problem. Am I missing something or making a mistake?
Sorry for my poor English, as your question has no more detail, I guess that you meet the same problme as me, if so, the following link resolved my problem, pls. pay attention to step "4".
http://hi.baidu.com/wangyucao1989/blog/item/279cef87c4b37c34c75cc315.html
Sorry for that is a page in Chinese. It said the problem is because the file hadoop-eclipse-plugin-0.20.203.0.jar lost 5 files "commons-configuration-1.6.jar , commons-httpclient-3.0.1.jar , commons-lang-2.4.jar , jackson-core-asl-1.0.1.jar 和 jackson-mapper-asl-1.0.1.jar ". You should:
Extract the "hadoop-eclipse-plugin-0.20.203.0.jar",
Add the 5 files into "hadoop-eclipse-plugin-0.20.203.0\lib" ,
Modify "hadoop-eclipse-plugin-0.20.203.0\META-INF\MANIFEST.MF" (modify the Bundle-ClassPath).
Re 'jar' the package and replace the old "hadoop-eclipse-plugin-0.20.203.0.jar".
The os the page referred is linux, my os is Win7.
good luck!
Instead of going for adding plugin u can just add the required libraries in eclipse and do your programming.
here is the list of library u will need. These files exists with the Apache hadoop distribution in lib folder.
hadoop-core-1.1.2.jar
log4j-1.2.15.jar
jackson-mapper-asl-1.8.8.jar
jackson-core-asl-1.8.8.jar
commons-logging-api-1.0.4.jar
commons-logging-1.1.1.jar
commons-lang-2.4.jar
commons-httpclient-3.0.1.jar
commons-configuration-1.6.jar

Netbeans 7: JVM Creation Failed, which settting to change in netbeans.conf (windows)?

I was having an issue with JVM Creation Failed when executing Netbeans in Windows, and after looking around i found 2 parameters that can fix the issue.
But i am unsure which to use, both fix the problem...
Can anyone tell me the difference and advise which i should be changing..
-J-Xmx512m
or
-J-XX:MaxPermSize=128m
Thanks in advance.
Not exactly answer to your question, but might help too:
If you are running for example Win 7 64bit and 32bit Java JDK, try to install 64bit JDK, it helps many people.
Another one solution, is to delete created temporary folders, which contain the file splash.PNG (in NB folder in Doc and Settings folder).
And maybe this can help too, close any opened PDFs in Adobe Reader (version 9 probably). I get this error more often while running the built app from NB IDE and running some PDF triggers this problem.