![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Install on Citrix problem - server not found message Topic Summary: Created On: 8-Mar-2007 17:51 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
We currently have DOORS 7.1 running just fine via Citrix. The server has Windows 2003 Standard Edition and Metaframe XP (1.3). I'm trying to install a DOORS 8.1 client pointing to a different data server for testing. I'm not familiar with Citrix, unfortunately.
So...remotely I logged onto the server with an administrator account given to me. I went into install mode and installed the client, no problems. I then published the application copying the properties for 7.1 (changing the executable path, ect.). I changed back to Execute mode and tried launching DOORS 8.1, but I get the message listed below. If I log into Citrix from my computer I also get the message. I get the "Initializing database..."splash screen for a while and then it gives me the "Cannot connect to server 36677@xxx.xx.xxx.xxx, server not found" message. The service is started, because I have no problem getting in using my desktop install, not going through Citrix. I've tried using the server name and IP address with the same results. I can ping the server OK from the Citrix box. Am I leaving out some step in the install process? Telelogic's documentation on this is pretty non-existent as far as I can see. Any thoughts? |
|
![]() |
|
![]() |
|
Not sure I exactly follow, but here's some info that will help.
You get the 'initializing db' splash screen when the DOORS service points to an empty file system location. You should also first have been forced to log into DOORS as the Administrator and SET its initial password. If you are migrating you shouldn't get that login and if you do, cancel since you've made a mistake installing the v8.1 service. If you get 'server not found' errors its because either you misspelled the port, misspelled the server IP or alias, the server is not on your network, the client isn't on the network, or because the server's fire wall has no hole defined for that port. 'Misspelled' often means 'extraneous trailing space' that you cannot see. If you are familiar with the Registry, try this: ** DISCLAIMER ** Edit the registry at your own risk. From Windows, Run >regedit.exe. Navitage here: HKEY_LOCAL_MACINE\SOFTWARE\Telelogic\DOORS\8.1\Config. The 'Data' value shows where the v8.1 DOORS client expects to find the data, and is in the form port@server. I'd copy that value, paste into Notepad, and make sure there are no extraneous spaces. If you are on the test Server housing the DOORS service, this Registry location tells the DOORS service where to find its data: HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\DOORS_Server\8.1\Config; value 'ServerData' is the file system location, value 'PortNumber' should be used by the clients. === Upgrade DOORS install === It may be a mistake to use the same port, 36677, for the new version of DOORS even if its on a different service. It will confuse folks. Choose a different port, perhaps 81000. === Same DOORS version on test Server === After I wrote this I see you are installing a new version, so the paragraphs below doesn't apply to you. You of course install the DOORS service and client on the new Test server. THAT client will of course point to that server and service. That works, fine. On normal clients including Citrix, if the test DOORS is the same version and the production DOORS, you do NOT have to reinstall DOORS; in fact you don't want to. Instead, let the client DOORS default to the production server but simply create a new DOORS icon that overrideds the default data location and point to the test server. In the Icon's 'target' field, add " -d TestPort@TestServer". Rename the icon to perhaps "Test DOORS v8.1". e.g. my 'target' looks like this: "c:\Program Files\Telelogic\DOORS_8.1\bin\doors.exe" -d 38801@DoorsTestServer By reinstalling DOORS on the clients you have taken away their pointer to the production server. You should reinstall it back the way it was, although of course you could just make new icons that point to the production server. - Louie |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.