Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Information Store
- Thread starter seanos
- Start date
1. What service pack is exchange at
2. Is Exchange the Enterprise version, if not make sure you store is no near or over 16gb
3. make sure you are not running out of disk space, less than 10mb left and the store shuts down automatically.
2. Is Exchange the Enterprise version, if not make sure you store is no near or over 16gb
3. make sure you are not running out of disk space, less than 10mb left and the store shuts down automatically.
- Thread starter
- #3
off course there is lots to be found about exchange problems on the internet. I give you some suggestions to get started right away and solve your problem quickly:
this is a good article on the two disaster recovery programs which MS included on the Exchange server CD.
Official MS documentation can be found on technet or in the MS knowledge base for example articles Q182081 or Q192185 for info about isinteg and esesutil utilities.
I wil bee checking this thread regurly so ask your question if you need any further assistance.
Regards.
this is a good article on the two disaster recovery programs which MS included on the Exchange server CD.
Official MS documentation can be found on technet or in the MS knowledge base for example articles Q182081 or Q192185 for info about isinteg and esesutil utilities.
I wil bee checking this thread regurly so ask your question if you need any further assistance.
Regards.
- Thread starter
- #6
Check the dependencies of the service that is causing this error.
Under Windows 2000 you can find the dependencies by clicking at the services icon in the control panel and then right click the service (check the event viewer) that caused this error to see its dependencies.
if you are using Windows NT try the following. Use regedt32.exe and click to the 'HKLM\SYSTEM\CurrentControlSet\Services\' key. Find the correct service that is causing the error and click its 'dependonservice' key.
If you find out which service the failing service (or services) depends on, you can see if they started correctly. If not, you'll have to find out why these services did not start correctly, crashed or did not start at all.
Hoped to have helped you.
Regards.
Under Windows 2000 you can find the dependencies by clicking at the services icon in the control panel and then right click the service (check the event viewer) that caused this error to see its dependencies.
if you are using Windows NT try the following. Use regedt32.exe and click to the 'HKLM\SYSTEM\CurrentControlSet\Services\' key. Find the correct service that is causing the error and click its 'dependonservice' key.
If you find out which service the failing service (or services) depends on, you can see if they started correctly. If not, you'll have to find out why these services did not start correctly, crashed or did not start at all.
Hoped to have helped you.
Regards.
- Thread starter
- #8
- Status
Similar threads
- Locked
- Question
- Locked
- Question