Opened 15 years ago
Last modified 15 years ago
#2814 new defect
SDE point layers don't work in mapserver v5.2
Reported by: | gdavis | Owned by: | hobu |
---|---|---|---|
Priority: | high | Milestone: | 6.0 release |
Component: | Input - Native SDE Support | Version: | unspecified |
Severity: | major | Keywords: | |
Cc: | jmckenna, assefa |
Description
I brought this problem up in the mapserver IRC channel last week, and have some more info regarding it. Basically I've built Mapserver v5.2 for a client on Windows as they wish to upgrade from v4.10. With the new version, none of the their ArcSDE point layers work. But polygon and other types seem to work fine with SDE. All of the problem point layers worked fine in version 4.10 (the only thing that has changed is the new mapserver).
I've since built them version 5.0 for them to test with (to try and narrow down where the problem was introduced). This version works fine for SDE point layers. So something has changed between versions 5.0 and 5.2 to prevent SDE point layers from working. The error message they receive is:
<ServiceExceptionReport version="1.1.1"> <ServiceException> msDrawMap(): Image handling error. Failed to draw layer named 'DBM_7H_MIL_POPULATION_POINT'. msDrawShape(): General error message. Unknown layer type. </ServiceException> </ServiceExceptionReport>
Attached is a snipet of the problem map file layer.
Attachments (1)
Change History (4)
by , 15 years ago
Attachment: | mapfile_snipet.txt added |
---|
comment:1 by , 15 years ago
Cc: | added |
---|
comment:2 by , 15 years ago
Cc: | added |
---|
I did a quick tests with a local build (mapserver svn/sde native support) and could load my test sde point layers I also used the ms4w (2.2.9 with the sde plugins: this is a mapserver 5.2 release) and was also able to load the point layer. Unfortunately, I could not replicate your error.
Couple of points:
- is ogrinfo on the layer successful
- if it is, you might want to give it a try with a connectiontype ogr
comment:3 by , 15 years ago
Milestone: | 5.6 release → 6.0 release |
---|
Is this bug still valid? Is there anything special about the layer? If point layers in SDE didn't work generally, we'd have been flooded by now, so something seems special about this case. Kicking forward to 6.0 for now...
..and i am curious how the same test does with the MS4W SDE plugin (I can't test this as I don't have access to SDE currently)