Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Exchange application event log error 8197

0 views
Skip to first unread message

kcds49

unread,
Feb 16, 2006, 4:14:11 AM2/16/06
to
I did a swing migration over the weekend.
The application event log is now showing the following error every 25
minutes:

Event Type: Error
Event Source: MSExchangeFBPublish
Event Category: General
Event ID: 8197
Date: 2/15/2006
Time: 11:34:58 PM
User: N/A
Computer: ML350G3
Description:
Error initializing session for virtual machine (Servername). The error
number is 0x8004011d. Make sure Microsoft Exchange Store is running.

For more information, click http://www.microsoft.com/contentredirect.asp.
---------------------------

The Exchange server appears to be running OK.

Any ideas?


Steven Zhu [MSFT]

unread,
Feb 20, 2006, 4:33:42 AM2/20/06
to
Hi,

Thanks for posting here.

From your post, I understand that you receive the following error message
every 25 minutes in the application log after you have done migration.


Event Type: Error
Event Source: MSExchangeFBPublish
Event Category: General
Event ID: 8197
Date: 2/15/2006
Time: 11:34:58 PM
User: N/A
Computer: ML350G3
Description:
Error initializing session for virtual machine (Servername). The error
number is 0x8004011d. Make sure Microsoft Exchange Store is running.

For more information, click http://www.microsoft.com/contentredirect.asp.
---------------------------

If I am off base, please feel free to let me know.

Based on my research, this issue may be occur if the relevant registry key
contains an invalid DS Server value that is specified with the name of a
particular domain controller/global catalog server. The relevant registry
key is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange Provider\DS Server

To resolve this behavior, delete the DS Server value from the Exchange
Provider key. Make sure that you remove the entire value from the key, not
just the value data. Follow these steps:
NOTE: Please export original KEY for a backup before you delete it.

1. Start Registry Editor (Regedt32.exe).

2. Locate the DS Server value under the following key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange Provider

3. Click DS Server, click Edit, and then click Delete. Click yes to confirm
the deletion.

4. Quit Registry Editor.

5. Please restart the Global Catalog server and the Exchange Server for the
change to take effect.

I hope the above information helps.

Have a nice day.

Best Regards,

Steven Zhu
MCSE
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng2006 when prompted. Once you have entered the
secure code mmpng2006, you will be able to update your profile and access
the partner newsgroups.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================


kcds49

unread,
Feb 20, 2006, 10:00:36 AM2/20/06
to
Thanks for your reply.
In the registry entry

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange Provider\DS Server
I find only one key, Rpc_Svr_Binding_Order, its value is
ncacn_ip_tcp.ncacn_vns_spp.


"Steven Zhu [MSFT]" <v-st...@online.microsoft.com> wrote in message
news:%23agx9Cg...@TK2MSFTNGXA01.phx.gbl...

Steven Zhu [MSFT]

unread,
Feb 20, 2006, 10:41:42 PM2/20/06
to
Hi,

Thanks for taking time respond.

I think the issue may be occur if the relevant registry key contains an

invalid DS Server value that is specified with the name of a particular
domain controller/global catalog server. The relevant registry key is:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\ExchangeProvider\DS Server

So please confirm you already deleted this key.

I am looking forward to your reply.

kcds49

unread,
Feb 20, 2006, 11:44:58 PM2/20/06
to
I did not delete the key, I could not find it as described, it does not
exist within
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\ExchangeProvider.

Thanks for you assistance.


"Steven Zhu [MSFT]" <v-st...@online.microsoft.com> wrote in message

news:Y9dD9ip...@TK2MSFTNGXA01.phx.gbl...

Steven Zhu [MSFT]

unread,
Feb 21, 2006, 4:10:00 AM2/21/06
to
Hi,

Thanks for taking time to respond.

From your reply, I understand that you do not find the following registry
key:


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\ExchangeProvider\DS Server

And the issue still exists. If I am off base, please feel free to let me
know.

According to my experience, please check if the information store service
is starting correctly and the databases are mounted correctly. If the
databases are mounted correctly, then I'd recommend you to reboot the GCs
in the environment and then the Exchange server.

Also, since Exchange Server is a member server, therefore, the
LMCompatibilityLevel registry key should never be above level 3. Please try
the following steps to check the key:

1. Start Registry Editor (Regedit.exe) on the Exchange Server.
2. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control
3. Check the following registry value:
Value Name: LMCompatibilitylevel
Data Type: REG_DWORD
Value: 2
4. Quit Registry Editor.
5. Restart the server and monitor the issue again.

If the problem persists, please send me the MPSReport for further analysis:

"http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd
915706/MPSRPT_Exchange.EXE"

You can send me the files to my working email address:
v-st...@microsoft.com

Please let me know the above information so that I can provide further
assistance on this problem. I am looking forward to your reply.

kcds49

unread,
Mar 6, 2006, 10:39:41 AM3/6/06
to
The information you are directing me to locate does not exist on this
server.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control, value name:
LMCompatibilitylevel

This server is a Small Business Server 2003, it is not a member server
The following shows up in the event log every 25 minutes with a red X:
----------------------------------------------------------------------------
----------------


Event Type: Error
Event Source: MSExchangeFBPublish
Event Category: General
Event ID: 8197

Date: 3/6/2006
Time: 9:08:52 AM
User: N/A
Computer: (server name)
Description:
Error initializing session for virtual machine (server name). The error


number is 0x8004011d. Make sure Microsoft Exchange Store is running.

----------------------------------------------------------------------------
----------------

"Steven Zhu [MSFT]" <v-st...@online.microsoft.com> wrote in message

news:dsgVbas...@TK2MSFTNGXA01.phx.gbl...

Steven Zhu [MSFT]

unread,
Mar 7, 2006, 2:10:13 AM3/7/06
to
Hi,

Thanks for posting here.

From your post, I understand that you don't find the LMCompatibilitylevel
under the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control. Please add
this registry value:

1. Start Registry Editor (Regedit.exe) on the Exchange Server.
2. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control

3. Add the following registry value:


Value Name: LMCompatibilitylevel
Data Type: REG_DWORD
Value: 2
4. Quit Registry Editor.
5. Restart the server and monitor the issue again.

Please let me know the result above so that I can provide further

assistance on this problem. I am looking forward to your reply.

Have a nice day.

Best Regards,

Steven Zhu
MCSE
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
======================================================

PLEASE NOTE the newsgroup SECURE CODE and PASSWORD were
updated on February 14, 2006.? Please complete a re-registration process
by entering the secure code mmpng06 when prompted. Once you have
entered the secure code mmpng06, you will be able to update your profile

0 new messages