|
Home > Archive > FrontPage Server Extensions for Windows > March 2005 > FPSE 2002 Exception / Access Violation
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
FPSE 2002 Exception / Access Violation
|
|
| Colin Bowern 2005-03-11, 5:53 pm |
| Has anyone seen these errors before? They seem to be preventing the
publishing of content (or even accessing remotely) a site.
--
Event Type: Warning
Event Source: FrontPage 5.0
Event Category: None
Event ID: 1000
Date: 3/11/2005
Time: 5:49:48 PM
User: N/A
Computer: WEBSERVER
Description:
Microsoft FrontPage Server Extensions:
(OS Error #-1073741819 Message: exception occurred at 0x32dcc94c)
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
--
Event Type: Warning
Event Source: FrontPage 5.0
Event Category: None
Event ID: 1000
Date: 3/11/2005
Time: 5:49:48 PM
User: N/A
Computer: WEBSERVER
Description:
Microsoft FrontPage Server Extensions:
http://www.mysite.com - Error #80002 Message: System exception: access
violation.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
---
The server is Windows Server 2003. The client is Windows XP SP2, FP 2003.
I really hope that with the next generation of FrontPage (and the server
extensions) that they overhaul the errors. These errors messages are
useless and should have been cleaned up well before the release of Windows
Server 2003!
I've tried reinstalling FPSE while preserving meta-data and there is no
resolve there. I'm reinstalling FPSE on the server as a whole now.
Cheers,
Colin
| |
| Colin Bowern 2005-03-11, 5:53 pm |
| Resolved it using this article:
http://support.microsoft.com/defaul...881&Product=fpw
However I am still cannot publish:
The server "" timed out. The current request did not complete successfully.
I looked at the network HTTP calls and it appears that the return from the
server is being chopped off in the middle of a list_documents RPC call. No
idea why it would get chopped off.
Cheers,
Colin
"Colin Bowern" <colin.bowern@nospam.officialcommunity.com> wrote in message
news:uLNqh2oJFHA.2764@tk2msftngp13.phx.gbl...
> Has anyone seen these errors before? They seem to be preventing the
> publishing of content (or even accessing remotely) a site.
>
> --
> Event Type: Warning
> Event Source: FrontPage 5.0
> Event Category: None
> Event ID: 1000
> Date: 3/11/2005
> Time: 5:49:48 PM
> User: N/A
> Computer: WEBSERVER
> Description:
> Microsoft FrontPage Server Extensions:
> (OS Error #-1073741819 Message: exception occurred at 0x32dcc94c)
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> --
> Event Type: Warning
> Event Source: FrontPage 5.0
> Event Category: None
> Event ID: 1000
> Date: 3/11/2005
> Time: 5:49:48 PM
> User: N/A
> Computer: WEBSERVER
> Description:
> Microsoft FrontPage Server Extensions:
> http://www.mysite.com - Error #80002 Message: System exception: access
> violation.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ---
>
> The server is Windows Server 2003. The client is Windows XP SP2, FP 2003.
> I really hope that with the next generation of FrontPage (and the server
> extensions) that they overhaul the errors. These errors messages are
> useless and should have been cleaned up well before the release of Windows
> Server 2003!
>
> I've tried reinstalling FPSE while preserving meta-data and there is no
> resolve there. I'm reinstalling FPSE on the server as a whole now.
>
> Cheers,
> Colin
>
| |
| Colin Bowern 2005-03-11, 8:51 pm |
| Time out message resolved by removing FPSE on the web including meta data
and re-extending the web and republishing back to the site.
Cheers,
Colin
"Colin Bowern" <colin.bowern@nospam.officialcommunity.com> wrote in message
news:euBiLIpJFHA.3340@TK2MSFTNGP14.phx.gbl...
> Resolved it using this article:
>
> http://support.microsoft.com/defaul...881&Product=fpw
>
> However I am still cannot publish:
>
> The server "" timed out. The current request did not complete
> successfully.
>
> I looked at the network HTTP calls and it appears that the return from the
> server is being chopped off in the middle of a list_documents RPC call.
> No idea why it would get chopped off.
>
> Cheers,
> Colin
>
> "Colin Bowern" <colin.bowern@nospam.officialcommunity.com> wrote in
> message news:uLNqh2oJFHA.2764@tk2msftngp13.phx.gbl...
>
>
|
|
|
|
|