When I have seen licensing problems, it logs it int the Tango log file. Troy
===== Original Message from [EMAIL PROTECTED] at 1/23/02 7:36 pm >Paul, > >Your possible diagnosis of licensing conflicts sounds reasonable. I had >some issues when trying to run T3 and T4 and ServerWatcher on the same >machine. During testing, Pervasive gave me a license number to use that was >valid and didn't conflict with other licenses. Although this didn't solve >my issue, maybe fooling your development machine with a dummy license (from >WITango) would at least confirm your diagnosis. > >Brent > >-----Original Message----- >From: Paul <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> >Date: Wednesday, January 23, 2002 5:13 PM >Subject: Re: Mysterious persistant non-reproducible error in R:Tango > > >>Brent, >> >>> Is your production server ever brought down? Does the dev server still >>have >>> a problem when the other is non-op? >> >>The production server exhibits the same error, but very rarely, and we had >>never seen it before the dev server came online. >> >>I cannot take the production server offline, so I do not know if bringing >it >>down would solve the dev server problem. I sure hope that this is not a >>required test! :) >> >> >>My previous experience with licensing conflicts occured when we tried to >>install a second instance of the same license on another box on the same >>subnet. Tango seems to look for this type of license violation, and >although >>it did not return a meaningful error message, Tango would not function >>correctly on either of the boxes (we were trying to test performance >between >>the two boxes). >> >>This experiment was several years ago, in the days of Tango 3.0. It seems >>possible that whatever this undocumented "feature" of tango was, it could >>reasonably be related to my current problem. >> >>Paul >> >>================================================ >>TO SEE MESSAGE POSTING GUIDELINES: >>Send a plain text email to [EMAIL PROTECTED] >>In the message body, put just two words: INTRO rbase-l >>================================================ >>TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] >>In the message body, put just two words: UNSUBSCRIBE rbase-l >> > >================================================ >TO SEE MESSAGE POSTING GUIDELINES: >Send a plain text email to [EMAIL PROTECTED] >In the message body, put just two words: INTRO rbase-l >================================================ >TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] >In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
