Opened 12 years ago

Closed 12 years ago

#2134 closed defect (wontfix)

Cannot delete resource with different schema version

Reported by: gBecker Owned by: jng
Priority: low Milestone: Maestro-5.0
Component: Maestro Version: 2.4.0
Severity: minor Keywords:
Cc: External ID:

Description

Configuration: MapGuideServer 2.4 (RC2) with Maestro 5.0.0.7047 (Beta4).

When I try do delete a resource with a different schema then the highest one that is supported by MapGuideServer (for example a WebLaout with schema version WebLayout-1.1.0.xsd when highest supported version is WebLayout-2.4.0.xsd) Maestro returns me an error. See error details in attached file.

Upgrading to the newest version before deleting the resource resolves the problem.

Attachments (2)

err.txt (1.9 KB ) - added by gBecker 12 years ago.
err_layer.txt (3.1 KB ) - added by gBecker 12 years ago.
Error when trying to open LayerDefinition

Download all attachments as: .zip

Change History (9)

by gBecker, 12 years ago

Attachment: err.txt added

comment:1 by jng, 12 years ago

Try this: Edit the raw XML header of that Web Layout and then save it (without any changes) and then try deleting it again.

If you can then delete it afterwards, something has changed in the dbxml regarding storage of resource header content because I've experienced this same problem.

comment:2 by gBecker, 12 years ago

After editing the raw XML header and saving it without changes I was able to delete the resource.

As a sidenote: I did not delete the Libray from MapGuideOpenSource 2.4 RC1 before installing RC2. Does it matter?

Second sidenote: I also recognised LayerDefinitions which I can't open anymore. Don't know if it is the same problem. Editing the raw XML header like above or upgrade the resource to the newest version doesn't take any effect! Error message is attached!

by gBecker, 12 years ago

Attachment: err_layer.txt added

Error when trying to open LayerDefinition

comment:3 by gBecker, 12 years ago

Please forget my second sidenote. The problem was due to a missing alias path in serverconfig.ini.

comment:4 by jng, 12 years ago

Was this repository originally from a 2.2 or older version of MapGuide?

comment:5 by gBecker, 12 years ago

It was an older version: 2.1 or 2.0.2 (more probably the second)

comment:6 by jng, 12 years ago

Was this repo a straight drop/replace of the Repositories folder into the new MG install?

eg. 2.0.2 repo -> drop into 2.2 install -> drop into 2.4 install

I'm thinking the 2.4 repo is somehow "tainted" by 2.0.2 data structures through this approach.

I would only consider this to be a serious bug if this issue is reproducible on a repository that was upgraded in this fashion: (http://wikihelp.autodesk.com/Infr._Map_Server/enu/2013/Help/0008-Installa0/0008-Installa8/0009-Upgrade_9)

comment:7 by jng, 12 years ago

Resolution: wontfix
Status: newclosed

The problem is most likely due to a tainted repository from an older version that was just dropped into the new install instead of going through the proper repository update procedure.

Either way, this is not Maestro's problem.

Note: See TracTickets for help on using tickets.