PST exports is not working. Is there a solution?

KB50980

Ultimo aggiornamento: 23 January 2013

PST exports not working

3.2.2

When an export job doesn't work it's necessary to check ASM logs for errors.

These are some of the possible errors in the ASM Export log (enginelog folder):

EXPT> error 1 in CFastOLAgent::Logon()
EXPT> export_messages() returned 1.

or 
 
EXPT> error 4 in CFastOLAgent::MakeStoreCurrent()
EXPT> export_messages() returned 4. Export FAILED 

 
Some other errors may be found in the PSTexport.log located in the export destination folder ( folder where is the deafult export folder and is an incremental number):
 
Fast OL agent created
Start Open Session
Close Current Folder
make given pst active; check file exists
file does't exist – create new one
create new pst file failed; error 0x8004010f
Close Current Folder
Close Current Session
Fast OL agent released
 
Fast OL agent created
Start Open Session
can't logon, try creating MAPI profile; error 0x80004005
Error initializing MAPI.; error 0x80004005
can't create MAPI profile; error 0x80004005
Fast OL agent released 

 
This errors, and other similar ones located in the export.log are usually due to MAPI support problems ("Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1" ). MAPI support could be missing on ASM Server or may have some issues due to the presence of Outlook or Exchange on the same machine.

 
Solutions:
 
1) Verify that MAPI support is installed on ASM server. If already present try to uninstall it and then to reinstall it. MAPI support can be downloaded from here. Take care that server must be restarted after MAPI installation to make this support effectively working.

2) Verify that ASM has enough permission on the destination folder (R&W). For a local folder permissions should be given to the user used to launch the ASM service while for a remote folder to the user configured in the administration page for Export jobs.

3) Verify that the following files are present on the ASM server (should be in windowssystem 32 or in program filescommon):

– MAPISVC.INF
– mspst32.dll

 
If found, edit the file MAPISVC.INF and verify the presence of the following section:

[Services]
MSPST MS=Personal Folders
 

[MSPST MS]
Providers=MSPST MSP
PR_SERVICE_DLL_NAME=mspst.dll
PR_SERVICE_SUPPORT_FILES=mspst.dll
PR_SERVICE_ENTRY_NAME=PSTServiceEntry
PR_RESOURCE_FLAGS=SERVICE_NO_PRIMARY_IDENTITY
 
[MSPST MSP]
34140102=4e495441f9bfb80100aa0037d96e0000
PR_PROVIDER_DLL_NAME=mspst.dll
PR_RESOURCE_TYPE=MAPI_STORE_PROVIDER
PR_RESOURCE_FLAGS=STATUS_DEFAULT_STORE
PR_DISPLAY_NAME=Personal Folders
PR_PROVIDER_DISPLAY=Personal Folders

If you can't find it, add it and retry the Export job.

You can find more details about MAPISVC:INF here
 
4) Verifiy the presence of the following registry keys:
 
HKLMSoftwareMicrosoftWindows Messaging SubsystemMSMapiApps 
and
HKLMSoftwareClientsMail 
 
If found try to modify the following:
 
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows Messaging SubsystemMSMapiAppsredemption.dll  with an empty string as value.
Restart the server and verify if the problem persist.

In case the problem isn't solved try to edit the same reg key and put the value ExchangeMAPI
Restart the server and verify if the problem persist.

This value is tipically set to Microsoft Outlook even if Outlook is not installed on the machine. Maybe ASM was installed when Outlook was present and then has been removed. If you need further info on MAPI calls you can check these sites:
 
PCreview forum & Microsoft MSDN

5) If the problem still isn't solved, further troubleshooting is needed.Please send us all the info collected till now (.inf file, reg. key export etc…)
It's also useful to send us the list of what appears in Internet Explorer in the section:
tools/internet options/programs