Archive for the ‘Exchange 2007’ Category

e-Mail error codes

Tuesday, August 31st, 2010

Regardless of the e-mail client you use – whether Microsoft Outlook, Thunderbird, or even a webmail application – and your e-mail configuration – POP, IMAP, etc. – you have no doubt had your patience tried by innumerable bouncebacks, unreceived e-mails, and other frustrating denials of service.  The following error codes can help you diagnose precisely what the issue is, who’s to blame – and more importantly,  how to fix it…

Email Error Codes (format: x.x.x)

The 1st digit indicates if the response was good, bad, or incomplete

1 =The Command was accepted, but the action is pending confirmation of a reply
2 =The action was completed successfully
3= The command was accepted, but the action is pending receipt of further information.
4 =The command was not accepted and the requested action did not occur. These are usually because of a temporary error or condition and one should try resending the request again.
5 =The command was not accepted and the requested action did not occur. This is a permanent failure message. Something needs to be fixed before the action will work.

The second digit

0 Syntax=Usually refers to a syntax error occurring.
1 Information=Reply to a request for information.
2 Connections=Refers to the channel transmitting
3 or 4=Undefined
5=Indicate the status of the receiver’s mail system

x.x.x Email Error Codes

    x.1.x Codes

  • X.1.0 – Other address status
  • X.1.1 – Bad destination mailbox address
  • X.1.2 – Bad destination system address
  • X.1.3 – Bad destination mailbox address syntax
  • X.1.4 – Destination mailbox address ambiguous
  • X.1.5 – Destination mailbox address valid
  • X.1.6 – Mailbox has moved
  • X.1.7 – Bad sender’s mailbox address syntax
  • X.1.8 – Bad sender’s system address
  • x.2.x Codes

  • X.2.0 – Other or undefined mailbox status
  • X.2.1 – Mailbox disabled, not accepting messages
  • X.2.2 – Mailbox full
  • X.2.3 – Message length exceeds administrative limit
  • X.2.4 – Mailing list expansion issue
  • x.3.x Codes

  • X.3.0 – Other or undefined mail system status
  • X.3.1 – Mail system full
  • X.3.2 – System not accepting network messages
  • X.3.3 – System not capable of selected features
  • X.3.4 – Message too big for system
  • X.3.5 – System incorrectly configured
  • x.4.x Codes

  • X.4.0 – Other or undefined network or routing status
  • X.4.1 – No answer from host
  • X.4.2 – Bad connection
  • X.4.3 – Routing server failure
  • X.4.4 – Unable to routev
  • X.4.5 – Network congestion
  • X.4.6 – Routing loop detected
  • X.4.7 – Delivery time expired
  • x.5.x Codes

  • X.5.0 – Other or undefined protocol status
  • X.5.1 – Invalid command
  • X.5.2 – Syntax error
  • X.5.3 – Too many recipients
  • X.5.4 – Invalid command arguments
  • X.5.5 – Wrong protocol version
  • x.6.x Codes

  • X.6.0 – Other or undefined media error
  • X.6.1 – Media not supported
  • X.6.2 – Conversion required and prohibited
  • X.6.3 – Conversion required but not supported
  • X.6.4 – Conversion with loss performed
  • X.6.5 – Conversion failed
  • x.7.x Codes

  • X.7.0 – Other or undefined security status
  • X.7.1 – Delivery not authorized, message refused
  • X.7.2 – Mailing list expansion prohibited
  • X.7.3 – Security conversion required but not possible
  • X.7.4 – Security features not supported
  • X.7.5 – Cryptographic failure
  • X.7.6 – Cryptographic algorithm not supported
  • X.7.7 – Message integrity failure

 

