Ping Kevin Spencer/Stefan Rusynko

M

MikeR

You guys done with the thread 'Another question on local/server diffs'? I had posted some
responses to your responses.
Thanks,
MikeR 1st
 
K

Kevin Spencer

I wasn't aware that I was participating in that thread. Perhaps you could
restate your remaining issues in this one.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Paranoia is just a state of mind.
 
M

MikeR

Hi Kevin -
Here is the OP fro 8/26. The whole issue is to get this line synced (sp?) on my host and
local IIS. dbname="DBQ=" & Server.MapPath("/db/qsl.mdb")
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
My host doesn't allow parent paths, citing security concerns. I have IIS on my local box,
and set parent paths off to match, so publishing doesn't break the data access pages.

Now, locally, dbname="DBQ=" & Server.MapPath("/db/qsl.mdb") gives me

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key
'Temporary (volatile) Jet DSN for process 0xdb4 Thread 0x204 DBC 0x1150064 Jet'.

Googling that finds a ton of references to error 80004005, but nothing that fixes the problem.
+++++++++++++++++++++++++++++++++++++++++++++++++++++
Your reply has for some reason expired, but if I recall correctly, you said you thought it
was a permissions issue. Stefan had the same reaction.
Following is my reply to you.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Hi Kevin -
Thanks for the reply.

I don't understand why, if it's a permission issue, this works (if parent paths are enabled)
dbname="DBQ=" & Server.MapPath("../db/qsl.mdb")
Isn't it reading the same registry key either way?

I'd been on the MS site you referenced, and I still don't see anything that matches my
error message, or resolves the issue. Can you point to a specific one?

The connection is
set conxtemp=server.createobject("adodb.connection")
conxtemp.Open "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
Server.MapPath("../db/qsl.mdb")
It works fine as long as using parent path is enabled.

I'm not being argumentative, just striving for enlightment.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Mike
 
B

Bob Lehmann

http://www.aspfaq.com/show.asp?id=2154

Bob Lehmann

MikeR said:
Hi Kevin -
Here is the OP fro 8/26. The whole issue is to get this line synced (sp?) on my host and
local IIS. dbname="DBQ=" & Server.MapPath("/db/qsl.mdb")
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++
My host doesn't allow parent paths, citing security concerns. I have IIS on my local box,
and set parent paths off to match, so publishing doesn't break the data access pages.

Now, locally, dbname="DBQ=" & Server.MapPath("/db/qsl.mdb") gives me

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key
'Temporary (volatile) Jet DSN for process 0xdb4 Thread 0x204 DBC 0x1150064 Jet'.

Googling that finds a ton of references to error 80004005, but nothing that fixes the problem.
+++++++++++++++++++++++++++++++++++++++++++++++++++++
Your reply has for some reason expired, but if I recall correctly, you said you thought it
was a permissions issue. Stefan had the same reaction.
Following is my reply to you.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Hi Kevin -
Thanks for the reply.

I don't understand why, if it's a permission issue, this works (if parent paths are enabled)
dbname="DBQ=" & Server.MapPath("../db/qsl.mdb")
Isn't it reading the same registry key either way?

I'd been on the MS site you referenced, and I still don't see anything that matches my
error message, or resolves the issue. Can you point to a specific one?

The connection is
set conxtemp=server.createobject("adodb.connection")
conxtemp.Open "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
Server.MapPath("../db/qsl.mdb")
It works fine as long as using parent path is enabled.

I'm not being argumentative, just striving for enlightment.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Mike

Kevin said:
I wasn't aware that I was participating in that thread. Perhaps you could
restate your remaining issues in this one.
Click to expand...
Click to expand...
 
K

Kevin Spencer

Hi Mike,

I can't tell you why it seems to work on your local machine when you use
parent paths, but not when you use root-relative paths. I can tell you that
it is a permissions issue with regards to the anonymous Internet User
account, under which ASP runs, being able to read the System Registry.

