Don't Use IE7 if you Publish With FrontPage

G

Guest

(Next day 9:00am UK)

"IIS based or disk based" You've lost me there. I have six active domains
mainly with one ISP on the same server. They are all created on a disk based
PC (I've probably completely missed the point through not knowing the
acronym). The one that crashed is one of the many one one ISP's server, the
others are with other individual ISPs. I publish them all by the same basic
ftp method.

One site has always started with any pages to publish actually saying the
pages are in conflict (? marks) instead of ticks, but after my confirmation
to overwrite it publishes fine. This is a 'one off' site on a server on its
own, and still worked despite this, so I have no issue with it.

All the others show ticks indicating they need to be published before they
publish fine. The one that failed simply failed after ie7 was installed and
the different wininet.dll's appeared on my PC.

The only obvious difference between the way the sites are written is that
the one that failed uses FP's own hierarchy, shared borders with dynamic
menus.

This means "the publish" has to account for the changes in the FP overlay
files etc which might affect pages you have not actually amended. It started
to remove any files not needed, but failed to publish or continue. However I
could drag and drop single files between the local and remote web site view.

This was 1) not right 2) didn't allow me to know the small overlay or other
files behind the scenes that also needed updating.

Like I say though - after ie7 all works fine, as the wininet.dll versions
have been removed.

I have to go now, as I'm teaching music to local kids now - much less
frustrating eh?
================================
 
R

Rob Giordano \(Crash\)

How do you open your local website?.. via;

C:\my webs\yourwebnamehere (or anything similar to this, with the local
drive letter preceeding the path)
or
http://localhost/yourwebnamehere

The first example is a disc-based web - no server running on local machine
The second example is a server (IIS) based system - IIS server running on
local machine.

It may help us diagnose the problem is we knew exactly what steps you take
to upload or Publish to your remote server.
While you are at it why not post the URL to your website?



| (Next day 9:00am UK)
|
| "IIS based or disk based" You've lost me there. I have six active domains
| mainly with one ISP on the same server. They are all created on a disk
based
| PC (I've probably completely missed the point through not knowing the
| acronym). The one that crashed is one of the many one one ISP's server,
the
| others are with other individual ISPs. I publish them all by the same
basic
| ftp method.
|
| One site has always started with any pages to publish actually saying the
| pages are in conflict (? marks) instead of ticks, but after my
confirmation
| to overwrite it publishes fine. This is a 'one off' site on a server on
its
| own, and still worked despite this, so I have no issue with it.
|
| All the others show ticks indicating they need to be published before they
| publish fine. The one that failed simply failed after ie7 was installed
and
| the different wininet.dll's appeared on my PC.
|
| The only obvious difference between the way the sites are written is that
| the one that failed uses FP's own hierarchy, shared borders with dynamic
| menus.
|
| This means "the publish" has to account for the changes in the FP overlay
| files etc which might affect pages you have not actually amended. It
started
| to remove any files not needed, but failed to publish or continue. However
I
| could drag and drop single files between the local and remote web site
view.
|
| This was 1) not right 2) didn't allow me to know the small overlay or
other
| files behind the scenes that also needed updating.
|
| Like I say though - after ie7 all works fine, as the wininet.dll versions
| have been removed.
|
| I have to go now, as I'm teaching music to local kids now - much less
| frustrating eh?
| ================================
| "Steve Easton" wrote:
|
| > Let me conjure on this a bit.
| > The fact that you get a wininet.dll error with web site "A" and not with
web site "B" makes no sense to me at this
| > moment.
| > ( Might have something to do with a couple of beers, it is Friday night
after all )
| >
| > Are the webs on your machine IIS based or disk based??
| >
| >
| > --
| > Steve Easton
| > Microsoft MVP FrontPage
| > FP Cleaner
| > http://www.95isalive.com/fixes/fpclean.htm
| > Hit Me FP
| > http://www.95isalive.com/fixes/HitMeFP.htm
| >
| >
| > | > > Yes. - this one site was all outlined in the detail days back. No one
picked
| > > up on it like no one picked up on the error codes. I refer to it a few
times
| > > when it doesn't seem too repetitive to do so.
| > >
| > > It is not a pretty site, but it is complex so I rely on the Frontpage
| > > dynamic menus, within shared borders to have any hope of keeping
track.
| > >
| > > I think there are well over 400 pages, and I've been developing it for
over
| > > five years.
| > >
| > > I firmly believe it is a call within wininet.dll that crashes
FrontPage, it
| > > is as if it starts the process of publishing the sequence then falls
over.
| > >
|
 
