How do I get Win7 & Outlook 2003 to connect to Exchange Server
Finally was able to get a Win 7 box to start checking compatibility and other issues of programs we use on a day-to-day basis. Most of our programs don't seem to have many issues as far as those that I have run on this box. I installed MS Office 2003 Sp3 and everything there seems to work. Outlook even seems to work mostly except when I try to setup an Exchange Server 2003 mail account in Outlook, the account exists on the server (it's my account!). I keep getting the message "There was an error locating one of the items needed to complete this operation. It might have been deleted". This is what I get when I just put in the server name and user name then click the "check name" box. If I type in the full server & domain name and the full user name and click next or more settings options I get "The account you have added is not fully configured. It might not work properly until re-configured correctly." And I can only hit cancel from here, it won't let me proceed any further. I have checked the event logs for any errors and warnings and found these: Application Event Log - Warning Security policies were propagated with warning. 0x534 : No mapping between account names and security IDs was done. Advanced help for this problem is available on http://support.microsoft.com. Query for "troubleshooting 1202 events". Error 0x534 occurs when a user account in one or more Group Policy objects (GPOs) could not be resolved to a SID. This error is possibly caused by a mistyped or deleted user account referenced in either the User Rights or Restricted Groups branch of a GPO. To resolve this event, contact an administrator in the domain to perform the following actions: System Event Log - Error The SNMP Service encountered an error while accessing the registry key SYSTEM\CurrentControlSet\Services\SNMP\Parameters\ TrapConfiguration. The Application log event gives steps to follow to correct the issue but about half way through the actual options in the mmc console veer off from what you're supposed to have according to the event log instructions. Following the Event Log Online help comes up with the "No results were found for your query" message. The accounts causing the issues are the IUSR & IWAM user accounts but I cannot find those on the computer in question, just on the domain servers. I have searched Technet and some other forums and found 2 other questions/queries similar to this but their solutions were of no help. I'm using Windows 7 Professional 32 bit and the computer is joined to the local domain. Thanks Joey P.S. I did install SP1 last week and that did not make any difference. Same messages before & after installation of SP1.
March 30th, 2011 6:31pm

There's a problem with the way your computer is joined to the domain. Remove it from the domain, give the DCs a few minutes to replicate any changes then make sure its account no longer appears in Active Directory Users and Computers - delete it manually if necessary and wait for the DCs to replicate again (or force the replication manually) - then rejoin the domain and try again.
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2011 6:52pm

Thanks for the reply Bob, That didn't seem to work. Even after I removed the computer from the Domain and deleted the computer's domain account and waited a day before rejoining it to the domain. I did a different search on MS support site than what I had previously done and found 3 documents very similar to my issue I am going to research these some and see if they can shed a little light on the problem. Thanks Joey
March 31st, 2011 6:58pm

Would these issues be what is keeping Outlook from properly connecting to Exchange? Okay one of the Docs ( Q324383) told how to create the winlogon.log to get all the details of the issues. I know it was for Win2K but this is the closest doc to the issue I have found so far. Here are the errors that repeatidly show up all through the log: Configure SERVERX\IWAM_SERVERX. Error 1332: No mapping between account names and security IDs was done. Cannot find SERVERX\IWAM_SERVERX. Configure SERVERX\IUSR_SERVERX. Error 1332: No mapping between account names and security IDs was done. Cannot find SERVERX\IUSR_SERVER1. Configure SERVERX\ASPNET. Error 1332: No mapping between account names and security IDs was done. Cannot find SERVERX\ASPNET. And Configure SERVERX\IWAM_SERVERX. Error 1789: The trust relationship between this workstation and the primary domain failed. Cannot find SERVERX\IWAM_SERVERX. Configure SERVERX\IUSR_SERVERX. Error 1789: The trust relationship between this workstation and the primary domain failed. Cannot find SERVERX\IUSR_SERVERX. Configure SERVERX\ASPNET. Error 1789: The trust relationship between this workstation and the primary domain failed. Cannot find SERVERX\ASPNET. The Document told how to fix the problem on an actual user account but aren't these System accounts on the server? And the Doc talks like it is most often a typo in account names that causes this issue. But it could also be a group policy issue. I'll continue researching this, but if anyone has some ideas or links to pertinent articles I would be very appreciative. Thanks Joey
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2011 7:27pm

