Opened 13 years ago

Closed 12 years ago

#547 closed defect (fixed)

Server is reporting product version not package version

Reported by: zspitzer Owned by:
Priority: high Milestone:
Component: Server Version: 2.0.0
Severity: blocker Keywords:
Cc: External ID:


using a trunk build (3154) on RH ES 4, Studio 2009 can't log in

I get the following error

"Unable to complete request from site" there is an error in xml document (23,4)

using fiddler the xml looks ok, but i did notice the version being reported as could that be the problem?

I think it's reporting the product version as opposed to the mapguide version, ie trunk/MgDev/Common/ProductVersion.h

2.0 released binary on windows reports


<DisplayName?></DisplayName?> <Status>Online</Status> <Version></Version>

whereas trunk build returns


<DisplayName?></DisplayName?> <Status>Online</Status> <Version></Version>

Attachments (1)

productversion.patch (372 bytes) - added by zspitzer 13 years ago.

Download all attachments as: .zip

Change History (6)

comment:1 Changed 13 years ago by tomfukushima

Not sure why we have in there. I guess that was the next logical progression after MapGuide 6.5, even though the two are completely unrelated. The should really just be the current trunk version, which now would be Could you change all the's and 7,0,0,1's in the code to the equivalent 2.1, recompile and test that it works, and then submit a patch for that? Thanks, Tom.

comment:2 Changed 13 years ago by zspitzer

I changed the product version which worked but i am still getting the same error from studio

AvailablePhysicalMemory? looks rather too negative, and the memory values are 0

<?xml version="1.0" encoding="UTF-8"?>
<SiteInformation xmlns:xsi="" xsi:noNamespaceSchemaLocation="SiteInformation-1.0.0.xsd">
			<Version>Linux, Kernel Version: 2.6.9-67.0.7.ELxenU</Version>

Changed 13 years ago by zspitzer

Attachment: productversion.patch added

comment:3 Changed 13 years ago by tomfukushima

Is this machine available on the Internet? If so could you email me (tom.fukushima at the details directly? I could then start the debugger up in Studio and see why it is failing.

comment:4 Changed 12 years ago by zspitzer

over in #633 it looks like the problem might be that <DisplayName/?> is being returned rather than <DisplayName?></DisplayName?> which is tripping up studio

comment:5 Changed 12 years ago by tomfukushima

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