MVP's, Did Microsoft Updates break my Frontpage?

[Down Home]

July 3, I installed the following MS update on my XP Home machine:
Critical Update for ADODB.stream (KB870669)

Yesterday, I installed the following MS updates:
Security Update for Windows XP (KB841873)
Security Update for Windows XP (KB840315)
Update for Background Intelligent Transfer Service (BITS) 2.0 and WinHTTP
5.1 (KB842773)
Cumulative Security Update for Outlook Express 6 SP1 (KB823353)

Today, I open FP 2000 (version 4.0.2.6625), try logging onto my website
[similar to www.abcxyz.com] to do some updating and as soon as I enter my
password and hit OK, my CPU usage jumps to 100% and FP hangs (I can close it
by right clicking taskbar icon).HOWEVER! If I log in with my IP address [as
123.456.789.012], FP works fine?!? ALSO, I have a subset of folders in the
same domain set up as a "subweb" with a seperate login that also works fine
(even using the www.abcxyz.com/subweb style login).

Both my OS (XP Home) and Office2000 have latest sevice packs and updates.

Web hosting is by SBC (NOT SBC Yahoo)
Webhost Server Version as of 7/15/2004:
Rapidsite/APA/1.3.29 (Unix) FrontPage/5.0.2.2510 mod_ssl/2.8.16
OpenSSL/0.9.7c

FrontPage Server Extension version 5.0.2.2623

Are the MS Updates a sheer coincidence, or could they be the culprit? I
originally considered it was a corruption of the FrontPage extensions, but
since the site opens fine using the IP login, and I can make changes, it
eliminates that possibility. The domain is listed as "Trusted" site in the
Internet settings and is not in the HOSTS file.

Thanks in advance.

 

[Down Home]

New piece of info:

Just tried and was successful at logging in by dropping the "www" prefix.
Very bewildering! Did one the MS updates ban the use of "www"?

 

[Kevin Spencer]

