URGENT : démarrage impossible de la banque d'informations
1 réponse
mca
Bonjour,
Mon serveur de messagerie a subitement red=E9marr=E9 sans que=20
l'on intervienne. Depuis, le service de la banque=20
d'informations ne d=E9marre plus. Ma messagerie est=20
compl=E8tement bloqu=E9e.
Si je regarde le journal d'=E9v=E9nement systeme, il=20
m'indique :=20
Type d'=E9v=E9nement : Erreur
Source de l'=E9v=E9nement : Gestion de contr=F4le des services
Cat=E9gorie de l'=E9v=E9nement : Aucune
ID de l'=E9v=E9nement : 7024
Description :
Le service de banque d'informations Microsoft Exchange=20
s'est arr=EAt=E9 avec l'erreur service particuli=E8re 0.
Cette action est irreversible, confirmez la suppression du commentaire ?
Signaler le commentaire
Veuillez sélectionner un problème
Nudité
Violence
Harcèlement
Fraude
Vente illégale
Discours haineux
Terrorisme
Autre
mca
base priv1.edb : 4Go97 base pub1.edb : 90 Mo
Je suis sour Serveur exchange 2000 SP2
Merci MCA
-----Message d'origine----- La base est t'elle conséquent pour le savoir utilisez eseutil pour vérifier que vos bases sont conséquentes.
INTEGRITY: DESCRIPTION: Verifies integrity of a database. SYNTAX: ESEUTIL /g <database name> [options] PARAMETERS: <database name> - filename of database to verify
OPTIONS: zero or more of the following switches, separated by a space:
/t<db> - set temp. database name (default:TEMPINTEG704.EDB)
/s<file> - set streaming file name (default: NONE)
/f<name> - set prefix to user for name of report files
(default: <I>database</I>.integ.raw)
/o - suppress logo NOTES: 1) The consistency-checker performs no recovery and always
assumes that the database is in a consistent state,
returning an error if this is not the case
autre solution XADM: Information Store Does Not Start with Event ID 7024
CAUSE This behavior can be caused in two ways. a.. Cause 1: Multiple recipient policies are displayed with the same priority.
b.. Cause 2: A Microsoft Exchange Server 5.5 site was removed from the organization, but it is still partially listed in the
Exchange System Manager and the Recipient Policy has a very unique name.
RESOLUTION To resolve this issue, perform the resolution that corresponds with the cause of the behavior (e.g., perform
Resolution 1 when the behavior arises due to Cause 1).
a.. Resolution 1: To resolve this issue, remove the recipient policies, and then recreate them with a higher policy number. You
may have to run Exchange 2000 Setup.exe again to reinstall Exchange 2000.
NOTE: Exchange Server 5.5 sites get the policies created automatically and all will be marked as having
highest priority. Do not delete these.
b.. Resolution 2: Delete the Exchange Server 5.5 site (Administrative Group) from Exchange System Manager as well as the
Recipient Policy for this Site (Administrative Group).
"mca" a écrit dans le message de news:2902101c464fb$10e97240
$
Bonjour, Mon serveur de messagerie a subitement redémarré sans que l'on intervienne. Depuis, le service de la banque d'informations ne démarre plus. Ma messagerie est complètement bloquée.
Si je regarde le journal d'événement systeme, il m'indique :
Type d'événement : Erreur Source de l'événement : Gestion de contrôle des services Catégorie de l'événement : Aucune ID de l'événement : 7024 Description : Le service de banque d'informations Microsoft Exchange s'est arrêté avec l'erreur service particulière 0.
Quelqu'un peut-il m'aider ?
Merci MCA
base priv1.edb : 4Go97
base pub1.edb : 90 Mo
Je suis sour Serveur exchange 2000 SP2
Merci
MCA
-----Message d'origine-----
La base est t'elle conséquent
pour le savoir utilisez eseutil pour vérifier que vos
bases sont conséquentes.
INTEGRITY:
DESCRIPTION: Verifies integrity of a database.
SYNTAX: ESEUTIL /g <database name> [options]
PARAMETERS: <database name> - filename of database to
verify
OPTIONS: zero or more of the following switches,
separated by a space:
/t<db> - set temp. database name
(default:TEMPINTEG704.EDB)
/s<file> - set streaming file name
(default: NONE)
/f<name> - set prefix to user for name of
report files
(default:
<I>database</I>.integ.raw)
/o - suppress logo
NOTES: 1) The consistency-checker performs no
recovery and always
assumes that the database is in a
consistent state,
returning an error if this is not the
case
autre solution XADM: Information Store Does Not Start
with Event ID 7024
CAUSE
This behavior can be caused in two ways.
a.. Cause 1:
Multiple recipient policies are displayed with the same
priority.
b.. Cause 2:
A Microsoft Exchange Server 5.5 site was removed from
the organization, but it is still partially listed in the
Exchange System Manager and the Recipient Policy has a
very unique name.
RESOLUTION
To resolve this issue, perform the resolution that
corresponds with the cause of the behavior (e.g., perform
Resolution 1 when the behavior arises due to Cause 1).
a.. Resolution 1:
To resolve this issue, remove the recipient policies,
and then recreate them with a higher policy number. You
may have to run Exchange 2000 Setup.exe again to reinstall
Exchange 2000.
NOTE: Exchange Server 5.5 sites get the policies
created automatically and all will be marked as having
highest priority. Do not delete these.
b.. Resolution 2:
Delete the Exchange Server 5.5 site (Administrative
Group) from Exchange System Manager as well as the
Recipient Policy for this Site (Administrative Group).
"mca" <anonymous@discussions.microsoft.com> a écrit dans
le message de news:2902101c464fb$10e97240
$a501280a@phx.gbl...
Bonjour,
Mon serveur de messagerie a subitement redémarré sans que
l'on intervienne. Depuis, le service de la banque
d'informations ne démarre plus. Ma messagerie est
complètement bloquée.
Si je regarde le journal d'événement systeme, il
m'indique :
Type d'événement : Erreur
Source de l'événement : Gestion de contrôle des services
Catégorie de l'événement : Aucune
ID de l'événement : 7024
Description :
Le service de banque d'informations Microsoft Exchange
s'est arrêté avec l'erreur service particulière 0.
-----Message d'origine----- La base est t'elle conséquent pour le savoir utilisez eseutil pour vérifier que vos bases sont conséquentes.
INTEGRITY: DESCRIPTION: Verifies integrity of a database. SYNTAX: ESEUTIL /g <database name> [options] PARAMETERS: <database name> - filename of database to verify
OPTIONS: zero or more of the following switches, separated by a space:
/t<db> - set temp. database name (default:TEMPINTEG704.EDB)
/s<file> - set streaming file name (default: NONE)
/f<name> - set prefix to user for name of report files
(default: <I>database</I>.integ.raw)
/o - suppress logo NOTES: 1) The consistency-checker performs no recovery and always
assumes that the database is in a consistent state,
returning an error if this is not the case
autre solution XADM: Information Store Does Not Start with Event ID 7024
CAUSE This behavior can be caused in two ways. a.. Cause 1: Multiple recipient policies are displayed with the same priority.
b.. Cause 2: A Microsoft Exchange Server 5.5 site was removed from the organization, but it is still partially listed in the
Exchange System Manager and the Recipient Policy has a very unique name.
RESOLUTION To resolve this issue, perform the resolution that corresponds with the cause of the behavior (e.g., perform
Resolution 1 when the behavior arises due to Cause 1).
a.. Resolution 1: To resolve this issue, remove the recipient policies, and then recreate them with a higher policy number. You
may have to run Exchange 2000 Setup.exe again to reinstall Exchange 2000.
NOTE: Exchange Server 5.5 sites get the policies created automatically and all will be marked as having
highest priority. Do not delete these.
b.. Resolution 2: Delete the Exchange Server 5.5 site (Administrative Group) from Exchange System Manager as well as the
Recipient Policy for this Site (Administrative Group).
"mca" a écrit dans le message de news:2902101c464fb$10e97240
$
Bonjour, Mon serveur de messagerie a subitement redémarré sans que l'on intervienne. Depuis, le service de la banque d'informations ne démarre plus. Ma messagerie est complètement bloquée.
Si je regarde le journal d'événement systeme, il m'indique :
Type d'événement : Erreur Source de l'événement : Gestion de contrôle des services Catégorie de l'événement : Aucune ID de l'événement : 7024 Description : Le service de banque d'informations Microsoft Exchange s'est arrêté avec l'erreur service particulière 0.
