Init Preview Error 80004005

Initialize error 80004005" error message appears while creating or editing a Messaging Application Programming Interface (MAPI) profile Article Number:000001637 First Published:August 15, 2015 snagit editor failed to initialize the snagit datastore Last Modified:August 15, 2015 Type:Support Environment BlackBerry Enterprise Server for snagit has stopped working Microsoft Exchange Microsoft Exchange Server 5.5 to 2010 Back to top ↑ Overview While creating or

Snagit Support

editing a Messaging Application Programming Interface (MAPI) profile, the following error message appears:MAPI Initialize error 800004005or if during the installation of BlackBerry Enterprise Server services at the MAPI Settings window:The setup application could not initialize the Microsoft Exchange Server MAPI client. Make sure that MAPI is installed and configured correctly and the Microsoft Exchange Server and mailbox that you specified are correct. Back to top ↑ Cause Cause 1Microsoft Exchange System Manager or Microsoft Exchange Server MAPI Client and Collaboration Data Objects version 1.2.1 is not installed on the computer running the BlackBerry Enterprise Server.Cause 2The fixmapisvc.exe tool has not yet been run on the BlackBerry Enterprise Server.Cause 3Group Policy is modifying the default Mail client from ExchangeMAPI to another client. Back to top ↑ Resolution Cause 1Microsoft Exchange System Manager or Microsoft Exchange Server MAPI Client and Collaboration Data Objects version 1.2.1 is not installed on the computer running the BlackBerry Enterprise Server.Resolution 1For Microsoft Exchange Server 5.5, install Exchange Administrator on the BlackBerry Enterprise Server. For Microsoft Exchange 2000 or 2003, install Microsoft Exchange System Manager on the BlackBerry Enterprise Server. For Microsoft Exchange 2007, install Microsoft Exchange Server MAPI Client and Collaboration Data Objects version 1.2.1. Refer to Microsoft Support for information on installing these programs.Cause 2The fixmapisvc.exe tool has not yet been run on the BlackBerry Enterprise Server.Resolution 2Run fixmapisvc.exe on the BlackBerry Enterprise Server. Complete the following steps:Stop all the BlackBerry Enterprise Server services. Rename Mapisvc.

80004005 - Unspecified ErrorThink of error 80004005 as meaning the script could not access your data. The most likely reason is a permissions related problem. Your best chance of resolving this problem is to study carefully any associated message, for example, 'File already in use', or 'Logon Failed'. Introduction to Error Code 80004005 Error 80004005 is a general error for all manner of events. I have to confess that I am still trying to understand all the causes of this code number. One thread that runs through error 80004005 problems is permissions. Another thread is incorrect format, for example you entering a number instead of a string. This is particularly true of telephone or fax http://support.blackberry.com/kb/articleDetail?ArticleNumber=000001637 numbers. My main interest is in VBScript errors, however, I have added database examples for completeness. The first branch in your decision tree is this an ASP error or some other ODBC error. Three types of 80004005 Error VBScript Connectivity Problems - E.g. SQL Data Access Components - MTS ‡ VBScript Symptoms What you see is WSH (Windows Script Host) message box. The script does not execute as you had hoped. Instead you get a http://www.computerperformance.co.uk/Logon/code/code_80004005.htm message box like this picture: The Causes of Code Error 80004005 VBScript / CScript 1) In this case, VBScript was trying to store a password. With error 80004005 there is usually an element of access denied. Insufficient rights, wrong permissions. 2) It can occur when a VBScript attempts to connect to scriptpw.dll. There are other causes, such as connecting to COM objects or ADO, or other database object. 3) Another thread is Number v String value format. If you are dealing with a phone number, make sure that you add it as string value and not as a pure number. Extra information supplied by Murda McLoud. 'I worked out that had to convert the number to a string to stop the 80004005 error. Then the objUser.Put would work properly and save the data.' Solutions for Error 80004005 This has been a very difficult error to track down. Possibly the error was due to using WScript instead of CScript.Check the underlying database, for example, names, exclusive locks and especially permissions.One additional problem that I had with Error 80004005 was due to a firewall blocking the relevant port, it was either 80 or 135. Example 1: VBScript with Error 80004005 I have to admit this may not be terribly useful example for your specific problem, but then Code 80004005 is invariably a vague permission problem. '