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!
|
|
Admin Account
Posted: 01 Feb 08 2:10 PM
|
Internal Risk Management at my company would like to restrict the use of the Admin account in our SalesLogix system. We have tried to create an user who has the rights to create remote databases and execute SQL but is not able to create new users. Unfortunatly the new user doesn't seem to have the same abilities as the Admin user.
Issues:
1. The remote databases that it is creating don't seem complete
2. The SQL statements only seem to work on part of the database.
Has anyone else experienced this?
Thank you! |
|
|
|
Re: Admin Account
Posted: 02 Feb 08 5:20 PM
|
What vers Slx? - I have no problem w/ this in v7.2.1. in fact, I'm not aware of any problems in this area (Roles) in 6.2.6/7.0.a/7.2.1 (current supported versions of Slx.).
Was this a database that had been upgraded from a 5.x? - If so, it's possible there are "internal" issues that are causing the problem. I'd suggest contacting SalesLogix Tech Support.. this is teh kind of thing they deal with.
--
RJLedger - rjlSystems |
|
|
|
Re: Admin Account
Posted: 02 Feb 08 5:46 PM
|
Can you elaborate on what you mean by 'don't seem complete'? A subset of tables, a subset of accounts, partial tables, ...?
Similarly in point 2 - can you give an example to clarify what you mean?
Cheers
Phil |
|
|
|
Re: Admin Account
Posted: 02 Feb 08 9:10 PM
|
| Thank you. This is a database that was recently upgraded from v5.2.6. I will call Sage on Monday, and I'll also try to get some more details for you on Monday after that call. |
|
|
|
Re: Admin Account
Posted: 24 Mar 08 5:01 PM
|
The error that I'm getting in makine the remote data bases is "Database creationfailed : Access violation at address 008BC165 in module 'Admin.exe'. Read of address 0000003D" and the solution to that error is to delete the tables that are in resynctabledefs that are not in the database any more. Refer to Sage resolution ID 470752 for more info.
The "error" with executing SQL had to do with the account ownership for the records in the database. My user had all the permissions possible but there were still 344 accounts that it couldn't view, but I think those accounts are personal accounts, or miscategorized accounts (since that is less than 3% of the total accounts in the database).
So it appears that my problems are solved for now. Thanks to everyone who helped me identify these issues. |
|
|
|