These error messages can appear if certain Microsoft Data Access Components (MDAC) Help files are missing or are located in the wrong folder on your hard disk.
Back to the top
RESOLUTION
To resolve this problem, you must re-run the SR-1 Update with verbose logging turned on. To do this, follow these steps: 1. On the Start menu, click Run.
2. In the Open box, type the following command line:
source path\Setup.exe /L2 /V
where source path is the full path to Setup.exe for the SR-1 Update, according to the following table. SR-1 Source <source path>
Windows Installer Office 2000 SR-1 Setup(####)_MsiExec.txt
The #### characters in the log file names are numbers that begin with 0001. They increment by 1 if you run the update multiple times. So the log file with the highest number is the log file for the last time that you ran the update.
NOTE: If you do not see the text "VERBOSE" in the first line of text of the "Office 2000 SR-1 Setup(####)_MsiExec.txt" file, you did not create the verbose log file correctly, and you must repeat the preceding command line with the correct command-line switches.
3. Open the Windows Installer log file by using WordPad, and search for Return value 3.
4. Back up a few lines in the log file to the line that contains the file that the update is having problems patching.
For the 2318 error, it is similar to the following: MSI (c) (8B:87): Note: 1: 2318 2: C:\Program Files\Common Files\System\Ado\ADO210.CHM
For the 1326 error, it is similar to the following: PatchFiles: File: C:\WINDOWS\system32\SQLSOLDB.HLP, Directory: C:\WINDOWS\system32\, Size:
This line identifies the problematic file and its correct location on your hard disk.
5. If the file listed on this line of the log file is listed in the table in step 6, continue with the steps in this article. If the file is not listed in the table, please contact Microsoft Product Support Services.
6. Copy the files listed in the following table from your Office 2000 CD into the specified folder location on your hard disk. File name Office 2000 CD1 location Hard disk location
Ado210.chm Pfiles\Common\System\Ado Program Files\Common Files\
System\ADO
Dao360.chm Pfiles\Common\Msshared\Dao Program Files\Common Files\
Microsoft Shared\DAO
Jetdef40.chm Pfiles\Msoffice\Office\1033 Program Files\Microsoft Office\
Office\1033
Jetsql40.chm Pfiles\Msoffice\Office\1033 Program Files\Microsoft Office\
Office\1033
Msjro.chm Pfiles\Common\System\Ado Program Files\Common Files\
System\ADO
Sqlsoldb.hlp \System See NOTE below.
NOTE: If the problematic file is Sqlsoldb.hlp, identify the correct hard disk location for this file from the log file line in step 4. Then copy Sqlsoldb.hlp from the \System folder on the Office 2000 CD to the hard disk location listed in step 4.
7. Re-run the SR-1 Update with verbose logging enabled. If you encounter another 2318 or 1326 error message, reapply steps 3 through 6 for the latest problem file listed in the log file.
There are in no way any ensures in malware battling, yet try this: in case you have an anti-virus, verify it has the main recent virus definitions and run an entire test with it in secure Mode with Networking. that frequently prevents malware from protecting itself. in case you don’t have one, a lot of human beings right here swear by making use of AVG (it’s loose). I propose you apart from mght acquire advert-conscious loose and Spybot S&D (they’re loose), installation them, replace them and run finished scans with them, lower back in secure Mode With Networking. additionally, turn off equipment restoration to evict any copies of undesirable stuff which would be lurking there. To get into secure Mode with Networking: a million. sign off and reboot your device. 2. while the device starts the reboot sequence, press the F8 key persistently. 3. go with secure Mode with Networking from the resultant menu. 4. Login. If the malware has replaced your password, try logging in as Administrator. by making use of default, Administrator has no password. 5. The device will proceed booting, however the domicile windows own computing gadget will seem diverse. 6. once you're complete doing what you could desire to do, sign off and reboot lower back into regularly occurring mode. notice that in spite of if the anti-malware classes do away with the malware, they won't be waiting to opposite the outcomes. seek the internet for attainable fixes. replace and run finished scans regularly, not purely once you think of you have already got malware. sturdy success.
Answers & Comments
Verified answer
CAUSE
These error messages can appear if certain Microsoft Data Access Components (MDAC) Help files are missing or are located in the wrong folder on your hard disk.
Back to the top
RESOLUTION
To resolve this problem, you must re-run the SR-1 Update with verbose logging turned on. To do this, follow these steps: 1. On the Start menu, click Run.
2. In the Open box, type the following command line:
source path\Setup.exe /L2 /V
where source path is the full path to Setup.exe for the SR-1 Update, according to the following table. SR-1 Source <source path>
------------------------------------------------------
You previously attempted
the SR-1 Update from the
Office Update download C:\Windows\Temp\SR1patch\
SR-1 Update CD <CD-ROM drive letter>:\Setup.exe
This creates the Setup log file and a verbose Windows Installer log file in the \Temp\SR1Patch folder. Log file for Log file name
---------------------------------------------------------------
Setup.exe Office 2000 SR-1 Setup(####).txt
Windows Installer Office 2000 SR-1 Setup(####)_MsiExec.txt
The #### characters in the log file names are numbers that begin with 0001. They increment by 1 if you run the update multiple times. So the log file with the highest number is the log file for the last time that you ran the update.
NOTE: If you do not see the text "VERBOSE" in the first line of text of the "Office 2000 SR-1 Setup(####)_MsiExec.txt" file, you did not create the verbose log file correctly, and you must repeat the preceding command line with the correct command-line switches.
3. Open the Windows Installer log file by using WordPad, and search for Return value 3.
4. Back up a few lines in the log file to the line that contains the file that the update is having problems patching.
For the 2318 error, it is similar to the following: MSI (c) (8B:87): Note: 1: 2318 2: C:\Program Files\Common Files\System\Ado\ADO210.CHM
For the 1326 error, it is similar to the following: PatchFiles: File: C:\WINDOWS\system32\SQLSOLDB.HLP, Directory: C:\WINDOWS\system32\, Size:
This line identifies the problematic file and its correct location on your hard disk.
5. If the file listed on this line of the log file is listed in the table in step 6, continue with the steps in this article. If the file is not listed in the table, please contact Microsoft Product Support Services.
6. Copy the files listed in the following table from your Office 2000 CD into the specified folder location on your hard disk. File name Office 2000 CD1 location Hard disk location
---------------------------------------------------------------------------
Ado210.chm Pfiles\Common\System\Ado Program Files\Common Files\
System\ADO
Dao360.chm Pfiles\Common\Msshared\Dao Program Files\Common Files\
Microsoft Shared\DAO
Jetdef40.chm Pfiles\Msoffice\Office\1033 Program Files\Microsoft Office\
Office\1033
Jetsql40.chm Pfiles\Msoffice\Office\1033 Program Files\Microsoft Office\
Office\1033
Msjro.chm Pfiles\Common\System\Ado Program Files\Common Files\
System\ADO
Sqlsoldb.hlp \System See NOTE below.
NOTE: If the problematic file is Sqlsoldb.hlp, identify the correct hard disk location for this file from the log file line in step 4. Then copy Sqlsoldb.hlp from the \System folder on the Office 2000 CD to the hard disk location listed in step 4.
7. Re-run the SR-1 Update with verbose logging enabled. If you encounter another 2318 or 1326 error message, reapply steps 3 through 6 for the latest problem file listed in the log file.
2
There are in no way any ensures in malware battling, yet try this: in case you have an anti-virus, verify it has the main recent virus definitions and run an entire test with it in secure Mode with Networking. that frequently prevents malware from protecting itself. in case you don’t have one, a lot of human beings right here swear by making use of AVG (it’s loose). I propose you apart from mght acquire advert-conscious loose and Spybot S&D (they’re loose), installation them, replace them and run finished scans with them, lower back in secure Mode With Networking. additionally, turn off equipment restoration to evict any copies of undesirable stuff which would be lurking there. To get into secure Mode with Networking: a million. sign off and reboot your device. 2. while the device starts the reboot sequence, press the F8 key persistently. 3. go with secure Mode with Networking from the resultant menu. 4. Login. If the malware has replaced your password, try logging in as Administrator. by making use of default, Administrator has no password. 5. The device will proceed booting, however the domicile windows own computing gadget will seem diverse. 6. once you're complete doing what you could desire to do, sign off and reboot lower back into regularly occurring mode. notice that in spite of if the anti-malware classes do away with the malware, they won't be waiting to opposite the outcomes. seek the internet for attainable fixes. replace and run finished scans regularly, not purely once you think of you have already got malware. sturdy success.
maybe u should try a differt kind of maple story there is also private maple^^:)
EX:
www.icyms.net
www.juicyms.net
www.ancientms.net