| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Error connecting MS SQL Server 2005 SP3 |
« View previous topic :: View next topic » |
| Author |
Message
|
| golam1983 |
 Posted: Wed Jun 12, 2013 2:04 pm Post subject: Error connecting MS SQL Server 2005 SP3 |
 |
|
Apprentice
Joined: 27 Jun 2008
Posts: 35
|
folks,
I was testing a simple test flow using WMB 7.0.0.5 to fetch some data from MS SQL Server 2005 SP3 using ODBC.
MQInput -->Compute -->MQOutput
SQL server I am trying to connect accepts windows NT Authentication method.
The error I am receiving -
| Code: |
| Database error: SQL State ''28000''; Native Error Code '18456'; Error Text ''[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.''. |
Result of mqsicvp
| Code: |
C:\Program Files\IBM\MQSI\7.0>mqsicvp MB7BROKER -n XXXXXX
BIP8270I: Connected to Datasource 'XXXXXX' as user 'xxxxx\xxxxxx'. The datas
ource platform is 'Microsoft SQL Server', version '09.00.4035'.
===========================
databaseProviderVersion = 09.00.4035
driverVersion = 03.85.1132
driverOdbcVersion = 03.52
driverManagerVersion = 03.52.3012.0000 |
Test from ODBC Adminitrative tool was successful too.
I issued mqsisetdbparms too (does not seems relevent as we need windows authentication).
Any insight to fix or address the error will be a help. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Jun 12, 2013 2:17 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Change the broker service to run under a different windows user id.
Instead of, you know, the LocalService user.
Or, really, issue mqsisetdbparms. |
|
| Back to top |
|
|
| golam1983 |
| Posted: Wed Jun 12, 2013 2:39 pm Post subject: |
|
|
Apprentice
Joined: 27 Jun 2008
Posts: 35
|
thanks mqjeff.
| Code: |
| Change the broker service to run under a different windows user id. Instead of, you know, the LocalService user. |
that resolved the issue. There was no need for mqsisetdbparms. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 12, 2013 2:52 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| golam1983 wrote: |
thanks mqjeff.
| Code: |
| Change the broker service to run under a different windows user id. Instead of, you know, the LocalService user. |
that resolved the issue. There was no need for mqsisetdbparms. |
Until you need to access a different SQLServer database from the same broker using a different userid...
You can also look at the properties of the DSN in the ODBC control panel. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
