DEV Community

Abdulrawof Totakhil
Abdulrawof Totakhil

Posted on

Oracle SQL Developer 26.2 Startup Failure on Windows: Fixing Netigso Errors and Recovering Database Connections

Oracle SQL Developer 26.2 Fails To Start On Windows – Fixing Netigso Errors & Recovering Connections

A practical example of troubleshooting an Oracle SQL Developer error when launching the application. This includes checking the ZIP archive, Java libraries, user profile and moving connections.

Windows x64 Environment

Oracle SQL Developer 26.2.0.186.2220

Previous version SQL Developer 24.3

Date: 15th November 2026

Topic: Oracle Database tools & Windows Troubleshooting.

Introduction

Oracle SQL Developer is a tool used by DBAs and Developers to interact with Oracle databases. This allows SQL to be run, database objects managed and general administration tasks performed.

Although upgrading to a newer version of SQL Developer should be a simple task, sometimes the application can have issues launching.

Example

When attempting to install Oracle SQL Developer 26.2 on a Windows workstation.

Upon trying to launch the application there were errors relating to multiple software modules failing to be loaded.

The application raised an initial warning:


Warning - could not install some modules

Enter fullscreen mode Exit fullscreen mode

There were also additional messages relating to Netigso and missing software bundles.

At first this appeared to indicate that there was an issue with the archive not being fully downloaded, or the application missing some files.

Further investigation showed that the downloaded archive had the correct checksum when compared to Oracle. The chosen Java libraries were also present.

The issue was resolved by backing up and refreshing the SQL Developer user profile.

This article covers how the issue was investigated, the commands used, the results and how DBAs should be cautious when dealing with similar errors.

  1. Understanding The Issue

The version of Oracle SQL Developer we had was:


26.2.0.186.2220

Enter fullscreen mode Exit fullscreen mode

Installed on Windows using the ZIP archive.

ZIP Archive:


sqldeveloper-26.2.0.186.2220-x64.zip

Enter fullscreen mode Exit fullscreen mode

Extracted application folder:


C:\oracle\SQLDeveloper26.2\sqldeveloper

Enter fullscreen mode Exit fullscreen mode

Upon attempting to launch the application there were errors relating to several modules not being initialised.

Errors:


Warning - could not install some modules

org.netbeans.InvalidException: Netigso

Not found bundle: oracle.jewt_core

Not found bundle: oracle.external.jdbc

Not found bundle: oracle.ide.editor

Not found bundle: oracle.javatools_jdk

Enter fullscreen mode Exit fullscreen mode

What Is Netigso?

Netigso is used by NetBeans to allow modules to be integrated into the application.

Oracle SQL Developer uses multiple modules.

If some modules are not loaded or initialised correctly then SQL Developer will raise warnings and fail to launch.

It is important to note that just because there is an error related to a missing bundle does not mean that the file is not present.

The module may be present however there may be another issue preventing it from loading.

It may not be best practice to replace the files.

  1. Checking The ZIP Archive

The first thing to do was check that the SQL Developer ZIP file had been downloaded correctly.

The issue with modules failing to load could be due to the archive being corrupt.

Oracle will provide checksums for their downloadable archives.

A checksum is used to help confirm that the file you have downloaded is the correct one.

Step 1 – Launch PowerShell

Open PowerShell on your Windows workstation.

Navigate to the folder containing the Oracle SQL Developer archive file, or enter the full path.

Step 2 – Get File Checksum

Run:


$zip = "C:\oracle\sqldeveloper-26.2.0.186.2220-x64.zip"

Get-FileHash -Path $zip -Algorithm SHA1

Enter fullscreen mode Exit fullscreen mode

The SHA1 value for this example was:


6A1BCA6CD756B821C11E92B821DB73A6AEB67D02

Enter fullscreen mode Exit fullscreen mode

Which matched the value provided on Oracle’s download page for the x64 Windows version.

What Does This Mean?

This confirms that the ZIP file was the same as the one provided by Oracle.

This makes it less likely that the issue was to do with the download being incomplete or modified.

