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!
|
|
User account corruption
Posted: 10 Apr 06 7:40 PM
|
fiogf49gjkf0d I have a huge dilemma here!
When I was trying to change the User Type to Retired User, the following message pops up:
Other users report to this user. This user cannot be retired.
The User Type is then reverted but after I clicked on OK, the whole application freezes. Now, Administrator crashes whenever the user list is loading. How can I troubleshoot, as it keeps crashing? Or does anyone know what the problem could be?
I am using SalesLogix Administrator version 6.1.2.
Any suggestions/ideas/fixes welcome!  Thanks!
|
|
|
|
Re: User account corruption
Posted: 11 Apr 06 2:48 AM
|
prednisolon 25 mg prednisolon kol fiogf49gjkf0d This issue has been resolved! Sorry to take up your valuable web space. 
|
|
|
|
Re: User account corruption
Posted: 12 Apr 06 2:28 AM
|
fiogf49gjkf0d Al, it is not a waste of space to have you report an issue and then resolve it yourself  . However, it would be great if you could share with the group how you resolved it.
Thank you!
Timmus |
|
|
|
Re: User account corruption
Posted: 13 Apr 06 8:42 AM
|
fiogf49gjkf0d That happened to me when I inadvertantly set the owner of the company to report to himself. I had to go into SQL and set it back to the admin. |
|
|
|
Re: User account corruption
Posted: 19 Apr 06 3:53 PM
|
fiogf49gjkf0d Here is how to get your USER LIST to load after it hangs when trying to start the SLX administrator tool:
1.Cancel the loading user list in SLX admin.
2.Open EXECUTE SQL, right click and select ADD, then add the contents of line 3 below:
3.Update sysdba.usersecurity set managerid='ADMIN' where userid<>'Admin' and userid=managerid or managerid = ''
4.Select execute statements on the Host database
5.Click Execute! |
|
|
|
Re: User account corruption
Posted: 23 Apr 06 9:52 PM
|
buy amoxicillin canada amoxicillin prescription no insurance lamictal pregnancy registry lamictal pregnancy fiogf49gjkf0d Hi Timmus,
This is how I resolve it:
As I knew the user account that was last updated before the corruption, I started by replicating the error in a copy of my development database and then compared the values of the user in the 2 databases through Enterprise Manager. I narrowed down to 2 tables (userinfo and usersecurity) where the rows had different values and then I replaced them, which solved the problem.
Thanks to all that replied. Hope my solution might help other people too.
Regards,Al 
|
|
|
|