RE: MSExchangeIS Private error message

2002-03-05 Thread Neil Hobson

As I said in the original message, it will more than likely involve
isinteg.  I'd get PSS on your side, though.

Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Gerald BAI (NCS) [mailto:[EMAIL PROTECTED]] 
Posted At: 05 March 2002 00:38
Posted To: Sunbelt Exchange List
Conversation: MSExchangeIS Private error message
Subject: RE: MSExchangeIS Private error message


Hmm... Well, I think we have the file-level scanning. So how did your
customer repair the database in the end?

Thanks for your help!

Gerald

-Original Message-
From: Neil Hobson [mailto:[EMAIL PROTECTED]] 
Sent: Monday, 04 March, 2002 5:25 PM
To: MS-Exchange Admin Issues
Subject: RE: MSExchangeIS Private error message


So was my customer.  H..but initially they were also scanning
the Exchange data with Norton file-level scanning, which we suspected
caused the damage.  Please say you're not using a file-level AV scanner
on this server as well, or at least that you're excluding the
\exchsrvr\*data directories...  :-)

Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Gerald BAI (NCS) [mailto:[EMAIL PROTECTED]] 
Posted At: 04 March 2002 09:19
Posted To: Sunbelt Exchange List
Conversation: MSExchangeIS Private error message
Subject: RE: MSExchangeIS Private error message


Norton Antivirus for Exchange

-Original Message-
From: Neil Hobson [mailto:[EMAIL PROTECTED]] 
Sent: Monday, 04 March, 2002 5:11 PM
To: MS-Exchange Admin Issues
Subject: RE: MSExchangeIS Private error message


By the way, what antivirus software do you have running on this machine?

Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Neil Hobson 
Posted At: 04 March 2002 09:09
Posted To: Sunbelt Exchange List
Conversation: MSExchangeIS Private error message
Subject: RE: MSExchangeIS Private error message


I've had the exact same error message with a customer before, and the
same symptoms.  I highly expect that you'll need to run isinteg,
ultimately with the -fix command, but initially without to see what
errors you get.  I also expect you will need to keep running isinteg
with -fix until you receive no further errors.  Sometimes running an
isinteg with -fix fixes some errors, but uncovers others.

However, what I do recommend is that you raise a call to PSS if you are
in any way unsure of what you are doing.  It will be money well spent,
particularly if any other problems are uncovered.

Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Gerald BAI (NCS) [mailto:[EMAIL PROTECTED]] 
Posted At: 04 March 2002 08:52
Posted To: Sunbelt Exchange List
Conversation: MSExchangeIS Private error message
Subject: MSExchangeIS Private error message


Hi all,

My Exchange 5.5 SP4 this morning gave this error message:


Event ID: 1101
Source: MSExchangeIS Private
Category: Background Cleanup

Description:
Error 0xfbd3 occurred on message 1c-409f0c during a background
cleanup.


All Exchange services are up, but users cannot log on to the Exchange
server.  The error message is gone after a reboot of the Exchange
server, and users can then log on to the Exchange server.

I am afraid that it will happen again tomorrow. What should I do? Seems
that the Private IS is having a problem. Do I need to run isinteg -patch
or eseutil /p /x to repair it?

Thanks and regards,

Gerald

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual to whom it is addressed.
Any view or opinions presented are solely those of the author and do 
not necessarily represent those of Silversands, or any of its 
subsidiary companies.
If you have received this email in error, please contact our Support 
Desk immediately by telephone on 01202-36 or via email at
[EMAIL PROTECTED]
**

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual to whom it is addressed.
Any view or opinions presented are solely those of the author and do 
not necessarily represent those of Silversands, or any of its 
subsidiary companies.
If you have received this email in error, please contact our Support 
Desk immediately by telephone on 01202-36

MSExchangeIS Private error message

2002-03-04 Thread Gerald BAI (NCS)

Hi all,

My Exchange 55 SP4 this morning gave this error message:


Event ID: 1101
Source: MSExchangeIS Private
Category: Background Cleanup

Description:
Error 0xfbd3 occurred on message 1c-409f0c during a background cleanup


All Exchange services are up, but users cannot log on to the Exchange
server  The error message is gone after a reboot of the Exchange server,
and users can then log on to the Exchange server

I am afraid that it will happen again tomorrow What should I do? Seems that
the Private IS is having a problem Do I need to run isinteg -patch or
eseutil /p /x to repair it?

Thanks and regards,

Gerald

List Charter and FAQ at:
http://wwwsunbelt-softwarecom/exchange_list_charterhtm




RE: MSExchangeIS Private error message

