www.geekadmin.com

You got the error “Process INETINFO.EXE (PID=1748). Topology Discovery failed, error 0×8007077f. ”
On your event viewer after you changed the IP from your server, and you don´t know what is it.
This error can appear on DSQuery, OWA, OMA and others Exchange 2003 and 2007 Servers.
What this error means?
It means the Exchange Server doesn´t know wich site it is located.
There is a great possibility you don´t include the new subnet on the list of your sites..
So Let´s fix It.

1. Open Active Directory Sites and Services
2. Go to Subnets

Check if your new IP has an subnet there. If not Include it.

3. Include the new subnet (remember class c = 255.255.255.0)

4. Wait 15 minutes or replicate the server manually.

I restart the server just to make sure he gets the new info.

After that your problems should go away
Any more questions enter in the forum.

Your fellow users, start to get their vacations and complain about this error on Outlook 2003 or 2007.

So what you do now?

This is a tricky problem, frequently this is an error on your local Outlook profile, If you go to the OWA everything will work without problem.

You may try running Outlook with the /cleanrules swith or just delete the .ost files and start a new perfil.

Remember .OST files. This files are created for the outlook cache function.

If you havy any comments or questions please visit our forum

http://www.geekadmin.com/forums

Usually this errors occurs when the client Outlook 2000/2003 didn´t receive the Offline Address Book (OAB) correctly or it is missing.

The main reasons for this are: corrupted OAB or missing OAB server file.

When the OAB is corrupted by some reason you must do a Rebuil this is very simple follow this steps:

1. Open the Exchange System Manager;
2. Go in the Recipients folders
3. Go in Offline Address List
4. Right Click and select REBUILD

Look on the application log, for the success rebuild of the address list.

If this doesnt fix your problem, maybe you just change or upgrade your Exchange Servers and the clients are still looking for the OAB on the wrong servers.

Each storage group has a location for the OAB, you must check this.

Follow this steps to check and fix:

1. Open the Exchange System Manager;
2. Open Servers;
3. Choose your server;
4. Choose your storage group;
5. Right click and select proprierities;
6. Check if there is a server like in the picture below.

If this fix your problem, please let me know. And if you have more suggestions we have now a forum for you! A friendly forum dont be shy

url for the forum http://www.geekadmin.com/forums/

How to Create a New Offline Address Book(OAB) o­n exchange
The Offline Address Book is used by the client o­n the cached mode, and inside it has a lot more about the users than o­nly the name and e-mail.

Certificates, email-systems and routing are included too o­n the Offline Address Book. A lot of problems happens because the Exchange Admin change something o­n the user, but the client has a old Offline address book being used.

To rebuild the Offline Address Book is very easy.Go to the Exchange System Manager –> Open recipients –> Open Offline Address Book and Right Click o­n the Default Offile Address Book, and Select REBUILD.

It will give a warning about the heavy load, but don´t worry.

Check the application log to see if it is already finished ok.The client MUST click o­n send and receive to download the new Address Book.

This error is very common now in larger networks and in this times of large mailboxes and frenetic users using their OutLook Rules.So whois to Blame?

OutLook and Exchange Server are the guilty.

The rules are composed by two parts: the properties of the rules and the recipients and conditions of the rules. Its common a rule use 900 bytes or 1kb of space. So if you have 32 of these you exceed the limit space for each folder. You can use 32kb in each folder, but usually the user uses the rules o­n the inbox.Solution?

Use distribution Lists (1 DL is o­ne recipient) and reduce the number of rules and conditions.If you want more information see this KB 241325