xxx Email Error Codes

    200 Codes

  • 211 – System status / system help reply
  • 214 – Help message
  • 220 – Domain service ready
  • 221 – Service closing transmission channel
  • 250 – Requested mail action okay and completed
  • 251 – will forward to forwardpath
  • 252 – Pending messages for node started. Cannot Verify user, will take message for this user and attempt delivery
  • 253 – pending messages for node started
  • 300 Codes

  • 354 – Start mail input; end with . server is ready to accept the message
  • 355 – Octet-offset is the transaction offset
  • 400 Codes

  • 421 – Domain service not available, closing transmission channel
  • 432 – Domain service not available, closing transmission channel
  • 450 – Requested mail action not taken: mailbox unavailable. request refused
  • 451 – Requested action aborted: local error in processing
    Request is unable to be processed, try again
  • 452 – Requested action not taken: insufficient system storage
  • 453 – No mail
  • 454 – TLS not available due to temporary reason. Encryption required for requested authentication mechanism.
  • 458 – Unable to queue messages for node
  • 459 – node not allowed: reason
  • 500 Codes

  • 500 – server could not recognize the command due to a syntax error
  • 501 – Syntax error, no parameters allowed
  • 502 – Command not implemented
  • 503 – Bad sequence of commands
  • 504 – Command parameter not implemented
  • 510 – Check the recipient address
  • 512 – Host unknown. Domain can not be found.
  • 515 – Destination mailbox address invalid
  • 517 – Problem with senders mail attribute, check properties
  • 521 – Machine does not accept mail
  • 522 – Recipient has exceeded mailbox limit
  • 523 – Server or connector limit exceeded. Message too large
  • 530 – Must issue a STARTTLS command first. Encryption required for requested authentication mechanism
  • 531 – Mail system Full
  • 533 – Remote server has insufficient disk space to hold email
  • 534 – Authentication mechanism is too weak. Message too big
  • 535 – Multiple servers using same IP
  • 538 – Encryption required for requested authentication mechanism.
  • 540 – No DNS Server for email address
  • 541 – No answer from host
  • 542 – Bad Connection
  • 543 – Routing server failure. No available route
  • 546 – Email looping
  • 547 – Delivery time-out.
  • 550 – Requested action not taken: mailbox unavailable.
  • 551 – User not local; please try forwardpath
  • 552 – Requested mail action aborted: exceeded storage allocation
  • 553 – Requested action not taken: mailbox name not allowed
  • 554 – Transaction failed

‘Microsoft Outlook was not shut down properly’ error

Wednesday, August 25th, 2010

We have an extremely e-mail intensive brokerage client who, due to the nature of their business,  has about three-plus years of unarchived e-mails, 80,000-plus objects, and so on, for an average Microsoft Outlook user.  No wonder they recently contacted us because one of the users was receiving the always annoying ‘Outlook was not shut down properly’ error, prompting a never-ending scan each time he attempted to reopen the program.

The error was traced back to the user’s .ost file, which had become corrupt and entirely unwieldy.  The only thing to do at that point was to close Outlook, delete the .ost file in the local folder (located by default in Outlook 2003, Outlook 2007 and Outlook 2010 at C:|Users|USER|AppData|Local|Microsoft|Outlook|outlook.ost), then reopen Outlook and wait for the .ost to be recreated; six hours later, we moved onto the archive process; 10 hours and an Outlook-induced computer crash later (necessitating a trip to the site to confirm everything had completed) and it was good as new.

Tip of the day:  archive your e-mails on a regular basis; it’s not like you’re losing them.  Although Outlook doesn’t have a specific limit per se, it actually does have a limit to how many e-mails you can keep and still retain optimal functionality.

Microsoft Online Services Offering: BPOS is the ultimate in cloud connectivity

Friday, August 20th, 2010

People have been talking about cloud computing, cloud storage, cloud networking – and on and on – for some time now, but with its newest offering, Business Productivity Online Suite (BPOS),  Microsoft Online Services has set the standard for cloud connectivity, encompassing computing, storage, networking, and pretty much anything else you could wish for.  The functionality of Office mainstays like Exchange, Communicator and SharePoint are included and integrated so it’s actually more like using one all-inclusive application instead of many.

 