2002-03-04 Thread Neil Hobson

I've had the exact same error message with a customer before, and the
same symptoms.  I highly expect that you'll need to run isinteg,
ultimately with the -fix command, but initially without to see what
errors you get.  I also expect you will need to keep running isinteg
with -fix until you receive no further errors.  Sometimes running an
isinteg with -fix fixes some errors, but uncovers others.

However, what I do recommend is that you raise a call to PSS if you are
in any way unsure of what you are doing.  It will be money well spent,
particularly if any other problems are uncovered.

Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Gerald BAI (NCS) [mailto:[EMAIL PROTECTED]] 
Posted At: 04 March 2002 08:52
Posted To: Sunbelt Exchange List
Conversation: MSExchangeIS Private error message
Subject: MSExchangeIS Private error message


Hi all,

My Exchange 5.5 SP4 this morning gave this error message:


Event ID: 1101
Source: MSExchangeIS Private
Category: Background Cleanup

Description:
Error 0xfbd3 occurred on message 1c-409f0c during a background
cleanup.


All Exchange services are up, but users cannot log on to the Exchange
server.  The error message is gone after a reboot of the Exchange
server, and users can then log on to the Exchange server.

I am afraid that it will happen again tomorrow. What should I do? Seems
that the Private IS is having a problem. Do I need to run isinteg -patch
or eseutil /p /x to repair it?

Thanks and regards,

Gerald

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual to whom it is addressed.
Any view or opinions presented are solely those of the author and do
not necessarily represent those of Silversands, or any of its
subsidiary companies.
If you have received this email in error, please contact our Support
Desk immediately by telephone on 01202-36 or via email at
[EMAIL PROTECTED]
**

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: MSExchangeIS Private error message

2002-03-04 Thread Neil Hobson

By the way, what antivirus software do you have running on this machine?

Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Neil Hobson 
Posted At: 04 March 2002 09:09
Posted To: Sunbelt Exchange List
Conversation: MSExchangeIS Private error message
Subject: RE: MSExchangeIS Private error message


I've had the exact same error message with a customer before, and the
same symptoms.  I highly expect that you'll need to run isinteg,
ultimately with the -fix command, but initially without to see what
errors you get.  I also expect you will need to keep running isinteg
with -fix until you receive no further errors.  Sometimes running an
isinteg with -fix fixes some errors, but uncovers others.

However, what I do recommend is that you raise a call to PSS if you are
in any way unsure of what you are doing.  It will be money well spent,
particularly if any other problems are uncovered.

Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Gerald BAI (NCS) [mailto:[EMAIL PROTECTED]] 
Posted At: 04 March 2002 08:52
Posted To: Sunbelt Exchange List
Conversation: MSExchangeIS Private error message
Subject: MSExchangeIS Private error message


Hi all,

My Exchange 5.5 SP4 this morning gave this error message:


Event ID: 1101
Source: MSExchangeIS Private
Category: Background Cleanup

Description:
Error 0xfbd3 occurred on message 1c-409f0c during a background
cleanup.


All Exchange services are up, but users cannot log on to the Exchange
server.  The error message is gone after a reboot of the Exchange
server, and users can then log on to the Exchange server.

I am afraid that it will happen again tomorrow. What should I do? Seems
that the Private IS is having a problem. Do I need to run isinteg -patch
or eseutil /p /x to repair it?

Thanks and regards,

Gerald

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual to whom it is addressed.
Any view or opinions presented are solely those of the author and do 
not necessarily represent those of Silversands, or any of its 
subsidiary companies.
If you have received this email in error, please contact our Support 
Desk immediately by telephone on 01202-36 or via email at
[EMAIL PROTECTED]
**

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual to whom it is addressed.
Any view or opinions presented are solely those of the author and do
not necessarily represent those of Silversands, or any of its
subsidiary companies.
If you have received this email in error, please contact our Support
Desk immediately by telephone on 01202-36 or via email at
[EMAIL PROTECTED]
**

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: MSExchangeIS Private error message

2002-03-04 Thread Gerald BAI (NCS)

Norton Antivirus for Exchange

-Original Message-
From: Neil Hobson [mailto:[EMAIL PROTECTED]] 
Sent: Monday, 04 March, 2002 5:11 PM
To: MS-Exchange Admin Issues
Subject: RE: MSExchangeIS Private error message


By the way, what antivirus software do you have running on this machine?

Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Neil Hobson 
Posted At: 04 March 2002 09:09
Posted To: Sunbelt Exchange List
Conversation: MSExchangeIS Private error message
Subject: RE: MSExchangeIS Private error message


