FP 2003 "Server error: client closed connection"

D

David Kirk

After attempting to open an mdb file on my live site using FP2003, I get the
error "Server error: client closed connection" a short while after I start to
publish from the live site to my hard drive. I've read another thread here
that suggests to me that the mdb file, which apparently can no longer be
opened directly in FP2003, must be corrupt or locked or something to that
effect. That thread suggested asking my host to delete the file frontpg.lck.
Yet I have info on other non MS FP sites that have complete references to
the entire erorr message above, that I should recalculate hyperlinks (did it;
same problem) and turn off my Norton file wall (did it; same problem). Since
I don't really understand what the frontpg.lck file is or does and since the
database contains all the data in my site's forums (membership, message
strings, newsletter subscription database, etc., etc. I don't want to fool
around with solutions I don't fully understand. Help??
 
T

Thomas A. Rowe

You have to export the database to your desktop from within FP or use a FTP application to download
it, you can not open it directly on line any longer from any version of FP.

The frontpg.lck control your access to the site via FP, and if the file become corrupt, then you
have to ask you host to delete it, then they need to run check on the extensions and maybe
recalculate hyperlinks.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
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.
==============================================
 
J

Jim Buyens

David Kirk said:
After attempting to open an mdb file on my live site using FP2003, I get the
error "Server error: client closed connection" a short while after I start to
publish from the live site to my hard drive.

Please explain exactly what you mean by this. For example, are you opening
your local site in FrontPage, then switching to Remote Site View, then
right-clicking the .mdb file on the Remote site and publishing it to the
local site?

Or are you publishing the whole remote site to local?

Or are you trying to retrieve the file bb FTP?

Or are you trhing to open the .mdb file by specifying an http:// address in
Access?

Or something else?
I've read another thread here
that suggests to me that the mdb file, which apparently can no longer be
opened directly in FP2003, must be corrupt or locked or something to that
effect. That thread suggested asking my host to delete the file frontpg.lck.

frontpg.lck has nothing to do with .mdb files.

Basically, the server extensions on the target site create a frontpg.lck
file whenever you start a Publish operation. They delete it when the Publish
ends. The presence of the frontpg.lck keeps anyone else from publishing to
the same site at the same time.

Occasionally, a Publish operation may fail part way through and not delete
the frontpg.lck file. In that case, you may not be able to publish until a
server admin deletes the frontpg.lck file manually.
Yet I have info on other non MS FP sites that have complete references to
the entire erorr message above, that I should recalculate hyperlinks (did it;
same problem) and turn off my Norton file wall (did it; same problem). Since
I don't really understand what the frontpg.lck file is or does and since the
database contains all the data in my site's forums (membership, message
strings, newsletter subscription database, etc., etc. I don't want to fool
around with solutions I don't fully understand. Help??

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
*-----------------------------­-----------------------
|\----------------------------­-----------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||----------------------------­-----------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/----------------------------­-----------------------
*-----------------------------­-----------------------
 
D

David Kirk

Well, guys, as my dad always said, "The Thot plickens!"

First to answer your questions:

YOU ASKED: Please explain exactly what you mean by this. For example, are
you opening your local site in FrontPage, then switching to Remote Site View,
then
right-clicking the .mdb file on the Remote site and publishing it to the
local site?

Not exactly. About two weeks ago, I swear I opened the site's database from
within FP, from the live site, even though the threads I've read here say
that's impossible. In any event, what I am doing is opening my live site in
FP and selecting "Publish Site" to my local server. It goes through all of
the dialogues about conflicting files and so forth then begins to publish.
It appears to get hung up at the .mdb file and in a minute or two, I get the
"Server Error: Client Closed Connection."

Or are you publishing the whole remote site to local?
YES

Or are you trying to retrieve the file bb FTP?
NO

Or are you trhing to open the .mdb file by specifying an http:// address in
Access?
NO

But here's where it gets curious: in frustration, I went to another computer
on our home network, fired up FP and published the live site to my hard drive
with no problems whatsoever. This suggests to me that something is going on
with the machine from which I was originally trying to publish the site. But
I am thoroughly flummoxed as to what it might be. I sure don't want to have
to go to the other computer everytime I want to publish the site for backup
purposes.

Any ideas?--
David Kirk
 
J

Jim Buyens

Try the procedure at:

FrontPage Publish Command Fails
http://www.interlacken.com/winnt/tips/tipshow.aspx?tip=24

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
*-----------------------------­-----------------------
|\----------------------------­-----------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||----------------------------­-----------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/----------------------------­-----------------------
*-----------------------------­-----------------------
 
D

David Kirk

Didn't work. I did the first 11 steps first. Then I changed the publication
settings. It went a bit further this time but got the same error a little
later down the line. Does it make sense to continue with steps 14+ if this
didn't work? Especially since it seems to be specific to this computer and
not another one on our network?
 
J

Jim Buyens

That's up to you; no procedure solves 100% of all problems. However, if
another computer can publish to the remote site and yours can't, the problem
would seem to be on your computer.

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
*-----------------------------­-----------------------
|\----------------------------­-----------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||----------------------------­-----------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/----------------------------­-----------------------
*-----------------------------­-----------------------
 
S

Stefan B Rusynko

Make sure if you are running Norton IS you turn it off before publishing
- I have seen NIS consider the .mdb as an attack and cause FP to generate that error

PS

The posters didn't say it was impossible to open the .mdb from a live site in FP,
- they said don't do it because it can corrupt the site/mdb or lock up your site
(especially if anyone is using it at same time)
- always safest to export/import and preferably stop the site before importing

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
_____________________________________________


