A/R Statements: Could Not Establish a MAPI Session - Also causes "Error Code 13: Type Mismatch& 1

[Ho3n3r]

I have an issue which has made me feel like an idiot, because I can't seem to resolve it. I am at my wit's end. Let's start at the beginning.

1. When trying to print an A/R Statement, using Preview first, the statements print to PDF fine. This is the initial screen with parameters:

2. Then, after the user is happy with the preview, she tries to change the Delivery Method to Customer, which is email. Then this error pops up. Please note, I have made sure her default mail app is Outlook, and restarted her PC several times since Thursday. The server has been restarted as well(not that it should make any difference to this particular error, but rather as a resolution to "reset" the error in point no. 3 below):

3. Then, changing Delivery method to Print Destination again to see the preview again, the following error is observed:

This last error can only be resolved by restarting the Accpac server.

System Info - Server:
- Windows Server 2008 R2 Enterprise 64 Bit
- Accpac 6.0A Update 2

System Info - User:
- Windows 10 Pro - 32 Bit
- Outlook 2013

Any advice would be appreciated. Thank you.

 

[Jay Converse]

Version 6.0?!?! Upgrading to the current version is the best option, because it uses a built-in SMTP server instead of Outlook.

Sage 300 Whisperer

 

[Ho3n3r]

I agree. But that's not my decision. Do you have any tips perhaps for the current version with the issues as pointed out?

Thanks again.

 

[Jay Converse]

Since this is a customized form, does the default ARSTMT10 have the same problem?

Sage 300 Whisperer

 

[Ho3n3r]

Thanks for the idea.

It gives the same error though - works fine before the MAPI error, then Error Code 13: Type Mismatch after the MAPI error.

 

[Ho3n3r]

Another potentially telling problem I forgot to mention: After the MAPI error occurs, the user is unable to edit the amounts on the Current Cust. Bal. From and To values - the other 3 are still editable at that stage, though.

 

[Ho3n3r]

Did a repair on Accpac last night. Error still persists, unfortunately.

 

[DjangMan]

I wonder if you have any fields with a single apostrophe in the value or some other value that is causing a dynamically generated value to be interpreted incorrectly.

In your screenshot you're printing for a range of customers. Can you do this successfully for just one customer (keeping in mind that the one customer you select could be causing the issue)?

As an aside - when we're tasked with mass emailing of Crystal reports we've been using Visual CUT with good success (

http://www.milletsoftware.com/Visual_CUT.htm).

It's relatively cheap (about $300) and is feature rich (300+ page manual). I've also heard about this software but I've never used (

https://www.arcanadev.com/reportcommander/).

It's about half the price of Visual CUT but I can't speak to it's feature set. So it might be worth looking at bailing on the built-in implementation and get a dedicated tool.

 

[Ho3n3r]

@Djangman thanks for the reply. I managed to solve it today.

MAPI Error:
Solved by enabiling Programmatic Access security in Outlook's Trust Center. It was greyed out for me (I am actually the developer, not the sysadmin, hence no administrator access).

Type Mismatch error:
Solved by setting decimal separator to . instead of ,. Region was set to South Africa, and the default decimal separator is , for some reason. I am unsure why the first preview run triggers this error, but I tested it without Current Cust. Bal. and it worked fine without this field - as mentioned above, I thought the MAPI error triggered it, but I was wrong and it was just an unfortunate coincidence.

Thanks for all the input, and hopefully this will help others in future.