S

Steve Easton

IIS based means you have IIS installed on your machine which means you work on your webs
as if they were on a server, using an http:// address

Disk based means you work on them in a file based mode using a file based address:
C:\foldername\webname


I asked because I'm trying to sort out what would cause one web to fail and not the others.
Knowing which type narrows down the search.

More later.
--
Steve Easton
Microsoft MVP FrontPage
FP Cleaner
http://www.95isalive.com/fixes/fpclean.htm
Hit Me FP
http://www.95isalive.com/fixes/HitMeFP.htm
 
S

Steve Easton

Ok.
If you're up for a little adventure:
Close FrontPage.

Go here: http://www.95isalive.com/fixes/fpclean.htm and download FP Cleaner ( with Expression Web Designer and
SharePoint Designer support )
Download links are at the bottom of the page.
Run the functions that clear:
The Hidden Temporary files.
The Hidden Cache (*.web) files.

Then run regedit and go to each of the following:
HKEY_CURRENT_USER\Software\Microsoft\FrontPage\Explorer\FrontPage Explorer\Recent File List
HKEY_CURRENT_USER\Software\Microsoft\FrontPage\Explorer\FrontPage Explorer\Recent Page List
HKEY_CURRENT_USER\Software\Microsoft\FrontPage\Explorer\FrontPage Explorer\Recent Publish List
HKEY_CURRENT_USER\Software\Microsoft\FrontPage\Explorer\FrontPage Explorer\Recent Web List
HKEY_CURRENT_USER\Software\Microsoft\FrontPage\Explorer\FrontPage Explorer\Recently Created Servers

and delete all entries in the right hand panel "Except" the one named (Default)

Close Regedit.

Then right click My Network places on your desktop, select Open.
When it opens, right click the entry for the malfunctioning web and Select delete
Close Network places.

Using Windows Explorer browse to C:\WINDOWS\Prefetch
and delete the entire contents of the Prefetch folder.

Reboot.
Before you do anything, install IE7.

After the system reboots after the install, open FrontPage and see if you can access the web that was giving problems




--
Steve Easton
Microsoft MVP FrontPage
FP Cleaner
http://www.95isalive.com/fixes/fpclean.htm
Hit Me FP
http://www.95isalive.com/fixes/HitMeFP.htm
 
D

David Berry

Steve, I saw your comment about deleting the prefetch files. Nice add. Not
many people know about those. have you tried CCleaner
http://www.ccleaner.com/ It not only deletes the prefetch but a lot of other
left over junk as well.
 
S

Steve Easton

Hi David,
I stumbled across some info on Prefetch when I was having trouble installing EW Beta1 after uninstalling the CTP
I normally only delete the prefetch files associated with whatever issue I'm having, but in this case it's best to
simply delete them all.

As for CCleaner, I've heard about it but I've never used it.


--
Steve Easton
Microsoft MVP FrontPage
FP Cleaner
http://www.95isalive.com/fixes/fpclean.htm
Hit Me FP
http://www.95isalive.com/fixes/HitMeFP.htm
 
D

David Berry

I get Maximum PC Magazine and they did a whole section on cleaning up
Windows a while back. That's where I heard about CCleaner, and some other
good tools for cleaning up the junk Windows leaves behind. It solves
problems and keeps things running smooth. My start up time is better too.
 