| Well, guys, as my dad always said, "The Thot plickens!"
|
| First to answer your questions:
|
| YOU ASKED: Please explain exactly what you mean by this. For example, are
| you opening your local site in FrontPage, then switching to Remote Site View,
| then
| right-clicking the .mdb file on the Remote site and publishing it to the
| local site?
|
| Not exactly. About two weeks ago, I swear I opened the site's database from
| within FP, from the live site, even though the threads I've read here say
| that's impossible. In any event, what I am doing is opening my live site in
| FP and selecting "Publish Site" to my local server. It goes through all of
| the dialogues about conflicting files and so forth then begins to publish.
| It appears to get hung up at the .mdb file and in a minute or two, I get the
| "Server Error: Client Closed Connection."
|
| Or are you publishing the whole remote site to local?
| YES
|
| Or are you trying to retrieve the file bb FTP?
| NO
|
| Or are you trhing to open the .mdb file by specifying an http:// address in
| Access?
| NO
|
| But here's where it gets curious: in frustration, I went to another computer
| on our home network, fired up FP and published the live site to my hard drive
| with no problems whatsoever. This suggests to me that something is going on
| with the machine from which I was originally trying to publish the site. But
| I am thoroughly flummoxed as to what it might be. I sure don't want to have
| to go to the other computer everytime I want to publish the site for backup
| purposes.
|
| Any ideas?--
| David Kirk
|
|
| "Jim Buyens" wrote:
|
| >
| >
| > "David Kirk" wrote:
| >
| > > After attempting to open an mdb file on my live site using FP2003, I get the
| > > error "Server error: client closed connection" a short while after I start to
| > > publish from the live site to my hard drive.
| >
| > Please explain exactly what you mean by this. For example, are you opening
| > your local site in FrontPage, then switching to Remote Site View, then
| > right-clicking the .mdb file on the Remote site and publishing it to the
| > local site?
| >
| > Or are you publishing the whole remote site to local?
| >
| > Or are you trying to retrieve the file bb FTP?
| >
| > Or are you trhing to open the .mdb file by specifying an http:// address in
| > Access?
| >
| > Or something else?
| >
| > > I've read another thread here
| > > that suggests to me that the mdb file, which apparently can no longer be
| > > opened directly in FP2003, must be corrupt or locked or something to that
| > > effect. That thread suggested asking my host to delete the file frontpg.lck.
| >
| > frontpg.lck has nothing to do with .mdb files.
| >
| > Basically, the server extensions on the target site create a frontpg.lck
| > file whenever you start a Publish operation. They delete it when the Publish
| > ends. The presence of the frontpg.lck keeps anyone else from publishing to
| > the same site at the same time.
| >
| > Occasionally, a Publish operation may fail part way through and not delete
| > the frontpg.lck file. In that case, you may not be able to publish until a
| > server admin deletes the frontpg.lck file manually.
| >
| > > Yet I have info on other non MS FP sites that have complete references to
| > > the entire erorr message above, that I should recalculate hyperlinks (did it;
| > > same problem) and turn off my Norton file wall (did it; same problem). Since
| > > I don't really understand what the frontpg.lck file is or does and since the
| > > database contains all the data in my site's forums (membership, message
| > > strings, newsletter subscription database, etc., etc. I don't want to fool
| > > around with solutions I don't fully understand. Help??
| > > --
| > > David Kirk
| >
| > Jim Buyens
| > Microsoft MVP
| > http://www.interlacken.com
| > Author of:
| > *-----------------------------­-----------------------
| > |\----------------------------­-----------------------
| > || Microsoft Windows SharePoint Services Inside Out
| > || Microsoft Office FrontPage 2003 Inside Out
| > ||----------------------------­-----------------------
| > || Web Database Development Step by Step .NET Edition
| > || Microsoft FrontPage Version 2002 Inside Out
| > || Faster Smarter Beginning Programming
| > || (All from Microsoft Press)
| > |/----------------------------­-----------------------
| > *-----------------------------­-----------------------
| >
 
M

MikeR

David -
I can't solve your problem, but I have opened an access db in access on the remote host
TONS of times, made changes, closed access, and all was fine. So you're not hallucinating
about that. Maybe it creates a temporary copy, but the end result is I get an updated DB.
MikeR
 
T

Thomas A. Rowe

Have you tried it with Windows XP SP2?

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
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.
==============================================
 
M

MikeR

Hi Thomas -
My box is Win XP SP2. My Access is 2000 and FP is 2002. I have no idea what the server is.
MikeR
 
T

Thomas A. Rowe

Mike,

What was the complete issue?

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
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

Kathleen Anderson [MVP - FrontPage]

I was able to do this today on Windows XP SP-2 running FP2002 - I opened a
remote web site running on Windows Server 2003 and was able to open the
database in the web in Access, make a change to it (renaming a field), and
close the database. I think this security feature was introduced with
FrontPage 2003.


--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
 
T

Thomas A. Rowe

Be careful, since the database is open via the temp file, and after you have saved and closed
Access, the database will then be rewritten back to the server and hopefully not overwrite any site
additions and is saved correctly.

If the database doesn't get written back correctly (I think this will occur if the database is open
for writing within the site), the database will become corrupted and will be no longer useable, so
make sure you have a recent backup of the database before doing this.


--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
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.
==============================================
 
M

MikeR

The OP said he's heard you couldn't open an Access DB on a remote server with Access, but
thought he remembered doing it.
MikeR
 
T

Thomas A. Rowe

Ok, it appears that MS has change the security setting in a recent update or it could be that I have
the site I was tested in my Trusted Zones, which now allow you to open a database on line in Access.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
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.
==============================================
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top