Problems Adding Exchange Profile on W2K box 1

[SATech]

I've probably setup over a thousand email profiles in the past few years but had a problem stop me dead in my tracks this week.

System Desc: Dell GX400, 1.4Ghz, W2KSP2, O2KSP2.

User 'A' was setup just fine Monday. He proceeded to install the Disk 2 setup for O2Kpro. Once setup was completed successfully, user rebooted and got an ad*.dll (can't remember the name exactly) error that mentioned that "The entry point could not be found...". I had to run the setup upgrade option from the W2K source disk to recover from it. Once complete, everything looked fine and dandy. User 'A' could log on to the LAN (TCP/IP), access Internet, server resources, etc.. ONLY problem was that when he opened Outlook, a message prompted him for his Exchange server. When server is typed in, the following message appears:

"The name could not be resolved. The Microsoft Exchange Address Book was unable to log on to the Microsoft Exchange Server computer. Contact you system administrator (that would be me) if the problem persists"

Well, sounds simple enough initially, but about 8 hrs over 3 days later I haven't gotten ANYWHERE! This isn't user specific, as anyone that logs on to the machine and attempts to create email profile gets the SAME message. User 'A' can check their email just fine from the computer next to this one. Up to now I have refused the suggestion to wipe the box clean because of a minor (or not) email problem but I may not have a choice. Here's what I've done thus far:

1. Ran repair option for Outlook 2K
2. Uninstalled/Re-installed Outlook 2K
3. Uninstalled/reinstalled Office 2K
4. Checked and rechecked TCP/IP settings
5. Pinged the Exchange Server successfully
6. Re-ran W2K setup (upgrade option)
7. Removed from and re-added the PC to the domain
8. Ensured the Computer name was listed in the exchange server manager.

OK...before I resort to reloading the box and possibly never know the cause of the problem, I'm open for suggestions to help me from going stir crazy!

Thanks in advance!

________
S. Joseph Vergara

 

[iowtech]

This sounds like it could be a name resolution issue. I know you've done this but.... From a command prompt type: ipconfig /all and compare settings with another machine who has no problem line by line.

When you say you can ping the exchange server, is that by name or by IP. If it is by name, does it resolve the correct IP?

Try adding a static entry to \winnt\system32\drivers\etc\hosts for the exchange server.

Is there a router/firewall etc between you and the exchange server? If so, are they blocking any ports?

Outlook connects to exchange through port 135 then exchange assigns to random port numbers which the client then uses.

Therefore, can you connect to port 135 on the exchange server? You can use telnet to check but you will need to kill telnet through task manager if you are successful!

From a command prompt type:

telnet <exchange server name> 135

If you get a clear screen with a flashing cursor, you can connect. If it says connect failed, that is your problem.

To get rid of the flashing cursor, kill telnet from task manager (messy I know)

Let me know how you get on.

 

[pbxman]

Sounds like your using the &quot;internet only&quot; option in outlook which uses SMTP instead of friendly name resolution.

On a domain - you should be using the &quot;Corporate or Workgroup&quot; option instead. Try that first..

Go to &quot;Help&quot; and &quot;About Microsoft Outlook&quot;
your installation option will be listed right under the first line.

Hope that works for ya.. Please let Tek-Tips members know their posts were helpful. Thanks!

Pbxman
Systems Administrator

 

[SATech]

Thanks for the insight folks...but I still have the problem.

iowtech: In response to your questions above, yes I can ping with the server/IP resolving correctly; Added the server to hosts file; No router/firewall blocks exist; Telneting to server on port 135 returns clear screen/flashing cursor.

pbxman: Exchange services option wouldn't be available if I didn't have &quot;Corporate or Workgroup&quot; selected. But you got me thinking about whether or not it was corrupted. I removed it from &quot;Corporate or Workgroup&quot; and selected &quot;Internet Only&quot; applied it, and then readded &quot;Corporate or Workgroup&quot;. No luck.

Update to what else I've done:
9. Removed PC to another building on a different segment of the network.
10. At new location, changed IP address, computer name, WINS/DNS.
11. Re-installed W2K SP2, Critical Updates, and W2K compatibilities update from WindowsUpdate

Have..plug....clutched..firmly.......in.......hand......T-10 seconds...and counting!

________
S. Joseph Vergara
SVergara@Texas.net

 

[pbxman]

why not use a clean install of office? Why was a user installing software anyway?

I'd wipe office out completely, and re-install it..or have you done this already? Please let Tek-Tips members know their posts were helpful. Thanks!

Pbxman
Systems Administrator

 

[SATech]

Yes (see step 3 above). I gave this experienced user permission to install 'Disk 2' of O2Kpro so that he could have MS Publisher. ________
S. Joseph Vergara
SVergara@Texas.net

 

[pbxman]

Oh - sorry about that one - i missed that step!
(doh!)

Have you tried deleting all .msi and Office 2000 text files out of the Temp directory after uninstalling Office? If those are not deleted, a &quot;clean&quot; re-install is not possible since it marks key configuration settings in them.

I always keep office on a network share so disks aren't needed, and choose &quot;run all from my computer&quot; to install office. It's much easier to add/remove features without trouble this way.

If that doesn't work - why not use this opportunity to flush & rebuild? As soon as my systems get errors like these - i re-install the OS and build from scratch. My outlook (no pun intended) is - if it's complaining about errors after an installation & reboot - too many chances for corruption & headaches are soon to follow.

If it's broke - fix it...if you cant fix it - build a brand-spankin new one..


Good luck Please let Tek-Tips members know their posts were helpful. Thanks!

Pbxman
Systems Administrator

 

[SATech]

...and rebuild I did and 2 hrs later the user was ready to log on business as usual. I've concluded that the problem resided in the registry - and when we are talking about W2K/O2K problems it's like finding that one special grain of sand on miles of beach.

As a consolation, I've exported the event logs for an autopsy to determine the cause of death at a later date.

Thanks to all who hung tough until the bitter end...oh, and pbxman...enough begging already - HERE'S YOUR STAR! yawnnnn <signing out> ________
S. Joseph Vergara
SVergara@Texas.net