How to re-create STM File in Exchange 2000/2003

本文提供了一种在没有有效备份的情况下重新创建*.STM文件的方法。适用于当*.STM文件与*.EDB文件不匹配导致信息存储服务无法挂载本地邮件/公共存储时。介绍了可能的原因及详细的解决步骤。
Article ID:555146
Last Review:June 22, 2004
Revision:1.0

SUMMARY

This knowledgebase provide information how to re-create the *.STM file in case you don’t have a valid backup

Back to the top

SYMPTOMS

When you run eseutil /P command or eseutil /mh, you may get error that indicate that the *.STM file doesn't match the *.EDB file that resides on the server.
Usually, in this case, the Information Store service cannot mount the local mail/public store.

Back to the top

CAUSE

There a few reasons for *.STM file corruption:
 
a. Antivirus software periodically scanning the *.EDB or/and *.STM file.
 
b. The *.EDB or/and *.STM size increases significantly.
 
c. Hardware problem.

 

RESOLUTION

By using the instructions in this guide may lose important data, and therefore should be only used as a last resorts. It is recommend that you backup the databases before implement these instructions. Always consider using a valid backup instead of these instructions.
 
The amount of the data that you may lose depends on your mail client software -  If everybody uses Outlook (MAPI protocol), then there will be very little user data in the .STM file. You may lose some in transit messages that haven't been delivered yet. If clients connect via POP3 or IMAP then most of their stuff will be in the .STM file, and its loss will be catastrophic to them. If clients use Outlook Web Access, messages will be in the .EDB file, but attachments sent will be in the .STM file.
 
 
1. Stop any antivirus software on the server.
 
2. Stop "Microsoft Exchange System Attendant" service.
 
     Note: This stage prevent from users to use the server.
 
3.  Go to "Start" -> "Run" and write "Regedit" and press on "Enter" button.
 
4. Navigate to:

    [HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/MSExchangeIS/VirusScan]
 
    In the right side of the screen change the value of "Enable" from 1 to 0.
 
5. Run eseutil /mh command to verity the need to recreate of the *.STM file:
 
       eseutil /mh "C:/Program Files/Exchsrvr/MDBDATA/priv1.edb"

       eseutil /mh "C:/Program Files/Exchsrvr/MDBDATA/pub1.edb"

    Note: If the *.EDB files reside in other locations, you may need to change the path to this files in eseutil /mh sentence.
 
6. Run eseutil /p /createstm command to create of the *.STM file:
 
            If the private mailbox store *.STM file may need to recreate, please use the following command:
 
            eseutil /p /createstm "C:/Program Files/Exchsrvr/MDBDATA/priv1.edb"
 
       If the public store *.STM file may need to recreate, please use the following command:
 
      eseutil /p /createstm "C:/Program Files/Exchsrvr/MDBDATA/pub1.edb"
 
7. Go to "Start" -> "Run" and write "Regedit" and press on "Enter" button.
 
8. Navigate to:

    [HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/MSExchangeIS/VirusScan]
 
    In the right side of the screen change the value of "Enable" from 0 to 1.
 
9. Start "Microsoft Exchange System Attendant" service.
 
10. Open Exchange "System Manager". Navigate to the problematic mailbox store/Public store.
 
11. Run "mailbox cleanup agent" on each mailbox store and choose "reconnect all mailboxes".
 
12. Optional: Open the problematic mailbox store/Public store, right click on the mailbox store/Public store and choose "properties".
         Press on "Database" tab and mark the checkbox "This database can be overwritten by a restore".
 
13. Mount the mailbox store/Public store.
 
   Note: If you Start "Microsoft Exchange System Attendant" service in phase 9, the mailbox store/public store should
                be mount automatically.
 
14. Start the antivirus software that was stop in phase 1.
 
15. Make full backup to the Exchange databases and the local server.

 

MORE INFORMATION