I've had the exact same error message with a customer before, and the same
symptoms.  I highly expect that you'll need to run isinteg, ultimately with
the -fix command, but initially without to see what errors you get.  I also
expect you will need to keep running isinteg with -fix until you receive no
further errors.  Sometimes running an isinteg with -fix fixes some errors,
but uncovers others.

However, what I do recommend is that you raise a call to PSS if you are in
any way unsure of what you are doing.  It will be money well spent,
particularly if any other problems are uncovered.

Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Gerald BAI (NCS) [mailto:[EMAIL PROTECTED]] 
Posted At: 04 March 2002 08:52
Posted To: Sunbelt Exchange List
Conversation: MSExchangeIS Private error message
Subject: MSExchangeIS Private error message


Hi all,

My Exchange 5.5 SP4 this morning gave this error message:


Event ID: 1101
Source: MSExchangeIS Private
Category: Background Cleanup

Description:
Error 0xfbd3 occurred on message 1c-409f0c during a background cleanup.


All Exchange services are up, but users cannot log on to the Exchange
server.  The error message is gone after a reboot of the Exchange server,
and users can then log on to the Exchange server.

I am afraid that it will happen again tomorrow. What should I do? Seems that
the Private IS is having a problem. Do I need to run isinteg -patch or
eseutil /p /x to repair it?

Thanks and regards,

Gerald

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

**
This email and any files transmitted with it are confidential and intended
solely for the use of the individual to whom it is addressed. Any view or
opinions presented are solely those of the author and do 
not necessarily represent those of Silversands, or any of its 
subsidiary companies.
If you have received this email in error, please contact our Support 
Desk immediately by telephone on 01202-36 or via email at
[EMAIL PROTECTED]
**

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

**
This email and any files transmitted with it are confidential and intended
solely for the use of the individual to whom it is addressed. Any view or
opinions presented are solely those of the author and do 
not necessarily represent those of Silversands, or any of its 
subsidiary companies.
If you have received this email in error, please contact our Support 
Desk immediately by telephone on 01202-36 or via email at
[EMAIL PROTECTED]
**

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: MSExchangeIS Private error message

2002-03-04 Thread Neil Hobson

So was my customer.  H..but initially they were also scanning
the Exchange data with Norton file-level scanning, which we suspected
caused the damage.  Please say you're not using a file-level AV scanner
on this server as well, or at least that you're excluding the
\exchsrvr\*data directories...  :-)

Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Gerald BAI (NCS) [mailto:[EMAIL PROTECTED]] 
Posted At: 04 March 2002 09:19
Posted To: Sunbelt Exchange List
Conversation: MSExchangeIS Private error message
Subject: RE: MSExchangeIS Private error message


Norton Antivirus for Exchange

-Original Message-
From: Neil Hobson [mailto:[EMAIL PROTECTED]] 
Sent: Monday, 04 March, 2002 5:11 PM
To: MS-Exchange Admin Issues
Subject: RE: MSExchangeIS Private error message


By the way, what antivirus software do you have running on this machine?

Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Neil Hobson 
Posted At: 04 March 2002 09:09
Posted To: Sunbelt Exchange List
Conversation: MSExchangeIS Private error message
Subject: RE: MSExchangeIS Private error message


I've had the exact same error message with a customer before, and the
same symptoms.  I highly expect that you'll need to run isinteg,
ultimately with the -fix command, but initially without to see what
errors you get.  I also expect you will need to keep running isinteg
with -fix until you receive no further errors.  Sometimes running an
isinteg with -fix fixes some errors, but uncovers others.

However, what I do recommend is that you raise a call to PSS if you are
in any way unsure of what you are doing.  It will be money well spent,
particularly if any other problems are uncovered.

Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Gerald BAI (NCS) [mailto:[EMAIL PROTECTED]] 
Posted At: 04 March 2002 08:52
Posted To: Sunbelt Exchange List
Conversation: MSExchangeIS Private error message
Subject: MSExchangeIS Private error message


Hi all,

My Exchange 5.5 SP4 this morning gave this error message:


Event ID: 1101
Source: MSExchangeIS Private
Category: Background Cleanup

Description:
Error 0xfbd3 occurred on message 1c-409f0c during a background
cleanup.


All Exchange services are up, but users cannot log on to the Exchange
server.  The error message is gone after a reboot of the Exchange
server, and users can then log on to the Exchange server.

I am afraid that it will happen again tomorrow. What should I do? Seems
that the Private IS is having a problem. Do I need to run isinteg -patch
or eseutil /p /x to repair it?

Thanks and regards,