R

Rob Giordano \(Crash\)

Steve, check this out: http://www.hagstrom.org.uk/_vti_inf.html


| IIS based means you have IIS installed on your machine which means you
work on your webs
| as if they were on a server, using an http:// address
|
| Disk based means you work on them in a file based mode using a file based
address:
| C:\foldername\webname
|
|
| I asked because I'm trying to sort out what would cause one web to fail
and not the others.
| Knowing which type narrows down the search.
|
| More later.
| --
| Steve Easton
| Microsoft MVP FrontPage
| FP Cleaner
| http://www.95isalive.com/fixes/fpclean.htm
| Hit Me FP
| http://www.95isalive.com/fixes/HitMeFP.htm
|
| | > (Next day 9:00am UK)
| >
| > "IIS based or disk based" You've lost me there. I have six active
domains
| > mainly with one ISP on the same server. They are all created on a disk
based
| > PC (I've probably completely missed the point through not knowing the
| > acronym). The one that crashed is one of the many one one ISP's server,
the
| > others are with other individual ISPs. I publish them all by the same
basic
| > ftp method.
| >
| > One site has always started with any pages to publish actually saying
the
| > pages are in conflict (? marks) instead of ticks, but after my
confirmation
| > to overwrite it publishes fine. This is a 'one off' site on a server on
its
| > own, and still worked despite this, so I have no issue with it.
| >
| > All the others show ticks indicating they need to be published before
they
| > publish fine. The one that failed simply failed after ie7 was installed
and
| > the different wininet.dll's appeared on my PC.
| >
| > The only obvious difference between the way the sites are written is
that
| > the one that failed uses FP's own hierarchy, shared borders with dynamic
| > menus.
| >
| > This means "the publish" has to account for the changes in the FP
overlay
| > files etc which might affect pages you have not actually amended. It
started
| > to remove any files not needed, but failed to publish or continue.
However I
| > could drag and drop single files between the local and remote web site
view.
| >
| > This was 1) not right 2) didn't allow me to know the small overlay or
other
| > files behind the scenes that also needed updating.
| >
| > Like I say though - after ie7 all works fine, as the wininet.dll
versions
| > have been removed.
| >
| > I have to go now, as I'm teaching music to local kids now - much less
| > frustrating eh?
| > ================================
| > "Steve Easton" wrote:
| >
| >> Let me conjure on this a bit.
| >> The fact that you get a wininet.dll error with web site "A" and not
with web site "B" makes no sense to me at this
| >> moment.
| >> ( Might have something to do with a couple of beers, it is Friday night
after all )
| >>
| >> Are the webs on your machine IIS based or disk based??
| >>
| >>
| >> --
| >> Steve Easton
| >> Microsoft MVP FrontPage
| >> FP Cleaner
| >> http://www.95isalive.com/fixes/fpclean.htm
| >> Hit Me FP
| >> http://www.95isalive.com/fixes/HitMeFP.htm
| >>
| >>
| >> | >> > Yes. - this one site was all outlined in the detail days back. No
one picked
| >> > up on it like no one picked up on the error codes. I refer to it a
few times
| >> > when it doesn't seem too repetitive to do so.
| >> >
| >> > It is not a pretty site, but it is complex so I rely on the Frontpage
| >> > dynamic menus, within shared borders to have any hope of keeping
track.
| >> >
| >> > I think there are well over 400 pages, and I've been developing it
for over
| >> > five years.
| >> >
| >> > I firmly believe it is a call within wininet.dll that crashes
FrontPage, it
| >> > is as if it starts the process of publishing the sequence then falls
over.
| >> >
| >
|
|
 
G

Guest

OK back again after music and Nitro remote cars day with son...

Well the shoe is on the other foot for sure now as technically I don't have
an issue anymore. However I can see where you are coming from, and like the
sound of what the tool does - and my PC is a four year old Dell, and could do
with some clear out ofter upgrade after upgrade after upgrade...

So, give me a while and I'll do it this evening / tomorrow morning!

Meantime you could view some rock music?
(My son's band)
I'm sorry I have to be so chatty - it's the way I am...
I'll be back!
=========================================================
 
G

Guest

Despite the large glass of Cabernet Sauvignon beside me it is not a
celebration...

Cleared Hidden Temporary Files - (a few hundred)
Cleared the Cache (*.web) files - (16)

Regedit deleted all (except the default) FrontPage related
Recent Files List
Recent Page List
Recent Publish List
Recent Web List
Recently Created Servers - inlc 1 recent server count (REG_DWORD)
The webs do not appear in the Network Places - so nothing to delete there
Deleted entire contents of C:\Windows\Prefetch
Reboot
Install IE7... ... ...
Checked for any updates (No)
Open Frontpage, change two pages locations in order to create a changed
environment.
Publish (Damn... my sign-on details have gone)
Open Cardbox Database retrieve details
Copy and Paste as required
Frontpage signs in to the remote website
Repeat Copy and paste sign-on
Wait........
Confirm pages to delete (moved)
Starts to pubish....
Miscrosoft Office FrontPage has encountered a problem and needs to close.
If you were in the middle of something, the information you were working on
might be lost.
Restart Microsoft Office Frontpage (Unticked as it only opens a blank new
page)
Sent 3347828.cvr Error Report as advised, after opening in TextPad
....and saving as 061111_3347828.cvr elsewhere (Just in case someone can read
the file format)
(You can request to receive by email attachment)

Went to event Viewer and copied the (only copyable section at the base):
In Bytes:
0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 66 00 72 00 6f 00 .f.r.o.
0030: 6e 00 74 00 70 00 67 00 n.t.p.g.
0038: 2e 00 65 00 78 00 65 00 ..e.x.e.
0040: 20 00 31 00 31 00 2e 00 .1.1...
0048: 30 00 2e 00 36 00 35 00 0...6.5.
0050: 35 00 32 00 2e 00 30 00 5.2...0.
0058: 20 00 34 00 32 00 34 00 .4.2.4.
0060: 62 00 37 00 31 00 34 00 b.7.1.4.
0068: 66 00 20 00 69 00 6e 00 f. .i.n.
0070: 20 00 77 00 69 00 6e 00 .w.i.n.
0078: 69 00 6e 00 65 00 74 00 i.n.e.t.
0080: 2e 00 64 00 6c 00 6c 00 ..d.l.l.
0088: 20 00 37 00 2e 00 30 00 .7...0.
0090: 2e 00 35 00 37 00 33 00 ..5.7.3.
0098: 30 00 2e 00 31 00 31 00 0...1.1.
00a0: 20 00 34 00 35 00 34 00 .4.5.4.
00a8: 32 00 38 00 33 00 62 00 2.8.3.b.
00b0: 34 00 20 00 66 00 44 00 4. .f.D.
00b8: 65 00 62 00 75 00 67 00 e.b.u.g.
00c0: 20 00 30 00 20 00 61 00 .0. .a.
00c8: 74 00 20 00 6f 00 66 00 t. .o.f.
00d0: 66 00 73 00 65 00 74 00 f.s.e.t.
00d8: 20 00 30 00 30 00 30 00 .0.0.0.
00e0: 30 00 31 00 61 00 33 00 0.1.a.3.
00e8: 35 00 0d 00 0a 00 5.....

In Words:
0000: 00700041 006c0070 00630069 00740061
0010: 006f0069 0020006e 00610046 006c0069
0020: 00720075 00200065 00660020 006f0072
0030: 0074006e 00670070 0065002e 00650078
0040: 00310020 002e0031 002e0030 00350036
0050: 00320035 0030002e 00340020 00340032
0060: 00370062 00340031 00200066 006e0069
0070: 00770020 006e0069 006e0069 00740065
0080: 0064002e 006c006c 00370020 0030002e
0090: 0035002e 00330037 002e0030 00310031
00a0: 00340020 00340035 00380032 00620033
00b0: 00200034 00440066 00620065 00670075
00c0: 00300020 00610020 00200074 0066006f
00d0: 00730066 00740065 00300020 00300030
00e0: 00310030 00330061 000d0035 000a

Took Screenshots of all popups and extention pages saved as jpg's in case
they are useful too.
(You can request to receive by email attachments)

Still kept my kewl, and wrote this £$%&^*^ing report....

Having previously sorted the problem by removing ie7 (which I liked a lot in
other repects)
I looked and yes all the previusly reported additional wininet.dll files
have miraculously reappeared too...
But all my Frontpage signons have gone (Boo)
(I hope it remembers them again soon after I trawl through to find each one)

They IMHO (not so humble after this actually) the wininet.dll files are the
source of the problem.
I have other webs with the same ISP which do not use the FrontPage dynamic
menus in shared borders that allow such moving around of pages to be
published fine - so far (trepidation returning fast!)

Second glass needed. I need to play guitar loudly for a while
....but it is 12.40am and although my son would join in, my wife would not.
Tomorrow is another day, thanks for your efforts.

Unless the reports mean anything to anyone this time around and have a
simple quick solution...
Goodbye ie7 again? - 'fraid so, I have to don't I?
Even if IE7 is much prettier than Firefox 2 in many ways.

I DO appreciate your efforts, but all I can say is to repeat:
....does MS recognise the ie7 induced wininet.dll fault yet?
....Don't use IE7 if you Publish With FrontPage... because:
Even if it turns out to be something in my website or my PC...
IE6 and FF2 can live with it - and that's what matters surely?

Goodnight Guys. Peace Love and Charity.
Now for that second glass.
 
G

Guest

Thank you Steve - You have been the most helpful guy here - in other threads
too.
All credit to you.
Despite this being my third glass, I don't hold you responsible if I become
an alcoholic either. Microsoft maybe...

Now that we have officially reached an impasse:
Enjoy:
This is an excellent set - even if I say it myself, and I'm just the Sound
engineer/MC.

"Never forget there's more to Life"
=======================================================
 
R

Rob Giordano \(Crash\)

AH...the page was so verbose I didn't see it was an error page...shorry.


| Right, it's a non extended server so trying to open the _vti_inf.html file
displays his custom 404 page.
|
| --
| Steve Easton
| Microsoft MVP FrontPage
| FP Cleaner
| http://www.95isalive.com/fixes/fpclean.htm
| Hit Me FP
| http://www.95isalive.com/fixes/HitMeFP.htm
|
|
| > Steve, check this out: http://www.hagstrom.org.uk/_vti_inf.html
| >
| >
| > | > | IIS based means you have IIS installed on your machine which means you
| > work on your webs
| > | as if they were on a server, using an http:// address
| > |
| > | Disk based means you work on them in a file based mode using a file
based
| > address:
| > | C:\foldername\webname
| > |
| > |
| > | I asked because I'm trying to sort out what would cause one web to
fail
| > and not the others.
| > | Knowing which type narrows down the search.
| > |
| > | More later.
| > | --
| > | Steve Easton
| > | Microsoft MVP FrontPage
| > | FP Cleaner
| > | http://www.95isalive.com/fixes/fpclean.htm
| > | Hit Me FP
| > | http://www.95isalive.com/fixes/HitMeFP.htm
| > |
| > | | > | > (Next day 9:00am UK)
| > | >
| > | > "IIS based or disk based" You've lost me there. I have six active
| > domains
| > | > mainly with one ISP on the same server. They are all created on a
disk
| > based
| > | > PC (I've probably completely missed the point through not knowing
the
| > | > acronym). The one that crashed is one of the many one one ISP's
server,
| > the
| > | > others are with other individual ISPs. I publish them all by the
same
| > basic
| > | > ftp method.
| > | >
| > | > One site has always started with any pages to publish actually
saying
| > the
| > | > pages are in conflict (? marks) instead of ticks, but after my
| > confirmation
| > | > to overwrite it publishes fine. This is a 'one off' site on a server
on
| > its
| > | > own, and still worked despite this, so I have no issue with it.
| > | >
| > | > All the others show ticks indicating they need to be published
before
| > they
| > | > publish fine. The one that failed simply failed after ie7 was
installed
| > and
| > | > the different wininet.dll's appeared on my PC.
| > | >
| > | > The only obvious difference between the way the sites are written is
| > that
| > | > the one that failed uses FP's own hierarchy, shared borders with
dynamic
| > | > menus.
| > | >
| > | > This means "the publish" has to account for the changes in the FP
| > overlay
| > | > files etc which might affect pages you have not actually amended. It
| > started
| > | > to remove any files not needed, but failed to publish or continue.
| > However I
| > | > could drag and drop single files between the local and remote web
site
| > view.
| > | >
| > | > This was 1) not right 2) didn't allow me to know the small overlay
or
| > other
| > | > files behind the scenes that also needed updating.
| > | >
| > | > Like I say though - after ie7 all works fine, as the wininet.dll
| > versions
| > | > have been removed.
| > | >
| > | > I have to go now, as I'm teaching music to local kids now - much
less
| > | > frustrating eh?
| > | > ================================
| > | > "Steve Easton" wrote:
| > | >
| > | >> Let me conjure on this a bit.
| > | >> The fact that you get a wininet.dll error with web site "A" and not
| > with web site "B" makes no sense to me at this
| > | >> moment.
| > | >> ( Might have something to do with a couple of beers, it is Friday
night
| > after all )
| > | >>
| > | >> Are the webs on your machine IIS based or disk based??
| > | >>
| > | >>
| > | >> --
| > | >> Steve Easton
| > | >> Microsoft MVP FrontPage
| > | >> FP Cleaner
| > | >> http://www.95isalive.com/fixes/fpclean.htm
| > | >> Hit Me FP
| > | >> http://www.95isalive.com/fixes/HitMeFP.htm
| > | >>
| > | >>
message
| > | >> | > | >> > Yes. - this one site was all outlined in the detail days back.
No
| > one picked
| > | >> > up on it like no one picked up on the error codes. I refer to it
a
| > few times
| > | >> > when it doesn't seem too repetitive to do so.
| > | >> >
| > | >> > It is not a pretty site, but it is complex so I rely on the
Frontpage
| > | >> > dynamic menus, within shared borders to have any hope of keeping
| > track.
| > | >> >
| > | >> > I think there are well over 400 pages, and I've been developing
it
| > for over
| > | >> > five years.
| > | >> >
| > | >> > I firmly believe it is a call within wininet.dll that crashes
| > FrontPage, it
| > | >> > is as if it starts the process of publishing the sequence then
falls
| > over.
| > | >> >
| > | >
| > |
| > |
| >
| >
|
|
 
W

Windsun

http://support.microsoft.com/default.aspx/kb/160158

There is also a spyware issue http://www.adwareaway.com/psguard.htm

However, IE7 supposedly fixed most wininet.dll issues, but according to a
couple of blogs, there may be old or corrupted files on computers that cause
inet.dll to crash when it tries to reference them. The conclusion was that
wininet.dll is not the problem but the the files it is calling.

-------------------------------------------------------------------------
 

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

Similar Threads

FrontPage fault wininet.dll 7.0.5730.11 1
FrontPage ftp stopped working since IE7 12
IE7 error when using ftp with Frontpage - CAN'T RESTORE EITHER 5
IE7 with FrontPage? 2
FrontPage & Publisher Errors 12
Can I use sharepoint team services with frontpage 2003? 7
Vista, with sloooooow IE7 Favorites and web pages when Protected Mode enabled 4
I don't think you need anti-virus with Vista 61

Top