I have a SQL 2000 (SP3) running on a Windows NT 4.0 (SP6) box used in our test environment. The SQL Server was configured to run under the local system account before I got here. In an effort to standardize things, I tried changing the SQL Service account to run under a designated domain user account purpose built for the job. We use this particular account for all of our new-build servers (which are W2K). This domain account is configured to be a "Power User" on the NT 4.0 Server in question.
Soon after changing things over to run under the new account, all the developers complained that they could no longer connect to the server. I could through QA and EM, but none of the developers could.
The developers are using WebLogic and JDBC drivers for the most part. I wasn't aware that the SQL Server service account affected client connectivity. Was I wrong or is there something else at work here?
Thanks,
hmscottDamn...I'm dealing with something similar right now...
The SSSA run things on behalf of the server...
My guess is that they all connect using sa blank (or whatever, connection pooling id and are still connectiong using sql server auth) and now that it's trusted, their connections are wrong...
How do they connect?
Like when you register a server in EM?
I don't think the service account has anything to do with it...
MOO|||Hi Brett,
They're connecting via various user accounts that are application-specific. Unfortunately, I am only beginning to make progress on convincing management to swing to all trusted connections. The developers insist that WebLogic doesn't support the concept of running under a service account.
Anyway, one guy was using sa, others were using different application accounts. I was able to connect successfully using a trusted connection (but then, I'm a Domain Admin, too, so there's no telling for sure.
It's far from an ideal setup; I'm just trying to correct things bit by bit.
Regards,
Hugh|||Hi Brett,
The developers insist that WebLogic doesn't support the concept of running under a service account.
That may be true...we use websphere and we set a connection pooling account that authenticates through sql server...but it's 1 id and many connections
Anyway, one guy was using sa
Hugh
There's always one...
Still no one is using the SSSA to connect...right?|||No, no one is using that account. I'm sure because the pasword is quite complex and other than being documented in a restricted folder for the DBAs, it's not known.
Thanks for your time...
Regards,
hmscott
Showing posts with label configured. Show all posts
Showing posts with label configured. Show all posts
Thursday, March 29, 2012
Monday, March 19, 2012
Changing SQL authentication method
Have a central SQL box (SQL server 2000 SP3a) which serves
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanksOn Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:
>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanksOn Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:
>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary
Labels:
authentication,
box,
central,
changing,
configured,
database,
method,
microsoft,
mysql,
oracle,
server,
servers,
servesrequests,
sp3a,
sql,
web,
windowsauthentication
Changing SQL authentication method
Have a central SQL box (SQL server 2000 SP3a) which serves
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanksOn Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:
>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi chaps
Thanks for the advice - thought as much, I'll give it a
whirl.
Gary|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanksOn Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:
>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi chaps
Thanks for the advice - thought as much, I'll give it a
whirl.
Gary|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary
Changing SQL authentication method
Have a central SQL box (SQL server 2000 SP3a) which serves
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanks
On Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:
>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks
|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks
|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanks
On Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:
>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks
|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks
|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary
Labels:
authentication,
box,
central,
changing,
configured,
database,
method,
microsoft,
mysql,
oracle,
server,
servers,
servesrequests,
sp3a,
sql,
web,
windowsauthentication
Thursday, March 8, 2012
Changing Reporting Website Language
Hi
We use English Server Operating Systems and Applications and German Client Software.
When we use our for German language configured Internet Explorers the Reporting Website is displayed in somewhat horrible translations.
How are we supposed to get the English website without changing the language settings at each IE we use?
You can remove the de driectory in the Report Manager\bin directory. This will disable the German translation. Just tried it myself and it works.
|||Thanks, it worked :).
Subscribe to:
Posts (Atom)