Improve company productivity with a Business Account.Sign Up

x
?
Solved

Sending from Exchange 2003

Posted on 2015-01-02
10
Medium Priority
?
53 Views
Last Modified: 2016-06-20
We have been wrestling with a move of MS Exchange to another server.  Because of many glitches it has been decided to move it back, but having done that, the email is failing to send from any workstation.

Is there a check list of things that might need setting?

I can Telnet out from the server and the internet is connecting fine.  We have not had any incoming emails either, so maybe both have been affected, I've just been concentrating on the outgoing.

Thanks for your help
0
Comment
Question by:CarmeldanIT
  • 4
  • 4
9 Comments
 
LVL 18

Expert Comment

by:Ivan
ID: 40528453
Hi,

if you moved mail server "back", have you reconfigured firewall/ nat, so that email will bi directed to mail server?
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40528812
We have been wrestling with a move of MS Exchange to another server.  Because of many glitches it has been decided to move it back, but having done that, the email is failing to send from any workstation.

Hi CarmeldanIT,

What process were you using to move the mail? Was it a new server? Were you P2V it into a virtual environment? Were you upgrading to a newer version of Exchange? Need more info to adequately answer.
0
 

Author Comment

by:CarmeldanIT
ID: 40528864
Hi,  Thanks for your replies.

We were trying to keep it simple!!!

The same version SBS 2003 was on both servers and planning to use the preconfigured server instead of re-installing because of software issues.  The transfer method was using PST file backup on workstations and then restoring to the new Exchange server.  This went though in both directions.  

To keep the NAT settings on the router the same, we changed the IP addresses of the servers so the routing would happen without changing the router.

I have received two NDRs from the server to a couple of test emails I sent from my office PC, so the Exchange server can send, but appears not to be processing emails internally.  

When trying to send from a user, the internal bounce back message says: -
 'phil-smith@inet-synergy.co.uk' on 03/01/2015 08:59            This
message could not be sent. Try sending the message again later, or
contact your network administrator.  Error is
[0x80004005-00000000-00000000].

It seems to refer to synchronisation issues, but I cannot see any way of dealing with this.  

I have changed the profile on the workstation, but as all emails are affected for all workstations suspect the problem is at the server end.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40529049
The same version SBS 2003 was on both servers and planning to use the preconfigured server instead of re-installing because of software issues.  The transfer method was using PST file backup on workstations and then restoring to the new Exchange server.  This went though in both directions.

So you created a brand new forest and domain? Or, did you follow the article of moving SBS to new hardware and kept the existing domain and forest?

Migrating SBS 2003 to New Hardware.
http://technet.microsoft.com/en-us/library/cc747454(v=ws.10).aspx
0
 

Author Comment

by:CarmeldanIT
ID: 40529158
No we used the existing domain.

THe point now is to make the Exchange work on the server it was working on before.  The reason for mentioning the other server was to explain what had happened.

We now want to make the email work on the old server as it was working, but for some reason Outlook and OWA users cannot access it.  The send receive says it is completing the task but nothing is received and send items are bounced back to the user within seconds.

I am seeing  events relating to Activesync and Bad pages, so wondering if this is the reason and whether I need to run a repair.  The Isinteg option doesn't run successfully so looking for alternatives?
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40529161
Can you confirm if all Exchange Services are started? Including the SMTP service and the WWW service?

When was the last time you rebooted the original server? Let's reboot it. Record Event Logs as soon as the server restarts. Likely the first few events post reboot are the key to all the failures.

What do you see when you try to browse to Outlook Web App from the server itself? (http://localhost/owa)

You mentioned you changed IPs. I assume the server name itself did not change? Sounds like no DNS changes were made externally as you made no firewall changes.
0
 

Author Comment

by:CarmeldanIT
ID: 40529336
Hi Gareth,

All the Exchange services are started.  There is no SMTP or www service in the services list.  Is this in 2003 or just when you move to 2007 and later?  When I load OWA (http://192.168.112.5/Exchange) I am able to log in and see the OWA pages, but cannot see new emails or send an email.  

The server has been restarted about an hour ago, but I can restart it again.

No DNS changes were made externally.  The server names were not changed.

The Event log is showing an error: -
Information Store (800) First Storage Group: A bad page link (error
-338) has been detected in a B-Tree (ObjectId: 68, PgnoRoot: 2333) of
database G:\ExchDB1\priv1.edb (17768530 => 17795137, 17795140).

Do you think this is the cause of the whole issue?  Why it has suddenly happened is another question.

Suggested solution for this is to run the repair utility "isinteg" or restore from backup The backup was one of the reasons for change the server so that is not an option.  Running isinteg is not working at present so we are getting deeper into the mire.
0
 
LVL 31

Assisted Solution

by:Gareth Gudger
Gareth Gudger earned 2000 total points
ID: 40529350
With regard to the Information Store error, that is not good. That is an indication of database corruption. In ESM, does the Mailbox Store show as currently mounted? Or does it keep dismounting?

Antivirus could be interfering. Make sure your antivirus software is configured to exclude the database and log locations. Or, for testing, completely remove the antivirus software.

This could also be an indication that log files were moved or deleted prior to being committed to the database.

What happens when you run ESEUTIL /MH against the database. Does it indicate a Dirty Shutdown?

Open a command prompt, switch to the Exchange server bin directory and run the following command. Be sure to change the path to wherever your database is located.
ESEUTIL /mh x:\exchsrvr\mdbdata\priv.edb

Open in new window


Reference of that command and switch here.
http://technet.microsoft.com/en-us/library/aa997795(v=exchg.65).aspx
0
 

Accepted Solution

by:
CarmeldanIT earned 0 total points
ID: 40539677
Hi Gareth ,

Sorry to take so long to reply and thank you for your input.  We have had a painful week!

We ran Isinteg and ESEutil last week but the system failed after about 13 hours on the final process "Deleting..." which everyone says takes hours, but having waited hours it was a disappointment to get this error.  

As a result, we removed the old Mail Store along with the closing of all exchange tasks on the users AD records as well as removing the email addresses in the distribution groups and contacts.  We were then able to remove the old store and create a new one.

Fortunately the Backed up PST files were good and though a few emails were lost during this period, all of the rest seem to have been recovered.
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

This is a very interesting topic. Ransomware has been around for a while but has increased drastically over the last year or so.
In migration, Powershell can be a very crucial tool to achieve success and finalize projects within deadline or even fix issues. X500 or Legacy Exchange DN Attribute can cause lots of issue during the migration
Planning to migrate your EDB file(s) to a new or an existing Outlook PST file? This video will guide you how to convert EDB file(s) to PST. Besides this, it also describes, how one can easily search any item(s) from multiple folders or mailboxes…
Watch the video to know the process of migration of Exchange or Office 365 mailboxes in absence of MS Outlook. It is an eminent tool which can easily migrate Public, Archive user mailboxes from one another Exchange server and Office 365. Kernel Migr…

606 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question