[mapguide-users] Cannot Establish Connection

[Dave Wilson]

To be frank no. It's more likely something such as a filter or styling or something in the data that causes the provider some serious grief. The trick is to figure out which layer is the likely culprit.

Another possibility is that some custom API coding is doing something incorrect or hitting some yet unidentified bug.

Check the following and see if this can help alleviate some of the grief:

http://support.microsoft.com/kb/911816

Dave

-----Original Message-----
From: mapguide-users-bounces at lists.osgeo.org [mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Mark Pendergraft
Sent: Thursday, June 12, 2008 1:26 PM
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] Cannot Establish Connection

I have been pouring through the Application and Error logs, and the one
Error I consistently get is "Please try your operation later as the
resource was busy"

This is a flaw in MGOS 2.0 which ties up the resource after using the
SetSelectionXML command.

Do you think that this error might be tied to the service constantly
stopping?

-----Original Message-----
From: mapguide-users-bounces at lists.osgeo.org
[mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of nclayton
Sent: Thursday, June 12, 2008 11:39 AM
To: mapguide-users at lists.osgeo.org
Subject: Re: [mapguide-users] Cannot Establish Connection


I've been dealing with this since MGOS 1.2 and continue to have the
problem
in 2.0.1

In the Application Error log, i'm getting:
========================================================================
=======
Faulting application mgserver.exe, version 2.0.0.2716, faulting module
msvcr80.dll, version 8.0.50727.1433, fault address 0x00008aa0.

AND

Faulting application w3wp.exe, version 6.0.3790.3959, faulting module
kernel32.dll, version 5.2.3790.4062, fault address 0x0000bee7.
========================================================================
=======

Then the System Error log has:
========================================================================
=======
The MapGuide Server v2.0 service terminated unexpectedly. It has done
this
XX time(s).

AND

A process serving application pool 'MGOS' suffered a fatal communication
error wit the World Wide Web Publishing Service. The process id was
'XXXX'.
The data field contains the error number.

That error number is: 8007006d
========================================================================
=======

A lot of the stability issues were corrected in 2.0.1 but I'm getting
more
crashes now than with 2.0...I've had to change my mgos restart script
from
running every 4 hours to every 1 hour and may have to reduce it
further...





Mark Pendergraft wrote:
>
> Ever since moving to MGOS 2.0 my map keeps crashing and giving users a
> "Cannot Establish Connection" error.  It appears the service is
actually
> stopping on the machine hosting the map, and I have to go in and
restart
> it.  It happens about every other day, and sometimes several times a
> day.
>
>
>
> The server running MGOS is using Windows Server 2000 sp4 and IIS 8.0
>
>
>
> Any ideas on why this is happening?  It's really starting to get
> annoying, and if I can't find a fix then I will have to downgrade to
> 1.2.
>
> Thanks.
>
> -Mark P.
>
>
> _______________________________________________
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-users
>
>

--
View this message in context:
http://www.nabble.com/Cannot-Establish-Connection-tp17803969p17806925.ht
ml
Sent from the MapGuide Users mailing list archive at Nabble.com.

_______________________________________________
mapguide-users mailing list
mapguide-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
_______________________________________________
mapguide-users mailing list
mapguide-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users