XADM: Exchange 2000 Server Eseutil Command Line Switches
http://support.microsoft.com/default.aspx?scid=kb;EN-US;317014
 
How to use Eseutil to test transaction log files for damage in Exchange 2000 Server and in Exchange Server 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;248122
 
XADM: Exchange and Antivirus Software
http://support.microsoft.com/default.aspx?scid=kb;[LN];328841
 
XADM: Ramifications of Running the ESEUTIL /P or EDBUTIL /D /R Command
http://support.microsoft.com/?id=259851
 
Preview: Exchange Server 2003 Disaster Recovery Planning Guide
http://www.microsoft.com/downloads/details.aspx?FamilyId=784BBEA2-28DD-409A-8368-F9914E993B28&displaylang=en
 
以上文章转贴:http://blog.5dmail.net/user1/1/200810231197.html
(Flightgpt) lixing@DESKTOP-2PJK7EV:~/FlightGPT/vllm$ rm -rf build/ (Flightgpt) lixing@DESKTOP-2PJK7EV:~/FlightGPT/vllm$ sudo ln -sf /usr/local/cuda-11.8/targets/x86_64-linux/include /usr/local/cuda/include (Flightgpt) lixing@DESKTOP-2PJK7EV:~/FlightGPT/vllm$ uv pip install -e . Using Python 3.10.18 environment at: /home/lixing/anaconda3/envs/Flightgpt Resolved 142 packages in 3.80s × Failed to build `vllm @ file:///home/lixing/FlightGPT/vllm` ├─▶ The build backend returned an error ╰─▶ Call to `setuptools.build_meta.build_editable` failed (exit status: 1) [stdout] running editable_wheel creating /home/lixing/.cache/uv/builds-v0/.tmpWurXDn/.tmp-17rijnpc/vllm.egg-info writing /home/lixing/.cache/uv/builds-v0/.tmpWurXDn/.tmp-17rijnpc/vllm.egg-info/PKG-INFO writing dependency_links to /home/lixing/.cache/uv/builds-v0/.tmpWurXDn/.tmp-17rijnpc/vllm.egg-info/dependency_links.txt writing entry points to /home/lixing/.cache/uv/builds-v0/.tmpWurXDn/.tmp-17rijnpc/vllm.egg-info/entry_points.txt writing requirements to /home/lixing/.cache/uv/builds-v0/.tmpWurXDn/.tmp-17rijnpc/vllm.egg-info/requires.txt writing top-level names to /home/lixing/.cache/uv/builds-v0/.tmpWurXDn/.tmp-17rijnpc/vllm.egg-info/top_level.txt writing manifest file '/home/lixing/.cache/uv/builds-v0/.tmpWurXDn/.tmp-17rijnpc/vllm.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file '/home/lixing/.cache/uv/builds-v0/.tmpWurXDn/.tmp-17rijnpc/vllm.egg-info/SOURCES.txt' creating '/home/lixing/.cache/uv/builds-v0/.tmpWurXDn/.tmp-17rijnpc/vllm-0.11.0rc2.dev71+ge18b714b2.cu118.dist-info' creating /home/lixing/.cache/uv/builds-v0/.tmpWurXDn/.tmp-17rijnpc/vllm-0.11.0rc2.dev71+ge18b714b2.cu118.dist-info/WHEEL running build_py running build_ext -- The CXX compiler identification is GNU 9.4.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Build type: RelWithDebInfo -- Target device: cuda -- Found Python: /home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/bin/python (found version "3.10.18") found components: Interpreter Development.Module Development.SABIModule -- Found python matching: /home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/bin/python. -- Could NOT find CUDA (missing: CUDA_INCLUDE_DIRS CUDA_CUDART_LIBRARY) (found version "11.8") -- Configuring incomplete, errors occurred! [stderr] /home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/torch/_subclasses/functional_tensor.py:279: UserWarning: Failed to initialize NumPy: No module named 'numpy' (Triggered internally at /pytorch/torch/csrc/utils/tensor_numpy.cpp:81.) cpu = _conversion_method_template(device=torch.device("cpu")) /home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools_scm/_integration/version_inference.py:51: UserWarning: version of None already set warnings.warn(self.message) CMake Warning at /home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/torch/share/cmake/Caffe2/public/cuda.cmake:31 (message): PyTorch: CUDA cannot be found. Depending on whether you are building PyTorch or a PyTorch dependent library, the next warning / error will give you more info. Call Stack (most recent call first): /home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/torch/share/cmake/Caffe2/Caffe2Config.cmake:86 (include) /home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/torch/share/cmake/Torch/TorchConfig.cmake:68 (find_package) CMakeLists.txt:84 (find_package) CMake Error at /home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/torch/share/cmake/Caffe2/Caffe2Config.cmake:90 (message): Your installed Caffe2 version uses CUDA but I cannot find the CUDA libraries. Please set the proper CUDA prefixes and / or install CUDA. Call Stack (most recent call first): /home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/torch/share/cmake/Torch/TorchConfig.cmake:68 (find_package) CMakeLists.txt:84 (find_package) Traceback (most recent call last): File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/command/editable_wheel.py", line 139, in run self._create_wheel_file(bdist_wheel) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/command/editable_wheel.py", line 340, in _create_wheel_file files, mapping = self._run_build_commands(dist_name, unpacked, lib, tmp) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/command/editable_wheel.py", line 263, in _run_build_commands self._run_build_subcommands() File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/command/editable_wheel.py", line 290, in _run_build_subcommands self.run_command(name) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 357, in run_command self.distribution.run_command(command) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/dist.py", line 1104, in run_command super().run_command(command) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 1021, in run_command cmd_obj.run() File "<string>", line 268, in run File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/command/build_ext.py", line 99, in run _build_ext.run(self) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 368, in run self.build_extensions() File "<string>", line 230, in build_extensions File "<string>", line 208, in configure File "/home/lixing/anaconda3/envs/Flightgpt/lib/python3.10/subprocess.py", line 369, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['cmake', '/home/lixing/FlightGPT/vllm', '-G', 'Ninja', '-DCMAKE_BUILD_TYPE=RelWithDebInfo', '-DVLLM_TARGET_DEVICE=cuda', '-DCMAKE_C_COMPILER_LAUNCHER=ccache', '-DCMAKE_CXX_COMPILER_LAUNCHER=ccache', '-DCMAKE_CUDA_COMPILER_LAUNCHER=ccache', '-DCMAKE_HIP_COMPILER_LAUNCHER=ccache', '-DVLLM_PYTHON_EXECUTABLE=/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/bin/python', '-DVLLM_PYTHON_PATH=/home/lixing/slam/Fast-LIO2/devel/lib/python3/dist-packages:/opt/ros/noetic/lib/python3/dist-packages:/home/lixing/anaconda3/envs/Flightgpt/lib/python310.zip:/home/lixing/anaconda3/envs/Flightgpt/lib/python3.10:/home/lixing/anaconda3/envs/Flightgpt/lib/python3.10/lib-dynload:/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages:/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/_vendor', '-DFETCHCONTENT_BASE_DIR=/home/lixing/FlightGPT/vllm/.deps', '-DNVCC_THREADS=1', '-DCMAKE_JOB_POOL_COMPILE:STRING=compile', '-DCMAKE_JOB_POOLS:STRING=compile=24', '-DCMAKE_CUDA_COMPILER=/usr/local/cuda-11.8/bin/nvcc']' returned non-zero exit status 1. /home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/_distutils/dist.py:1021: _DebuggingTips: Problem in editable installation. !! ******************************************************************************** An error happened while installing `vllm` in editable mode. The following steps are recommended to help debug this problem: - Try to install the project normally, without using the editable mode. Does the error still persist? (If it does, try fixing the problem before attempting the editable mode). - If you are using binary extensions, make sure you have all OS-level dependencies installed (e.g. compilers, toolchains, binary libraries, ...). - Try the latest version of setuptools (maybe the error was already fixed). - If you (or your project dependencies) are using any setuptools extension or customization, make sure they support the editable mode. After following the steps above, if the problem still persists and you think this is related to how setuptools handles editable installations, please submit a reproducible example (see https://stackoverflow.com/help/minimal-reproducible-example) to: https://github.com/pypa/setuptools/issues See https://setuptools.pypa.io/en/latest/userguide/development_mode.html for details. ******************************************************************************** !! cmd_obj.run() Traceback (most recent call last): File "<string>", line 11, in <module> File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/build_meta.py", line 468, in build_editable return self._build_with_temp_dir( File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/build_meta.py", line 404, in _build_with_temp_dir self.run_setup() File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/build_meta.py", line 317, in run_setup exec(code, locals()) File "<string>", line 648, in <module> File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/__init__.py", line 117, in setup return distutils.core.setup(**attrs) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 186, in setup return run_commands(dist) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 202, in run_commands dist.run_commands() File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 1002, in run_commands self.run_command(cmd) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/dist.py", line 1104, in run_command super().run_command(command) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 1021, in run_command cmd_obj.run() File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/command/editable_wheel.py", line 139, in run self._create_wheel_file(bdist_wheel) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/command/editable_wheel.py", line 340, in _create_wheel_file files, mapping = self._run_build_commands(dist_name, unpacked, lib, tmp) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/command/editable_wheel.py", line 263, in _run_build_commands self._run_build_subcommands() File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/command/editable_wheel.py", line 290, in _run_build_subcommands self.run_command(name) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 357, in run_command self.distribution.run_command(command) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/dist.py", line 1104, in run_command super().run_command(command) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 1021, in run_command cmd_obj.run() File "<string>", line 268, in run File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/command/build_ext.py", line 99, in run _build_ext.run(self) File "/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 368, in run self.build_extensions() File "<string>", line 230, in build_extensions File "<string>", line 208, in configure File "/home/lixing/anaconda3/envs/Flightgpt/lib/python3.10/subprocess.py", line 369, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['cmake', '/home/lixing/FlightGPT/vllm', '-G', 'Ninja', '-DCMAKE_BUILD_TYPE=RelWithDebInfo', '-DVLLM_TARGET_DEVICE=cuda', '-DCMAKE_C_COMPILER_LAUNCHER=ccache', '-DCMAKE_CXX_COMPILER_LAUNCHER=ccache', '-DCMAKE_CUDA_COMPILER_LAUNCHER=ccache', '-DCMAKE_HIP_COMPILER_LAUNCHER=ccache', '-DVLLM_PYTHON_EXECUTABLE=/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/bin/python', '-DVLLM_PYTHON_PATH=/home/lixing/slam/Fast-LIO2/devel/lib/python3/dist-packages:/opt/ros/noetic/lib/python3/dist-packages:/home/lixing/anaconda3/envs/Flightgpt/lib/python310.zip:/home/lixing/anaconda3/envs/Flightgpt/lib/python3.10:/home/lixing/anaconda3/envs/Flightgpt/lib/python3.10/lib-dynload:/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages:/home/lixing/.cache/uv/builds-v0/.tmpTQTjD1/lib/python3.10/site-packages/setuptools/_vendor', '-DFETCHCONTENT_BASE_DIR=/home/lixing/FlightGPT/vllm/.deps', '-DNVCC_THREADS=1', '-DCMAKE_JOB_POOL_COMPILE:STRING=compile', '-DCMAKE_JOB_POOLS:STRING=compile=24', '-DCMAKE_CUDA_COMPILER=/usr/local/cuda-11.8/bin/nvcc']' returned non-zero exit status 1. hint: This usually indicates a problem with the package or the build environment. (Flightgpt) lixing@DESKTOP-2PJK7EV:~/FlightGPT/vllm$
09-25
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值