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: DoorsNET Session Manager
Topic Summary:
Created On: 2-Jul-2004 22:02
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.
 2-Jul-2004 22:02
User is offline View Users Profile Print this message


Andrew Troup

Posts: 4
Joined: 4-Dec-2003

After upgrading from 7.0 to 7.1, I can't get the DoorsNET session manager
to start. The service keeps dying. I've called tech support but no luck yet!

Has anyone else had this problem?

Thanks,
Andrew
Report this to a Moderator Report this to a Moderator
 3-Jul-2004 23:35
User is offline View Users Profile Print this message


Ewen Miller

Posts: 99
Joined: 20-Nov-2002

This sounds like a similar problem when upgrading from 5 to 6 - session manager can get confused with the previous DOORSnet installation. As I recall the fix was: you uninstall the previous DOORSnet session manager via the DOS prompt and install via the DOS prompt - the exact workaround is under the "Known Issues" section of the Telelogic website.

Ewen Miller
QinetiQ Ltd
emiller@QinetiQ.com
Report this to a Moderator Report this to a Moderator
 6-Jul-2004 19:01
User is offline View Users Profile Print this message


mary gibbons

Posts: 27
Joined: 9-Oct-2002

You may have to navigate to "C:\Program Files\Telelogic\DOORS 7.1\tools\doorsnet\bin" or wherever your doornet bin is installed > via a cmd prompt. Then at the cmd prompt type in dnsesman -remove. This will remove the doorsnet session manager. Then to reinstall the doorsnet session manager use dnsesman -install.

You could also try to the DOORSNet session manager in console mode until it dies again and send Telelogic support the error messages from the output.

These are the steps:
Stop the doorsnet session manager. On the server, in the Control Panel, go to Administrative Tools > Services. Right-click on the DOORSnet Session Manager and click Stop.

Open a command prompt. Navigate to "C:\Program Files\Telelogic\DOORS 7.1\tools\doorsnet\bin" or wherever your doorsnet bin is and run this command:

C:\Program Files\Telelogic\DOORS 7.1\tools\doorsnet\bin>dnsesman -console

That will run the session manager in console mode and display errors that occur.

Send the error messages to Telelogic support.



Report this to a Moderator Report this to a Moderator
 6-Jul-2004 19:22
User is offline View Users Profile Print this message


Andrew Troup

Posts: 4
Joined: 4-Dec-2003

Thanks--I'll try these suggestions!

Andrew
Report this to a Moderator Report this to a Moderator
 20-Jul-2004 23:37
User is offline View Users Profile Print this message


Justina Loar

Posts: 3
Joined: 11-May-2004

Andrew,

Any luck yet?

I am having the same problem, every time I reboot the server the session manager service dies and I have to do a DNSESMAN -remove and -install to get it to start.

I would like to know why this is happening and fix it so it does not happen again. Support said they do not know.

-Justina
Report this to a Moderator Report this to a Moderator
 21-Jul-2004 13:13
User is offline View Users Profile Print this message


Andrew Troup

Posts: 4
Joined: 4-Dec-2003

Justina,
The problem for us was a corrput registry entry. One of the keys for FlexLM was set incorrectly.
It was the key that specifies which port to look for the license manger on. Somehow, when we
upgraded to 7.1, it added some data to the key for the LM port, it added "@ourhostname." Written correctly, the key should be
"port@ourhostname". So somehow, the port got dropped off.

The strange part was that I didn't get any FlexLM errors, even though it was a FlexLM key
that was messed up. The fix was to delete the "@ourhostname" data in the registry key,
and leave the old data alone "c:\license.dat". Before I started hacking it up that key
had @ourhostname and c:\license.dat.

Hope this helps,
Andrew

Edited: 21-Jul-2004 at 13:15 by Andrew Troup
Report this to a Moderator Report this to a Moderator
 27-Jul-2004 23:46
User is offline View Users Profile Print this message


Justina Loar

Posts: 3
Joined: 11-May-2004

Thank You Andrew,

Your solution worked for me!!


Thanks a million.
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.