[mapguide-users] Problem connecting, but only on one server

[_Jon_]

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
running into a problem.  I created a package on my development machine and
loaded it on my production machine.  Then, I copied the published web site
files over and created an application for them in IIS.

The site appears to load, but it is painfully slow.  Much, much slower than
on my development machine (which is actually a VM).  Second, I noticed that
one of my layers is not showing up on the production server.  Figuring that
the two problems are related, I went to investigate this in Studio.  It
seems that there is something wrong with the feature source, which is an
ODBC connection to a SQL Server database.  When I test the connection, it
says "An exception occurred in FDO component. RDBMS: No current open
database. "  I ran the connection test from the web-based mapagent and I get
the same result.  Using SQL Server Management Studio, was able to connect to
the database from my production server using the credentials that my feature
source is using.  In addition, I have another feature source pulling
polygons from the same database, so 

I used the same Package to copy my site to my Windows 7 laptop and it works
fine there, so MapGuide is working with the same data on all three.  Also in
all three cases, the same database is being used - it is on another server. 
Any ideas about what could cause this behavior?  I am at a complete loss. 
Thanks in advance for any insights that you can offer.

Jon

--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Problem-connecting-but-only-on-one-server-tp7121934p7121934.html
Sent from the MapGuide Users mailing list archive at Nabble.com.