Bob's article link may be of help to you. In addition, I don't remember
whether or not it was you whom I was addressing regarding this, but using
ODBC is not necessary, nor is it the most desirable way to access a
database. ODBC is a wrapper for OLE DB, and you can connect without a DSN
using OLE DB, which doesn't require System Registry access. See
http://www.connectionstrings.com for an Access OLE DB Connection String.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Paranoia is just a state of mind.

MikeR said:
Hi Kevin -
Here is the OP fro 8/26. The whole issue is to get this line synced (sp?)
on my host and local IIS. dbname="DBQ=" & Server.MapPath("/db/qsl.mdb")
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
My host doesn't allow parent paths, citing security concerns. I have IIS
on my local box, and set parent paths off to match, so publishing doesn't
break the data access pages.

Now, locally, dbname="DBQ=" & Server.MapPath("/db/qsl.mdb") gives me

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Microsoft Access Driver]General error Unable to open
registry key 'Temporary (volatile) Jet DSN for process 0xdb4 Thread 0x204
DBC 0x1150064 Jet'.

Googling that finds a ton of references to error 80004005, but nothing
that fixes the problem.
+++++++++++++++++++++++++++++++++++++++++++++++++++++
Your reply has for some reason expired, but if I recall correctly, you
said you thought it was a permissions issue. Stefan had the same reaction.
Following is my reply to you.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Hi Kevin -
Thanks for the reply.

I don't understand why, if it's a permission issue, this works (if parent
paths are enabled)
dbname="DBQ=" & Server.MapPath("../db/qsl.mdb")
Isn't it reading the same registry key either way?

I'd been on the MS site you referenced, and I still don't see anything
that matches my error message, or resolves the issue. Can you point to a
specific one?

The connection is
set conxtemp=server.createobject("adodb.connection")
conxtemp.Open "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
Server.MapPath("../db/qsl.mdb")
It works fine as long as using parent path is enabled.

I'm not being argumentative, just striving for enlightment.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Mike

Kevin said:
I wasn't aware that I was participating in that thread. Perhaps you could
restate your remaining issues in this one.
Click to expand...
Click to expand...
 
M

MikeR

Bob -
Thanks. I had seen that page before, and had assigned the privs to the temp directory, as
suggested. No joy, same error. I'm having a hard time seeing it as a permission thing, as
it works fine IF parent paths are enabled, and the path has the ..

So I changed the connection to
cst = "Provider=Microsoft.Jet.OLEDB.4.0;" & "Data Source=" &
Server.MapPath("\fpsubwebname\db\challenge.mdb")
set conntemp = Server.CreateObject("ADODB.Connection")
conntemp.open cst

as suggested, and it worked. However, on the host the connection has to be

st = "Provider=Microsoft.Jet.OLEDB.4.0;" & "Data Source=" &
Server.MapPath("\db\challenge.mdb")
set conntemp = Server.CreateObject("ADODB.Connection")
conntemp.open cst

which still leaves me with a mis-match between my local and hosted "versions", my original
complaint.

I have enough pages that use a database so it's tedious to have two paths.

Mike

Bob said:
http://www.aspfaq.com/show.asp?id=2154

Bob Lehmann

Hi Kevin -
Here is the OP fro 8/26. The whole issue is to get this line synced (sp?)
Click to expand...

on my host and
local IIS. dbname="DBQ=" & Server.MapPath("/db/qsl.mdb")

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++

My host doesn't allow parent paths, citing security concerns. I have IIS
Click to expand...

on my local box,
and set parent paths off to match, so publishing doesn't break the data
Click to expand...

access pages.
Now, locally, dbname="DBQ=" & Server.MapPath("/db/qsl.mdb") gives me

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Microsoft Access Driver]General error Unable to open
Click to expand...

registry key
'Temporary (volatile) Jet DSN for process 0xdb4 Thread 0x204 DBC 0x1150064
Jet'.

Googling that finds a ton of references to error 80004005, but nothing
Click to expand...

