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!
|
|
sysdba password
Posted: 23 May 06 5:36 PM
|
fiogf49gjkf0d What are the potential problems with changing the sa and sysdba passwords every 30 days?
There has to be something.
Thanks,
Ian |
|
|
|
Re: sysdba password
Posted: 23 May 06 6:43 PM
|
fiogf49gjkf0d Changing the sa password would have no effect. The effect of changing the sysdba password depends on the version of SLX you're on. If it is v6 or higher, then not too bad since you just have to change it on the SLX Server. If it is v5.x or lower then a real pain since you have to make the change in the BDE config for the alias on each machine. |
|
|
|
Re: sysdba password
Posted: 24 May 06 6:12 AM
|
fiogf49gjkf0d Ryan,
What about the sync server, etc? We run 6.2 and always had issues with the sync server after changing a password. Actually I think it was the SLX admin password that caused the great amount of issue.
Are there guidelines somewhere that outlines the procedures that have to be done when changing the sysdba or admin passwords? I'm guessing the SA password don't matter much beyond remembering what it is.  |
|
|
|
Re: sysdba password
Posted: 24 May 06 2:06 PM
|
fiogf49gjkf0d All SLX applications (for v6 and up) do not store the database level passwords. The get those from the SLX server, so as long as the passwords are changed on the SLX server then that is all the matters. |
|
|
|
Re: sysdba password
Posted: 25 May 06 7:56 AM
|
fiogf49gjkf0d The main thing that we encountered when we changed our Admin password had to do with the sync server/service. We were told to simply stop the service, change the password, rerun the sync server manually (logged in as the SLXSync user), and then restart the service. We ended up needing to actually reboot the server to get the sync service to run correctly again.
Also, don't forget any custom interactions with SalesLogix connectors that use the Admin password. They will need to be updated too. |
|
|
|
Re: sysdba password
Posted: 25 May 06 6:26 PM
|
fiogf49gjkf0d Now wait, are we talking database level passwords, or SLX ones?
The sync service will read the database level connection info (ie: password change) from the SLX server - however, you would need to cause it to re-read that from the SLX server. IIRC, that info is only read once when it is first stared (so you'd have to cause that to change again). This would be the same for any SLX user that the service used to connect to the SLX server and provider with. |
|
|
|
Re: sysdba password
Posted: 26 May 06 11:03 PM
|
fiogf49gjkf0d There was a defect in SLX v6.1 where the Admin password was stored (encrypted) in the Sync server job definition. If you changed the Admin password, the sync server job did not get updated. You had to actually delete the Sync server job and re-create (sometimes editing the job worked as well).
That defect was corrected in v6.2 and possibly in a later v6.1.x service pack or hot fix.
|
|
|
|
Re: sysdba password
Posted: 26 May 06 11:09 PM
|
buy sertraline 50mg buy sertraline uk fiogf49gjkf0d Any external integrations will likely be effected as an SLX user name and password is - by necessity - stored somewhere for the integration application(s) to use.
examples: KnowledgeSync, DynaLink, Scribe, Inaport, FAX Rush?, etc.
|
|
|
|
Re: sysdba password
Posted: 01 Jun 06 2:59 PM
|
fiogf49gjkf0d Originally posted by Todd Hardin
That defect was corrected in v6.2 and possibly in a later v6.1.x service pack or hot fix. |
|
You are right Todd - SP1 for 6.1 corrected the issue |
|
|
|