[foxboro] AIM_AT Authorization Code Gotchas (Users Beware)
- From: Tom VandeWater <tjvandew@xxxxxxxxx>
- To: foxboro <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 17 Feb 2009 09:38:09 -1000
List,
There was a lot of talk about a license regenerator but you
have to be a Foxboro employee to access it. There was also a lot of
hype about a temporary 90 day license that could be used to get you
going but the number changes every 90 days and the users don't have
access to see that number either. Russ Boulay says the current number
is 8f47b67ad and that it is good til May 2009. That just sounds like
a HOSTID but you would still need the individual package authorization
codes for each package so the users are pretty much bound to
contacting Foxboro to get these numbers. Not a good thing if you are
trying to rebuild a box in the middle of the night.
Ed Larsen says that Aim*AT hostid is based on the SID when the
Operating system is loaded. Anytime you use the Dell Restore Cd, it
runs SID walker at the end generating what is supposed to be a unique
SID. When a new HostID is generated, all AIM*AT applications such as
AIMHIS –(AIM*Historian Package), AIMODB -(AIM*AT ODBC Driver Package),
OLEDB1 -(AIM*OLEDB Package), and anything you see in the API_Admin
application window will need new Authorization Codes for each
individual application under the AIM_AT hood. This means that you
have to fill out a form and FAX it to a constantly changing person at
FOXMASS and wait for them to plug your new HostID into an application
that generates a long confusing authorization string for each of your
licensed application subsets. Ed Larsen says there is an email
address that you can send your request to now:
aimauthorization@xxxxxxxxxxxxxxxx
When they mail that back to you, you have to login to the
AIM_AT API_ADMIN environment, locate the NOT AUTHORIZED text adjacent
to the app you want to authorize, click once on NOT AUTHORIZED to
highlight it in Blue, wait a few seconds and click again to make the
text editable, type the exact string that was sent from Foxboro in,
and hope you didn't make a mistake, hit enter and hope it says
AUTHORIZED. This may be the most asinine thing that Foxboro has done
in recent history because you won't get the AIM apps running without
it. If you can restore a full backup to a like Model Box I am told
you don't have to worry about this. If you have to rebuild a box from
scratch you are hosed. You have no hope of getting these critical
apps running until you go back and forth with FoxMass which is time
consuming in Hawaii with the time difference at the very best. This
assumes that you even realize that you have to jump through all of
these hoops to get an application that you paid Foxboro good money for
to restore to a new box that you also paid Foxboro good money for.
This kludge needs to be re-engineered or Foxboro needs to give access
to the Authorization Code re-generator or temporary license info on
their website.
Tom VandeWater
Control Conversions, Inc
Kapolei, HI
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
- » [foxboro] AIM_AT Authorization Code Gotchas (Users Beware) - Tom VandeWater
