Connect button disabled. How to re-enable

[muradkhan]

I periodically end up with sessions that seem to have gotten corrupted. Is there a way to reset a session so that the session connection dialog does not display a disabled button.

[bgagnon]

Hello muradkhan,

Are you using both SecureCRT and SecureFX?

What version?

Is it in one or the other of the applications that the Connect button is grayed out?

If so, this is generally indicative of a session that was created in SecureCRT when installed as a standalone application (rather than a part of the SecureCRT+SecureFX bundle).
If the bundle is installed later, that older existing session will still be available, but since it was created in SecureCRT (standalone, no File Transfer capability with SecureFX), the File Transfer protocol will be "None" as seen in the Connection category of Session Options:

Terminal protocol (for use with SecureCRT)
and
File transfer protocol (for use with SecureFX)

When you run SecureCRT and SecureFX as separately installed standalone applications pointing to the same configuration folder, the sessions created in SecureCRT will not be "connectable" from within SecureFX until you edit that session in SecureFX and set the File Transfer protocol. Solution? Uninstall SecureCRT, uninstall SecureFX, and install the SecureCRT+SecureFX bundle instead.

If, for some reason, you don't install using the integrated installer and you cannot use a shared config, then the workaround would be to duplicate all the sessions and have one set that is configured for SecureCRT and the other appropriate for use in SecureFX.

[muradkhan]

Thanks Brenda

Running SecureCRT 6.7.5. Sorry, I know it's old.

I launch connect, and from the list of available sessions, some have the connect button disabled.

[bgagnon]

Hello muradkhan,

I understand the issue.

Are you saying SecureFX is not installed on the machine at all?

Was the config possibly migrated from an "integrated installation"?

With a bit of reading between the lines, I believe your answer is found in my prior post. Please reread it thoroughly.

[muradkhan]

You were exactly correct. I have now created a folder structure within the Sessions Dialog box, and keep my SecureCRT sessions in one place and my FX connections in another place

Thanks for your astute guidance

[rich@shroop.net]

I also had this problem, but for a different reason. Had to edit the ini file for the session and change

S:"Transfer Protocol Name"=None

to

S:"Transfer Protocol Name"=SFTP