MapGuide Enterprise 2011 – LicenceError.log

If you are running MGE 2011, you might want to have a look in your installation’s Logs folder:

C:\Program Files\Autodesk\MapGuideEnterprise2011\Server\Logs

If you see a LicenseError.log file you might want to read on.

It seems that some installs are writing to a log file named LicenseError.log.  Now writing to a log file isn’t typically a bad thing, but in many instances, it is writing to this file many times a second anytime MGE is being accessed.  As such, this file can rapidly grow in size, and in all likelihood, could be affecting the performance of your MGE.

At this time Autodesk is aware of the issue, however, it will require changes to the code to resolve this so there is no ‘fix’ for the issue.

One solution I implemented as soon as I encountered this was to create a batch file to delete the LicenseError.log file, and scheduled the batch file to run once a day.

Until next time,
Take care

Warren

Comments

Anonymous said…
great blog name, although at the same time the online news outlet that was gisdevelopment.net is now also called Geospatial World - good luck with things
August 30, 2010 at 9:28 AM
Warren J. Medernach, BGIS, GISP said…
Yes, I noticed that a while back... Thanks for stopping by.
August 30, 2010 at 11:26 PM
Anonymous said…
Is there is something new about this file?
February 25, 2011 at 10:05 AM
Post a Comment

Popular posts from this blog

ArcGIS: Packaging error - General function failure

Image
Whoa... 2 posts within 2 months...  I'm on a roll baby...   :-) In today's episode I want to document what I've discovered with the following lovely error when attempting to create a Map Package: I've had this very insightful (hint:sarcasm) message box pop-up a number of times when trying to create a Map Package.  After much copying/pasting, renaming, re-connecting data sources I finally figured out what the problem was in this particular instance. This particular map had some DWG files connected to the map, and some of these DWG names contained a special character "#", and also contained extra 'dots' in the name to delimit a date.  For example: Name#-2013.04.09.dwg In my testing and trials, removing the '#' symbol did not resolve the issue, and it wasn't until I removed the extra 'dots' in the name that I was finally able to successfully generate the package.  Further testing revealed that the '#' symbol
Read more

More ArcGIS Woes with 'Special' Characters...

Image
It's no secret that I've griped and complained about many of ArcGIS's quirks that seem stuck or rooted in the 80's ...  One would think I wouldn't be surprised anymore when I come across such silly issues... But I am. The latest 'undocumented feature' I've discovered is that the Field Calculator will fail if there is forward slash ( '\' ) in the Layer name. ArcGIS 11 can't come soon enough.
Read more

ArcGIS Collector: Update Error Code 1006

Image
Alright, this is the second time this happened to me, and I neglected to document it the first time, so I had to search again to find the answer, so I will document it here, and now. Here goes... If you happen to come across ArcGIS Collector throwing an error when updating a feature, and the error states something along the lines of: Invalid untrusted Html content detected in field: Have no fear, there is a simple fix.  Well, that is, it's a simple fix if this is 'local' map, not accessible to the general public.  That's only because ESRI doesn't actually 'recommend' this fix. So what is 'this fix' I speak of? A little more background... If you have any fields that contain HTML content, there is a chance that Collector could see that as malicious content, and it will block it.  You can see a list of allowable HTML tags in Collector a this link . In my instance, I am running some database triggers to populate and update a URL field, where
Read more