that fixes the problem.
+++++++++++++++++++++++++++++++++++++++++++++++++++++
Your reply has for some reason expired, but if I recall correctly, you
Click to expand...

said you thought it
was a permissions issue. Stefan had the same reaction.
Following is my reply to you.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Hi Kevin -
Thanks for the reply.

I don't understand why, if it's a permission issue, this works (if parent
Click to expand...

paths are enabled)
dbname="DBQ=" & Server.MapPath("../db/qsl.mdb")
Isn't it reading the same registry key either way?

I'd been on the MS site you referenced, and I still don't see anything
Click to expand...

that matches my
error message, or resolves the issue. Can you point to a specific one?

The connection is
set conxtemp=server.createobject("adodb.connection")
conxtemp.Open "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
Server.MapPath("../db/qsl.mdb")
It works fine as long as using parent path is enabled.

I'm not being argumentative, just striving for enlightment.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Mike


could
Click to expand...
Click to expand...
 
M

MikeR

Thanks Kevin -
I guess mysteries are what keep us going. Everything was so nice until my host disabled
parent paths.

There is no DSN involved. I changed the connection to the one outlined in Bob's link, and
it works, but I am left with my original problem, a different path on the local machine
and the host.

Mike, scratching head in Puzzlement(about 40 miles south of DOH).
 
T

Thomas A. Rowe

MikeR,

The path issue is why I continue to use System DSN, as it doesn't matter where the database is
located since I woork with databases stored outside of the web root.

You might be able to solve your path issue by always storing the database in the fpdb folder.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================
 
K

Kevin Spencer

Hi Mike,

Sorry about the DSN thing. But ODBC apparently requires System Registry
access as well. As I haven't used ODBC in years, I suppose I forgot!

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Paranoia is just a state of mind.
 
K

Kevin Spencer

Hi Thomas,

If he had used a System DSN, he would stilll have had a Registry permissions
issue.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Paranoia is just a state of mind.
 
T

Thomas A. Rowe

Not by default, as I have never had to make any permissions changes to use it locally, I know my web
host does because it is only accessible for the site/account is created for.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================
 
B

Bob Lehmann

You can set the path to the DB dynamically by first determining which server
you are on.....

If Request.ServerVariables("Server_Name") = "dev" Then
cst = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" &
Server.MapPath("/databases/sm2.mdb")
Else
cst = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" &
Server.MapPath("/cgi-bin/sm2.mdb")
End If

Bob Lehmann
 
M

MikeR

Thanks Jim -
That link has already been perused. There is a fairly humerious bit on it.
1. Start Registry Editor (Regedt32.exe).
2. Select the following key in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\ODBC
3. On the Security menu, click Permissions.
4. Type the required permissions for the account that is accessing the Web page.
5. Quit Registry Editor.
I don't have the version of Windows that offers a Security menu in Regedit.
Mike
 
J

JIMCO Software

MikeR said:
Thanks Jim -
That link has already been perused. There is a fairly humerious bit
on it. 1. Start Registry Editor (Regedt32.exe).
2. Select the following key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC 3. On the Security menu, click
Permissions.
4. Type the required permissions for the account that is accessing
the Web page. 5. Quit Registry Editor.
I don't have the version of Windows that offers a Security menu in
Regedit. Mike
Click to expand...

If you don't, then you don't have a version of Windows that supports a Web
server. What version of Windows do you have? Realize that if you are on
more recent versions, you would use regedit.exe.

--
Jim Cheshire
JIMCO Software
http://www.jimcosoftware.com

FrontPage add-ins for FrontPage 2000 - 2003
 
M

MikeR

Good idea Bob -
I appreciate all the suggestions and links.

So Bland, with palsied fingers and a thumping heart, slowly turned the dial. 13 left.....
21 right....

Mike
 
S

Steve Easton

Hi Jim.
Regedit.exe has been around since Windows 95.

regedt32 came about with NT / 2K

;-)

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 
Top