Opened 10 years ago

Closed 8 years ago

#2541 closed defect (fixed)

Cannot connect to WMS service after editing configuration document

Reported by: gBecker Owned by: jng
Priority: medium Milestone: 3.0
Component: Maestro Version:
Severity: critical Keywords:
Cc: External ID:

Description

When editing the configuration document of a WMS FeatureSource in MGOS 3.0 via the editor, the connection to the WMS server fails. Hitting the "Test Connection"-Button results in an unclassified error.

<2015-02-26T11:44:53> 	15904	MapGuide Maestro v6.0.0.8244	::1	Administrator
 Error: Resource data was not found: MG_USER_CREDENTIALS
 StackTrace:
  - MgResourceServiceHandler.ProcessOperation() line 80 file c:\working\build_area\mapguide\3.0.0\x64\mgdev\server\src\services\resource\ResourceServiceHandler.cpp
  - MgOpDeleteResourceData.Execute() line 101 file c:\working\build_area\mapguide\3.0.0\x64\mgdev\server\src\services\resource\OpDeleteResourceData.cpp
  - MgServerResourceService.DeleteResourceData() line 1917 file c:\working\build_area\mapguide\3.0.0\x64\mgdev\server\src\services\resource\ServerResourceService.cpp
  - MgApplicationRepositoryManager.DeleteResourceData() line 1065 file c:\working\build_area\mapguide\3.0.0\x64\mgdev\server\src\services\resource\ApplicationRepositoryManager.cpp
  - MgTagManager.GetTag() line 372 file c:\working\build_area\mapguide\3.0.0\x64\mgdev\server\src\services\resource\TagManager.cpp	
<2015-02-26T11:44:53> 	18132	MapGuide Maestro v6.0.0.8244	::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:\working\build_area\mapguide\3.0.0\x64\mgdev\server\src\services\feature\FeatureServiceHandler.cpp
  - MgOpTestFeatureSourceConnection.Execute() line 100 file c:\working\build_area\mapguide\3.0.0\x64\mgdev\server\src\services\feature\OpTestFeatureSourceConnection.cpp
  - MgServerFeatureService.TestConnection() line 244 file c:\working\build_area\mapguide\3.0.0\x64\mgdev\server\src\services\feature\ServerFeatureService.cpp
  - MgFdoConnectionManager.Open() line 333 file c:\working\build_area\mapguide\3.0.0\x64\mgdev\server\src\common\manager\FdoConnectionManager.cpp

I've also recognized that all entries in the "Select FDO Provider" box exists twice when you have another connection to an older MGOS version aside a MGOS 3.0 server connection in Maestro. For example:

"OSGeo FDO Provider for WMS" and "WMS Provider"

Change History (4)

comment:1 by jng, 10 years ago

Can you provided detailed steps for reproduction?

comment:2 by gBecker, 10 years ago

These are the steps to reproduce the problem:

  1. Open a connection to a MapGudie 3.0 Server via Maestro
  2. Create a new FeatureSource of type "OSGeo FDO Provider for WMS"
  3. Assign a "Feature Server". For example http://geoportal.frankfurt.de/opendata/odlb12fbgqgk.exe or any other server.
  4. Test the connection. Everything should be fine.
  5. Push the "Advanced"-Button and save the configuration. You don't have to make any changes.
  6. Test the Connection again: An error message should appear (as mentioned before).

comment:3 by jng, 10 years ago

It appears to be an issue with the WMS provider that came with the Preview 1 release.

I do not have this issue with trunk FDO, I'll consider this issue resolved when I put out 3.0 Beta 1

If the duplicate provider entry in Maestro still persists, please move that off to a separate ticket.

comment:4 by jng, 8 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.