Hi Joey, From your description, it is better to find the answer through Exchange Forum. Exchange Forum http://social.technet.microsoft.com/Forums/en/category/exchangeserver From Windows 7 side, please understand if you recreate the new account with the previous name, its corresponding registry is difference. Make sure Windows 7 can ping Exchange Server successfully. Best Regards, NikiPlease remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
April 1st, 2011 5:46am

These errors show that Windows 7 is not properly joined to your domain. The only time I've seen similar errors is when I tried to join a Windows 7 machine to a Windows 2000 domain. It would say it was properly joined, but the account mapping errors prevented me from actually using any domain resources - like Exchange. Upgrading my domain to Windows 2003 solved this, but now that I think back I may just have needed to add the W2k3 AD extensions to make it work. I'm not saying this is your issue, since you didn't say what your domain level is, but you may be looking at something similar. Or you might just need to reinstall Windows 7 to replace missing components.
Free Windows Admin Tool Kit Click here and download it now
April 4th, 2011 4:00pm

Niki, Thanks for your reply, but I don't think this is an Exchange issue. From the few things I have been able to find it appears to be an account issue, either with the computer & the domain or as Bob pointed out below something missing/incomplete within the initial Windows 7 installation. I can ping the server without any errors, I can also connect to the server from this computer via RDP and browse via explorer and connect to printers on that server. ( hmm.. I haven't actually tried to use that printer yet. I will attempt that & see what happens.)Just because you can do something doesn't mean you should. Most times it is better to KISS (Keep It Simple Stupid!).
April 5th, 2011 12:02pm

Bob, I have a Win Server 2003 AD network. All of my other computers on this network are XP-SP3 and one I was working on the other day I saw the same errors in the App Event Log so I went and checked another computer, it also had the same errors. Neither of these computers has a problem connecting to Exchange. So what you're saying makes sense. I'll research that direction and see if I can find something. Thanks Joey Just because you can do something doesn't mean you should. Most times it is better to KISS (Keep It Simple Stupid!).
Free Windows Admin Tool Kit Click here and download it now
April 5th, 2011 12:08pm

Correction, I was doing some research and discovered I'm still running a Win2K AD Forest. I have one Win2K server I have been trying to retire but I found I still have it set as a Domain Controller. Bob, what AD extensions are you referring too? Is it a download from MS or is it something within Win7 the just needs installing/activating? I am going to see if there is any reason I still need that old server as a domain controller and if I can dcpromo it out! I still need it as a server for a little while for some software we're using, but I think if I can remove it as a domain controller it might solve some issues. JoeyJust because you can do something doesn't mean you should. Most times it is better to KISS (Keep It Simple Stupid!).
April 13th, 2011 6:52pm

They're on the Windows 2003 installation CD, but I don't remember where. The AD extensions are to allow a Windows 2000 domain to accept a Windows 2003 DC. If you have any W2k3 DCs at all then the extensions are already installed because you can't run a Windows 2003 DC on a native Windows 2000 domain. You're probably running as a hybrid, mixed-mode domain because you can't have W2k DCs on a native Windows 2003 domain either. After you remove the W2k DC you'll have to go into your AD domain and change it to a W2k3 functional level otherwise there's no point to removing the Windows 2000 DC. In case you're wondering, W2k can be a member server on a native W2k3 domain, just as W2k3 can be a member server on a W2k domain without the AD extensions (it just can't be a DC.)
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2011 7:15pm

Thanks Bob, Yes those were instaled when I setup my first W2K3 domain server a while back. I thought you meant something that was supposed to be installed on Win7, which there was under Programs - enable/disable Windows features. I figured out that wasn't the issue. I opened Word 2K3 and got a lot of weird error messages, most about version issues. I knew that Word and Outlook are closely tied so I went and looked at installed programs (Add/Remove) and found some components that I somehow missed when I uninstalled the pre-installed MSOffice 2K7 that came on this computer. So I uninstalled EVERY office component I could find in the installed programs list, rebooted the computer, re-installed my Office 2K3, applied the service packs and guess what Outlook works now! woohoo! Just think it's a bit strange that I got no errors when I was installing it the first time. Under XP & Vista if I missed uninstalling any of the pre-installed Office stuff I would get version conflict errors when installing the service packs. Thanks for your help!Just because you can do something doesn't mean you should. Most times it is better to KISS (Keep It Simple Stupid!).
April 18th, 2011 3:48pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics