Visio 2000 EE Auto-discover broken after MSDE SP4

[Julian Harty]

Visio's Auto-discover now fails to load after I applied
service pack 4 to the MSDE Engine. I have SR-1 of Visio
Enterprise Edition (which works with a password for the
sa account). I've used SQL Profiler (from another server)
to trace the SQL activity and I can see Visio makes
several requests into the ADLClassmap database before it
gives up

NB: This is the 3rd time I've installed Visio 2000 EE to
resolve the Auto-discovery problems. The product doesn't
seem very robust...

 

[al edlund]

perhaps you might share with us a little more on your configuration. Per a recent search
on the download site it appears that the latest MSDE fix is MSDE 2000 for sql2Ksp2 or
sql srv 7 sp4. what is the database version, operating system, and error code(s).

 

[Julian Harty]

The OS is Windows XP Pro SP1 and all auto-updates, IE6
SP1, Office 2000, etc, all patched.

The database is MSDE version 1.0 and I've now reinstalled
it at least 10 times so far. Generally, Visio will work
with SQL service packs upto and including SP3. SP4 seems
to break it, and the post SP4 hotfix 815495 doesn't fix
the problem caused by SP4. Note: There are some reported
problems (on Technet as well) where SP4 for SQL7 fails to
update some shared replication files - which Visio
appears to need for some reason...

I've noticed Visio 2000 EE is very sensitive to SQL
passwords - even with SR-1 of Visio (which I have also
deinstalled and reinstalled at least 5 times). Visio
appears to cache the login info somewhere. If I try to
install SQP service packs 3 and leave a blank sa
password, Visio works OK afterwards. However if I then
use sp_password via OSQL to set a password, Visio
generally complains it can't load, etc. However, and
paradoxically Visio sometimes works, and correctly
prompts me to enter a new password next time I restart
visio.

Finally, the product is prone to disappearing (once I've
managed to get / keep Auto-Discovery working) generally
with an exception in a dll, as follows.

=====================================================
Exception code: C0000005 ACCESS_VIOLATION
Module: C:\Program Files\Visio\Solutions\Network
Diagram\_Bin\vnom.dll
=====================================================

Oh how I wish Microsoft would release a robust, reliable
product...

Hope this answers your questions.

Julian

-----Original Message-----
perhaps you might share with us a little more on your

configuration. Per a recent search

 

[al edlund]

well I think part of my confusion is that when I check my own installation the core
sql server is sql2000 and the Visio is 2002, so that appears to be part of why mine
may be a little more stable. regarding MS making it more stable that is probably a
dream we will have to fight for since the stopped support shortly after I purchased
this version and it is not supported in the 2003 version. my advice has been to those
that need the tool (like I do) is to pretty much dedicate a system to it, stabilize it, and
hope it doesn't break.
I wish I could be more help, but maybe with the additional data you've given somebody
else can chime in.
Al