unexpected protocol charactor during authentication
От | Will |
---|---|
Тема | unexpected protocol charactor during authentication |
Дата | |
Msg-id | 20020416093707.19992.qmail@sanity.demonkarma.net обсуждение исходный текст |
Список | pgsql-odbc |
"Test connection failed because of an error in initializing providor. Unexpected protocol charactor during authentication; Socket has been closed." The above is the error I get from ODBC in Visual Basic when hiting "Test Connection" when connecting via SSH tunnel to the server. PgAdmin spit out the following Debug info also: -- Debug output -- 4/16/2002 2:25:50 AM - Entering pgSchema:pgServer.Connect("localhost", 5432, "will", "********") 4/16/2002 2:25:50 AM - Opening cnPostgreSQL: SERVER=localhost;PORT=5432;UID=will;PWD=*******;DATABASE=parallax;DRIVER={PostgreSQL};READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS=;FETCH=100;SOCKET=4096;UNKNOWNSIZES=0;MAXVARCHARSIZE=254;MAXLONGVARCHARSIZE=65536;OPTIMIZER=1;KSQO=1;USEDECLAREFETCH=0;TEXTASLONGVARCHAR=1;UNKNOWNSASLONGVARCHAR=1;BOOLSASCHAR=1;PARSE=0;CANCELASFREESTMT=0;EXTRASYSTABLEPREFIXES=dd_;COMMLOG=1;DEBUG=1; 4/16/2002 2:25:50 AM - Done - 0.5 Secs. 4/16/2002 2:25:50 AM - Error in pgAdmin II:frmConnect.cmdConnect_Click: -2147217843 - Unexpected protocol character during authentication; Socket has been closed. ------ This happened after we took down the PostgreSQL database after upgrading to 7.2 to the old 7.1 version long enough to dump a database which we restored to the 7.2 version... when we brought it back up... all of our applications no longer worked, nor did PgAdmin II. Although PHP and the PgSQL tools work fine. Any ideas? Thanks, -- Will Robertson Systems Administrator DemonKarma Networks ________________________________________________ This mail was sent by DemonKarma WebMail 1.0
В списке pgsql-odbc по дате отправления: