11/29/2024 9:23:36 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss installing SalesLogix and general installation topics. View the code of conduct for posting guidelines.
|
|
|
|
Unable to Retire Network Users
Posted: 01 Apr 10 2:28 PM
|
Hopefully someone has run into this.
I am installing SLX 7.5.0.1484 on a server that had a previous installation of SLX 7.0?? I did extensive removal of the previous SLX (see below). When I run the Administrator for the first time, strangely, all the old licenses are still there (in red), though I thought everything was removed. It also said I had too many Web and Network users. The previous system had 30 network, my current install is 10. I have been able to 1) delete previous licenses, 2) install new licenses 3) retire 2 Web Users and 24 Network Users. I am not able to retire the lat 6 network users and cannot get past this error in the Administrator, "Unable to Retire 6 Network Users". I do not have the previous install's CustomerNo. SLX is obviously still seeing the old install and licensing somehow, but how, where? Is there something I can delete or remove?
Thanks in Advance.
Tim Conway
My new install is to use SQL 2005, the previous install SQL 2000. I have fully (I think) removed the previous install, that is, uninstalled client and administrator, all database files, misc references to SLX in the registry (of which there were many) and any remaining SLX files I could find just laying around on the machine. I shut off SQL Server 2000 and only have SQL 2005 running. I only know to look for "SalesLogix" and there may be other file names I can search for. Any ideas?
|
|
|
|
Re: Unable to Retire Network Users
Posted: 02 Apr 10 9:32 AM
|
OK, found this on Sage
How to manually remove SalesLogix when unable to remove through Add/Remove Programs
I'll post how it goes....
Thanks
Tim |
|
|
|
Re: Unable to Retire Network Users
Posted: 02 Apr 10 12:45 PM
|
OK, in the spirit of "since there are only so many days in a lifetime, it reaches a point where you get it working and forget the rest", we have reached an acceptable "solution".
!. The Sage "How to manually remove SalesLogix when unable to remove through Add/Remove Programs" was of no help for the current "how to get rid of licenses and retire users" problem, which does not say it will not have beneficial effect on the install. Do it, you need as clean an install as possible.
2. The problem was after complete uninstall and manual removal of everything SalesLogix on the server (NOTE: be wary of free used servers when the office closes it's doors for good, they can have their problems) the existence of previous licenses from the old install persists. Where, why or how remains at this point a binary mystery. After full install of the new SLX, it's time to install licenses. But opening the Administrator in EVAL database shows in RED all previously installed licenses as still existing!! ("What are you doing here, I thought I got rid of you guys") . It might seem like deleting them is the solution ("teach those old licenses a lesson once and for all"). This was my first mistake. Once deleted, the Administrator detected 6 Network Users, but was unable to retire them. Soooo, why delete the licenses? Remove and reinstall time again. Just add the new ones this time. This is what eventually worked. All the RED licenses are now in binary limbo, but there existence is still known by their RED presence in the administrator, but who cares, the new install works!! Plus, RED adds a little color and interest to the installation.
Hope this helps some fellow sufferer.
Tim |
|
|
|
Re: Unable to Retire Network Users
Posted: 03 Apr 10 10:15 AM
|
Licenses are stored in the Database.
You get rid of old licenses by Clearing the Licenses TAble (or removing them from the License Module on the Administrator).
As far as retiring users, you could flag them all as retired directly in the DB (changing the Type to "R" on the USERSECURITY table) [off course, don't change Admin's type] |
|
|
|
Re: Unable to Retire Network Users
Posted: 03 Apr 10 12:23 PM
|
What is not clear to me though is this; I completely clean out ALL SalesLogix from the server, that is everything I can find, folders, files, registry entries, hidden files, databases, everything stripped to the walls. Then I install clean, new CD, newer version SLX, copy the EVAL and Production database right off CD, put it in a new Drive/Folder location, even a different install and instance of SQL Server (from 2000 to 2005) and shut all SQL 2000 services off prior to install.
All set for a clean install, right?
After "clean install", start the Administrator and there are the old licenses!?? How did they get there, or better, why are the still there?
I don't understand how they can be in the database when it's copied empty off the CD? It's driving me crazy.
I missed something on the complete removal because I can only get into the EVAL database at the moment, the production database, (again, empty and new from the CD) is asking for a password for the admin user when trying to open Administrator and I can't get in. There's no password, but it is detecting the presence of one from somewhere, but where?
Thanks for the help.
Tim |
|
|
|
Re: Unable to Retire Network Users
Posted: 05 Apr 10 7:51 AM
|
Did you rebuild your Connection entries in Connection Manager?
If not, you are probably still pointing to the old Production database, which would explain why it is picking up the old Licenses and the Password.
Bottom line, to clear out the old Licenses, just truncate the Licenses table inside the SLX Database.
|
|
|
|
Re: Unable to Retire Network Users
Posted: 05 Apr 10 9:46 AM
|
You were absolutely right on the Licenses. Opened the table and there they all were. Truncated the table and entered the licenses again and they no longer appear.
The last issues are the continued detection of 7 Network Users that need to be retired and the incorrect login for Admin on the production database when it's an empty database copied from the CD. But we'll be working on that today and will report any results.
Thanks for the help Raul
Tim Conway |
|
|
| |
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|