Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Item is not in expected folder
Topic Summary:
Created On: 20-Nov-2003 13:57
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 20-Nov-2003 13:57
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

I've got a module I can open. All the locks (via the DOORS interface and via DXL) have been removed.

However, when I try to delete the module or move it to another folder, I get the "Item not in expected folder" error. I suspect the DOORS server crashed while moving the module last week.

Anybody recognize this problem?

- Louie
Report this to a Moderator Report this to a Moderator
 20-Nov-2003 23:21
User is offline View Users Profile Print this message


Paul Miller

Posts: 376
Joined: 2-Oct-2002

Yuk!!!

Sounds like the database index expected to find the module somewhere else.

Every module has a unique pointer reference, I would say that the DB index has registered a differant location path to that unique pointer reference. So when you try to move/delete it, it complains that it's not in the expected location.

You could try and use the "fullName(Item)" function to reveal the full location path of the module - I'm hopeing that this is reconciled with the DB index so that it shows the expected location. Select the folder that contains the module and use Tools>Edit DXL in the DOORS Explorer window to run the simple loop below.

Item i
for i in current Folder do {
print fullName(i) "\n"
}

Sounds like it could be a job for Telelogic, I would be surprised if they didn't have tools to view the encrypted DB index information and apply a fix.




-------------------------
Paul Miller
Specification Practices Specialist,
EuroCyber,
Melbourne, Australia.
Mobile: +61 (0)418 135 103
Web Site: http://www.eurocyber.biz
E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz
Report this to a Moderator Report this to a Moderator
 21-Nov-2003 15:08
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

I can open the module. 'fullName' and 'name' of both the module and the item show the item in the expected folder. There is only one such item in the Project (and in the current Folder). 'uniqueID' reveals the stored folder path for the module, but I have no access to the server file system.

I was hoping we could look at the file system to debug the problem.

- Louie
Report this to a Moderator Report this to a Moderator
 21-Nov-2003 20:46
User is offline View Users Profile Print this message


Alec Witham Crawford

Posts: 24
Joined: 2-Jul-2003

I am seeing the exact same problem on one of our databases. Unfortunately, Telelogic has been unable to rectify the situation. I'm almost ready to just archive the projects I need and start a new database. Luckily, the project I can't purge is just a sample project.

I'm curious if Telelogic gives you some clues to how to fix the problem.

Alec
Report this to a Moderator Report this to a Moderator
 24-Nov-2003 15:12
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Rumor has it that DOORS server crashed WHILE this module was being moved to a different location. I'll let you know if we figure it out.
Report this to a Moderator Report this to a Moderator
 11-Dec-2003 12:53
User is offline View Users Profile Print this message


Boyd McKillican

Posts: 2
Joined: 16-Jul-2003

Good Luck Louie,

We had this problem twice in the last two years. Based on my experience I can say the following. It is serious. You don't want to change the structure (folders/projects/renaming or deleting modules, etc.) of the project that generates this error message. Get in contact with Telelogic support very soon.

The first time we had this problem (v5.2) the offending module was moved and/or deleted resulting in further incorrect indexing and then a useless database. In the end we had to resort to backups. The second time (v6.0) we were smarter and shutdown the database and fixed the problem immediately, resulting in much less downtime and NO data loss.

I don't know what's going on under the hood, but I would recommend, having support cut out the offending project via exchanging *.dtc files, so that other projects are not affected. Then working on the problem project in a second database created from a backup. Again, have support cut out the offending module(s) until you are able to make an archive (I assume you can't do this on the project right now). Then restore the archive to the first database (and replace all Access rights! These are not carried over in the archive.)

Boyd


-------------------------
Boyd McKillican
T-Systems GEI GmbH
Email: boyd.mckillican@t-systems.com
Internet: www.t-systems.de
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.