suddenly, my SQL Developer turned off, i can't add any connection to connect to my work remote databases, i tried to factory reset the views, uninstalled and reinstalled the app. still can't figure out how to fix it !
Your connections.json file has probably been corrupted.
You can find that file and try to repair it yourself, OR you can rename it to something else, and when SQLDev starts up, it'll give you a default connection panel, but no connections in it, you'll start from scratch.
Older copies of sqldev will have a connections.xml.
Found the solution, i needed to configure the JDK under AppData\Roaming\sqldeveloper\21.4.1\product.conf
"SetJavaHome C:\Program Files\Java\jdk1.8.0_301"
Related
When running Sitecore Setup the following error pops up:
Failed to open XML file, system error:-2147024786
I've tried going through the eventviewer but to no avail.
Not unimportant is that I used the installer but forgot to change my rootdirectory. As a consequence I had to uninstall (using the same installer Sitecore).
Now however it "feels" as though there are some references or remnants left behind somewhere.
Who has a clue or can give me an idea of what is going on?
You are correct, this issue is because the previous Sitecore instance, with the same name, has not been removed completely. You will need to manually complete the following tasks to remove the remnants and be able to run the installer, it has worked for me in past;
Stop the App Pool for the uninstalled site in IIS
Stop the Web Application for the uninstalled site in IIS
Perform an iisreset in command line
Delete the App Pool and Web app in IIS
You should now be able to completely delete the folder containing the Website and Data folder completely
If you are still having trouble deleting it check the folder's Security Permissions, the Users and their Permissions and Read Only checkbox. Ensure you have control to delete
Delete the relating entry in the hosts file
If you also installed Databases access them via MSSQL Management Studio, take all relating databases Offline then delete them.
This will effectively remove all remanants of the previous site. If what ever reason the issue still persists, Sitecore's own Sitecore Instance Manager has a delete option which will completely uproot the site for you. Try installing with SIM then.
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.
I have recently experienced a new problem using RAD 8.0.2. When I launch a WAS server from within RAD, with or without any apps published to it, WAS will start and will show output in the console. I can even access the server from my web browser. However, RAD never recognizes that WAS has started successfully and after the timeout limit is reached, RAD claims that the server failed to start. I have tried this with WAS 6.1 and 7.0 test environments and WebSphere Portal 6.1 external environment and I always get the same result. Naturally, this makes development extremely difficult and I am anxious to get this fixed. Any help would be greatly appreciated! - John
May be an SSL certificate expiration problem, try this
http://www-01.ibm.com/support/docview.wss?uid=swg21514601
I don't think the issue is with RAD 8.0. I had similar issue which is caused by overridden .Metadata properties. Please follow the steps mentioned below.
Close RAD
Kill Java and Javaw.exe on the TaskManager which runs in the background to run eclipse/RAD
Remove the .Metadata properties from the workspace path( Remember when you remove this properties, the workspace settings and the server will be removed from your workspace)
Open RAD as Administrator, it automatically creates .metadata in your workspace path. But, it would be a default (without the workspace settings).
Need to update the user libraries in your workspace and add the servers again( The server settings would be still available as the Server profile was never changed). These settings would update your .Metadata on your workspace.
Try toggling the SOAP and RMI option to see if that helps you.
Sometimes it has trouble and it always works if you switch the protocols that RAD uses to connect to Test envionment server.
Also as a sanity check ensure that the port numbers that are specified in the server configuration in RAD is correct. There are chances that an incorrect port number could be a culprit too.
HTH
Manglu
I could solve the problem by deleting the server profile "AppSrv1" (Windows -> Preferences -> Servers) and by creating a new one using the profile management tool at the same page.
I have oracle 10.2.0.4 version..Some days before everything was well..but after changing tnsnames.ora file(I had just one SID of database,which is located on my computer.Then I have added SIDs of other databases which are located on another servers) OracleServiceSID stops itself after a while and user is automatically disconnected...How to solve this problem?I want OracleServiceSID to remain started...
After searching on the internet I found the following:
Start->All Programs->Oracle..->Configuration and Migration Tools->Administration Assistant for Windows
Collapse the following folders:
Oracle Managed Objects->Computers->Comp_name->Databases->SID<-right click->Start Service
File->Save
And after that everything works fine...Maybe It is a solution or temporary solution..Not sure..
You should need to investigate why this issue occurred to prevent this issue in future too. Check event viewer for further investigation of issue.
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.