Rick, We encountered this same issue when moving from an old dev server to a new one. What we found is that the AR System Server ID was the same on both servers. I believe this is what causes this error message to come up.
Christopher Pruitt Consultant Specialist EDS - Bank of America I3-Inventory IW Infrastructure Team Phone: +1-972-605-7702 (8-835) mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Confidentiality Notice: This message and any files transmitted with it are intended for the sole use of the entity or individual to whom it is addressed, and may contain information that is confidential, privileged, and exempt from disclosure under applicable law. If you are not the intended addressee for this e-mail, you are hereby notified that any copying, distribution, or dissemination of this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately destroy, erase, or discard this message. Please notify the sender immediately by return e-mail if you have received this e-mail by mistake. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Thursday, February 08, 2007 10:48 AM To: [email protected] Subject: Purging a server license in ARS 6/7 ** How does Remedy limit the ability to run concurrent servers on what is essentially one server license? I ask because I purged a server license about 35 days ago, and have been getting messages since that prohibit a user from being logged on to both the old and new servers at the same time. That seems fair enough - the users can keep working on the old server while I develop on the new one until we're ready to throw the switch. There was no expiration date to enter into the old server license, and there is no "Purge" function in the 6.3 or 7 license GUI, so I assumed that I could keep this arrangement until we were ready to migrate to the new server. Problem is that since this morning, no one could log into either server until we shut the new one down and kept it that way. Anyone who tries gets an ARERR 99 - can't log into <oldserver> and <newserver> until one is shut down. Has anyone seen this before, and if so, how did you get around it? Old server: ARS 6.3 patch 16 New server: ARS 7.0 patch 2 Windows 2003/SQL 2000 -- Rick Cook Cook Enterprises 253-278-4112 __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
