Video Screencast Help

Could not get a MAPI session from the session pool... Journaling Service Pr

Created: 13 Dec 2005 • Updated: 09 Apr 2013 | 47 comments
This issue has been solved. See solution.

Hi all,
I have 3 Journaling Services running on the Vault Server. 2 Journaling Services work fine (knock on wood), but 1 Journaling Services does not grab messages from the journaling mailbox posting 'Could not get a MAPI session from the session pool' message every 5 min
Any help would be greatly appreciated.
Thanks in advance,
Victor

Discussion Filed Under:

Comments 47 CommentsJump to latest comment

Matthew Edwards's picture

In the JournalServiceEntry table in the EnterpriseVaultDirectory database, try changing the system mailbox from the exchange alias to SMTP:. Then restart journal service.

David Messenger 2's picture

Victor,

you need to do what Matt says if you have EV mailboxes with similar names.

another reason might be you are out of resources (MAPI leaks) and rebooting sorts that (although not a very good long term plan).

Victor Geyyer's picture

Thank you for your response...
The problem: I already checked and changed the System Mailbox and also restarted the server multiple times...
Any other ideas?
Thanks again,
Victor

David Messenger 2's picture

Any MAPI error the first thing to do is to try to connect to the problem mailbox using the main EV administration account. Log on to the EV server as this account, run Outlook and set up a brand new profile with the problem mailbox as the primary.

When you changed the mailbox did you change it on all the services that use MAPI (archivng, retrieval and journallin) specifically in the SQL database?

Victor Geyyer's picture

Thanks A LOT, David...
It was extremely helpful...
Turns out that I can't log in to the KVS system mailbox through Outlook, even though I can log in to the Journaling mailbox without any issues... I reviewed permissions on those 2 mailboxes/accounts and they look exactly the same... What would you recommend as the fastest fix of the problem?
I don't have Archiving and Retrieval Services against that Exchange Server...
Thanks again,
Victor

Matthew Edwards's picture

You could create a new mailbox for EV to use as a system mailbox.

Archiving and Retrieval services are not required if the Exchange server is only being used for journaling.

Victor Geyyer's picture

Thank you, Matthew...
Are you suggesting re-creating the Journaling Service? I could not find the place to change the system mailbox (if I create a new one)...
Is it the simplest way?
Thanks again,
Victor

Matthew Edwards's picture

create a new mailbox, verify connectivity within Outlook and then update the system mailbox column on the table I mentioned earlier. A restart of the journal service should then do the job.

The mailbox is arbitrary, its a requirement of MAPI that a valid endpoint exists on the server you're connecting to.

You won't need to recreate the journal service for that Exchange server.

Victor Geyyer's picture

I did what you suggested and still no luck (I even restarted the KVS Server)... Now I can log in to both System mailbox and Journaling Mailbox, but Journaling Service still does not work... Could it be related to installing SP1 for Windows 2003 Server on Exchange Server?
Thanks,
Victor

Matthew Edwards's picture

are you still getting the same MAPI session errors? How many MAPI profiles has EV created for the service account?

Victor Geyyer's picture

Yes... I'm still getting 2 errors every 5 min:

Source: EV
Category: Journal Service
Event ID: 3231
Description:
Could not get a MAPI session from the session pool
Error:<0x80040115>
....

and
Source: EV
Category: Journal Service
Event ID: 2216
Description:
Message dispenser will suspend processing for 5 min due to a recoverable error

Also I have 2 profiles "VaultMbxAgent-badserver-..."

Besides that I have
16 profiles "VaultMbxAgent-goodserver1-..."
35 profiles "VaultMbxAgent-oldserver1-..."
1 profile "VaultMbxAgent-oldserver2-..."
11 profiles "VaultMbxAgent-goodserver2-..."

Thanks in advance,
Victor

Aaron Mears's picture

Could just be a network problem. Any other network issues or erros in the app log, RPC, Exchange, GC?

http://support.microsoft.com/default.aspx?scid=KB;...

The error code relates to "MAPI_E_NETWORK_ERROR"

Also,

How many versions of MAPISVC.INF do you have on the EV server? (Should be one)

How many Outlook profiles? HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows
Messaging Subsystem\Profiles\

They should clean up automatically, but maybe you are over the top. With the services stopped (archive, retrieval, public folder, journaling) you can remove the auto-created profiles. Just make sure the services are stopped since they use these profiles (and will make new ones when they start).

Matthew Edwards's picture

