Hello,
I am having trouble getting MGOS 2.1 running on Windows Server 2008. I
installed rebooted the server, but when I try to log in to mapadmin, I get
the error Cannot establish connection. I double checked the steps in this
document, but everything appears to be set up correctly:
Hello all,
I am still struggling with this. To add some more information, I am trying
to install to the D: drive. I placed a file with a phpinfo() statement into
the mapadmin directory and it appears to be working. I tried reinstalling,
but that didn't help. I suspect that it has something
Well, now I feel rather silly. I can't belive that never occurred to me.
That did the trick. THANK YOU!
Jon
--
View this message in context:
http://n2.nabble.com/Installation-problem-tp4914540p4933613.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
Hello,
I have a version 1.1 repository that I wish to migrate to 2.1. Is there
anything special that i need to do, or can I just make a package in 1.1 and
load it in 2.1? A long time ago, I thought that I read something about a
significant change that required a more in-depth migration
That's the document I was looking for, thanks! However, if saving and
loading a package will work I think I will do that. The security settings
are very simple the data set it reasonably small. Thanks for the
information.
Jon
--
View this message in context:
Okay - I installed 2.1 on Windows 2008. I migrated my data from 1.1 by
exporting/importing a package. I migrated my application, and it was
working for a little while - until suddenly it wasn't. After about a half
hour of the application working, attempts to load my site came up with
Error 503
My migration saga continues. I just migrated my site from 1.1 to 2.1. I was
able to migrate the data by exporting a package from 1.1 and loading it in
2.1. While everything appears to have come over, some things are just not
right. I noticed that a join which was previously working properly
The join is between a SQL Server database view accessed via OBDC and an sdf
file. Back in 1.1, this was the only way to do a join. I know that joins
are a bit flaky, and they're the reason why I've waited this long. I
previously tried migrating this site to 2.0 and I experienced a different
Maestro throws an exception when I try to open the feature source. I guess
I'll start over by migrating the simple stuff and manually redefining
anything touching the joins. This repositiory has been around since 1.0, so
it's probably safer to start over, anyways. On occasion, my existing
Okay, this is still not right. I started over by manually re-building my
repository from scratch. I manually re-created the database connections and
my load procedures, and loaded all of my SDF files into the Library. I went
through and I defined the joins on a few of them. However, when I
That does indeed look like it might be related. I'm not exactly sure what
the GWS query engine is or when it is involved in querying features, but if
I am interpreting this correctly, this would mean that ANY left outer join
would behave like an inner join. The severity is marked as trivial,
Thanks for the information. pre-alpha does sound a bit scary, but I could
throw it onto a VM to see if it works. It would probably be a lot easier to
get this version running test it than it would be to isolate the exact
issue, create a ticket, etc. I may still end up having to do it, but
Hi Jason,
Good news! Both of my issues appear to be fixed in the 2.2 version that you
directed me to. Pre-alpha is a bit too scary for me to trust with my live
site, but at least I know that the problem has been fixed.
I was disappointed, however, that the performance of that 2.2 build is
I don't notice a significant performance drop from 1.1 to 2.2. The
performance seems about the same between those two versions. When I was
testing 2.1, I noticed a significant performance improvement over 1.1, but
that improvement disappeared in 2.2. However, the joins were not being
computed
Hello,
I have developed a site using MGOS. It works great on my development
machine (a 32 bit Windows Server 2008 virtual machine), and also on another
test machine that I have (Windows 7 x64). Now I am trying to get the site
running on my production server (32 bit Windows Server 2003) and I am
I'm not sure that I understand the question. If they are all using the same
feature source definition and the same version of FDO, doesn't this mean that
they are all using the same client? Please explain.
Thanks,
Jon
From: vd [via OSGeo.org]
I guess I missed that thread in my search. Installing the latest SQL Server
client did the trick. I guess I assumed that MGOS included those drivers,
although in hindsight, I'm not sure why it would. Thanks!
From: vd [via OSGeo.org] [mailto:ml-node+s1803224n7122073...@n2.nabble.com]
Sent:
Hello,
I have developed a site on MGOS 2.2. I built the (.NET) site on a 32-bit
windows 2008 development machine, which is not my primary development
machine. I am now trying to get the site to build on my 64-bit Windows 7
development machine, and I am having trouble. The strange part is that
Hello list,
I seem to be having trouble getting started with 2.5. I had the 32 bit
version of 2.2 installed, and I am trying the 64 bit version of 2.5. I
installed MGOS, and I was able to access the admin interface, load my
package, and connect to my site with Studio. I am trying to get the
Thanks for the replies, Gordon. It looks like 1.2 is actually working for
most of our servers. I think I had previously only been testing 1.0, 1.1
and 1.3. I am told that my certificate already supports 1.2. I still seem
to be having a few issues in maestro, however. Certain activities still
yes, I am using the FQDN.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapguide-users
Our IT department disabled TLS 1.0 on our servers over the weekend, and it
broke our mapguide (3.1.2) sites. They have since re-enabled it to get us
going again, but this is a very old, obsolete, and insecure protocol and
they would very much like to disable it as soon as possible. By any
Most of our mapguide-related servers are Windows Server 2016, though we do
have at least one that is 2012R2. The issue seems to be related to
mapguide's communication with SQL Server 2016, though I haven't totally
ruled out other issues unrelated to SQL Server as I can't seem to preview
SDF files
Hello,
I have created a SQL Server data source, defined a feature class, and copied
a bunch of polyline features into it. When I preview the feature source in
Maestro, I can see my feature class listed with the attributes (and key)
that I defined. If I click View Data from the feature source
I face a similar quandry to the original poster as I work with the same type
of data. I do not wish to use LL because floor plan data has values
exceeding the range and there are occasions when we need to translate units.
Do you happen to know of any coordinate systems for M, FT or IN that have
I have been successful using the arbitrary systems as well - I was just
concerned by your comment "Yes the arbitrary XY is not the best coordinate
system for MapGuide". can you elaborate on why?
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
I have been having difficulty viewing data that is stored in SQL Server as a
GeometryCollection. If the collection is split up into its component
LINESTRING, COMPOUNDCURVE and CIRCULARSTRING elements I can see them just
fine but I don't see anything when these features are stored in a
collection.
Real world coordinates are actually what is difficult when you are dealing
with floor plan information. Sure, it is easy enough to move and rotate the
data to its actual position, but once you do this, viewing it in the
original "building north" rotation does not seem an easy (or even possible?)
That would certainly explain what I am seeing. thank you for the info!
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
I am trying to create a theme using my data. I have a nullable integer
property defined that I would like to use to make a heat map for each
feature. In Maestro, when I click on "Create Theme" for the area style, I
select my property, Maestro throws the following error:
"Unable to read data
False alarm, sorry. There was an error in my feature class. I was defining
it manually in SQL server, and I didn't realize that the name of the
attribute in f_attributedefinition was case-sensitive. live and learn!
--
Sent from:
31 matches
Mail list logo
