ArchiCad path in PM

[Anonymous]

I did a search and can't seem to find this issue (though I thougt I'd read it before). Anyway, I'm trying to update a PM file after linking to a renamed PLN. Trouble is, as PM is trying to update, it gives me a message - see attached. Needless to say, I've been using it problem-free on this machine for quite some time, so this message is weird, to say the least.

Anybody have any ideas?

[Anonymous]

Sergio, Just curious if you have you recently updated to the US (2219) Version. I am not saying that this "fix" is causing the Error, but I guess I am always a little worried of updating.

If it ain't broken do not fix it.

Your signature still states the (2172), but we often forget to change this.

[Anonymous]

Jay wrote:
Sergio, Just curious if you have you recently updated to the US (2219) Version.

Nope, not yet. I don't like updating when I'm close to a deadline, which is the case right now. Too many risks I'd rather not deal with.

[Anonymous]

Sounds like you and me both would not like Automatic Updates at program start-up as mentioned here.

[Anonymous]

K, now this is getting quite a bit more frustrating. I am trying to pull the views into Plotmaker and have nothing but problems. I tried doing it from a different machine, and it was telling me that it can't open the file. I figured the file may be corrupted, so I merged it to a new file, copied the layer settings, etc to the new file and CREATED the viewsets (is there a way to copy those over also or do you have to create them from scratch?).

After all this, PM STILL can't read the file. I need to issue a submittal on Monday, and so far no go. ANY help would be appreciated. None of the setting have changed lately, and other projects worked well. Could it be the fact that I have some (4) unloaded Xrefs in this project? Somebody? Anybody? I haven't tried it yet, but I may just end up exporting the views as PlotMaker files, even though I prefer not to go that route.

[__archiben]

Jay wrote:
Sounds like you and me both would not like Automatic Updates at program start-up as mentioned here.

just because they're available doesn't necessarily mean that you've got to press the 'go' button! that discussion was more about the availability of new updates and patches wasn't it? i have many applications with automatic update detection built in . . . none of them will install anything without my say so but at least i know when an update is available!

~/archiben

[__archiben]

Sergio wrote:
...so I merged it to a new file, copied the layer settings, etc to the new file and CREATED the viewsets (is there a way to copy those over also or do you have to create them from scratch?).

unfortunately not.

After all this, PM STILL can't read the file. I need to issue a submittal on Monday, and so far no go. ANY help would be appreciated. None of the setting have changed lately, and other projects worked well. Could it be the fact that I have some (4) unloaded Xrefs in this project? Somebody? Anybody? I haven't tried it yet, but I may just end up exporting the views as PlotMaker files, even though I prefer not to go that route.

can it read the views in other files? have you tried sharing the project as a teamwork file (different file 'type') and seeing if PM can read the PLP views? are you sure you're not using an older version of plotmaker with a newer version of archiCAD (clutching at straws!)?

failing that, a re-install of archiCAD? it could be that the system's file-type configuration has got a bit screwy. i wouldn't know where to begin unravelling that on a PC though . . . sorry.

~/archiben

[Djordje]

Just reinstall ArchiCAD. To be VERY safe, unistall and reinstall. Don't repair. Apply patched, don't forget to keep you WE and SSIs safe, as well as any libraries changed.

I have seen this only once, on an extremely messy laptop ...

[Ignacio Azpiazu]

If you can afford the time to unlink/embed and relink every drawing, switching everything to PMKs is rock-solid, and works faster, and just avoids the whole BGArchiCAD mess and Teamwork Admin views mess.

Probably not a nice thing to do before a deadline, but it's nice to know that that *will* work if nothing else works.

[Aussie John]

Have you renamed or moved the software folder or renamed the application? That would cause that error.