mapisvc.inf and mapi32.dll need to be the ones that came with Outlook. ( see http://www.udstech.com/whitepapers/wp.tryfirst.pdf )

Normally a typical EV server will have 3 versions... Outlook, ESM and the one that comes with the O/S. You'll see by the sizes of these files that they are very different in nature.

It seems strange that 2 of your journal services do work if this is the problem....
Did you try the SMTP:<> fix?

Victor Geyyer's picture

Thanks to everyone for the support...
The Exchange Server my "broken" Journaling Service is running against is in the subsidiary domain and it does seem like everything became broken after the applied SP1 for Windows 2003 Server...
The question is:
Does EV support Windows 2003 Server SP1 on Exchange (long after SP1 got released EV did not support it, but maybe now they support it)?
Do you have any ideas why installing SP1 could broke MAPI network connection between my EV server (Journaling Service) and subsidiary Exchange Server (on Windows 2003 Server SP1)?
Any ideas will be really appreciated...
Thanks,
Victor

Matthew Edwards's picture

No known issues with SP1 on the Exchange server, but yes on the vault server.

I know that the old 'send as, receive as' rights need to be explicitly set for the vault service account at the server level in ESM if the O/S of the Exchange server is WIndows 2003, but I don't think that is changed in SP1. (Please check anyway! click on the advanced button in the security tab of the server properties in ESM and add the vault service account with 'send as and recieve as' rights)

Are you sure that SP1 broke it?

Victor Geyyer's picture

No, I'm not sure that SP1 broke it... It's just looking this way: after they upgraded the server to SP1 it stopped working...
:(
Permissions are fine...
Thanks,
Victor

Brian Spooner's picture

One other thing you might check.... Find the information store where your journaling mailbox lives...is journaling enabled in Exchange for that store? That can be a big problem and Microsoft does not recommend it. Basically, the journal mailbox journals itself and cause all kinds of issues. The journal mailbox should reside in it's own info store that does NOT have journaling enabled on it.

This caused us quite a bit of grief and making these changes fixed them for us.

-Brian

David Messenger 2's picture

Stuff on MAPI versions in "Try this 1st" White Paper on www.UDStech.com.

You need to make sure you can open the EV mailbox that is on the Journal server and the Journal mailbox itself using Outlook on the EV server whilst logged in as the Service Account. Create new profiles for both these mailboxe. Don;t open them as secondaries of use File -- Open Other Users Folder.

Not 100% sure you have done this and it's an important step b4 we start fannying around with other stuff. If you have, forgive me for being a pedant :-)

When you create he new MAPI profiles use the alias name of the mailbox to generate the profile. If Outlook prompts you to make a mailbox choice then this tells you to use the SMTP:mailboxessmtp@address.com format in the SQL on all the services. If not it's not needed but still good practice.

Could be perms in the sub-domain OU - the above will check this for you (amongst other stuff).

Still unclear as to what's happened. It worked but then it stopped when someone W2k3 SP1'd the Exc server? Not seen that 1 b4....?!?

Michael Bilsborough's picture

Hi,

Vault System Mailbox on that server hasn't been hidden has it?

David Hamilton's picture

An excerpt from a MAPI troubleshooting doc I receive from KVS Support.

Run the Outlook utility fixmapi.exe
As part of the Outlook installation, it installs a utility called fixmapi.exe. Usually you can find it in C:\WINNT\system32.

To run this utility, simply double click on it. Note that this utility runs very quickly and does not display any output so you might not realise it has run.

After you have completed the above steps, you need to reboot the server to be sure that the changes take effect.

David Messenger 2's picture

David,

scan this thread http://forums.veritas.com/discussions/thread.jspa?...?

There are some links in there to other documents as well.

I *think* fixmapi is actually an Outlook Express thing (hawk, spit). When we first built EV (version 5.0 when it was actually masquerading as version 4.1 nearly 2 years back (or is it 3?)) we ran thru Outlook trying to "heal itself" with the KVS consultant (who I trust A LOT). He said do not under any circumstances let Outlook heal itself. This is effectively what fixmapi is doing. Overwriting ESM MAPI with Outlook MAPI.

We built 8 EV servers. They worked about as well as I expected them to (i.e. a bit crap but could be worse) and then started playing up severely. Loads of errors and service crashes. All sorts of stuff. Took me ages to figure out that someone on the KVS support desk (who I trust NOT AT ALL) had advised one of my team to run fixmapi.exe. I'm still not sure why. I guess it was on his list of "things to do to get rid of a case quickly even if you haven't a clue what the problem is"?!? It might fix someone who was runnig the O/S MAPI on an NT4 server I suppose...

I asked them (Veritas at that point) why they'd done this. They didn't know. I escalated the call. What version of MAPI do we need? "We don't know, it's up to you". WTF?!?! :-( :-( :-( It's Gold Certified by MS and totally MAPI based but they don't know what versions of the files we should have on the servers!! Confidence rock bottom by this stage. Posted the above thread. Implemented the fix and....

... everything is much better thank you (rember how you built the EV server? O/S --> Outlook --> Exchange --> EV). You can't import Unicode PST files (well you can, you just swap the MAPI files out when you do it and make sure there's no archive runs imminent, you probably have to stop the services temporarily to release the file locks) but IMHO you get fewer issues running day to day with ESM MAPI. I could be wrong but I'm sticking with what I've seen in the field for now until convinced otherwise.

Hope that helps!! :-)

Matthew Edwards's picture

David's right about Fixmapi -its not going to fix this problem.

Looking through this thread, if you've tried everything suggested to the letter then we are beginning to run out of things to try.

Let's try a different approach.

Can you temporarily point the journal service at a different mailbox on the server and see if it can suck the items out of it (don't switch the Exchange journal for now...let that carry on filling the mailbox). If the journal service likes a different mailbox, then there is something definitely wrong with the original one. At this point switch the Exchange journal mechanism to point to the new box and manually copy the old journal mailbox's contents into it using Outlook or Exmerge.

I know that this is a work around more than a fix - but its a low-risk approach and heck I'm sure that most of us will still sleep well even without getting to the bottom of it :)

Victor Geyyer's picture

Guys,
You are perfect...
You are not leaving me in the trouble...
I run fixmapi too fast and it did not fix the problem and I will have other problems later :(
Ok...
I was frustrated enough to re-point the Journaling Service to another mailbox, which did not fix the issue... Furthermore more interesting stuff appeared: now I have 2 exactly same errors complaining about MAPI session (see above) on 2 mailboxes: JournalOld and JournalNew...
....
I was surprised where the information about JournalOld pop up and went ahead and remove the Journaling Service and created the new one pointing to the new mailbox JournalNew... After I started the service I got 2 same old 'MAPI session' errors for JournalNew... and JournalOld... I don't know where the new Journaling Srevice took the information about JournalOld from: I totally removed the Journaling Service and readded it... I checked the database and at least JornalingServiceEntry table does not have any knowledge about JournalOld...
....
Strange things are happening... I'm glad that 2 other Journaling Services work properly (so far)...
...
Thanks for not leaving me out in cold... :)
-Victor

Victor Geyyer's picture

Hi all,
Here is the update on the issue:
After we restarted the troubled Exchange Server, I'm getting different issue now:
I can't start the Journaling Service with the following error message:

Source: EV
Event ID: 3077
Description:
Unable to determine the version of the Exchange server Server1, the service will shut down
Reason: Access Denied
....
Any ideas how to fix this?
Thanks,
Victor

Michael Bilsborough's picture

Is the Exchange server running Win2k3 sp1?

If so it's a known win2k3 sp1 bug. You need to either make vault service account member of local admins on exchange server or speak to microsoft regarding a hotfix which is available(I think) or goto V6 sp1

Victor Geyyer's picture

The Vaul Admin account is in the Administrators group on the Exchange Server...
Anything else?
Thanks a lot...
-Victor

Michael Bilsborough's picture

Hi,

On the EV server goto computer manager and then switch to the exchange server and list the services. Does that work or do you get Access denied.

That is effectively what EV is doing at that point. So if it doesn't work you need to get computer mgt working first.

David Messenger 2's picture

3 pages. Longest thread yet. Don't know about you lot but I'm totally confused....

Matthew Edwards's picture

Ok - this looks a little better (the error - not the issue!)

Could you make the EV service account a member of the local Administrators group in the domain where the Exchange server is located (not the Domain Admins group but the in the BUILTIN OU).

Also is the domain in the same AD forest?

Are there any firewalls between the EV server and the Exchange server?

Tremaine's picture

Have you tried adding the EV service account to the Exchange server in question local admin group?

Victor Geyyer's picture

Hi to all,
The original error came back...
The Vault Server and Exchange Server are in the different forests and yes, there are firewalls between two networks...
But we've been through the original setting up the Journaling Service (open ports on firewalls, creating trusts on domain level, adding Vault System account to the admin groups both on the domain level and local for Exchange, setting up appropriate permissions for Vault System account on Exchange)...
And it was working before!... Before installing SP1 on Windows 2003 on Exchange Server... Maybe it is a coincidence, but I don't think so...
Thank you for your help… And if you continue sharing ideas, I would be grateful…
-Victor

David Messenger 2's picture

Why are your firewalls there? Are you doing any NATting? What ports are you blocking? Any changes recently?

Victor Geyyer's picture

> Why are your firewalls there?

Because it's 2 different companies...

>Are you doing any
> NATting?

As far as I know, it's PIX-to-PIX firewall, I don't think there "NATting" involved... It's in hands of network engineers, but nothing has changed recently and it worked fine prior to W2k3 SP1 installation...

> What ports are you blocking? Any changes
> recently?

David Messenger 2's picture

Outlook (which is a lot of what EV is) won;t work properly thru NAT (beacuse UDP can't route).

Can you confirm -- different companies, but same AD and same Exchange Organisation right?

Victor Geyyer's picture

> Outlook (which is a lot of what EV is) won;t work
> properly thru NAT (beacuse UDP can't route).

There is no NATting…

>
> Can you confirm -- different companies, but same AD
> and same Exchange Organisation right?

NO...
There are 2 forest (not the same ADs) and 2 different Exchange Orgs - trust relationship between domains… It worked just fine and it is still working fine (knock-knock on wood) for one of our other subsidiary – different ADs, different Exchange Orgs...

Matthew Edwards's picture

Victor

Can you check the ports open on your firewall (avoid the Sp1 loop - I still think it's a red herring).

Look at the following KB article for reference:

http://support.microsoft.com/?id=270836

Outlook 2003 uses dynamic port assignments which play havoc with firewalls (normally in highly partitioned environments I recommend RPC over HTTPS for clients - EV needs the full monty RPC connection however.)

Could your firewall guys give you a temporary 'open connection' just between the EV server and exchange server for testing?

You also need to turn up logging on the Exchange server and look at DS/DSProxy related errors.

Finally. Use the Outlook 2003 connection checker to verify DS access.

( -CTRL+Click the Outlook tray icon:

CTRL+Click

-Click 'Connection Status...')

David Messenger 2's picture

Matt,

if Victor is following the advice on the thread then he already has the mailbox opened from the EV server using Outlook.

Matthew Edwards's picture

True

But this problem may not be MAPI related, it might be the Name Service Provider Interface (NSPI) interface, although this would probably affect opening a mailbox as well.

I need to increase the number of messages per thread - 15 isn't enough and means I invariably skip the first 2 pages of this one!

Victor - can you reconfirm that there is no problem opening a mailbox in Outlook 2003 on the target server?

Victor Geyyer's picture

Thanks to all one more time...
Most of the times I can open Outlook without any problems, but sometimes I am getting pop-up message saying that Exchange Server is unavailable (which is weird enough), but even when I can open Outlook, Journaling Service does not work :(
My current plan is to install another Exchange Server in the remote site with no SP1 for Windows 2003 and see how it goes...
Maybe I'm crazy, but I do think that upgrading to SP1 for OS broke some permissions...
In a meantime, I'm going on vacation until next year, so
THANK YOU once again for the support...
I will let you know results of my test next year...
-Victor

Matthew Edwards's picture

Have a good holiday.

I think we should try to keep this thread going in your absence.... it's already turning into an epic. People may starting loosing interest otherwise! ;)

David Messenger 2's picture

Can't contact Exchange. Either the IP connectivity is being blocked (firewall) or the name resoultion is up the wall. I assume Outlook 2003 so it's looking for it's own GC. Presume the serv's DNS points to the Domain holding the EV server rather than the one with the Exc box in it. Check what GC you are binding to and then look at the zone transfers for it and try a few and tracerts.

TonySterling's picture

You could try creating the Journal service using the FQDN for that exchange server.

additionally, you say you have this for profiles:

Also I have 2 profiles "VaultMbxAgent-badserver-..."

Besides that I have
16 profiles "VaultMbxAgent-goodserver1-..."
35 profiles "VaultMbxAgent-oldserver1-..."
1 profile "VaultMbxAgent-oldserver2-..."
11 profiles "VaultMbxAgent-goodserver2-..."

you could set the ProfileExpiry registry key to 0 and restart all the services. It is under HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault\Agents\
This should clear out the profiles that are left there.
Be sure to set it back to 3 or what ever it was after you are done and restart the services again.

If it doesn't get rid of the old ones you can delete them manually. I believe they are under HKEY_CURRENT_USER\Software\Microsoft\Windows NT\Current Version\Windows Messaging Subsystem\Profiles

Message was edited by:
A WSMessage was edited by:
A WS

David Messenger 2's picture

Can't remember where we are at withy this one but there is a bug in EV5 SP6 for Exchange running on Win2k SP1. Here is the release text for SP6:

http://seer.support.veritas.com/docs/280664.htm

Victor Geyyer's picture

Hi all,
I opened that thread and I feel appropriate for me to close it... :)
My planned worked... We installed the Exchange 2003 SP1 on Windows 2003 NO SP1 Server in the remote site and configured Journaling Service for mailbox on that server and it WORKS...
Thanks to everyone for sticking around...
-Victor

SOLUTION