There seems to be a problem with the RFC SDK (and I assume therefore .NET connector too) whereby an attempt to connect to an SAP system by supplying the saplogon ID will fail if there are blank description entries in the saplogon.ini file.
For example, suppose my saplogon.ini file contains entries like:
If I establish an RFC connection using SAP logon ID "Development" it will work, provided the logon details are correct. However if the saplogon.ini file contains entries like those that follow, then the connection attempt will fail.
The RFC SDK seems to get thrown by the blank item description and returns indicating that the saplogon entry for "Development" cannot be found.
I'm not actually using .NET connector, but rather the SDK function RfcOpenEx directly, however I imagine the problem should exist for both. Can anyone using the .NET connector confirm whether this problem exists there too?