Quote:
Originally Posted by James Wittrell
In general when an application crashes it writes the information to an
event log. This information should include the application executable,
version number, module name and version with fault address. If the
application is running in safe mode then it is most likely there is
something being loaded in normal mode that is causing Visio to crash. You
may want to open a support case because we will need to review your system
information file and events to figure out what is causing the crash.
James W.
--------------------
James Wittrell;3288310 Wrote:
So as I understand it Visio will run in safe mode. That being the case
do
you have any add-on for Visio that are being loaded during the normal
startup if so you may want disable them. Have you tried performing a
repair
of Visio from add and remove programs? You can also check the event
logs
this may offer some clue to what is going on.
James W.
--------------------
I have tried to install Vision Professional 2007 Professional on a
machine running XP SP3 with an AMD Athlon 64 3400+, with 2GB of RAM. I
previously had installed Office Enterprise 2007, but after getting
frustrated with the new interface, I removed it, an re-installed MS
Office Professional 2003. I did have Visio Professional 2007 installed
along with Office Enterprise, but removed it as well. After
re-installing Office 2003, I then installed Viso Pro 2007. Before I
ran
Office update to check for the latest security updates, etc, I was
able
to run Visio Pro 2007 and all seemed well. After running Office
update,
when I try to start Visio Pro 2007, I immediately get an error which
states that "Microsoft Office Visio has encountered a problem and
needs
to close. We are sorry for the inconvenience." If I close the error
message, I get a message stating that "Visio failed to start correctly
last time. Starting Visio in safe mode will help you correct or
isolate
a startup problem in order to successfully start the program" Visio
will start and run in safe mode. This behavior is exhibited no matter
how I try to access Visio Pro, if I double click on any Visio file or
open Visio from a shortcut or program menu. What could be causing this
problem?
--
Honeybunkle
I have no add-ons listed or installed to the best of my knowledge.
Visio does not let me check any of the options, such as default file
locations for stencils, drawings, etc. The only thing that shows up is
the location of my stencils when running in safe mode. Should I be
looking at the registry keys?
I ran a repair installation from Control Panel and the Office
Diagnostics, but they found nothing wrong. I checked the event logs in
Computer management and found nothing additional In Application
Management, MS Office diagnostic Errors, or MS Office Sessions that
points to anything obvious other than Visio ended in a crash and then
was successfully started in Safe mode. Where else can I look?
--
Honeybunkle
|
Problem now fixed! I did look at the event log but didn't find anything that helped me directly. Yesterday I logged off of my normal user account and logged in as Admin. I tried running Visio 2007 Pro and it started up normally. This got me to wondering what could cause the problem when logged in under my normal user account. There must be something that was an incorrect entry in file locations or files that were trying to be loaded at Visio start up that could be causing the crash. I backed up the registry and then started poking around to find my normal user profile and compare it to the administrator. Low and behold I found it at HKEY_USERS\S-1-5-21-57989841-1214440339-682003330-1003\Software\Microsoft\Office\12.0\Visio. Looking further at the entries, I discovered that locations that were identified under the Application subkey pointed to items that were no longer valid, particularly the drawing path, stencil path and template path. I cleared those item entries, closed the registry, rebooted, and logged back in under my normal user account. Visio now starts normally. It appears that when I uninstalled Visio 2007, the old values for the file locations were still stored in the Registry.
I hope this will help others who may have the same or similar problems. This is sloppy work on the part of the removal of the program. Junk left behind by the uninstall came back to haunt me!
Thanks for your help!