[THIN] Re: Connection Licensing -- Please help

  • From: DMelczer@xxxxxxxx
  • To: thin@xxxxxxxxxxxxx
  • Date: Thu, 15 Aug 2002 07:23:13 -0400

Jim-

qfarm just shows me the servers that have direct SQL connections, not the
machines going through the data collector.

I want all of the servers in one farm, one zone for now -- I don't think
chfarm is going to help...unless you think I should change it to a temp farm
and then back again?

Thanks for the input.

-Dave Melczer
dmelczer@xxxxxxxx


-----Original Message-----
From: Jim Kenzig [mailto:jimkenz@xxxxxxxxxxxxxx]
Sent: Wednesday, August 14, 2002 3:19 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Connection Licensing -- Please help



What does qfarm command from a dos prompt show you? You should use the
chfarm command to change a server to a different farm.

JK

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of DMelczer@xxxxxxxx
Sent: Wednesday, August 14, 2002 3:13 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Connection Licensing -- Please help



Looks like connection licensing happens to be the topic du jour...

I have a production farm with 2 servers connecting to a backend SQL database
through a dedicated data collector.

I'm trying to migrate the farm to provide more flexibility (namely for a DR
site), so I just put online a new server which bypasses the data collector
and accesses the SQL database directly through a system DSN, thereby
becoming another data collector, I think.

The new server sees the server licensing, but not the connection licensing.
No users can log in except for designated MetaFrame administrators.  Here's
the real kicker -- the new server can list ALL licensing information in the
SQL database through the CMC, but the connection licenses are reported as
ZERO...huh?

Also, the new server only sees other servers that have a direct SQL
connection (my production data collector, namely)...the main production
metaframe boxes don't appear in the server section of the CMC navigation
tree.  However, when I publish an app, NFuse picks up the new app without an
issue.

All server configs are as follows:

NT4 TSE SP6
MetaFrame XPa 1.0 FR1

SQL database is Microsoft SQL Server 2000

Does anyone have an idea what to check?  I've already ensured that the new
server is in the same farm and zone as the production boxes, I've checked to
ensure the Feature Release level is consistent, and I've double and
triple-checked the Product Code to ensure it is consistent.

Someone please help...this is driving me crazy!

Thanks in advance.

-Dave Melczer
dmelczer@xxxxxxxx


===================================
This weeks Sponsor:
ThinPrint
- High resolution, DRIVER FREE PRINTING with no loss of quality in color.
- Removes print spooling and rendering tasks from your terminal server.
http://www.thinprint.com
===================================
For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link.

http://thethin.net/citrixlist.cfm


*****************************************************************************
Please be advised that this transmittal may be a confidential attorney-client 
communication or may otherwise be privileged or confidential.  If you are not 
the intended recipient, please do not read, copy or re-transmit this 
communication.  If you have received this communication in error, please notify 
us by e-mail (postmaster@xxxxxxxx) or by telephone (call us collect at 
212-403-4357) and delete this message and any attachments. Thank you in advance 
for your cooperation and assistance.
*****************************************************************************


===================================
This weeks Sponsor:
ThinPrint
- High resolution, DRIVER FREE PRINTING with no loss of quality in color.
- Removes print spooling and rendering tasks from your terminal server.
http://www.thinprint.com
===================================
For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link.

http://thethin.net/citrixlist.cfm

Other related posts: