DSN pointing to another server

[ChuckG]

I'm setting up a web page to pull information from our live manufacturing system.

I've been able to place a copy of the Visual Foxpro table I'm going to use for my data into the web site, and make a DSN to it and pull data perfectly.

But when I try and make a new System DSN that points to another server (on our NT Domain) and access the DBC I continue to get

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Visual FoxPro Driver]Cannot open file


But in my ASP page, as soon as I tell it to go back to the DSN pointing to the file on the Web Server it works perfectly.

It appears to be some sort of Security issue, but I can't find anything that wouldn't allow the server access.

I found MS Knowledge Base article Q164145 which sounds similar to this problem, but turning the Fetch Data in Background off didn't help at all.

Internally I've got the Web Server which is a stand alone NT Server attached to our NT Domain, and the DSN is pointing to a BDC of the domain.

Thanks for any help
Chuck

 

[SnakeHollywood]

Are you trying to point the DSN to a database on another server over the network?
e.g

\\servername\my files
You need to map a drive to the machine with your database so you can reference it as though it were local.


Russ Michaels
russ@satachi.com

http://www.satachi.com

For my personal book recommendations visit

http://www.satachi.com/books.html

 

[ChuckG]

Yes I was attempting to use the UNC path for the database.

I'll give it a try at mapping a drive out to it and see if that works.

Thanks
Chuck

 

[ChuckG]

Russ,

Even after I went back and changed the path of the DSN from \\server\apps\applicat\data\master.dbc

(server\share\path\file)

and then mapped L: to \\server\apps

and made the DSN look at L:\applicat\data\master.dbc

I still get the following error.

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Visual FoxPro Driver]Cannot open file l:\applicat\data\master.dbc.

But still if I change it to a copy of the file on the web server it works perfectly.

Chuck

 

[JohnYingling]

Look at File DSN.

http://www.msdn.microsoft.com

/ MSDN Library /Platform SDK / Data Services.

http://WWW.VBCompare.Com

 

[ChuckG]

Thanks for the info, I took a look at it, there's alot of discussion about it but not much technical detail.
I'm not sure how well a file DSN would work on a web site, our programmer here keeps telling me I need to use a System DSN, but I'll keep digging into it.

 

[ChuckG]

I've found an answer to this problem (although with the answer, I've come across another issue lol)

To get the system DSN to access the DB residing on another domain server, I had to create a Domain account matching the IIS anon account, and make sure it had access to the location the DB was in. Then tell IIS that the domain account was the "anon" instead of the one it created.

Once I did that, I was able to pull data from the live DB with no problem.


The new problem I'm running into is, the script that runs does a conditional URL forward (if the value of a specific field is Y then it send the user to a passworded site, if it's N then it sends them to a static page telling them they don't have access).

The problem occurs when they are forwarded to the passworded site, and enter their information in (a domain account/password) once they do that, it refuses to to pull data from the DB again, (giving the same "can not open file" error).

I've verified that the individual's domain account has access to read/write to the DB. and I've even tried adding

objConn.ConnectionString = "DSN=inv_data2;UID=IUSR_SI-EXCHANGE;PWD=password"

the UID and PWD fields to the connection string trying to force it to use the anon account to access the DSN/DB

Any idea's?