Got a laptop here, running Windows 2000. When the laptop is undocked or even just unplugged from the network, if you start Word or Excel they will run for a few seconds and then crash.
Any ideas on where to start?
Printable View
Got a laptop here, running Windows 2000. When the laptop is undocked or even just unplugged from the network, if you start Word or Excel they will run for a few seconds and then crash.
Any ideas on where to start?
Error message?
Event viewer?
Have apps been installed to "Run all from network?"
Were they installed on admin account?
What do you mean by crash? (What are symptoms/displays?)
Ditto what NooNoo said....
Good luck!
Application popup: WINWORD.EXE - Application Error : The instruction at "0x77805c55" referenced memory at "0x013d3000". The memory could not be "written".
Office has been installed locally under the admin account.
When unplugged from the network and with MS Word or Excel started, it pops up the above message after a few seconds, and then Word or Excel goes down.
strangely.... might have something to do with it.
Also network printers which are set as default printers and finally service packs need reapplying.
Quote:
Originally Posted by NooNoo
It's not Outlook, since I specifically do not install it here (Lotus Notes).
It does use a networked printer.
I'll check service packs on Monday.
Corrupted template files will crash Word and Excel. Rename or delete the Normal.dot files for these apps, then start them.
Well, I don't think that Office is to blame. Here's why:
Office was at SR-1, upgraded to SR-3. No change in behavior.
Windows was at SR-2, upgraded to SR-3. No change in behavior.
Got irritated with MS Office, so I installed OpenOffice 1.1.0. OpenOffice also crashes in the same way. That's what got me thinking that it is a different problem.
New info: If you have Word or Excel started before unplugging the network, it does not crash. If you start them after unplugging, they crash.
check the default "save to" file setting.
had that probl when users had the default on a network or mapped drive
:redeyes:
Quote:
Originally Posted by Drone2903
Nope, his default is to his C: Drive.
Another one of those mysterious god damn office installer issues ? or more correctly Microsofts Installer MSI ...
The installer that is used to patch office is 'broke' updates for it are included in sp1 for xp & I think sp3 for w2k, this affects pretty much all versions of office & no amount of patching that fixes it.
What you have to do is completely remove office, then patch xp/w2k, then re-install office & then patch that, it mightn't be that at all, but this ones got me many times ! :eek2:
There's a host of mysterious issues connected with this (& none of them are on the kb, because of course if you get the order of install right nothing should be wrong), worth eliminating if nothing else..
BTW what error kicks back from openoffice?
(I like openoffice muchly, pdf authoring support & diy flash authoring too all added to my favourite word 'free' ! :D)
[I understand this behaviour seems to be assocaited with products other than Office, however, you might like to try installing this MS Office 2000 feature and see if it can assist you further with your troubleshooting
Good Luck
Quote:
Originally Posted by Commander Klarg
OK, then this:
try to "disable" the card before unplugging it.
If that helps or change the message in any ways, I suspect the memory is not properly released when word/excel is trying to adress it.
If that's the case, try a good old "exclude" of all the mem used by this card.
keep us posted.
I'm gonna give it one more try, and it is still doesn't want to work, I will probably go with the format and re-load. Probably take me less time to do. :mad: :guns:
Here is what OpenOffice gave me for a message:
---------- report ----------
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE errormail:errormail PUBLIC "-//OpenOffice.org//DTD ErrorMail 1.0//EN" "errormail.dtd">
<errormail:errormail xmlns:errormail="http://openoffice.org/2002/errormail" usertype="">
<reportmail:mail xmlns:reportmail="http://openoffice.org/2002/reportmail" version="1.0" feedback="false" email="">
<reportmail:title></reportmail:title>
<reportmail:attachment name="description.txt" media-type="text/plain;charset=UTF-8" class="UserComment"/>
<reportmail:attachment name="user.dmp" media-type="application/octet-stream" class="UserDump"/>
</reportmail:mail>
<officeinfo:officeinfo xmlns:officeinfo="http://openoffice.org/2002/officeinfo" build="645m19(Build:8693)" platform="wntmsci8.pro" language="01" procpath="C:\Program Files\OpenOffice.org1.1.0\program\" exceptiontype="0xC0000005" product="OpenOffice.org"/>
<systeminfo:systeminfo xmlns:systeminfo="http://openoffice.org/2002/systeminfo">
<systeminfo:System name="Windows NT" version="5.0" build="2195" locale="0x00000409"/>
<systeminfo:CPU type="x86"/>
</systeminfo:systeminfo>
<errormail:Stack type="Win32">
<errormail:StackInfo pos="0" ip="0x7800167C" rel="0x0000167C" ordinal="wcscmp+0x0000000A" name="MSVCRT.DLL" path="C:\WINNT\system32\"/>
<errormail:StackInfo pos="1" ip="0x04244C8B"/>
</errormail:Stack>
</errormail:errormail>
I have noticed that Excel no longer crashes, but Word and OpenOffice still do.
long shot: is the default printer a network printer?
(if so, go with a local printer as default)
word can be sensitive to what is the actual printer as it has a direct impact on the page format.
Dan
I know what the openoffice error relates to anyway & maybe your office crashes crahes are related ... MSVCRT.DLL - to fix that one up you need to go get - the Microsoft Libraries Update - its a libarary of standard C calls that many applications use, periodically it gets updated but certain installers introduce older or non standard versions of it which can cause problems.
Drone:
The default printer is a network printer, and it's the only printer he's got available.
confus-ed:
I also suspected MSVCRT.DLL, but when I took a look at it, there didn't seem to be anything out of the ordinary compared to other Win2K machines.
Worth a try, though.
Well, it had something to do with the networked printer. I deleted the printer, and then checked to see if it would crash, and it didn't!
I then reloaded the printer and it's still working! Bonus!
Thanks to all for your suggestions! :thumbs: