reference issue with Vault

[Anonymous]

Here is my senerio. I have an existing surface in drawing A. I check the
surface and drawing A into Vault. I create drawing B which I also check into
Vault and create a surface reference to the existing surface. I changed my
working folder to the network, now when I check out drawing B, all I see is
Broken AeccDbSurfaceTin Reference in the drawing instead of my surface. I
checked the box to include dependencies when I checked Drawing B out. It
appears that it will only work if the drawings are in the original location
they were when the reference was created. I also tried opening Drawing B in
LDT 2007 and I see the same Broken Reference. What good is vault if there is
no way to share the drawings with other people with different paths or with
different programs? I even tried copying both drawings to my hard drive to
represent someone taking files home to work on and the surface reference
would only show up if I was still mapped to the network drive where my
working folder was and I was logged into Vault. My proxygraphics is set to 1
which is what I would think it should be set to so it would create the
proxygraphic of the reference object so when the actual reference is not
available, it would still display the proxygraphic. This is a very big issue
to us and could stop us from implementing Civil 3D in our multi person
project team environment.

[Anonymous]

1. Xrefs ALWAYS fail if you change paths drastically, this has been the case
as long as they have been around. To achieve what you're after, you need to
be Xrefing the dwg that resides in your working folder. In your case, I'm
not clear on whether or not you changed the Xref path now that the working
folder should be the path for the Xref file.

Also, the way to use Vault from a laptop perspective is to use Offline
Folders. This preserves the drive mapping, pathing, etc., and avoids the
issues you're running into.

2. Proxygraphics are only intended for use for people that do not have the
creating software, i.e. Acad, ADT, etc can use the proxygraphics to display
C3D objects if they choose not to install the full object enabler.

HTH

--
James Wedding, P.E.
Engineered Efficiency, Inc.
Civil 3D 2007
XP Tablet, SP2, 2GHz, 2G
www.eng-eff.com
www.civil3d.com

[Anonymous]

I know the xrefs will fail, but if all the drawings were originally in the
same folder and they are all located in the new folder, then the xrefs will
work. My problem is the surface reference becomes broken with no way of
fixing it.

"James Wedding" wrote in message
news:5187753@discussion.autodesk.com...
1. Xrefs ALWAYS fail if you change paths drastically, this has been the case
as long as they have been around. To achieve what you're after, you need to
be Xrefing the dwg that resides in your working folder. In your case, I'm
not clear on whether or not you changed the Xref path now that the working
folder should be the path for the Xref file.

Also, the way to use Vault from a laptop perspective is to use Offline
Folders. This preserves the drive mapping, pathing, etc., and avoids the
issues you're running into.

2. Proxygraphics are only intended for use for people that do not have the
creating software, i.e. Acad, ADT, etc can use the proxygraphics to display
C3D objects if they choose not to install the full object enabler.

HTH

--
James Wedding, P.E.
Engineered Efficiency, Inc.
Civil 3D 2007
XP Tablet, SP2, 2GHz, 2G
www.eng-eff.com
www.civil3d.com

[Anonymous]

hey james,

i'm experiencing the same problem, at one workstation a surface was referenced from drawing A into another drawing, lets say drawing B, both attached to the same project, working folder not changed, drawing B was then checked in. a short time later at my workstation, i checked out drawing B and the reference was broken. the next day, at the workstation the surface reference was created, drawing B was checked out and the surface reference wasn't broken. any ideas.

[Anonymous]

I've seen some very interesting things with Vault and networking that's even
the slightest bit shaky. 5 minutes in time, everything can change it seem.

Have you checked the default timeout on the IIS that you're using to drive
Vault? There seems to be some issues that come up if that timeout period is
to short. IIRC, it need to be about 900, but don't quote me. Check the docs
on that one!

--
James Wedding, P.E.
Engineered Efficiency, Inc.
Civil 3D 2007
XP Tablet, SP2, 2GHz, 2G
www.eng-eff.com
www.civil3d.com

[Anonymous]

James Wedding wrote:

> Have you checked the default timeout on the IIS that you're using to drive
> Vault? There seems to be some issues that come up if that timeout period is
> to short. IIRC, it need to be about 900, but don't quote me. Check the docs
> on that one!


Just checked the IIS default timeout on my server - I remember the Vault
install requiring that I change that. It's set to 900, and I remember
changing it to what Vault recommended.

Did I mention that I owe you big for suggesting VMWare?

--
Jason Hickey

Civil 3D 2007, SP1A
Dell Precision M70
2 GIG RAM, 256 MB nVidia Quadro FX Go1400
Intel Centrino 2 gHz Processor

http://beneaththelines.blogspot.com

[Anonymous]

what did vault recommend

[Anonymous]

Scott Laxton wrote:
> what did vault recommend


900, which is what I set it to.

--
Jason Hickey

Civil 3D 2007, SP1A
Dell Precision M70
2 GIG RAM, 256 MB nVidia Quadro FX Go1400
Intel Centrino 2 gHz Processor

http://beneaththelines.blogspot.com

[Anonymous]

how do i get to that setting

[Anonymous]

Vault Administrator will let you set it there.
Advanced settings

John P.

[Anonymous]

jpostlewait wrote:
> Vault Administrator will let you set it there.
> Advanced settings


John - does it need to be set on the server IIS properties as well?

(showing my ignorance a bit)


--
Jason Hickey

Civil 3D 2007, SP1A
Dell Precision M70
2 GIG RAM, 256 MB nVidia Quadro FX Go1400
Intel Centrino 2 gHz Processor

http://beneaththelines.blogspot.com

[Anonymous]

I don't know.
That's just the place we used to set it.
Don't try to get into an ignorance game with me.
You will lose badly.

It's Friday afternoon.
YIPPEE!!!!!!!!!!!!!

John P.

[Anonymous]

i think i win this game of ignorance...i discovered the problem...the referenced object is done so via the working folder file...the two workstations' working folders were set to different paths...thus creating a broken reference path. sure, makes sense now.

[Anonymous]

Yet another reason for Shared Working folders and Vault level
enforcement....

--
James Wedding, P.E.
Engineered Efficiency, Inc.
Civil 3D 2007
XP Tablet, SP2, 2GHz, 2G
www.eng-eff.com
www.civil3d.com