Error -1012 (Exchange Related)

[honarya]

[color:blue]Retrospect is giving several errors that "File (user name, fold[color:blue][/color]er name with a lot of letters and numbers which refers to a message):can't read, error -1012 (feature unsupported)

T-820: MBDatainputStream::prepareLongProperty: Failure (winner = ox80070003)". This happens when it is backing up Exchange mailboxes. It happens only with certain messages (not all). I do not have any problems with Exchange. I have not been able to figure out what causes this. I have searched this web site, Microsoft web site and other places but no luck. Can anyone help?[/color]

[Mayoff]

This might help:

 

http://kb.dantz.com/article.asp?article=9643&p=2

 

I think you probably have some corrupted messages in the mailbox.

[honarya]

[color:brown]Thanks for your quick response. But my error message is -1012. Your reference is for error -1101. This happens on many mailboxes with both new and old messages. I have tried to remove the server and then added, reinstalled the client but nothing has helped.

Any other suggestions?

[/color]

[Mayoff]

From the document I noted above.

 

2) The mailbox may contain a message with an illegal subject line (often caused by SPAM), corrupt attachment or other problem that prevents correct reading of the message.

 

To see which email could not be copied do the following:

 

1) Go to the History tab of the Activity Monitor

2) Highlight the entry for the backup that failed

3) Click the "errors..." button. You should now see a list of file that could not be copied with that script. You can then delete any bad messages from the mailbox.

Edited May 2, 2008 by Guest

[honarya]

We are getting over 6700 error messages on 30-40 Exchange mailboxes. Some users have several hundreds errors. We cannot go through each mailbox and find the ones that Retrospect cannot backup. Also this happens with new messages. And I do not have access to people's mailboxes. There should be something that causes Retrospect to get so many error messages. Thanks again for your help. [color:brown][/color]

[Mayoff]

Make sure you have configured mailbox backup correctly using these steps:

 

http://forums.dantz.com/linkhit.php?id/104/

 

[honarya]

Thanks Robin. I have changed the user name to a new admin. user name (I had domain administrator for user name). I will let you know the result next week.

[honarya]

Hi Robin,

 

I followed all the steps (Post#106524)and changed the user name with a new one. Did not change anything. The same result (error -1012). Any other suggestions?

 

Thanks.

[Mayoff]

Microsoft seems to define the hex code in your original post as:

 

0x80070003

The System Cannot find the path specified.

 

I found this item on google but I don't know if this is why you get the error.:

 

CAUSE

 

This issue may occur if the Microsoft Internet Information Services (IIS) metabase entry for the Microsoft Exchange Routing Engine service is removed or becomes corrupted. The routing engine component of Exchange runs under IIS and uses information that is contained in the IIS metabase. Typically, this issue occurs when IIS is removed from and reinstalled on a computer that is running Exchange 2003 or Exchange 2000. Additionally, this issue may occur when IIS stops responding or when the Exchange computer is turned off before the IIS shutdown is complete.

 

To confirm that this is the issue, follow these steps on the Exchange computer:

1. Click Start, click Run, type cmd, and then click OK.

2. Type cd\Inetpub\AdminScripts, and then press ENTER.

3. Type cscript adsutil.vbs ENUM_ALL resvc, and then press ENTER.

 

If you are experiencing this issue, you receive the following error message:

Path not found

ErrNumber: -2147024893 (0x80070003)

Error Trying To ENUM the Object (GetObject Failed): resvc

Back to the top

 

RESOLUTION

 

To resolve this issue, use one of the following methods.

Back to the top

 

Method 1

 

If you have a recent backup of the IIS metabase from some time after you installed Exchange, restore the metabase from the backup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

302573 (http://kbalertz.com/Feedback.aspx?kbNumber=302573/) How to back up and restore IIS

Back to the top

 

Method 2

 

If no backup of the metabase exists, you can run the Exchange Setup program with the /reinstall switch. This will cause the Exchange Setup program to copy all the Exchange Server files and to replace missing entries in the metabase. You must also reapply any service packs and hotfixes.

 

If you have not recently removed IIS, it may be a good idea to try to determine the cause of the metabase corruption. If other IIS services are affected and will not start, you may have to remove and reinstall IIS before you complete the reinstallation of Exchange. Possible causes of metabase corruption include write caching, virus scanning, or editing of the metabase.bin file in an unsupported manner. A power failure or other type of system problem may also be the root cause.

Back to the top

 

http://kbalertz.com/841576/Microsoft-Exchange-Routing-Engine-service-start-events.aspx

 

[honarya]

Hi Robin, Thanks for sending the information on the error message. I followed the steps that Microsoft suggested for confirming the error but I am not getting an error message. It passes the test. Everything seems to be working correctly with the Exchange server. Only Retrospect is giving the error message. Also I do not see an error message in Event Viewer on the Exchange server.

 

Thank you again for all you help.

Edited May 8, 2008 by Guest

[Mayoff]

Your original post contained

T-820: MBDatainputStream::prepareLongProperty: Failure (winner = ox80070003)

 

The 0x8007003 error is reported directly by the exchange server and is not a Retrospect error.

 

Does your log contain any other hex code errors?

[honarya]

Our Exchange server does not show any errors. This is only from Retrospect. I uninstalled/reinstalled Retrospect from the Exchange server, hoping that the newer version (7.6) would take care of this. But the problem is still there. I am out of ideas what else can be done with this. This happens with many newly created mailboxes too. The error messages are over 9000. Do you have any other suggestions? Thanks.