[blueshockeynut]

Ok gang,

Looked thru to see if I could find anything on this and have had no luck.

Running 4.1.4 for GW, we decided to make the switch from SQL Authentication to Windows Trusted Authentication, no problem, went thru like a champ and is running grand.

Here in lies the problem, our DBA went to go change the "sa" user id password on the SQL box, when he went to do that, we started getting a ton of errors between the BES and the SQL Database, once we reverted back to the old password everything was fine.

Does the BES hold the SQL Authentication anywere that I should know about, or is cached somewere, as the DBA's really want to change that password now.

Any help would be great, Thanks.

B

[marduo]

How did you do switch over to Trusted? Did you use the Configuration Manager? Did you do a test?

[blueshockeynut]

Used the server configuration manager, did the test, even ran a couple of tests from the SQL box, everything works fine, it just seems that when we go to change the "sa" password the SQL box has a fit. Almost like it is cached somewere.

B

[marduo]

What's the error message? Did you restart SQL?

[ashworth]

Did you run through the wizard or just change it on the one tab. To make the change you should go through the wizard to make sure the services are stopped so they are no longer user SA and then started using Windows Auth.

[blueshockeynut]

Ash, did not go thru the wizard, just changed it on the one tab. Will give that shot.

marduo, wish i had the error message to post, it was more on the SQL side then the BES, and I dont believe the DBA guys restarted the server.

Will give both of these a try and let everyone know.

Thanks.

B

[penguin3107]

I don't think this is BES related at all... because even when set up with SQL authentication BES doesn't use the sa account. It would use the BES service account. (besadmin, or something like it.)

Unless you had BES connecting to SQL using the sa account... which would just be NUTS.

[blueshockeynut]

Point well made, but at the time we were having major issues with AD, and that was the only account BES would talk to SQL on, so we used it for about 4 days, before we finally got the AD crappola figured out.

B