#1680 closed defect (fixed)
WMS connection problem
Reported by: | janvw | Owned by: | jng |
---|---|---|---|
Priority: | medium | Milestone: | Maestro-3.5 |
Component: | Maestro | Version: | |
Severity: | critical | Keywords: | |
Cc: | External ID: |
Description
Unable to connect to a specific WMS server (not publically accessible) in Maestro 3.0.0 with MGOS 2.2. When trying to save the resource (with the validating option turned off), the attached error is being displayed. The configuration document is also attached.
Attachments (3)
Change History (14)
by , 14 years ago
by , 14 years ago
Attachment: | config.xml added |
---|
comment:1 by , 14 years ago
Milestone: | Maestro-4.0 → Maestro-3.0 |
---|---|
Version: | → 2.2.0 |
comment:2 by , 14 years ago
Milestone: | Maestro-3.0 → Maestro-3.1 |
---|---|
Version: | 2.2.0 |
comment:3 by , 14 years ago
Severity: | blocker → critical |
---|
comment:4 by , 14 years ago
by , 14 years ago
Attachment: | wms-error.jpg added |
---|
comment:5 by , 14 years ago
I tried with Maestro 3.1. There's still an error (see attached file wms-error.jpg). In the Errorlog I get the following information:
<2011-06-01T10:52:22> 404 MapGuide Maestro v3.1.0.5859 127.0.0.1 Administrator
Error: Problem:\nThe application encountered a problem and could not finish the operation you just requested properly.\n\nSolution:\nIf it\'s the first time you met this problem, try again or restart the application / session; otherwise, describe the steps to reproduce this problem to the server administrator for suggestions. StackTrace:
- MgFeatureServiceHandler.ProcessOperation() line 83 file c:\builds\mg22win32\mgdev\server\src\services\feature\FeatureServiceHandler.cpp
- MgOpDescribeSchemaAsXml.Execute() line 110 file c:\builds\mg22win32\mgdev\server\src\services\feature\OpDescribeSchemaAsXml.cpp
- MgServerFeatureService.DescribeSchemaAsXml() line 361 file c:\builds\mg22win32\mgdev\server\src\services\feature\ServerFeatureService.cpp
- MgServerDescribeSchema.DescribeSchemaAsXml() line 622 file c:\builds\mg22win32\mgdev\server\src\services\feature\ServerDescribeSchema.cpp
- MgServerDescribeSchema.DescribeSchema() line 558 file c:\builds\mg22win32\mgdev\server\src\services\feature\ServerDescribeSchema.cpp
- MgServerDescribeSchema.DescribeFdoSchema() line 199 file c:\builds\mg22win32\mgdev\server\src\services\feature\ServerDescribeSchema.cpp
- MgFdoConnectionManager.Open() line 313 file c:\builds\mg22win32\mgdev\server\src\common\manager\FdoConnectionManager.cpp
follow-up: 7 comment:6 by , 14 years ago
The original problem I had discovered (and my theory on the problem) was that some of the WMS layers had umlauts and other strange characters in their names.
Do you know of any public WMS servers that may be serving such similar layers (ie. Layer name has an umlaut or other non-alphanumeric characters) so I can test and verify that this could possibly be the case?
comment:7 by , 14 years ago
Today I finally found a WMS server that has a layer (BPL Änderung) with umlaut:
http://geoportal.landkreis-osterode.de/cgi-bin/wms_bauleitplanung.exe?
comment:8 by , 14 years ago
Milestone: | Maestro-3.1 → Maestro-3.5 |
---|
comment:9 by , 13 years ago
Please test against Maestro 3.5 beta 1 and report your findings. I'm pretty sure the problem has been resolved.
follow-up: 11 comment:10 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Resolving as fixed in Maestro 3.5 beta 1. Please re-open if this is not the case.
Please check if the release of Maestro 3.1 resolves this issue for you.