AutoCAD Electrical not using the correct database

[djs]

I recently encountered an issue with ACE 2017. Say I have a computer with ACE 2014 installed. I install ACE 2017. Both are network installations. However they each have different WD.ENV files which point to different catalog databases. When I open ACE2017 and try to do a catalog lookup, I get a message that the catalog database is not in the correct format. I check the project settings and the active catalog is set to the correct 2017 version of the catalog. Other installations of ACE 2017 from the same installer on a clean machine do not have this issue. It looks like ACE 2017 sees the 2014 version and sets all of the file pointers to those values regardless of what the WD.ENV file paths are. I have also checked the Options-> Files and everything is set up pointing to the correct paths.

[Anonymous]

djs,

I had an issue when I deleted the local copy of the ACADE2017 MDB file. Once i put back the local copy back it went to the network copy.

Not sure if this is your issue but might want to check this out:

https://forums.autodesk.com/t5/autocad-electrical-forum/network-mdb-acade2017-quot-could-not-find-fi...

Hope this helps

Dennis

[djs]

Ok did some more testing:\

Typed in (c:ace_find_file "default_cat.mdb" 3) and returns the correct file

Copied the correct network version of default_cat.mdb over the three instances of that find on the workstation

Check the project settings (see attached files)

Don't really know what more to check or change.

[Anonymous]

Is the database working on 1 machine and not another?

What do you mean by working and not working?

The data base will have to be migrated the be able to be used on 2017. The old database of 2014 will not work in 2017.

Thanks

Dennis

[djs]

Many months ago I migrated the database from 2014 to 2017. Both instances are ACE 2017, both are networked and both are suppose to be looking at the same database. According to the settings listing they are. But one works and the other doesn't.

[Anonymous]

Is there another ENV file that the one station maybe looking at?

Search for any ENV files and delete any on the workstation. Make sure the path is at the top on the search files in the options.

Other than that I am also stumped!!!

Good Luck!!!

Dennis

[dougmcalexander]

If you followed my instructions for networking (www.ecadconsultant.com/tips.html) you should all be sharing the same wd.env file.  That said, you don't even need to edit the wd.env file if you followed my instructions for networking.  You move the AeData folder to the network, place this network path at the top of the support file search path, and make certain that any AeData folders left on the local drive of all computers are renamed to AeData_local.  This forces the software to use the same databases for catalog lookup, footprint lookup, schematic lookup, PLC, etc.

[djs]

With our old 214 installation I had a networked WD.ENV file. However due to a bug in AutoCAD which will delete paths if not found, I decided to move the WD.ENV file to the local drive. Both installations are from the same installer which installs the same WD.ENV file. The problem is that I have replaced ALL local instances of the default_cat.mdb files on the non-working machine with the migrated version. Still does not work. The non-working installation is not looking for the default_cat.mdb file in any of the configured paths, instead it is looking in the path configured in the 2014 version!

[TRLitsey]

Hi there,

This may not have anything to do with the price of apples but have you checked the ACE options on the machine that is working correctly to the one that is not?  In one of your posts I think you said you had checked the "Options".  Have you checked both Project Properties support paths AND ACE Options support paths, check behaving machine compared to misbehaving machine?

Good luck

[dougmcalexander]

TRLitsey is on to something. When something defies all reasoning it often turns out to be something fundamental that was missed or assumed to be correct. Try to perform a Lookup on the same component in the same project on both the working and non-working computer. Also compare the Project Settings to verify where the software is looking for the default_cat.mdb to be located. Just right-click over the project name in the Project Manager and choose Settings.

As for the issue related to the software deleting paths if something happens and the network paths are temporarily unavailable, I install a Lisp routine for my customers that runs at startup and resets the path each time AutoCAD Electrical starts up, just in case any were removed. This allows everyone in the design group to take full advantage of the benefits gained by sharing the AeData folder and thus the same wd.env file, databases, projects, etc. Once AutoCAD Electrical finds the AeData folder it can locate everything else by relative path, unless the subfolders under AeData have been moved or renamed.  Note that I have a request on the Idea Station for Autodesk to solve this.  If enough of us "vote up" my idea maybe it can get some attention.

[djs]

Sorry that is not a solution. Both instances are using the same project file. In any case the primary catalog database is not set by the project. In any case is you look at the two settings files you will see that the active catalog is the same between the two of them.

[dougmcalexander]

The project shouldn't point to a different catalog database. You can just use Project Settings to verify that each computer is looking at the same database in the same location.

[djs]

I have attached the two settings screen shot to this post

[TRLitsey]

Bummer,  but those are just the Project Settings.  SOMETHING is different between the two machines.  Have you compared the ACE Options settings?  You have not said anything about Option, just Project Settings and they are not the same thing, similar but not the same.  Sorry this is giving you such heart ache.  I would tend to take a look at Doug's method.  You may have to throw away some of the work that you have done but if you can not find the needle in the hay stack ... well it works or it doesn't.

One last trip down the rabbit hole.  Found this post. it was posted in 2011 but it makes an interesting point that may or may not apply to 2017, I don't know.  The comment that caught my eye was "you can not define the path to the wd.env file from within the wd.env file".  You may want to take a look.  I am thinking it may still be valid only because I find a wd_load.lsp folder in my ACE 2017 install files.

Good luck

https://forums.autodesk.com/t5/autocad-electrical-forum/wd-env-file-env-codes-vs-globals/m-p/3227526...

[rhesusminus]

Is there a project specific database in the projects folder?
Just check the project folder, and see if there's a file there, named the same as the project, with a mdb-extension.

And also, out of curisosity... I answered you on the Autodesk support case. Did you receive the reply from me?

[djs]

There is no project specific catalog. In addition, both computers are using the same project.  I have not received any replies from the support case. I am still looking for a solution.

[rhesusminus]

I've seen this before, where the catalog browser don't care about what the wd.env file says about the folder for catalog.

Can you turn on debugging by typing AEONLISPDEBUG ? Then, open the edit component on let's say a terminal, and press the  catalog lookup button.

Press OK, and get back to the command line (Press F2 to "expand" it).

If you can copy/paste the contents of the command line from the edit component command was issued, maybe we can get a closer clue on what happens.

Regarding the support case... Can you check your spam folder, to see if you've got a reply from directly/autodesk support? I'm sure I answered you there...

[djs]

Ok I have run the debug session, I have attached the results to this posting. Since starting this process, several other users within our organization have encountered the same issue. One of them was/is using a VM. I have a copy of that VM so can more easily preform testing.

[rhesusminus]

Did you press the catalog Lookup here?

[djs]

Yes I did. An update. Autodesk support suggested that I try to do a reset to defaults. There is a program installed and listed in the start menu. That program worked. According to Autodesk support, there are registry entries which override the catalog search path. The reset program changes those registry entries that nothing else touches. I even did a repair/re-install that did not do the trick.

Add one more thing to ACE 2017 weirdness.