Express Error; ASP 0178 : 8007005 after upgrade to MailSite 7

Document ID: 10369

Synopsis

After upgrading to MailSite 7, when attempting to log into MailSite Express the following error is seen: Server object error 'ASP 0178 : 80070005' Server.CreateObject Access Erro

More Information

Express Error; ASP 0178 : 8007005 after upgrade to MailSite 7

After upgrading to MailSite 7, when attempting to log into MailSite Express the following error is seen:

Server object error 'ASP 0178 : 80070005'

Server.CreateObject Access Error

?, line 0

This can occur if the MSComI18N.dll file was not registered properly. To correct the problem you need to manually register this file. The steps below explain how to register this .dll file.

  1. Open the command prompt and navigate to the MailSite install directory
  2. Enter the following command: Regsvr32 MSComI18N.dll You will receive a confirmation message

We also need to check the permissions on the folders under MailSite installation are correct.

  1. Open the properties of the MailSite folder from Windows Explorer
  2. Under Security, ensure that the permissions are being inherited and are propagating to all child objects.
  3. Select the check-box to 'Replace/Reset permissions entries on all child objects...'
  4. Hit OK, this may take a minute for the permissions to reset.
  5. Stop and Restart IIS, Express should now function

If the above solution does not work, then try:

  1. Stop the MailSite services and IIS service
  2. Rename the current 'express' folder under the MailSite installation folder
  3. Run the installer again, select the 'Repair' option
  4. A new express folder will be created and all the .dll files should be re-registered
  5. Apply any hotfixes or customizations again

Note: The NT account used under the Express virtual directory in IIS, needs to have permissions on the MailSite directory. The MailSite installer will assign the MSIISUSER account for the Express virtual directory.

To further troubleshoot Express related problems you can use utilities such as filemon.exe (provided by Sysinternals). Run this utility on the server and then attempt to log into Express. Check the filemon.exe screen and you should be able to see where the login process fails and then correct the issue.