Lesson learnt

Always check the software package has the correct checksum provided by the vendor. This will help to avoid having to reinstall, or download multiple times.

  1. Checking Application Libraries

Now we know that the ZIP has the correct checksum we can now check that some of the important .jar files are present.

.java Archive Files normally use the .jar extension.

There are many .jar files within SQL Developer.

Multiple errors were raised relating to modules and Java libraries.

Step 1 – Find Installation Folder

The application had been extracted to:


C:\oracle\SQLDeveloper26.2\sqldeveloper

Enter fullscreen mode Exit fullscreen mode

Step 2 – Check 5 JAR Files

The below PowerShell script will check that 5 JAR files are present.


$base = "C:\oracle\SQLDeveloper26.2\sqldeveloper"

@(

"external\oracle.jewt-core.jar",

"external\oracle.external.jdbc.jar",

"external\oracle.external.woodstox.jar",

"ide\lib\annotations.jar",

"jdev\lib\jdkver.jar"

) | ForEach-Object {

[PSCustomObject]@{

File   = $_

Exists = Test-Path (Join-Path $base $_)

}

}

Enter fullscreen mode Exit fullscreen mode

Results

Java Library | Present

--- | ---

oracle.jewt-core.jar | True

oracle.external.jdbc.jar | True

oracle.external.woodstox.jar | True

annotations.jar | True

jdkver.jar | True

All 5 JAR files were present.

What Does This Prove?

That all 5 JAR files are present.

Although it does not prove that they are all correct, or that the modules can all be loaded, when combined with the ZIP having the correct checksum it shows that there may be an issue with something else.

We do not need to copy random JAR files from another SQL Developer installation.

  1. Understanding SQL Developer User Settings On Windows

Oracle SQL Developer stores some user settings in a separate folder.

This may be your application settings, connections, UI settings etc.

The user settings on Windows are usually located in:


%APPDATA%\SQL Developer\

Enter fullscreen mode Exit fullscreen mode

For the SQL Developer 26.2 version this was:


%APPDATA%\SQL Developer\system26.2.0.186.2220

Enter fullscreen mode Exit fullscreen mode

This is important as even though the application files may be correct, the user settings may have an impact on the application launching.

The next controlled action we can take is to refresh the user profile for this version.

Why Backup?

The user settings folder may contain important settings.

Removing this folder straight away may make it difficult to get back to your previous settings.

It is better to rename the folder.

This will make it easier to revert.

  1. Fixing The Issue By Refreshing User Profile

Ensure SQL Developer is closed.

IMPORTANT! These commands will affect your chosen version user profile. Ensure you backup any settings or connections you need.

Step 1 – Close SQL Developer

Ensure that SQL Developer 26.2 is closed.

If you need to, ensure that no processes are running for the application before renaming the configuration folder.

Step 2 – Find User Profile Folder

Open PowerShell and run:


$profile = Join-Path $env:APPDATA `

"SQL Developer\system26.2.0.186.2220"

Test-Path -LiteralPath $profile

Enter fullscreen mode Exit fullscreen mode

If the folder exists you will receive:


True

Enter fullscreen mode Exit fullscreen mode

Ensure that this is the correct version of SQL Developer.

Step 3 – Rename User Profile

Rather than delete the folder, we will rename it with a timestamp.


$profile = Join-Path $env:APPDATA `

"SQL Developer\system26.2.0.186.2220"

