![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Inability to retrieve data from DOORS Topic Summary: Total lock out of DOORS database from a single client PC Created On: 22-Feb-2006 16:21 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
As of Wednesday last week I am unable to open any folder ot project in DOORS 8.0. I have logged in using the Administartor account and my account on the PC and cannot get past the top level directory view. If I go to another PC and login all is well. To make matters more interesting, I can create a new user in the database set security to that user and logout. This would suggest that I can actually alter files in the database. The new user I created cannot login on the suspect PC.
As a side note. I also have DOORS 7.1 running on this machine. The DOORS 7.1 session works fine. I exit out of the 7.1 session and try 8.0 and the same conditions described above happens. I did uninstall the DOORS 8.0 app and the DOORS 7.1 app. Reloaded them and nothing changed. I did do a total PC backup and reinstall Window XP and reload the DOORS 8.0 app. It worked one time. Once I logged out of DOORS and tried to enter it again, the same things happen. Telelogic has never seen this issue. Has anyone ever seen this? Ed Janonis |
|
![]() |
|
![]() |
|
Its very likely that the local PC is accessing a local V8.0 database on that client; and is NOT accessing your production database. Run the following DXL from both clients. It queries the client for where it thinks the data is located. The 2nd printed paramater is the one you care about.
string DData1 = getenv("Data") string DData2 = getenv("DOORSDATA") print ".......<" DData1 "> <" DData2 ">\n" When run from my local sandbox DB I get this printout: .......<19353@DOORSServer> <37788@LouieMachine> Wheras when I run it from my client to the productionDB I get this printout: .......<19353@DOORSServer> <19353@DOORSServer> <<< Note to the several of you gurus who noticed: Yes, IT set up our data port to be the default license port for Telelogic licensing, 19353. Yup, out of 50,000 available ports they HAD to pick the one that would cause the most confusion. Grrrrrrr but I digress.... >>> Notice the change to the 2nd parameter; that's the one currently in use. If your printouts are the same on both clients then the rest of this messages if FUBAR. I access my Sandbox Database by creating a new DOORS icon and redirecting the data; the "target" of the icon looks like this: "C:\Program Files\Telelogic\DOORS 7.1\bin\doors.exe" -d 37788@LouieMachine notice the "-d" parameter is the same as the 2nd parameter in the first printout above. When you installed DOORS you probably also installed the Server software on this client, and likewise directed the DOORS client to access it. To reach the production machine you need the port@server info you get from the printout from a client that works, then create a new DOORS icon, perhaps named "Doors 8.0 Production" and insert the "-d port@server" onto the end. I'd rename your existing icons something like "Doors 8.0 Local". - Louie [1] Its also possible you chose to install the "Doors Tutorial" which sets up a server on your client, and the DOORS icon you use is accidentally the tutorial one. The symptoms are the same as if you selected to load the DOORS server when installing. [2] If your printouts are the same then I suppose its possible your particular client is disallowed from talking to that server and you'll need "Dumbo the IT Magician" to find and fix it. But don't call him Dumbo until he's done. |
|
![]() |
|
![]() |
|
Well I have narrowed it down to the network connection. The server timesout waiting for my client to respond. Somewhere my packets are getting dropped or my PC never sent the packets. We are now playing with the wait timing at the server.
Dumbo is not a happy camper.
|
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.