Opened 13 years ago

Closed 13 years ago

#1881 closed defect (fixed)

Maestro failes to run a profile on MapServer 2012

Reported by: hm Owned by: jng
Priority: low Milestone:
Component: Maestro Version:
Severity: trivial Keywords: Maestro 4 RC1
Cc: External ID:

Description

I have setup a simple ODBC FeatureSource that connects to a an MS SQL Server table with about 100 rows with coordinates. I've added a single layer to a map. Using Maestro 4 RC1 (9298) running the Profile on the map, it fails. Server: Autodesk Infrastructure MapServer 2012 build 2.3.4202. Output:

Profiling MapDefinition: Session:8b26a014-2005-11e1-8000-080027cb642a_en_7F0000010B060B050B04//17ec8685-5db2-4a8a-b186-0c3c30f020a3.MapDefinition Profiling LayerDefinition: Library://Byggesag/ByggesagLayer.LayerDefinition Identity fetching (ms): 0,5001 Runtime layer creation (ms): 3458,4391 Time to render scale range [0 : 10000000] (ms): 152,0193 Rendering scales (ms): 4646,09 Failed while profiling Layer Definition: Library://Byggesag/ByggesagLayer.LayerDefinition ============= ERROR DETAILS ========== System.Exception: The remote server returned an error: (559) MgInvalidStreamHeaderException.: Invalid stream header exception.

---> System.Net.WebException: The remote server returned an error: (559) MgInvalidStreamHeaderException.

at System.Net.HttpWebRequest.GetResponse() at OSGeo.MapGuide.MaestroAPI.HttpServerConnection.DownloadData(String req) in C:\Maestro\OSGeo.MapGuide.MaestroAPI.Http\HttpServerConnection.cs:line 1162 --- End of inner exception stack trace --- at OSGeo.MapGuide.MaestroAPI.HttpServerConnection.DownloadData(String req) in C:\Maestro\OSGeo.MapGuide.MaestroAPI.Http\HttpServerConnection.cs:line 1182 at OSGeo.MapGuide.MaestroAPI.HttpServerConnection.RenderRuntimeMap(String resourceId, Double x, Double y, Double scale, Int32 width, Int32 height, Int32 dpi, String format, Boolean clip) in C:\Maestro\OSGeo.MapGuide.MaestroAPI.Http\HttpServerConnection.cs:line 923 at OSGeo.MapGuide.MaestroAPI.MgServerConnectionBase.RenderRuntimeMap(String resourceId, Double x, Double y, Double scale, Int32 width, Int32 height, Int32 dpi) in C:\Maestro\OSGeo.MapGuide.MaestroAPI\MgServerConnectionBase.cs:line 210 at Maestro.Base.UI.ProfilingDialog.ProfileLayerDefinition(ILayerDefinition ldef) in C:\Maestro\Maestro.Base\UI\ProfilingDialog.cs:line 228 at Maestro.Base.UI.ProfilingDialog.ProfileMapDefinition(IMapDefinition mapDef) in C:\Maestro\Maestro.Base\UI\ProfilingDialog.cs:line 274

======== END ERROR DETAILS ============= Total for runtime Map Generation (ms): 9832,7486 Runtime map generation in one go (ms):562,0714 Full map rendering (ms): 260,5331 Failed while profiling MapDefinition rendering: Session:8b26a014-2005-11e1-8000-080027cb642a_en_7F0000010B060B050B04//17ec8685-5db2-4a8a-b186-0c3c30f020a3.MapDefinition ============= ERROR DETAILS ========== System.Exception: The remote server returned an error: (559) MgInvalidStreamHeaderException.: Invalid stream header exception.

---> System.Net.WebException: The remote server returned an error: (559) MgInvalidStreamHeaderException.

at System.Net.HttpWebRequest.GetResponse() at OSGeo.MapGuide.MaestroAPI.HttpServerConnection.DownloadData(String req) in C:\Maestro\OSGeo.MapGuide.MaestroAPI.Http\HttpServerConnection.cs:line 1162 --- End of inner exception stack trace --- at OSGeo.MapGuide.MaestroAPI.HttpServerConnection.DownloadData(String req) in C:\Maestro\OSGeo.MapGuide.MaestroAPI.Http\HttpServerConnection.cs:line 1182 at OSGeo.MapGuide.MaestroAPI.HttpServerConnection.RenderRuntimeMap(String resourceId, Double x, Double y, Double scale, Int32 width, Int32 height, Int32 dpi, String format, Boolean clip) in C:\Maestro\OSGeo.MapGuide.MaestroAPI.Http\HttpServerConnection.cs:line 923 at OSGeo.MapGuide.MaestroAPI.MgServerConnectionBase.RenderRuntimeMap(String resourceId, Double x, Double y, Double scale, Int32 width, Int32 height, Int32 dpi) in C:\Maestro\OSGeo.MapGuide.MaestroAPI\MgServerConnectionBase.cs:line 210 at Maestro.Base.UI.ProfilingDialog.ProfileMapDefinition(IMapDefinition mapDef) in C:\Maestro\Maestro.Base\UI\ProfilingDialog.cs:line 349

======== END ERROR DETAILS ============= * Done *

Change History (2)

comment:1 by jng, 13 years ago

Give r6299 a go.

comment:2 by hm, 13 years ago

Resolution: fixed
Status: newclosed

I can confirm that the Profile button now works connected to a AIMS 2012 server.

Note: See TracTickets for help on using tickets.