if (Test-Path -LiteralPath $profile) {

$backupName = "system26.2.0.186.2220.backup-" +

(Get-Date -Format "yyyyMMddHHmmss")

Rename-Item -LiteralPath $profile `

-NewName $backupName

Write-Host "Profile backed up as:" $backupName

} else {

Write-Host "Profile folder not found."

}

Enter fullscreen mode Exit fullscreen mode

Step 4 – Launch SQL Developer 26.2

Launch the application from the installation folder.

E.g:


C:\oracle\SQLDeveloper26.2\sqldeveloper\sqldeveloper.exe

Enter fullscreen mode Exit fullscreen mode

You will be asked if you want to import settings from a previous installation. In this example we chose No to ensure we had a clean configuration.

A new user profile was created.

Step 5 – Confirm Application Launched Successfully

The application launched successfully.

The Welcome Page opened, and we could confirm that we had the correct version installed.


Help > About

Enter fullscreen mode Exit fullscreen mode

The version shown was:


26.2.0.186.2220

Enter fullscreen mode Exit fullscreen mode

What Was The Fix?

By renaming and replacing the user profile we were able to get the application to launch successfully.

Although we do need to be careful with our conclusions.

We were unable to confirm what the exact cause was of the Netigso error on launch.

We can confirm that the previous user profile had an impact on the issue however we cannot confirm what file in the configuration was causing the error.

  1. Confirm Previous Version Of SQL Developer Works

We also had Oracle SQL Developer 24.3 installed on the workstation.

Sometimes when upgrading an application you may worry that the new version will affect the previous working version.

In this case we were able to use SQL Developer 24.3 as the new installation was in a separate application folder, and we only renamed the user settings folder for version 26.2.

Best Practice

When testing a new version of SQL Developer:

Have a separate installation folder.

Keep the previous working version until you have confirmed the new version works.

Backup any user configuration folders.

Ensure that any critical connections are still working.

Only remove older versions once you have accepted the upgrade (based on your maintenance policy).

This means that if the new application does not meet your requirements you can go back to your previous tools.

  1. Moving Connections From 24.3 To 26.2

Once we had launched SQL Developer 26.2 we needed to ensure that we kept our connections.

SQL Developer allows you to export connections from one installation and import them.

This should only be done for authorised connection profiles.

Step 1 – Launch SQL Developer 24.3

Launch SQL Developer 24.3.

Navigate to the Connections panel.

Step 2 – Export Connections

Right click on the Connections node and select:


Export Connections

Enter fullscreen mode Exit fullscreen mode

Select the connections you wish to move.

Complete the wizard and save the connections in a JSON file.

Store this file somewhere secure. Connection files may contain sensitive information.

Where possible ensure that you have password protection enabled.

Step 3 – Launch SQL Developer 26.2

Launch the recovered SQL Developer 26.2.

Navigate to the Connections panel.

Step 4 – Import Connections

Right click on the Connections node and select:


Import Connections

Enter fullscreen mode Exit fullscreen mode

Select the connection file you wish to import and complete the wizard.

Your connections should now appear in the Connections navigator.

Step 5 – Confirm Connections

Check all important connections.

Ensure that the connection properties are correct. If authorised, check the connections work.

Pay particular attention to connections using:

TNS Aliases

Oracle Wallet files

SSH or network tunnels

External authentication

Custom JDBC properties

Connection settings for the environment.

Just because you have moved a connection profile does not mean that all external files, passwords, network access and authentication have been moved.

Other Things To Consider

There may be other things you want to keep from SQL Developer. This can include:

SQL History

Snippets

Reports

Templates

Preferences

These should be checked separately as the connection export is not intended to move all application user data.

Note: The original troubleshooting confirmed that SQL Developer 26.2 launched successfully and that SQL Developer 24.3 was still working. The export/import process is guidance to help you move your connections, it was not confirmed that all connections were tested.

  1. Summary Of Troubleshooting

Below is a summary of what we found.

Step | Findings | Outcome

--- | --- | ---

Launch SQL Developer 26.2 | Module installation warnings | Fail

Review Netigso messages | Multiple bundles not available | Error

Check ZIP | SHA1 matched Oracle | Pass

Check 5 JAR files | All 5 JAR files present | Pass

Backup old 26.2 profile | Renamed existing settings folder | Complete

Launch with fresh profile | Application launched | Success

Check Help > About | Version 26.2.0.186.2220 | Confirmed

Check previous version | SQL Developer 24.3 still works | Confirmed

The main thing we found was that by refreshing the user profile for version 26.2 we were able to use the application. Despite the warnings suggesting modules were not available.

This shows that it is important to investigate multiple factors when troubleshooting an application.

  1. Screenshots & Evidence

Including screenshots in a technical troubleshooting article helps to make it more useful. Below are the screenshots we should include from the original issue.

Screenshot 1 – Application Error

A screenshot of the initial warning. This should show that some modules couldn’t be installed.

Include Netigso messages if available.

Remove any personal details from your Windows account.

Screenshot 2 – Check ZIP

A screenshot of the Get-FileHash command in PowerShell. This should show that the checksum matches Oracle.

Screenshot 3 – Check JAR Files

A screenshot of the PowerShell output confirming that the 5 application libraries are present.

Screenshot 4 – Application Launched

A screenshot of the Welcome Page for SQL Developer 26.2.

Screenshot 5 – Application Version

A screenshot of the Help > About screen confirming the version.

Ensure that the screenshots are original, clear and relevant. Do not fake any screenshots showing a success. Do not include any connection details for your live databases.

  1. Lessons Learnt

We learnt a few lessons from this troubleshooting.

Missing Bundle Doesn’t Mean Missing File

The initial error suggested that the application couldn’t find the required modules. However by checking we confirmed that the chosen JAR files were present.

Always Check The Archive

Comparing the checksum is a great first step. Often you will be able to avoid downloading the package multiple times as it will match the published checksum.

Backup Before Refreshing

It is better to rename the user settings folder. This means that if you need to get back to your previous settings you can.

Keep Previous Working Application

By keeping SQL Developer 24.3 we were able to investigate the new version. This is useful when troubleshooting tools used for operational activities.

Document Troubleshooting

When troubleshooting an issue it is important to document what you have done. This will help other DBAs understand what was checked to resolve the issue. Avoid assuming anything without verifying it.

Application May Be Recovered But Not Root Cause

Whilst we were able to recover the application we were unable to prove what the exact root cause was. By creating a fresh profile we were able to resolve the issue. A deeper investigation would be required to determine what part of the profile was causing the Netigso error.

  1. Troubleshooting Checklist

When troubleshooting an Oracle SQL Developer launch error on Windows:

Check what version & package you have installed.

Check relevant Java requirements.

Compare download checksum to vendor.

Check application files have been extracted into the correct folder.

Check what error you are receiving.

Check relevant application libraries.

Backup version specific user profile.

Test application with fresh profile.

Do not overwrite previous working installation.

Confirm application launched & version.

Carefully restore required connection profiles.

Document & remove sensitive details.

Not all launch errors will have the same cause. Refreshing the profile may be one option.

Conclusion

Oracle SQL Developer launch errors can be tricky to troubleshoot. In this article we looked at an example of Oracle SQL Developer 26.2 on Windows. We had issues with the application not launching and had errors relating to Netigso modules.

We confirmed that the downloaded installation ZIP had the correct checksum from Oracle. We also confirmed that the 5 JAR files were present.

By renaming the version specific user profile and creating a fresh profile we were able to get the application to launch successfully. We also confirmed that the previous SQL Developer 24.3 installation was still working.

The main takeaway from this is by taking a methodical approach, being cautious when recovering the configuration and keeping the existing settings we can have a safer and more effective solution.

By documenting the steps taken this can be a useful reference for DBAs in the future.

References

Oracle SQL Developer Downloads

https://www.oracle.com/database/sqldeveloper/technologies/download/

Official installation packages, versions & download checksums.

Oracle SQL Developer 26.2 Installation Guide

https://docs.oracle.com/en/database/oracle/sql-developer/26.2/rptig/index.html

Installation requirements & guidance.

Migrating Information From Previous Releases

https://docs.oracle.com/en/database/oracle/sql-developer/26.2/rptig/migrating-information-previous-releases.html

Oracle guidance for keeping connections & information when moving between versions.

SQL Developer Concepts & Usage

https://docs.oracle.com/en/database/oracle/sql-developer/26.2/rptug/sql-developer-concepts-usage.html

Abdulrawof Totakhil

Top comments (0)