ODBC Buffer Error (reply)
Art,
Need a bit clarification.
Case #1: Let`s call it a Server with IIS4/ASP and aspDB-Server DLL loaded and a WIN98 local WS with PWS/IIS4/ASP and aspDB-Local DLL loaded. If the server has the DSN (I prefer system DSN) pointing to the dfb directory and you are accessing it from the WS by executing like "www.server.com/rundbf/tes1.asp" then you do not need any local setup.
Case #2: If you are running everything local then you local DSN pointing to the dbf directory will do it.
Are you usng case #1 or case #2 ? I suggest that you get the ALL local solution going first. It sounded like you are using a local DSN pointing to a Network directory on a separate Server box. I`ve never try that before and I`ll do some experiement. Also, give some details in your ODBC setup will help.
Frank
On 9/18/98 6:57:10 PM, Art wrote:
> Greetings All,
All went well with the DLL registered locally & PWS and
> then...
I published the page to my NT4/IIS4/MTS web server. Here`s the
> setup:
1. DLL in the same folder as the Web (the Eval DLL)
2. DLL is
> registered in MTS & appears OK
3. File DSN is on a separate server
4.
> dBase IV DBF is on the same server as the DSN
Now it returns the
> following error:
Microsoft OLE DB Provider for ODBC Drivers error
> `80004005`
[Microsoft][ODBC Driver Manager] General error: Unable to
> create file buffer
----------------
I tracked the process on my local
> machine and it uses the WindowsTemp directory to create the buffer. I was
> wondering if there was a way to specify the TEMP path for the buffer
> creation so I don`t have to mess with permissions of system folders. --TIA
ODBC Buffer Error (reply)
On 9/19/98 10:09:40 AM, Frank wrote:
> Art,
Need a bit clarification.
[snip]
Hi Frank,
Here`s the skinny...
Scenario 1 (Everything works fine when everything but the data & DSN are local):
1. Win95 client (OSR2)using IE4(SP1)
2. PWS4.0 running on the client
3. the DLL regsvr32`d locally on the client
4. the file DSN is located in a subfolder of the data folder
(i.e. \FileServerMyDataDatasrcMyDSN.dsn) pointing to the folder
(\FileServerMyData) containing the two (2) dbf`s that are used (on the file server
5. the dBase IV (actually Clipper dbf`s) dbf`s are on the file server (\FileServerMyDataTable1.dbf & \FileServerMyDataTable2.dbf)and have no memos or BLOB`s
6. ASP`s on client hitting PWS running on client (http://Win95PWS/MyWeb/ASPdbTest.asp)
Scenario 2 (When I attempt to publish the same stuff on our intranet):
1. Same client (PWS stopped & DLL un-regsvr32`d)
2. Same DSN & data (System DSN works fine, but then the admin "pains" increase... so call me lazy, I`m a programmer--lazy is my credo!)
3. IIS4 running on webserver (\WebServer) under NT4
4. ASP moved to webserver (\WebServerMyWebASPdbTest.asp or http://TestSvr/MyWeb/ASPdbTest.asp)
5. DLL registered in MTS2.0 running on the webserver.
--under these circumstances the buffer error is generated.
The crux of the issue seems to be permissions on the folder in which the buffer is being created (when using a file DSN). The problem is determining which folder it is (in Scenario 1 it is c:windows emp). The solution would be to specify the `TEMP` folder.
Things around here change--OFTEN. I was hoping to have a single point of administration (one File DSN) for the access to this data. That way I can just pop open NotePad and modify the DSN as desired obviating the need to modify system DSN`s on each of the servers involved.
I realize this has nothing to do with ASPdb per se. I just hoped that someone had run into this before & had resolved it.
Thanx (no response required),
Art
