Announcements
IMPORTANT. Forum in Read Only mode. You can no longer submit new questions or replies. Please read this message for details
Autodesk Architectural Desktop 2007 & Prior
Welcome to Autodesk’s Autodesk Architectural Desktop 2007 & Prior Forums. Share your knowledge, ask questions, and explore popular Autodesk Architectural Desktop 2007 & Prior topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Project Properties not saving

9 REPLIES 9
Reply
Message 1 of 10
Anonymous
659 Views, 9 Replies

Project Properties not saving

Whenever I create a new project, or attempt to edit existing projects, I can open the dialogs to edit the properties of the project, but they don't save. ie. when I close the dialog, they revert back to their initial setting.
I can open up the .apj file and manually change some things, and they will stay changed, but I that's obviously not the correct method.

Any ideas why this would be happening?
9 REPLIES 9
Message 2 of 10
Anonymous
in reply to: Anonymous

Is your project on a network drive? If so, what NOS are you running?

--

Matt Dillon
Autodesk Architectural Desktop Certified Expert

View my ADT Blog "Breaking Down the Walls" at
http://www.modocrmadt.blogspot.com

wrote in message news:4946477@discussion.autodesk.com...
Whenever I create a new project, or attempt to edit existing projects, I can
open the dialogs to edit the properties of the project, but they don't save.
ie. when I close the dialog, they revert back to their initial setting.
I can open up the .apj file and manually change some things, and they will
stay changed, but I that's obviously not the correct method.

Any ideas why this would be happening?
Message 3 of 10
Anonymous
in reply to: Anonymous

The projects are stored on a hard drive connected by a network cable.
So the answers to your questions are "yes" and "none".

The server drive we use is here
Message 4 of 10
Anonymous
in reply to: Anonymous

By NOS I meant what network operating system are you running?

--

Matt Dillon
Autodesk Architectural Desktop Certified Expert

View my ADT Blog "Breaking Down the Walls" at
http://www.modocrmadt.blogspot.com

wrote in message news:4946481@discussion.autodesk.com...
The projects are stored on a hard drive connected by a network cable.
So the answers to your questions are "yes" and "none".

The server drive we use is
href="http://www.snapappliance.com/page.cfm?name=1100main&nav=1100">here
Message 5 of 10
Anonymous
in reply to: Anonymous

Yeah, there is no network operating system. The workstations are running WinXPpro, and they hook into a router. The Snap Server also just plugs into the router. It acts (and is) a hard drive that is accessible to all the workstations. It has no processor, or operating system.

I did create a new project on my local drive, which was editable and functional. So the problem lies in creating a usable project on the Snap Server.

Check that link I posted above for info on the unit.
Thank you.
Message 6 of 10
Anonymous
in reply to: Anonymous

Knowing nothing about your "Snap Server", I'd still have to say that's where
your problem lies. Either there are permissions issues or there is something
in the communications protocol that is preventing Project Navigator and
Project Browser from properly saving data to the XML file.

I've seen similar situations on other non-Windows-based NOS's.

--

Matt Dillon
Autodesk Architectural Desktop Certified Expert

View my ADT Blog "Breaking Down the Walls" at
http://www.modocrmadt.blogspot.com

wrote in message news:4946519@discussion.autodesk.com...
Yeah, there is no network operating system. The workstations are running
WinXPpro, and they hook into a router. The Snap Server also just plugs into
the router. It acts (and is) a hard drive that is accessible to all the
workstations. It has no processor, or operating system.

I did create a new project on my local drive, which was editable and
functional. So the problem lies in creating a usable project on the Snap
Server.

Check that link I posted above for info on the unit.
Thank you.
Message 7 of 10
Anonymous
in reply to: Anonymous

It functions just like a remote drive. Like if another workstation had a shared directory that was write-enabled, or if a usb flash drive were plugged in. Same functionality, permissions, etc...

Do you know of any programming issues, where ADT wouldn't like to work with a project in either of those examples?
Message 8 of 10
Anonymous
in reply to: Anonymous

I'm not familiar with the protocols being used, so I really can't answer
that, beyond saying that, again, I have seen issues with Project Navigator
when being used in a non-Windows NOS environment.

--

Matt Dillon
Autodesk Architectural Desktop Certified Expert

View my ADT Blog "Breaking Down the Walls" at
http://www.modocrmadt.blogspot.com

wrote in message news:4946525@discussion.autodesk.com...
It functions just like a remote drive. Like if another workstation had a
shared directory that was write-enabled, or if a usb flash drive were
plugged in. Same functionality, permissions, etc...

Do you know of any programming issues, where ADT wouldn't like to work with
a project in either of those examples?
Message 9 of 10
Anonymous
in reply to: Anonymous

scothand wrote:
> It functions just like a remote drive. Like if another workstation had a shared directory that was write-enabled, or if a usb flash drive were plugged in. Same functionality, permissions, etc...

> Do you know of any programming issues, where ADT wouldn't like to work with a project in either of those examples?

Your "Snap Server" does indeed use some type of NOS, else it could not
"Talk" over the network or process information.

According to http://www.snapappliance.com depending on what type of
device you have a variety of transfer and file protocols that are
controllable via a browser. I think you should call whomever set this up
and let them know it's not working properly (that's not to say ADT isn't
brain dead when implementing stuff, but ADT works fine with win NT, 2k &
2003 servers). Perhaps start with talking a look at how the device does
it's file locks, perhaps it is not releasing them, or another person has
the file locked for writing (most likely). Turning on or off NetBEUI,
and looking at your NetBIOS over TCP/IP settings on the device and the
workstations could be the next step.... Either way, you need to get
someone familiar with your network setup to trouble shoot it.


--
David Kurtz
Peckham & Wright Architects, Inc.
Columbia, Missouri
Message 10 of 10
damian.keckeisen
in reply to: Anonymous

I am having the exact same problem with the project properties not saving after editing anything. 

 

The only way around it I found was to immediatley open another project after editing the properies, then switching back. 

 

This only started happening when we upgraded from Arch 2009 to Arch 2012.  Same network, same operating systems.  Nothing is set to read only. 

 

Anyone have any idea on the fix???

 

Damian

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report