| Author |
Can't connect to my long standing site with Frontpage 2003
|
|
| NWViewer 2006-01-06, 2:57 am |
| I have had this site fro several years and always worked on it with FP. But
now I am getting the message servor error:error 2 opening registry key
"Software\Microsoft\Shared Tools\Web Server Extensions\Ports\Port 80
with this one site. I can connect to other sites that I support.
I can neither open the site or publish to it.
Thanks
--
Diane
| |
| Thomas A. Rowe 2006-01-06, 7:55 am |
| Contact your web host and ask them to run a Server Health Check.
--
========================================
======
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.
========================================
======
"NWViewer" <NWViewer@discussions.microsoft.com> wrote in message
news:C8A6F577-93E0-49F4-BE81-6B16EC5B581D@microsoft.com...
>I have had this site fro several years and always worked on it with FP. But
> now I am getting the message servor error:error 2 opening registry key
> "Software\Microsoft\Shared Tools\Web Server Extensions\Ports\Port 80
>
> with this one site. I can connect to other sites that I support.
>
> I can neither open the site or publish to it.
>
> Thanks
> --
> Diane
| |
| NWViewer 2006-01-06, 5:54 pm |
| Thanks Thomas. I have requested that.
--
Diane
"Thomas A. Rowe" wrote:
> Contact your web host and ask them to run a Server Health Check.
>
> --
> ========================================
======
> 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.
> ========================================
======
>
> "NWViewer" <NWViewer@discussions.microsoft.com> wrote in message
> news:C8A6F577-93E0-49F4-BE81-6B16EC5B581D@microsoft.com...
>
>
>
|
|
|
|