Seems like you ran into a(nother) bug ... the failure message is at least explanatory ... it obviously expects a SID and cannot do without it.
Lets hope Jeff Smith will also read it and give it to developer to fix the issue.
do you have any non alphabetic characters in your hostname or service name?
No non-alphabetic characters in the username, hostname, or service name.
The end customer is in the process of downloading the 4.0.2 version of sqldeveloper with JDK 1.7 to see if that works for them. I'll let you know. They were actually the first to have the "invalid connection string error" with 4.1.1. and JDK 1.8.
I would carefully examine the connections.xml files in the 4.0.2 user profile versus the 4.1.1 user profile. Perhaps something got corrupted and there are non-printing characters in the 4.1.1 file. Or just create a new connection using the same credentials but type in everything manually.
The end-customer was able to get 4.0.2 working, but still not with 4.1.1, Same as me.
I carefully re-downloaded and reinstalled 4.1.1, when it starts up, it asks to import connection settings from a previous version of sqldeveloper. I did that, got the connections that work in 4.0.2, but when tried in 4.1.1, the "invalid connection string format" occurs.
Afterwards, I performed a diff between connections.xml of 4.0.2 and 4.1.1, they were identical. There are no ghost characters in the domain names for the host name or service name.
The hostname and service names both use domain extensions, ie: the connection string is of the format: username@//host.x.company.com:1521/service.x.company.com
1 person found this helpful
You say you have no non-alphabetic characters, but review this earlier discussion (a hyphen was the problem) and see if any of Jeff's suggestions work for you: Connection error after upgrade to 4.1
I also read another (non-SQL Developer) post where an at-sign (@) in the password was an issue, but perhaps that does not apply to your case.
I'm having the same issue.
For me, the services with a period in the full name get that error message. The services without a period in their name work fine.
Maybe the slashes in the hostname do the harm?
aye, hence my original follow-up question:
>>non alphabetic characters?