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: DOORS 7.1 DB Server (service) keeps stopping
Topic Summary: DOORS 7.1 DB Server (service) keeps stopping
Created On: 11-Dec-2007 21:36
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.
 11-Dec-2007 21:36
User is offline View Users Profile Print this message


Laura Norton

Posts: 17
Joined: 6-Apr-2004

I have DOORS 7.1 on a Windows 2003 server, with the data residing on a Netapp server. The DOORS DB service keeps stopping and I can't figure out why. I moved the data to the local C drive where the server application is installed and it works fine, but I cannot keep it there.

With the DB server pointing to the data on the Netapp server, I log onto the DB server remotely, start the service, and then try to launch Doors from another machine's client. It always gives me the "Cannot connect to 36677@server" type of message, which in my experience means the service isn't started. And, alas, it is not.

This is quite perplexing...I know this configuration works fine and is supported because I have the same configuration on our WAN and many other classified labs.

Have any of you ever seen this happen before?
Report this to a Moderator Report this to a Moderator
 12-Dec-2007 06:31
User is offline View Users Profile Print this message


Pekka Mäkinen

Posts: 276
Joined: 18-Mar-2004

Are there any messages about problems in the Application section in server Events? (Event Viewer / DOORS DB Server)

-------------------------
Pekka.Makinen@softqa.fi
SoftQA Oy -http://www.softqa.fi/
Report this to a Moderator Report this to a Moderator
 12-Dec-2007 10:00
User is offline View Users Profile Print this message


Carl Wilson

Posts: 3
Joined: 6-Dec-2002

I've seen it happen with DOORS 7.1 on a Win2K server - but no reason and no fix. It usually happens after doing an export. Service has always restarted ok and goes on working for weeks or months until I need to do another export. Doesn't always stop then.

Service does get restarted every day due to backup.

Hoping that DOORS 8.2 is better.

Carl Wilson
Thales Underwater Systems
Report this to a Moderator Report this to a Moderator
 12-Dec-2007 19:22
User is offline View Users Profile Print this message


Justin Gravois

Posts: 9
Joined: 4-Aug-2006

The DOORS Server doesn't support mapped drives for the data directory. I know this restriction is in DOORS 8 and later; not sure if it was in DOORS 7.1. When you start the DOORS DB service, it should fail, and the event log entry will say something along the lines of 'Cannot find data directory.' There is a blurb somewhere in the Installation docs about this - took me a while to find after attempting to install a DOORS server this way.

--Justin
Report this to a Moderator Report this to a Moderator
 12-Dec-2007 23:44
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

The notion of 'mapped' drives was dropped in v6, but that notion allowed a single client to access the database directly, presumably locally, without the need for a data service. That is, the v5.2 client could map directly to a file folder and would not map to a Port@Server. That was a disaster when there was more than one DOORS client accessing the same database. Since you are using v7.1 you are obviously not using this sort of 'mapped' drive.

Its strange that the data would not be on the same server as the data service; where 'strange' means 'highly undesirable'. The client has to go across to the network to the service, and now the service has to go across the network to get the data.

I suppose its possible the service is impatient and times-out a data request because the network could not respond fast enough. I don't know how fast is 'should' be, but if you logged into the DOORS service server, started a DOS command prompt, and issued: ping MyNetAppServer, then you may find out how 'far away' that Netapp server really is; perhaps 20ms per ping. Do the same in your classified lab to see how far away the data is from the service, I suspect you may be shockedat the difference. My semi-intellegent semi-educated guess is that if the data is more than 10ms away from the service then you'd have problems. (Compared to Client being 40ms from the Service to have problems).

Its also possible that the DOORS service insits on the data being on a true 'mapped' drive, meaning it accesses is via a drive letter perhaps "g:\Doors-Data"; perhaps it doesn't like a network location perhaps "\\MyNetAppServer\Doors-Data". If you are doing the later, then manually map a drive and change the -Data switch in the service, and restart the service.

- Louie
Report this to a Moderator Report this to a Moderator
 14-Dec-2007 17:52
User is offline View Users Profile Print this message


Laura Norton

Posts: 17
Joined: 6-Apr-2004

Ah...the drive letter suggestion triggers a vague memory of something similar in another lab around 4-5 years ago. It seems like I did in fact have to map a drive and point to the server data that way. (Perhaps I'll take note of it this time...). I can't try it until next week, I have to wait for IT, but I'll post if it works or not.

Thanks so much!
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.