innerconx
asked on
AutoExec.main Error
Windows 98 box running Office 2000.
Everytime Word, Excel or another app that is part of the Suite is opened or closed a pop up appears stating there is an error in the AutoExec.main. Click OK and all goes well. I cannot seem to pinpoint the cause of the error.
I have tried disableing NAV etc., but to no avail.
Any comments would be appreciated. A fresh re install did not help either.
Everytime Word, Excel or another app that is part of the Suite is opened or closed a pop up appears stating there is an error in the AutoExec.main. Click OK and all goes well. I cannot seem to pinpoint the cause of the error.
I have tried disableing NAV etc., but to no avail.
Any comments would be appreciated. A fresh re install did not help either.
ASKER
Yes to all of the above, that's what is so puzzleing.
Hi... some Office documents can have macros that can be triggered when they are opened or closed. Check you normal.dot and book.xlt files.
Bye
Bye
indeed seems like the melissa virus and a security bulletin on this can be found here
http://www.ciac.org/ciac/bulletins/j-037.shtml
but it seems a but dated to spring up now and especially with a virus checker on
you can also try regedit
and look for the melissa signature there in a find if found then just throw ONLY that key away
if that still doesn't help look into the startup directory under the office program directory
HAGD:O)Bruintje
http://www.ciac.org/ciac/bulletins/j-037.shtml
but it seems a but dated to spring up now and especially with a virus checker on
you can also try regedit
and look for the melissa signature there in a find if found then just throw ONLY that key away
if that still doesn't help look into the startup directory under the office program directory
HAGD:O)Bruintje
ASKER
Once again, did the registry check for Melissa as well as a deep scan with updated virus definitions. All negative results for Melissa. This was the first thing I checked on this customers machine.
what about starting the office programs with the SHIFT key still get the error?
the shift key should supress all automatic code at startup
as nfernand said have you checked the templates?
the shift key should supress all automatic code at startup
as nfernand said have you checked the templates?
ASKER
The SHIFT Key still generated the error. I will however check the template for bogus code.
Hi innerconx, any update on this?
Hello innerconx@lc, what came out the test?
ASKER
In the end, I dumped all of their templates and macros, which solved the problem. Shortly thereafter they lost their drive due to a mechanical failure, and of course they never listened to me about doing back-ups.
In fact I expanded their network today and FINALLY got them to invest in some imaging software and a dedicated back up drive.
In fact I expanded their network today and FINALLY got them to invest in some imaging software and a dedicated back up drive.
hehe so a corrupt drive or something ? at least you can go on now because this problem is *solved* by itself
what to do with the Q?
i would say
-PAQ and a refund of the points
:O)Bruintje
what to do with the Q?
i would say
-PAQ and a refund of the points
:O)Bruintje
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This error is caused by Acrobat's PDFwriter macros. One cause for this error is uninstalling Acrobat.
To fix it look in the Microsoft Office directory and check the startup and XLstart folders for leftover PDF Writer files. Uusually you can just delete them to cure the error.
To fix it look in the Microsoft Office directory and check the startup and XLstart folders for leftover PDF Writer files. Uusually you can just delete them to cure the error.
Have you checked for viruses with a current signature? The stuff I found about autoexec.main pointed to the Melissa virus. You can run a free, updated scan at http://housecall.antivirus.com