Not sure what cxaused your problem. However, there are some changes that
will affect web development in the new XP Service Pack 2, none of which I
know of causing any change in functionality in FrontPage (not meaning that
there aren't any that are not known). Anyway, you can read about it at:

http://msdn.microsoft.com/security/productinfo/XPSP2/default.aspx

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

New piece of info:

Just tried and was successful at logging in by dropping the "www" prefix.
Very bewildering! Did one the MS updates ban the use of "www"?

July 3, I installed the following MS update on my XP Home machine:
Critical Update for ADODB.stream (KB870669)

Yesterday, I installed the following MS updates:
Security Update for Windows XP (KB841873)
Security Update for Windows XP (KB840315)
Update for Background Intelligent Transfer Service (BITS) 2.0 and WinHTTP
5.1 (KB842773)
Cumulative Security Update for Outlook Express 6 SP1 (KB823353)

Today, I open FP 2000 (version 4.0.2.6625), try logging onto my website
[similar to www.abcxyz.com] to do some updating and as soon as I enter my
password and hit OK, my CPU usage jumps to 100% and FP hangs (I can

close

it
by right clicking taskbar icon).HOWEVER! If I log in with my IP address [as
123.456.789.012], FP works fine?!? ALSO, I have a subset of folders in the
same domain set up as a "subweb" with a seperate login that also works fine
(even using the www.abcxyz.com/subweb style login).

Both my OS (XP Home) and Office2000 have latest sevice packs and updates.

Web hosting is by SBC (NOT SBC Yahoo)
Webhost Server Version as of 7/15/2004:
Rapidsite/APA/1.3.29 (Unix) FrontPage/5.0.2.2510 mod_ssl/2.8.16
OpenSSL/0.9.7c

FrontPage Server Extension version 5.0.2.2623

Are the MS Updates a sheer coincidence, or could they be the culprit? I
originally considered it was a corruption of the FrontPage extensions, but
since the site opens fine using the IP login, and I can make changes, it
eliminates that possibility. The domain is listed as "Trusted" site in the
Internet settings and is not in the HOSTS file.

Thanks in advance.

 

[Down Home]

Thanks Kevin,

I reviewed the link and associated references. Nothing "stands out" as a
possible culprit, but it could be ages before we find all the little nuances
caused by XP-SP2. The good news is that I have not lost capability, only
familiarity (I now have to drop the "www"). Thanks for your time. At least
now we know that if someone has trouble with FP logging in and hanging, try
the IP or drop the "www".

Down Home

Not sure what cxaused your problem. However, there are some changes that
will affect web development in the new XP Service Pack 2, none of which I
know of causing any change in functionality in FrontPage (not meaning that
there aren't any that are not known). Anyway, you can read about it at:

http://msdn.microsoft.com/security/productinfo/XPSP2/default.aspx

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

New piece of info:

Just tried and was successful at logging in by dropping the "www" prefix.
Very bewildering! Did one the MS updates ban the use of "www"?

July 3, I installed the following MS update on my XP Home machine:
Critical Update for ADODB.stream (KB870669)

Yesterday, I installed the following MS updates:
Security Update for Windows XP (KB841873)
Security Update for Windows XP (KB840315)
Update for Background Intelligent Transfer Service (BITS) 2.0 and WinHTTP
5.1 (KB842773)
Cumulative Security Update for Outlook Express 6 SP1 (KB823353)

Today, I open FP 2000 (version 4.0.2.6625), try logging onto my website
[similar to www.abcxyz.com] to do some updating and as soon as I enter my
password and hit OK, my CPU usage jumps to 100% and FP hangs (I can

close

it
by right clicking taskbar icon).HOWEVER! If I log in with my IP

address
[as

123.456.789.012], FP works fine?!? ALSO, I have a subset of folders in the
same domain set up as a "subweb" with a seperate login that also works fine
(even using the www.abcxyz.com/subweb style login).

Both my OS (XP Home) and Office2000 have latest sevice packs and updates.

Web hosting is by SBC (NOT SBC Yahoo)
Webhost Server Version as of 7/15/2004:
Rapidsite/APA/1.3.29 (Unix) FrontPage/5.0.2.2510 mod_ssl/2.8.16
OpenSSL/0.9.7c

FrontPage Server Extension version 5.0.2.2623

Are the MS Updates a sheer coincidence, or could they be the culprit? I
originally considered it was a corruption of the FrontPage extensions, but
since the site opens fine using the IP login, and I can make changes, it
eliminates that possibility. The domain is listed as "Trusted" site in the
Internet settings and is not in the HOSTS file.

Thanks in advance.

 

[Kevin Spencer]

Could be a DNS (Domain Name Server) issue. Have you tried to ping the "www"
domain name?

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

Thanks Kevin,

I reviewed the link and associated references. Nothing "stands out" as a
possible culprit, but it could be ages before we find all the little nuances
caused by XP-SP2. The good news is that I have not lost capability, only
familiarity (I now have to drop the "www"). Thanks for your time. At least
now we know that if someone has trouble with FP logging in and hanging, try
the IP or drop the "www".

Down Home

Not sure what cxaused your problem. However, there are some changes that
will affect web development in the new XP Service Pack 2, none of which I
know of causing any change in functionality in FrontPage (not meaning that
there aren't any that are not known). Anyway, you can read about it at:

http://msdn.microsoft.com/security/productinfo/XPSP2/default.aspx

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

New piece of info:

Just tried and was successful at logging in by dropping the "www" prefix.
Very bewildering! Did one the MS updates ban the use of "www"?


July 3, I installed the following MS update on my XP Home machine:
Critical Update for ADODB.stream (KB870669)

Yesterday, I installed the following MS updates:
Security Update for Windows XP (KB841873)
Security Update for Windows XP (KB840315)
Update for Background Intelligent Transfer Service (BITS) 2.0 and WinHTTP
5.1 (KB842773)
Cumulative Security Update for Outlook Express 6 SP1 (KB823353)

Today, I open FP 2000 (version 4.0.2.6625), try logging onto my website
[similar to www.abcxyz.com] to do some updating and as soon as I

enter
my

password and hit OK, my CPU usage jumps to 100% and FP hangs (I can close
it
by right clicking taskbar icon).HOWEVER! If I log in with my IP address
[as
123.456.789.012], FP works fine?!? ALSO, I have a subset of folders

in
the

same domain set up as a "subweb" with a seperate login that also works
fine
(even using the www.abcxyz.com/subweb style login).

Both my OS (XP Home) and Office2000 have latest sevice packs and updates.

Web hosting is by SBC (NOT SBC Yahoo)
Webhost Server Version as of 7/15/2004:
Rapidsite/APA/1.3.29 (Unix) FrontPage/5.0.2.2510 mod_ssl/2.8.16
OpenSSL/0.9.7c

FrontPage Server Extension version 5.0.2.2623

Are the MS Updates a sheer coincidence, or could they be the

culprit?

I extensions,
but

changes,

it in
the

 

[Down Home]

Pings fine and comes accross in IE fine (even after clearing cache).

Down Home

Could be a DNS (Domain Name Server) issue. Have you tried to ping the "www"
domain name?

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

Thanks Kevin,

I reviewed the link and associated references. Nothing "stands out" as a
possible culprit, but it could be ages before we find all the little nuances
caused by XP-SP2. The good news is that I have not lost capability, only
familiarity (I now have to drop the "www"). Thanks for your time. At least
now we know that if someone has trouble with FP logging in and hanging, try
the IP or drop the "www".

Down Home

which

I

know of causing any change in functionality in FrontPage (not meaning that
there aren't any that are not known). Anyway, you can read about it at:

http://msdn.microsoft.com/security/productinfo/XPSP2/default.aspx

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

New piece of info:

Just tried and was successful at logging in by dropping the "www" prefix.
Very bewildering! Did one the MS updates ban the use of "www"?


July 3, I installed the following MS update on my XP Home machine:
Critical Update for ADODB.stream (KB870669)

Yesterday, I installed the following MS updates:
Security Update for Windows XP (KB841873)
Security Update for Windows XP (KB840315)
Update for Background Intelligent Transfer Service (BITS) 2.0 and
WinHTTP
5.1 (KB842773)
Cumulative Security Update for Outlook Express 6 SP1 (KB823353)

Today, I open FP 2000 (version 4.0.2.6625), try logging onto my website
[similar to www.abcxyz.com] to do some updating and as soon as I enter
my
password and hit OK, my CPU usage jumps to 100% and FP hangs (I can
close
it
by right clicking taskbar icon).HOWEVER! If I log in with my IP address
[as
123.456.789.012], FP works fine?!? ALSO, I have a subset of

folders

in culprit? changes,

site

in

 

[Jim Cheshire]

New piece of info:

Just tried and was successful at logging in by dropping the "www"
prefix. Very bewildering! Did one the MS updates ban the use of "www"?

July 3, I installed the following MS update on my XP Home machine:
Critical Update for ADODB.stream (KB870669)

Yesterday, I installed the following MS updates:
Security Update for Windows XP (KB841873)
Security Update for Windows XP (KB840315)
Update for Background Intelligent Transfer Service (BITS) 2.0 and
WinHTTP
5.1 (KB842773)
Cumulative Security Update for Outlook Express 6 SP1 (KB823353)

Today, I open FP 2000 (version 4.0.2.6625), try logging onto my
website [similar to www.abcxyz.com] to do some updating and as soon
as I enter my password and hit OK, my CPU usage jumps to 100% and FP
hangs (I can close it by right clicking taskbar icon).HOWEVER! If I
log in with my IP address [as 123.456.789.012], FP works fine?!?

I suspect that this has nothing to do with these patches or the network. I
suspect that you are dealing with a corrupt meta cache file. That would
explain why it works when you use a different naming convention or IP, but
fails when you use www.site.com.

Go to C:\Documents and Settings\<you>\Application Data\Microsoft\Web Server
Extensions\Cache and delete all the files there. Now try it again.

--
Jim Cheshire
Jimco
http://www.jimcoaddins.com
================================
Author of Special Edition
Using Microsoft Office FrontPage 2003
5 Stars on Amazon and B&N
================================
The opinions expressed by me in the
newsgroups are my own opinions and
are in no way associated with my
employer or any other party. Jimco is
not associated in any way with any other
entity.

 

[Down Home]

I am now replacing John 'Bluto' Blutarsky with Jim Cheshire as as my new
idol. I had no idea that FrontPage even had a cache! I thought it might be a
security concern to even have one. Jim's idea did it! (Though I only only
deleted the address at issue). I can now log on. No idea how it could have
become corrupt unless the MS Updates changed the security requirements as to
how it is read/interpreted.

Thank you! Thank you! Thank you!

New piece of info:

Just tried and was successful at logging in by dropping the "www"
prefix. Very bewildering! Did one the MS updates ban the use of "www"?

July 3, I installed the following MS update on my XP Home machine:
Critical Update for ADODB.stream (KB870669)

Yesterday, I installed the following MS updates:
Security Update for Windows XP (KB841873)
Security Update for Windows XP (KB840315)
Update for Background Intelligent Transfer Service (BITS) 2.0 and
WinHTTP
5.1 (KB842773)
Cumulative Security Update for Outlook Express 6 SP1 (KB823353)

Today, I open FP 2000 (version 4.0.2.6625), try logging onto my
website [similar to www.abcxyz.com] to do some updating and as soon
as I enter my password and hit OK, my CPU usage jumps to 100% and FP
hangs (I can close it by right clicking taskbar icon).HOWEVER! If I
log in with my IP address [as 123.456.789.012], FP works fine?!?

I suspect that this has nothing to do with these patches or the network. I
suspect that you are dealing with a corrupt meta cache file. That would
explain why it works when you use a different naming convention or IP, but
fails when you use www.site.com.

Go to C:\Documents and Settings\<you>\Application Data\Microsoft\Web Server
Extensions\Cache and delete all the files there. Now try it again.

--
Jim Cheshire
Jimco
http://www.jimcoaddins.com
================================
Author of Special Edition
Using Microsoft Office FrontPage 2003
5 Stars on Amazon and B&N
================================
The opinions expressed by me in the
newsgroups are my own opinions and
are in no way associated with my
employer or any other party. Jimco is
not associated in any way with any other
entity.

 

[Jim Cheshire]

I am now replacing John 'Bluto' Blutarsky with Jim Cheshire as as my
new idol. I had no idea that FrontPage even had a cache! I thought it
might be a security concern to even have one. Jim's idea did it!
(Though I only only deleted the address at issue). I can now log on.
No idea how it could have become corrupt unless the MS Updates
changed the security requirements as to how it is read/interpreted.

Thank you! Thank you! Thank you!

Good to hear. Thanks for the update.

--
Jim Cheshire
Jimco
http://www.jimcoaddins.com
================================
Author of Special Edition
Using Microsoft Office FrontPage 2003
5 Stars on Amazon and B&N
================================
The opinions expressed by me in the
newsgroups are my own opinions and
are in no way associated with my
employer or any other party. Jimco is
not associated in any way with any other
entity.