Bug


December 28, 2006: 5:37 pm: hcanoBug, Exchange, How-To, Outlook, SySAdmin, Windows

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

April 9, 2006: 10:25 pm: hcanoBug, Exchange, How-To, SySAdmin, Technology, Windows

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.

OAB-Browse

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/

February 9, 2006: 1:04 am: hcanoBug, Errors, SySAdmin, Technology, Windows

When you open the Group Policy Editor you receive the following error “The following entry in the [strings] section is too long and has been truncated”.

This is a harmless error, dont worry.

What really happened is that the policies was upgraded with an .adm file, or by upgrading the Domain Controlers.

You can just press enter (several times) or install the hotfix on the KB 842933

This Hotfix on the KB 842933 was tested on Windows Server 2003 SP1 DC just upgraded from 2000 Domain Controlers.

If you have another question or issues enter in our forum we are friendly :)