DBF Connection from Win2k Server Web site to Windows Small Business Server 2003 over VPN
I am having difficulty connecting from an asp web site (web server on win2k server) through an automatically established VPN to an Windows 2003 Small business server share into a folder containing the dbf
I get lots of wonderfull errors.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC dBase Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0x9dc Thread 0x488 DBC 0x38771bc Xbase'.
with the asp coding for above is simply
Set whConn = CreateObject("ADODB.Connection")
whConn.Open "Driver={Microsoft dBASE Driver (*.dbf)};" & _
"Dbq=f:\testwhdb"
(the f:\testwhdb is the already established VPN network share into the remote machine)
OR errors like
Microsoft JET Database Engine error '80004005'
'\\SERVERNAME\testwhdb\whprods.dbf' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.
with asp simply
whconn.open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\boss\testwhdb\whprods.dbf"
OR errors like
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC dBase Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0x9dc Thread 0x880 DBC 0x387bc24 Xbase'.
with asp as
whconn.open "Driver={Microsoft dBASE Driver (*.dbf)};'Dbq=\\boss\testwhdb;"
I am confused
I have looked for things like permissions using IUSR_machine name in the remote machine but still no joy...
The vpn will allow any ports, so nothing is blocked...
+--------------+ VPN +------------+
| Webserver |---------------------------| dbf file |
+--------------+ +------------+
ASP script
runs here
Is this correct?
Does the code work if you put the dbf file locally on the webserver (not suggesting this as a solution but to eliminate whether it is a VPN problem or a config problem on the web server)?
0
CybordaxAuthor Commented:
yes, my friend, i have copied locally and it works fine...
I can put the same asp coding in a visual basic program and run it... i.e. on the web server and it goes through vpn and pulls the data from the dbf. (but it takes like 1 minute to get one record specified by the program i.e. where the fieldname = whatever)
To me it suggests security permissions, which i have put to basic permissions, etc... mapped a network drive...
pretty much everything...
Next stage is what happens if you put the file on another resource on your LAN - i.e. leave out the VPN and use another workstation on the same LAN as the server - does that work.
0
In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!
intriguing. that was something i should have tested... but did not......
i get an error
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC dBase Driver] '(unknown)' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.
i set up the dsn on the web server and the dbf on another machine lan based but no joy, tried the following asp
Set whConn = CreateObject("ADODB.Connection")
whConn.Open "Driver={Microsoft dBASE Driver (*.dbf)};" & _
"Dbq=f:\testwhdb" also trued UNC
also did normal dsn.
hmmm... i am confused now. also disabled any firewalls
There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.
+--------------+ VPN +------------+
| Webserver |-------------------------
+--------------+ +------------+
ASP script
runs here
Is this correct?
Does the code work if you put the dbf file locally on the webserver (not suggesting this as a solution but to eliminate whether it is a VPN problem or a config problem on the web server)?