delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2007/01/19/21:14:01

X-Spam-Check-By: sourceware.org
Message-ID: <192cb2440701191813t2f53fe14lb9f93aee62310393@mail.gmail.com>
Date: Fri, 19 Jan 2007 18:13:35 -0800
From: "Mike Yoder" <yoderme AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: When ssh'd in, cannot run MS compiler /Zi debug option
MIME-Version: 1.0
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

This is sort of a repost of a previous question to this mailing list.
I am running into

Fatal Error C1902: Program database manager mismatch; please check
your installation.

When attempting to use the visual studio compiler from within cygwin
when logged in via ssh.  I found the following in the archives:

On Jul 19 04:06, Mark Charney wrote:
> I suspect I'm missing some "rights".
>
> When I try to compile using the debug-option (/Zi) to the
> Microsoft Visual Studio Pro 2005 compiler:
>     cl /Zi hello.cpp
> it only works from within cygwin if I am on the console or
> remote desktop. If I ssh-in to the same machine, it fails with
> a error message:
>
>      Fatal Error C1902: Program database manager mismatch; please
>      check your installation.
>
> Compiling without /Zi works fine anywhere we try it.

To which Corinna Vinschen replied:

> The problem is that there's arguably an identification bug in Windows.
> Try "/cygdrive/c/WINDOWS/system32/whoami.exe" and you will see that
> you're identified as "sshd_server", not as yourself.

Indeed this is what I observe, with one wrinkle (below)

> Either use password authentication instead of public key authentication
> when loging in through ssh.  Password authentication creates a valid
> logon session, so you're correctly identified and the problem should go
> away.

I see that using password authentication does make the problem go away
for accounts local to the machine.  But if I ssh into this machine
using a domain account and use password authentication, whoami still
tells me that I'm the sshd_server.  (I built /etc/passwd using
'mkpasswd -c -l -d'; when on the console whoami says 'DOMAIN\username'
as expected)  Any ideas why this is?

Anyway, I was wondering if there is an actual fix out there or any
sort of workaround.  I'd really like to be able to use public key
authentication.  I thought I'd ask the list since I haven't seen any
traffic on this topic since July.  (Or, at least my search for "C1902"
only returned hits in July - please accept my apologies if I missed
something.)  Right now it looks like the only thing I can do is remove
this machine from the domain, add some local accounts, and use
password auth. :-(

Thanks in advance for your help,
-Mike Yoder

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019