Ever since we got Outlook Anywhere working on our Exchange Server 2007, we have been getting an error in the application event log:Log Name: ApplicationSource: MSExchange RPC Over HTTP AutoconfigDate: 1/28/2009 9:47:18 AMEvent ID: 2007Task Category: GeneralLevel: ErrorKeywords: ClassicUser: N/AComputer: exchange-2007.blood-horse.localDescription:The configuration application APPCMD.EXE failed with exit code 1346. Command parameters:list config "Default Web Site/Rpc/" -Section:system.WebServer/ServerRuntime.When I run %systemroot%\system32\inetsrv\appcmd with the above from a command prompt, everything seems to work fine. However, when I run it from the %systemroot%\SysWOW64\inetsrv\appcmd, it fails with the following:INFO ( timetaken:187, hresult:80070003, objects:0 )ERROR ( message:Configuration errorFilename: \\?\C:\Windows\System32\RpcProxy\web.configLine Number: 0Description: Cannot read configuration file. )This kind of makes sense to me because the RpcProxy folder doesn't exist in 64bit. My questions are:Is MSExchange RPC Over HTTP Autoconfig using the SysWOW64 appcmd?Is there any way to tell it to use the System32 version to stop this error?We are running Windows Server 2008 with IIS7. Everything seems to be working fine, even Outlook Anywhere. I just like a clean application event log. Any help is much apprediated!

Do you have a web.config file at all in your vDir? I am having the same error after trying to resolve a problem with the Service host.

I thought of this myself. I generated one using the %systemroot%\system32\inetsrv\appcmd and placed it in RpcProxy folder. At best I was hoping for a different error. No luck though. It still tells me it can not read the file. I really think this boils down to the fact that x64 doesn't technically have RpcProxy folder. Just open up a %systemroot%\SysWOW64\cmd.exe and> cd \Windows\System32> dir rpc*There is no RpcProxy folder. I even tried creating the RpcProxy folder and sticking a web.config in there while I was in the SysWOW64 cmd. I still got the same errror. I've been googling this for the last two days and still no luck in finding an answer.

After some more research, I think the error is related to some type impersonation. On MSDN I found a list of exit codes and it listed this:1346: Either a required impersonation level was not provided, or the provided impersonation level is invalid.So now I'm looking down another path. I'm pretty sure MSExchange RPC Over HTTP Autoconfig is calling the correct appcmd.exe, it just can't do what it needs to do. I'm certain there is some setting somewhere that can fix this. Just got to find it.

Looking at the error message in the event viewer: The configuration application APPCMD.EXE failed with exit code 1346. Command parameters:list config "SBS Web Applications/Rpc/" -Section:system.WebServer/ServerRuntime. I really think this error exists because it can't find the web.config file. I have been checking out the other folders in IIS. They (almost) all got a web.config file. And since the 32bit appcmd.exe doesn't generate any errors it can only come from the 64bit appcmd.exe. Correct me if I am wrong. Since I don't know how to build a web.config file I can't get any further. I am also very sure that MS exchange is calling the right appcmd.exe. It just needs to be able to read a configuration or some sort. Maybe a MS exchange pro can clarify some things.

I'm pretty sure that this is some obscure permissions issue somewhere. Our lab exchange 2007 server, from which we based our production machine, does not have this issue. I think I know what it is trying to do when this command fails. It is checking to see if appConcurrentRequestLimit="65535" for the "Default Web Site/Rpc". If it is not set, it will run appcmd set config to make it so. I set this manually on our production server. There may be more setup that goes on, but this is the only difference between our lab and production servers I can currently find. Still looking for a solution.

I have figured out why this error is occurring, but not how it happened or exactly how to fix it.I correlated the time stamps from the Application Events with the Security Events. Here is the culprit:Account Whose Credentials Were Used: Account Name: busoftware Account Domain: DOMAIN-NAME Logon GUID: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}Target Server: Target Server Name: localhost Additional Information: localhostProcess Information: Process ID: 0x17fc Process Name: C:\Windows\System32\inetsrv\appcmd.exeWe use Arcsever Backup 12 Exchange agent for information store and brick-level backups. That is the only difference between our lab and production server. So now I know why it's happening. I just need to figure out the how's and why's. I guess my first start is to uninstall the agent and see where that takes me.

Obscure it was. Answer I found.It had nothing to do with the backup agent. Just my own stupidity. In diagnosing a completely separate problem, I went in to the advanced settings of the Default Web Site and set the "Physical Path Credentials" to that of DOMAIN-NAME\busoftware. I had completely forgotten about it. I went in to IIS7 and removed the credentials setting, restarted the Microsoft Exchange Service Host, and away went Event ID 2007.

Thank you man...this resolved my prolbem right away!!! I'm hoping this also resolves some of my other problems I've been having with Oulook "Offline Address Book" ("ask 'Microsoft Exchange Server' reported error (0x8004010F) : 'The operation failed. An object could not be found.'") and my ActiveSyn errors, but at least, one less problem to resolved.

magallz1, I am a little lost. Was that in IIS manager where you made changes to the Default website? I am new to Exhange. Thanks for the help.