Information Store Warnings

0 pts.
Tags:
Tech support
How do I fix these warnings in my Private & Public store. ISinteg -fix does not seem to do it. Do I need to fix these before upgrading to Exchange 2K3. Warning: MsgFolder 1 (Fid=0001-000000001B8E, Mid=0006-0000000898A3, Inid=0006-00000009DA5E): Prop ptagLocalized(676D0102) was not found in the ptagMsgPropList.
ASKED: February 3, 2005  11:29 AM
UPDATED: February 10, 2005  9:27 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hello,

I’ve tried a few searches for the warning information provided but came up empty. Could you describe in better detail what you were doing when these warnings were generated, and provide some info on your version of Exchange? Have you noticed any problems with user mailboxes, send/receive functionality, public folders etc. that may be associated with these? The more detail you can provide the better chance your going to have to get a solution.

As for upgrading to Exchange 2003…. well, you can give it a shot, if there are any critical issues with your current version the install will most likely stop and prompt you to correct the problems.

Good Luck

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Mercer
    I do not have any reports from users of missing mailbox content or problems. However, the store.exe has crashed four times in the last three weeks, with a Dr. Watson log generated (we are currently on NT 4.0 SP6a). This is what prompted me to run ISINTEG in the first place, which reported these warnings. However the fix options did not repair any of them. The store has been running fine for a week or so, but I was concerned about the ISINTEG warnings. The first crash came about (I think) because of a filled logging disk, due to backup problems, which has been corrected. All of the Dr. Watsons logs point to the same routines in the stack. The only unusually configuration settings I have is a set of event scripts which run on a timed basis to clean out and record messages flagged as spam by our spam filtering relays.
    0 pointsBadges:
    report
  • Pedwards17
    Quick questions--first, is your Exchange server version 5.5? If so, do you have any Outlook 2003 clients with mailboxes on that server? This is a strange problem, but Outlook 2003 clients can crash the store on an Exchange 5.5 server. If this is your scenario, apply the November 2004 Rollup Patch for Exchange 5.5 (KB841765) to correct the problem. We had the same issue and the patch resolved it for us. Hope it helps.
    0 pointsBadges:
    report
  • Petroleumman
    Hello, Pedwards 17 has a valid point. This is a known compatibility issue with 5.5 and Outlook 2003. Let us know if the patch resolves your problem. Good Luck!
    0 pointsBadges:
    report
  • Mercer
    I can't believe I never included the versions in my messages. We are running Exchange 5.5 and various Outlook 2000, 2003 and 2002. In addition we are running Macaffe's groupshield for Exchange 5.5. I will download the patch and apply it. I will let you all know the result.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following