General discussion

  • Creator
    Topic
  • #2073840

    help from Exchange experts needed

    Locked

    by soia ·

    Hello,

    I’ve got an NT4 server with Exchange 5.5
    Today someone tried to import an Excel sheet into his contacts. After 53000 records I killed this because everything went very slow. But then the trouble started. The machine is very slow due to excessive paging. i’ve rebooted the server a dozen times, added some RAM, enlarged the pagefile but nothing seemded to help. I don’t know much about exchange but is it possible the server is still cooping with that Excel import???? The situation at this point is that nobody can use Outlook because it’s slow or not responding, because the server’s too busy. Any help on this is appreciated!!!
    Thanks in advance,

    Chris

All Comments

  • Author
    Replies
    • #3785017

      help from Exchange experts needed

      by mckaytech ·

      In reply to help from Exchange experts needed

      I think you’re going to need to take the Exchange server off-line and do a repair on the Information Store. But see note below first and review the Event Log for signs and clues.

      But before you do that, you might want to try going into Exchange Administrator, highlight the server name, double-click on Directory Service and then click the Knowledge Consistency Checker button.

      It is possible that the Information Store is still trying to digest the 53,000 record import. However, there is alot at risk here and however much I would appreciate having the 3,000 points, I would rather see you open an incident with Microsoft Technical Support for this type of problem.

      paul

    • #3785010

      help from Exchange experts needed

      by steve cody ·

      In reply to help from Exchange experts needed

      You said that you rebooted the server “a dozen times”. I am hoping that you are doing a normal shutdown and reboot. If not, the server is doing an automatic repair of the Exchange database files. When you have the server booted, look in the EventViewer and look at the Application log. Look for entries for the Exchange Information Store, or System Attendant. Also, check the services on the server and see if all of the Exchange services have started. If they have not, then the server may be busy repairing itself. Also, look for any errors relating to Exchange, in the Application log.

      One note on rebooting. It is a good practice on an Exchange Server computer to stop all of the Exchange services PRIOR to attempting a shutdown. This will allow you to shut down your server without waiting 15 to 30 minutes or so.
      I hope this gives you some info. If you need more help, or have other information, feel free to email me. It would be nice to see any App log errors that you may have.

      Steve Cody, MC

    • #3785006

      help from Exchange experts needed

      by steve cody ·

      In reply to help from Exchange experts needed

      One more thing….

      If, in fact, the server is just doing maintenance to repair itself because of improper shutdown, you just have to wait for the services to start up. Also, check the Task Manager and see what Exchange processes have high utilization.

      If my assumption is wrong, and the problem is related to paging, then you can run the Exchange Optimizer and limit the amount of RAM that the I.S. will use. Give that a try and it might fix you up.

      Steve Cody, MCSE

    • #3783130

      help from Exchange experts needed

      by csu_tech ·

      In reply to help from Exchange experts needed

      I have to assume that the information store is just trying to recover itself from the amount of data that was attempted to import that Excel sheet. It may be a good idea to run isinteg.exe to check and possibly corrrect the problem in the information store. You she definately take the server offline and run the eseutil.exe. This is the Offline Defrag Tool that may help clear up alot of the fragmentation that took place when the file import was run and then aborted.

      Jason
      MCSE

    • #3783059

      help from Exchange experts needed

      by viperian ·

      In reply to help from Exchange experts needed

      I had some same problem a year ago. By a corrupt csv template the database grew more than 400 %. By using ESEUTIL i fixed the problem by first repairing and than defragmentating.

      If you interrupt a import of a csv template you stand the change of corrupting the priv.edb database. You can take the exchange server offline and try to repair and check the database. Microsoft Exchange Server 5.5 includes a utility called Eseutil, this utility can Defragmentate, Recover, Check Integrity, Upgrade,make a file Dump and Repair a corrupted database.

      By repairing and defragmetation you can regain your speed. If the database is for example 2Gb in space you will need at least 2GB free space for a repair and an defragmetation.

      For more information about eseutil see technet article Q182903.

      Good luck.

    • #3784544

      help from Exchange experts needed

      by starkc ·

      In reply to help from Exchange experts needed

      Microsoft Exchange Server 5.5 includes a utility called Eseutil, this utility can Defragmentate, Recover, Check Integrity, Upgrade, make a file Dump and Repair a corrupted database.

    • #3784302

      help from Exchange experts needed

      by reinaldo.velez ·

      In reply to help from Exchange experts needed

      You have to check your config.sys and autoexec.bat these two files have to be empty. Some time if you have large instructions in any of these file the will work slowly.

    • #3783811

      help from Exchange experts needed

      by philanderson ·

      In reply to help from Exchange experts needed

      Just a comment to the guy saying “empty your conifg.sys etc…”
      What are you talking about? or smoking…
      to the guy with the question- DO NOT empty those files…DUH…good luck.

Viewing 7 reply threads