Gerald

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual to whom it is addressed.
Any view or opinions presented are solely those of the author and do 
not necessarily represent those of Silversands, or any of its 
subsidiary companies.
If you have received this email in error, please contact our Support 
Desk immediately by telephone on 01202-36 or via email at
[EMAIL PROTECTED]
**

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual to whom it is addressed.
Any view or opinions presented are solely those of the author and do 
not necessarily represent those of Silversands, or any of its 
subsidiary companies.
If you have received this email in error, please contact our Support 
Desk immediately by telephone on 01202-36 or via email at
[EMAIL PROTECTED]
**

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual to whom it is addressed.
Any view or opinions presented are solely those of the author and do
not necessarily represent those of Silversands, or any of its
subsidiary companies.
If you have received this email in error, please contact our Support
Desk immediately by telephone on 01202-36 or via email at
[EMAIL PROTECTED

RE: MSExchangeIS Private error message

2002-03-04 Thread Gerald BAI (NCS)

Hmm... Well, I think we have the file-level scanning. So how did your
customer repair the database in the end?

Thanks for your help!

Gerald

-Original Message-
From: Neil Hobson [mailto:[EMAIL PROTECTED]] 
Sent: Monday, 04 March, 2002 5:25 PM
To: MS-Exchange Admin Issues
Subject: RE: MSExchangeIS Private error message


So was my customer.  H..but initially they were also scanning the
Exchange data with Norton file-level scanning, which we suspected caused the
damage.  Please say you're not using a file-level AV scanner on this server
as well, or at least that you're excluding the \exchsrvr\*data
directories...  :-)

Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Gerald BAI (NCS) [mailto:[EMAIL PROTECTED]] 
Posted At: 04 March 2002 09:19
Posted To: Sunbelt Exchange List
Conversation: MSExchangeIS Private error message
Subject: RE: MSExchangeIS Private error message


Norton Antivirus for Exchange

-Original Message-
From: Neil Hobson [mailto:[EMAIL PROTECTED]] 
Sent: Monday, 04 March, 2002 5:11 PM
To: MS-Exchange Admin Issues
Subject: RE: MSExchangeIS Private error message


By the way, what antivirus software do you have running on this machine?

Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Neil Hobson 
Posted At: 04 March 2002 09:09
Posted To: Sunbelt Exchange List
Conversation: MSExchangeIS Private error message
Subject: RE: MSExchangeIS Private error message


I've had the exact same error message with a customer before, and the same
symptoms.  I highly expect that you'll need to run isinteg, ultimately with
the -fix command, but initially without to see what errors you get.  I also
expect you will need to keep running isinteg with -fix until you receive no
further errors.  Sometimes running an isinteg with -fix fixes some errors,
but uncovers others.

However, what I do recommend is that you raise a call to PSS if you are in
any way unsure of what you are doing.  It will be money well spent,
particularly if any other problems are uncovered.

Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Gerald BAI (NCS) [mailto:[EMAIL PROTECTED]] 
Posted At: 04 March 2002 08:52
Posted To: Sunbelt Exchange List
Conversation: MSExchangeIS Private error message
Subject: MSExchangeIS Private error message


Hi all,

My Exchange 5.5 SP4 this morning gave this error message:


Event ID: 1101
Source: MSExchangeIS Private
Category: Background Cleanup

Description:
Error 0xfbd3 occurred on message 1c-409f0c during a background cleanup.


All Exchange services are up, but users cannot log on to the Exchange
server.  The error message is gone after a reboot of the Exchange server,
and users can then log on to the Exchange server.

I am afraid that it will happen again tomorrow. What should I do? Seems that
the Private IS is having a problem. Do I need to run isinteg -patch or
eseutil /p /x to repair it?

Thanks and regards,

Gerald

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

**
This email and any files transmitted with it are confidential and intended
solely for the use of the individual to whom it is addressed. Any view or
opinions presented are solely those of the author and do 
not necessarily represent those of Silversands, or any of its 
subsidiary companies.
If you have received this email in error, please contact our Support 
Desk immediately by telephone on 01202-36 or via email at
[EMAIL PROTECTED]
**

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

**
This email and any files transmitted with it are confidential and intended
solely for the use of the individual to whom it is addressed. Any view or
opinions presented are solely those of the author and do 
not necessarily represent those of Silversands, or any of its 
subsidiary companies.
If you have received this email in error, please contact our Support 
Desk immediately by telephone on 01202-36 or via email at
[EMAIL PROTECTED]
**

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

**
This email and any files transmitted with it are confidential and intended
solely for the use of the individual to whom it is addressed. Any view