Product: MapXtreme 2004/2005
Version: 6.0, 6.1, 6.2, 6.5, 6.6, 6.7, 6.7.1, 6.8
Platform: Not Platform Related
What causes COM+ activation failed errors in MapXtreme web applications?
In a MapXtreme .Net web application, sometimes the errors "COM+ Activation failed because an initialization function failed. Check the event log for more information" or "COM+ activation failed because the activation could not be completed in the specified amount of time." occur. What is the cause of these and how can they be fixed?
There are a number of reasons why COM+ activation can fail in a MapXtreme .Net web application.
- Cause: There was a problem loading the default .mws workspace file specified in the web.config file.
Solution: Confirm the .mws workspace file works in another application such as the Workspace Manager. If any errors occur when opening the tables, it will cause a COM+ error in a web application.
- Cause: There was a problem with license verification.
Solution: A web application requires either an active trial license, an SDK license for development use, or a web license for production use. First verify that the proper .lic license file is in the directory C:\Program Files\Common Files\MapInfo\MapXtreme\<version number>. If a web license is needed, contact Customer Service to have one created. If the license is there but not working, contact Tech Support for assistance.
- Cause: The user waited longer than the COM+ activation timeout value for a request to process.
Solution: Either increase the available number of COM+ objects, increase the activation/creation timeout value, decrease the amount of data loaded in the workspace, or decrease the amount of work a user is allowed to request at once.
- Cause: The user does not have permission to read the directory that contains the workspace file(s).
Solution: Typically giving the ASPNET user, or other user account if the application is using impersonation, read access to the directory that contains the .mws file(s) will allow the start up procedure to load the data into the ISession object.
If these solutions do not work or more assistance is required, please contact Technical Support.