There should be an error message in the log, describing the problem.
If not, you can enable the TRACE log (which will slow the server quite a
bit), and see the last operation and parameters there.
You might also try to upload the package through the http interface:
http://localhost/mapguide/mapagent/index.html
Once you figure out what the problem is, you can fix the package by
doing this:
1. Rename from .mgp to .zip
2. Extract to a folder
3. Edit the file MgResourcePackageManifest.xml and remove the broken item
4. Update the .zip file
5. Rename back to .mgp
Regards, Kenneth Skovhede, GEOGRAF A/S
Rock Beans skrev:
Is there any way for the log to say what file is actually missing. We
have a client that is loading 150MB packages at times and when you get
this error is very frustrating. How do you know what went wrong? If
you don't know what DWF is missing how can you fix? Right now my only
answer is sorry you wasted your time for the past 2 weeks restore an
older package and start over. There has to be a better way. Anyone
else deal with bad packages or something similar to this?
The Rock
------------------------------------------------------------------------
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