After sign-in, the icon for the application stays open on your toolbar and you simply right-click to access any of the included services.  The company portal is also accessible and allows you to download necessary software (for instance, .Net is a requirement for BPOS) and enter SharePoint intranet sites and Live Meeting rooms.

Live Meeting has some particularly cool options, including the ability to record audio and video, view all attendees in panorama view (making everyone appear to be sitting across the same table from you even though they’re in multiple locations), and a number of meeting planning and management options.  SharePoint Services online offers something even cooler: the ability to view your Microsoft Outlook OWA mailbox right in the SharePoint homepage – no more multiple browser pages!

Microsoft SharePoint online

There are many more features available, so check it out if you’re intersted.  Microsoft is currently offering a free one-month trial of BPOS to anyone interested in sampling its cloud productivity services, and Microsoft partners are able to secure a one-year, 250-seat license for free.  Can’t beat that deal ….

Users begin by installing the sign-in application, which becomes the launch point for accessing all of the included functionality.

Exchange CCR error – Event ID: 2059

Friday, July 23rd, 2010

Recently, we had a customer who had an attached storage drive fail on them. An Exchange 2007 CCR cluster was hosted on this drive quite the disruption. Long story short, we got the data back and started to resume the CCR. Unfortunately, the status would keep going from “Healthy” to “Failed”. Checking the results, this is the error we would keep getting:

Source: MSExchangeRepl

Event ID: 2059

Description:

The log file 612083 for Server\Storage Group is missing on the production copy. Continuous replication for this storage group is blocked. If you removed the log file, please replace it. If the log is lost, the passive copy will need to be reseeded using the Update-StorageGroupCopy cmdlet in the EMS.

Now of course, those transaction log files that it was asking for no longer existed (Due to the corruption – again, long story). But here is were we figured out the problem to be. If we took down the exchange db, and did: “eseutil /mh .\database.edb”, we got the following bit of information:

Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 08.02
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating FILE DUMP mode…

<truncated>

Previous Full Backup:
Log Gen: 612070-612083 (0x956e6-0x956f3) – OSSnapshot
Mark: (0x956F4,8,16)
Mark: 07/10/2010 12:34:52

<truncated>

Notice that it was trying to get the log generation files from the previous backup. Two options… back up the 250Gb Database (Takes about 18 Hours), or trick it, get the CCR going again (And then do the backup). We choose to trick it. How? Here is how:

On the mail store, we went to the powershell (Command prompt is fine also) and did this:

Diskshadow
set context persistent
writer verify {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
begin backup
add volume f: alias shadow_f (F: is where the datastore is…)
create (Takes 2-5 minutes)
However, before I could finish, I got an error:
ERROR: The writer “{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}” was not included. Aborting …
Check the syntax of the writer name and writer ID.
The reason was because my transaction logs were somewhere else (Another Drive), and my system Drive was C:, so added those as well:
add volume c: alias shadow_c
add volume f:\exchange-logs\ alias shadow_logs
create (Again! This time it took 2-5 minutes and it WORKED!)
expose %shadow_f% y:
end backup
delete shadows exposed y:
exit
The whole process took about 7 minutes, and the new result when I ran: “eseutil /mh ./database.edb”:
Previous Full Backup:
Log Gen: 641830-641842 (0x9cb26-0x9cb32) – OSSnapshot
Mark: (0x9CB33,8,16)
Mark: 07/21/2010 01:24:36
It WORKED! Those were the current generation of logs that we wanted… so what exactly did we just do? Well Server 2008 RTM and R2 have the ability to make shadow copies of live databases, and access them using the tool: Diskshadow. Now, when we do this, Exchange detects this as a successful backup, and marks the database as such. No extra Hard Drive was used during this time (Perhaps a few MB), and it was very quick. Trick complete. Restart CCR (Had to reseed unfortunately – this was so the old database that had the old information could be replaced with the new database with the “correct” backup time), and then did a successful backup. Hope this helps someone!