Re: New Computer OE Problem
From: Jim Pickering (jimp_at_mvps.invalid)
Date: 07/09/04
- Next message: PCR: "Re: hosts :-)"
- Previous message: Brian: "Link problem"
- In reply to: E/B: "Re: New Computer OE Problem"
- Next in thread: Steve Cochran: "Re: New Computer OE Problem"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 9 Jul 2004 11:42:03 -0700
The log files can be deleted from the store folder. All they are doing is
wasting disk space as the 6.83 MB file proves.
With respect to the identity, it should create no problems. Once you switch
to it (by closing Outlook Express with the File/Exit and Log Off Identity so
it will prompt you to choose the new one on startup), you can easily import
your messages by using the menu, File/Import/Messages and selecting From an
Identity. This type of corruption is commonly seen when the identity in use
is the "Main Identity" created with a default installation of Outlook
Express while user created identities do not seem to have the same problem.
If you're still unsure, you can make backup copies of both your message
store folder and your WAB (Address Book) files to another location on your
drive for insurance, but the problem will most likely persist until you
create the new identity. Good luck.
-- Jim Pickering, MVP-Outlook Express Please reply only to newsgroup. "E/B" <embillma@earthlink.net> wrote in message news:%2310BGzWZEHA.3228@TK2MSFTNGP12.phx.gbl... > Found 2 files using KB258034 and cleared the 'greyed-out' Read Only > checks. > So far so good altho' the errors have been sporadic over the recent days. > > With respect to the log size in the Store Folder (IF I am at the correct > location): the files are the same as the Identities files found above: one > has 912KB, the other 6.83MB. > > Not being technically inclined - what does that tell me? Should I be > taking > any action? > > Must admit I am leery of fooling with new identity as after trying to > correct earlier problem last month by creating new I ended up with blank > WAB; messed around and 'somehow' created a correct WAB (found a second WAB > with triple entries as there was a time where I didn't see any reaction to > the click and did it, and did it. That is indicative of my limitless lack > of > tech capability). > > Try to search for assistance but admit to hesitancy due to failing to > understand a lot of what is written in the KB. I plead guilty to being a > 'computer user'. > Appreciate the seemingly limitless time the MVPs donate to help we "less > fortunate". > > Jim Pickering wrote: >> Sorry, might want to look at this KB article for some ideas. In >> general, the problem has usually been some corruption has occured in >> the registry for the identity involved. The usual fix is to create a >> new identity, switch to it and import the mail messages from the old >> store folder or identity. The DBX files being marked read only >> should not apply in your case. >> >> But the shlwapi.dll error should go away when you clear the >> troubleshooting boxes. You might also want to look and see what the >> size of the log files in the existing store folder are. Post back >> and let us know what happens. >> >> 258034 - OLEXP: Error Message: Msimn.exe Has Generated Errors and >> Will Be Closed by Windows: >> http://support.microsoft.com/?kbid=258034 >> >> "E/B" <embillma@earthlink.net> wrote in message >> news:OTroQfTZEHA.3228@TK2MSFTNGP12.phx.gbl... >>> Mr. Pickering: >>> Must admit have always (don't know why) had all the troubleshooting >>> items checked; 'no more' on this two-month old computer. Hope that >>> fixes the shlwapi.dll situation. >>> >>> With respect to the first and most troublesome item: are my >>> "ole32.dll" and >>> the "msoe.dll" the same? >>> Ask because twice in the first 5 minutes since compacting I received >>> the same "sorry for the inconvenience" spiel and next click closed >>> the OE. Culprit shown as msimn.exe in module ole32.dll both >>> instances. Haven't noted >>> msoe.dll involved so far. >>> >>> Jim Pickering wrote: >>>> Most msoe.dll errors are caused by corruption in one or more of the >>>> DBX files in your message store folder. Often a manual compacting >>>> while working offline can repair "minor" corruption. If two >>>> attempts at compacting do not fix it, see the advice at this link: >>>> http://www.fjsmjs.com/OE/directdb.htm >>>> >>>> The shlwapi.dll error is usually caused by having the option set in >>>> OE's Tools/Options/Maintenance to create troubleshooting logs to >>>> track down errors in mail handling. Those options should only be >>>> set for serious troubleshooting and then disabled since you can >>>> create huge log files (also stored in the message store folder) >>>> that can grow to immense size since each check for messages only >>>> appends another entry to the log file. Some users have wondered >>>> where all their disk space is going to, only to find they have >>>> created log files that are many megabytes in size. >>>> >>>> "E/B" <embillma@earthlink.net> wrote in message >>>> news:uL%23MuoQZEHA.1764@TK2MSFTNGP10.phx.gbl... >>>>> Follow-up to problem below. >>>>> Just encountered another error window needing to close OE. This >>>>> also was at >>>>> msimn.exe but now module is 'shlwapi.dll'. (Did not find this .dll >>>>> in the OE6 list under About OE?????? - should it be there along >>>>> with the others??) >>>>> Tech knowledge limited here but it appears everything is up-to-date >>>>> (Win Update does not show any Criticals/Svc Pks needed. Could not >>>>> find any assist >>>>> at MS KB or Tomsterdam's site.) >>>>> Help solicited. Thanks >>>>> >>>>> E/B wrote: >>>>>> New 4600 computer (mid - May): 2.8 mhz; 512 RAM; 80 HD; IE and >>>>>> OE 6 (SP1 installed); XP Home (SP1 - build 2600) included from >>>>>> Dell. Also using NSW Pro, Zone Alarm, SpamFighter. >>>>>> >>>>>> Receiving about once-a-day error message telling me OE has to >>>>>> close. Problem at msmin.exe in Module ole32.dll. >>>>>> >>>>>> MS KB tells me this module problem can be resolved by downloading >>>>>> MSMsgr 4 or higher. Have d/l and installed MSMsgr on previous >>>>>> occasion and now have taken version 6.... Shutdown error window >>>>>> has re-occured. >>>>>> >>>>>> Any other suggestions for resolution? Thanks > >
- Next message: PCR: "Re: hosts :-)"
- Previous message: Brian: "Link problem"
- In reply to: E/B: "Re: New Computer OE Problem"
- Next in thread: Steve Cochran: "Re: New Computer OE Problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
