X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:cc:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=uCbyU8DOmwzff3FHevb6nA5SE/pbv
	ZE67Mzd6ipIxAbcF1UBV5iXWeUm16cPlw+gHbAyoDyUUGBLmYQU30TvECmn0Aufd
	DujMRfzkeW1JxmNWZtIZ5oQ4+CaEccVxJeXsR3QdG8VgSTYF332KMvrPFyE19apT
	bhwQqvfyvm1BQ0=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:cc:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=EmPvrVLO7Dx9+y37k0Tt5vwQmwU=; b=ZH5
	BogmBD3RyWMpWkqGTsnf/Uz9kl17AiOst6/0gFiV86TxddhGdrEgx14QulHJ1zgs
	OnFYgN38fS4/0sfUgl0iIpL/izhmMgJ68QZVwVoT3RVJkuMGnT+SX4sKMjWqgV2/
	a9bdjRa0Kh8IdnezA7DbuAZVxEvChRkn/DY8SOPA=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-6.4 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=danny DOT fournier AT dfo-mpo DOT gc DOT ca, U*Danny.Fournier, D*gc.ca, Danny DOT Fournier AT dfo-mpo DOT gc DOT ca
X-HELO: VSNSBIODMZEDG01.DFO-MPO.GC.CA
From: "Fournier, Danny G" <Danny DOT Fournier AT dfo-mpo DOT gc DOT ca>
To: "Gluszczak, Glenn" <Glenn DOT Gluszczak AT dell DOT com>
CC: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: RE: ERROR: A specified logon session does not exist. It may already have been terminated
Date: Wed, 18 Oct 2017 12:03:59 +0000
Message-ID: <513AA0729B894545B2D793D01FFF8B6D471A10CD@SVNSBIOMBX01.ENT.dfo-mpo.ca>
References: <513AA0729B894545B2D793D01FFF8B6D4719B909 AT SVNSBIOMBX01 DOT ENT DOT dfo-mpo DOT ca> <91DCAC3CB99C724EB365BB64677FBE7B1EFC1B60 AT MX204CL04 DOT corp DOT emc DOT com> <513AA0729B894545B2D793D01FFF8B6D4719B986 AT SVNSBIOMBX01 DOT ENT DOT dfo-mpo DOT ca> <91DCAC3CB99C724EB365BB64677FBE7B1EFC1B90 AT MX204CL04 DOT corp DOT emc DOT com> <513AA0729B894545B2D793D01FFF8B6D4719BB61 AT SVNSBIOMBX01 DOT ENT DOT dfo-mpo DOT ca> <91DCAC3CB99C724EB365BB64677FBE7B1EFC1C9B AT MX204CL04 DOT corp DOT emc DOT com> <513AA0729B894545B2D793D01FFF8B6D471A0719 AT SVNSBIOMBX01 DOT ENT DOT dfo-mpo DOT ca> <91DCAC3CB99C724EB365BB64677FBE7B1EFC501E AT MX204CL04 DOT corp DOT emc DOT com> <513AA0729B894545B2D793D01FFF8B6D471A0D3B AT SVNSBIOMBX01 DOT ENT DOT dfo-mpo DOT ca> <91DCAC3CB99C724EB365BB64677FBE7B1EFC5305 AT MX204CL04 DOT corp DOT emc DOT com>
In-Reply-To: <91DCAC3CB99C724EB365BB64677FBE7B1EFC5305@MX204CL04.corp.emc.com>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id v9IC4Qsm019782

I did not add the password to the registry (not knowingly in any case). When we initially setup, we logged in by providing the password and used ssh-copy-id to setup the key.

-----Original Message-----
From: Gluszczak, Glenn [mailto:Glenn DOT Gluszczak AT dell DOT com] 
Sent: October-17-17 5:11 PM
To: Fournier, Danny G
Subject: RE: ERROR: A specified logon session does not exist. It may already have been terminated

Good detective work.   I need to think about why key only authentication would cause an impact.

Did you add the password to the registry?
(Log in as the user and the run "passwd -R").

To get proper identity from a filesystem basis, a process still needs to log in.
SSH uses a behind the scene login if it finds the password.  If you log in directly, it doesn't need to access the registry one.

Glenn

-----Original Message-----
From: Fournier, Danny G [mailto:Danny DOT Fournier AT dfo-mpo DOT gc DOT ca]
Sent: Tuesday, October 17, 2017 3:32 PM
To: Gluszczak, Glenn; cygwin AT cygwin DOT com
Subject: RE: ERROR: A specified logon session does not exist. It may already have been terminated

Here's what I just did:

1. created new local administrator account 2. ran mkpasswd -l > /etc/passwd 3. removed all instances of server name in /etc/passwd (ie. MYSERVERNAME+) 4. remotely connected successfully 5. successfully ran schtasks, it listed all jobs configured 

I just retried with the other user, where I connect specifying a shared key and got the error message.

For good measure, I changed the password on the problematic user, connected directly without the key and provided the password. I then ran schtasks and it ran fine. It listed all the jobs configured.

It would seem that our issue is related to connecting over SSH using a shared key.

-----Original Message-----
From: Gluszczak, Glenn [mailto:Glenn DOT Gluszczak AT dell DOT com]
Sent: October-17-17 11:08 AM
To: Fournier, Danny G
Subject: RE: ERROR: A specified logon session does not exist. It may already have been terminated


Does ssh with Administrator and running schtasks fail as well?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple