Re: Attention people licensing 7.1 on a Linux server
Hey David- thanks for the follow-up. We don't have a defect ID. The tech we were on the phone with included a note he would be looking into the issue. Here is the work note he put in after our webex: Phone Call - Outbound to BOB MILLER Held a Webex with Bob Miller, Charles and Chris. Charles and Chris are the engineers while Bob is the project manager. Charles showed me the error he was getting whenever he applied the licenses using the User Tool. He told me that they were getting this error regardless of the license they tried to apply. Sudipta from the licensing support team had provided them a temporary license and even this one did not work. This was a new Red Hat Linux server, where they installed AR Server 7.1. I told Chris that I was able to successfully applied a license on a Redhat Linux, but I had used the Admin on 7.0.1 tool to do this. He said he had tried the Admin tool on 6.3 an dhad gotten the same error. He then quicly installed the 7.0.1 Admin tool and applied the license and sure enough it worked! He then went and applied the permanant non-expiring license and that also worked just fine. Interesting!! They were happy in getting the server license, there were a couple more questions and I told them I would provide them information on the following issues. 1. On the Admin licenses window (form), why does the format show 6.0? What does this mean? 2. Why doesn't the 7.1 User tool work for applying the license? I was going to try it and see if I got the same error. Get back to them with these answers. The issue number was ISS03180336. If you got it to work using the 7.1 user client then I suppose we still have an issue that could be specific to us, but with a work around of using the older admin tool. Chris Moore From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Easter, David Sent: Friday, October 05, 2007 12:48 PM To: arslist@ARSLIST.ORG Subject: Re: Attention people licensing 7.1 on a Linux server FYI, I followed up with development on this issue and we couldn't duplicate it in house. Adding or upgrading a valid license (i.e. not expired) through the Administration Console to an AR System 7.1.00 server running on Linux worked just fine. Do you have a defect number logged against your issue? I'd like to ensure that the information you posted applies to all customers or perhaps identify that this was a unique situation for you. Thanks, -David J. Easter Sr. Product Manager, Service Management Business Unit BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carpenter, Michael Sent: Friday, September 28, 2007 2:45 PM To: arslist@ARSLIST.ORG Subject: Re: Attention people licensing 7.1 on a Linux server ** Chris, I also saw your previous post about this issue. We had the same issue you described with the "key is not valid for this server" followed by the "BMC Software hereby grants licensee..." messages except we are running Windows 2003 Server and SQL Server 2005. It turned out that when we purged our license from our old 6.3 server, the new license generated for our 7.1 server showed the "Number of Licenses" as 3. BMC Support regenerated our license key with "Number of Licenses" as 1 and it worked just fine. Michael Carpenter From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Moore, Chris Sent: Friday, September 28, 2007 9:28 AM To: arslist@ARSLIST.ORG Subject: Attention people licensing 7.1 on a Linux server ** We've had an issue open with BMC for a couple of weeks now because we could not get a license applied on our Red Hat 5 server. As you know, you have to use the User tool to apply licenses in 7.1. We'd input the information, get a warning that the key was not valid for the server, then a conformation that "BMC herby grants use of..." making it look like it was accepted. We found out it wasn't when we tried to install Incident and the def file for City was failing because of the 2000 max record limitation. BMC sent a few different keys, none of which worked. Today, a BMC rep asked if we had tried using the admin tool to apply the licenses. I told him I had tried our 6.3 admin tool and got the same error. He said he had done it with the 7.0.1 admin tool and it worked, so we downloaded it and they took. Apparently there is some sort of bug with Linux ser
Re: Attention people licensing 7.1 on a Linux server
FYI, I followed up with development on this issue and we couldn't
duplicate it in house. Adding or upgrading a valid license (i.e. not
expired) through the Administration Console to an AR System 7.1.00
server running on Linux worked just fine.
Do you have a defect number logged against your issue? I'd like to
ensure that the information you posted applies to all customers or
perhaps identify that this was a unique situation for you.
Thanks,
-David J. Easter
Sr. Product Manager, Service Management Business Unit
BMC Software, Inc.
The opinions, statements, and/or suggested courses of action expressed
in this E-mail do not necessarily reflect those of BMC Software, Inc.
My voluntary participation in this forum is not intended to convey a
role as a spokesperson, liaison or public relations representative for
BMC Software, Inc.
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Carpenter, Michael
Sent: Friday, September 28, 2007 2:45 PM
To: arslist@ARSLIST.ORG
Subject: Re: Attention people licensing 7.1 on a Linux server
**
Chris,
I also saw your previous post about this issue. We had the same issue
you described with the "key is not valid for this server" followed by
the "BMC Software hereby grants licensee..." messages except we are
running Windows 2003 Server and SQL Server 2005. It turned out that
when we purged our license from our old 6.3 server, the new license
generated for our 7.1 server showed the "Number of Licenses" as 3. BMC
Support regenerated our license key with "Number of Licenses" as 1 and
it worked just fine.
Michael Carpenter
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Moore, Chris
Sent: Friday, September 28, 2007 9:28 AM
To: arslist@ARSLIST.ORG
Subject: Attention people licensing 7.1 on a Linux server
**
We've had an issue open with BMC for a couple of weeks now because we
could not get a license applied on our Red Hat 5 server. As you know,
you have to use the User tool to apply licenses in 7.1. We'd input the
information, get a warning that the key was not valid for the server,
then a conformation that "BMC herby grants use of..." making it look
like it was accepted.
We found out it wasn't when we tried to install Incident and the def
file for City was failing because of the 2000 max record limitation.
BMC sent a few different keys, none of which worked.
Today, a BMC rep asked if we had tried using the admin tool to apply the
licenses. I told him I had tried our 6.3 admin tool and got the same
error. He said he had done it with the 7.0.1 admin tool and it worked,
so we downloaded it and they took.
Apparently there is some sort of bug with Linux servers and the user
tool licensing. If anyone is planning to upgrade to 7.1 on a Linux
server, remember to keep a copy of the 7.0.1 admin tool around until
there's a patch for this.
Chris Moore
__20060125___This posting was submitted with HTML in
it___
___
NOTICE: This communication and any attachments ("this message") may
contain confidential information for
the sole use of the intended recipient(s). Any unauthorized use,
disclosure, viewing, copying, alteration,
dissemination or distribution of, or reliance on this message is
strictly prohibited. If you have received this
message in error, or you are not an authorized recipient, please notify
the sender immediately by replying to
this message, delete this message and all copies from your e-mail system
and destroy any printed copies.
__20060125___This posting was submitted with HTML in
it___
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
Re: Attention people licensing 7.1 on a Linux server
Chris,
I also saw your previous post about this issue. We had the same issue
you described with the "key is not valid for this server" followed by
the "BMC Software hereby grants licensee..." messages except we are
running Windows 2003 Server and SQL Server 2005. It turned out that
when we purged our license from our old 6.3 server, the new license
generated for our 7.1 server showed the "Number of Licenses" as 3. BMC
Support regenerated our license key with "Number of Licenses" as 1 and
it worked just fine.
Michael Carpenter
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Moore, Chris
Sent: Friday, September 28, 2007 9:28 AM
To: arslist@ARSLIST.ORG
Subject: Attention people licensing 7.1 on a Linux server
**
We've had an issue open with BMC for a couple of weeks now because we
could not get a license applied on our Red Hat 5 server. As you know,
you have to use the User tool to apply licenses in 7.1. We'd input the
information, get a warning that the key was not valid for the server,
then a conformation that "BMC herby grants use of..." making it look
like it was accepted.
We found out it wasn't when we tried to install Incident and the def
file for City was failing because of the 2000 max record limitation.
BMC sent a few different keys, none of which worked.
Today, a BMC rep asked if we had tried using the admin tool to apply the
licenses. I told him I had tried our 6.3 admin tool and got the same
error. He said he had done it with the 7.0.1 admin tool and it worked,
so we downloaded it and they took.
Apparently there is some sort of bug with Linux servers and the user
tool licensing. If anyone is planning to upgrade to 7.1 on a Linux
server, remember to keep a copy of the 7.0.1 admin tool around until
there's a patch for this.
Chris Moore
__20060125___This posting was submitted with HTML in
it___
___
NOTICE: This communication and any attachments ("this message") may contain
confidential information for
the sole use of the intended recipient(s). Any unauthorized use, disclosure,
viewing, copying, alteration,
dissemination or distribution of, or reliance on this message is strictly
prohibited. If you have received this
message in error, or you are not an authorized recipient, please notify the
sender immediately by replying to
this message, delete this message and all copies from your e-mail system and
destroy any printed copies.
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
Attention people licensing 7.1 on a Linux server
We've had an issue open with BMC for a couple of weeks now because we could not get a license applied on our Red Hat 5 server. As you know, you have to use the User tool to apply licenses in 7.1. We'd input the information, get a warning that the key was not valid for the server, then a conformation that "BMC herby grants use of..." making it look like it was accepted. We found out it wasn't when we tried to install Incident and the def file for City was failing because of the 2000 max record limitation. BMC sent a few different keys, none of which worked. Today, a BMC rep asked if we had tried using the admin tool to apply the licenses. I told him I had tried our 6.3 admin tool and got the same error. He said he had done it with the 7.0.1 admin tool and it worked, so we downloaded it and they took. Apparently there is some sort of bug with Linux servers and the user tool licensing. If anyone is planning to upgrade to 7.1 on a Linux server, remember to keep a copy of the 7.0.1 admin tool around until there's a patch for this. Chris Moore ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
