Обсуждение: Upgrade to Win XP Service Pak 2 SP2 causes connection failure

I've got an app written with Access XP using a PostgreSQL backend internet
connection (using the latest ODBC driver) that was deployed 2 years ago.
Recently a client upgraded to XP Service Pack 2. After the upgrade she was
unable to connect to the remote database, getting the error:

Unable to connect to remote database File Name=C:\Program Files\Common
Files\ODBC\Data Sources\PostgresCNI.dsn Error message: The file is not a
valid compound file.

I did some research and found people recommending the connection string use
'FileDSN=<dsn file>' instead of 'File name=<dsn file>'

So I changed it from:

    Set conn = New ADODB.connection
    conn.Open "File Name=C:\Program Files\Common Files\ODBC\Data
Sources\PostgresCNI.dsn"


to

    Set conn = New ADODB.connection
    conn.Open "FileDSN=C:\Program Files\Common Files\ODBC\Data
Sources\PostgresCNI.dsn"

Now the app gives this error:

This file is located outside your intranet or on an untrusted site.
Microsoft Acess will not open the file due to potential security problems.
To open the file, copy it to your machine or an accessible network location.

We've tried turning off the WinXP firewall entirely, adding the server IP to
trusted internet sites, all to no avail.

Any one else run into this?


--
Randall Perry
sysTame

Xserve Web Hosting/Co-location
Website Design/Development
WebObjects Hosting
Mac Consulting/Sales

http://www.systame.com/

On Wed, 20 Oct 2004, Randall Perry wrote:

> Now the app gives this error:
>
> This file is located outside your intranet or on an untrusted site.
> Microsoft Acess will not open the file due to potential security problems.
> To open the file, copy it to your machine or an accessible network location.
>
> We've tried turning off the WinXP firewall entirely, adding the server IP to
> trusted internet sites, all to no avail.

I have seen similar things happening with any application not of the
Microsoft fold.  One case where xmms on a Linux box had to download/copy
the whole album from a Win2003 share before it would play (no streaming).

   And another where a MS Office application (on a new WinXP Home desktop
with all non-SP2 updates applied) requests a virus scan when opening a
file on a SAMBA share (rather old RHL/SAMBA installation though) and would
take up to 2+ minutes (I tweaked settings and got it down to 20-30
seconds) to open a simple spreadsheet.  OpenOffice.org opened it in 3-5
seconds.

> Any one else run into this?

Not yours specifically but I see a pattern here.  I'll ask the guy that
sorted out the xmms issue what he did to fix it.


Rod
--
    "Open Source Software - You usually get more than you pay for..."
     "Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"

As I've been playing with differing versions of psqlodbc I've been editing
odbc.ini with "abandon"... But now I'd like to understand a little better...
I've yet to find a document that explains what each term implies, but have
found a number of examples.

What I'll do here is to include a portion of my odbcinst and odbc.ini files
and add "comments" with my questions.

; ### sample odbcinst.ini ###
[PostgreSQL]
Description     = ODBC for PostgreSQL
Driver          = /usr/lib/psqlodbc.so
Setup           = /usr/lib/libodbcpsqlS.so
;
; I notice that the psqlodbc source tree does not build a Setup
; library. If that is the case, what is the right entry for it?
;
FileUsage       = 1
CPTimeout       =
CPReuse         =

[ODBC]
Trace           = Yes
TraceFile       = /tmp/ODBCsql.log
ForceTrace      = Yes
Pooling         = No
;
; Does this stanza have any relationship to the same one in /etc/odbc.ini?
;

; ### sample odbc.ini ###
[ODBC Data Sources]
Mustang = PostgreSQL Database from unixODBC
Mustang_07.03.0200_02.50 = PostgreSQL using 07.03.0200_02.50
Mustang_07.03.0200_03.00 = PostgreSQL using 07.03.0200_03.00
Mustang_07.05.0001_03.00 = PostgreSQL using 07.05.0001_03.00
Mustang_08.00.0001_03.00 = PostgreSQL using 08.00.0001_03.00
Mustang_08.00.0002_03.00 = PostgreSQL using 08.00.0002_03.00
;
; Are their any restrictions on characters in a DSN name?
; From other experiments, I found that the <tab> char is
; not <whitespace> in this stanza. Are their other restrictions?
;

[DEFAULT]
;
; I've seen both [Default] and [DEFAULT] in samples, is there
; a correct one? There is no reference to "default" as a string
; in the source.
;
; When I tried to actually use this as a default (setting common
; options here and just setting DSN specific settings elsewhere
; I saw errors about certain values not being set and no default
; being set.
;
; Also, does this "default DSN" need to be named in the
; [ODBC Data Sources] section?
;
Driver          = /usr/lib/libodbcpsql.so
Trace           = Yes
TraceFile       = /tmp/trace_psqlodbc.log
;
; Is this attribute overridden somewhere? I have never seen one
; of these trace files on my system. Although I have seen files
; with names of the form:
;    /tmp/mylog_<uid><pid>.log    /tmp/psqlodbc_<uid><pid>.log
;
Servername      = localhost
Username        = postgres
Password        = swp123
Port            = 5432
Protocol        = 6.4
;
; What does this version imply? I have seen both 6.4 and 7.0 in
; sample files on the net. This line was produced by ODBCConfig
; but I have no idea whether it pulled it out of a specific
; psql driver or not. The 07.05.0001 source suggests version 6.4
; is the default. The source references up to version 7.3.
; What do I check in either my data manager (unixODBC) or Postgres
; backend (7.4.5-2) to find what the correct setting should be?
;
ReadOnly        = No
RowVersioning   = No
ShowSystemTables        = No
ShowOidColumn   = No
FakeOidIndex    = No
ConnSettings    =
Debug           = 1
CommLog         = 1

[Mustang]
Description     = Mustang using default driver
Driver          = /usr/lib/libodbcpsql.so
Database        = Mustang
TraceFile       = /tmp/trace_odbc_libodbcpsql.log
Database        = Mustang
Trace           = Yes
Servername      = localhost
Username        = postgres
Password        = swp123
Port            = 5432
Protocol        = 6.4
ReadOnly        = No
RowVersioning   = No
ShowSystemTables        = No
ShowOidColumn   = No
FakeOidIndex    = No
ConnSettings    =
Debug           = 1
CommLog         = 1
; <others omitted for "brevity"

[ODBC]
InstallDir    = ???
;
; I've seen in some documents that this entry is required
; but it does not exist in the sample sent out with various
; Linux RPMs.
;
; Is it required? And what should it be set to? In a sample
; I have it references a shared library (the entry is /usr/lib/libiodbc.so)
; If I am using unixODBC, what should it be set to?
;

I hope this wasn't too long...
Thanx for the help...
Rich