Error: can not connect to the database

Hello
First of all, let me tell you, I have no knowledge of SQL server at all. We
have an SQL Server 2005 that has been installed by an external company. I
have installed a new database on it, using the default settings that were
displayed on my screen.
When I try to connect to the database (I'm a domain administrator),
everything works just fine. If an end user tries the same the following erro
r
is shown of the screen:
Error: can not connect to the database. ConnectionString:
Provider=SQLOLEDB.1; Integrated Security Info=False;Inital
Catalog=ZeugnisManager2006; Data Source=RBS-W11
I'm almost sure that my end user needs some additional rights to have to be
declared in the SQL console... but when I try to add a domain user in the
permissions option, the object isn't recognized... I checked that the Window
s
Authentication is allowed on the SQL server, so I really do not know where t
o
start from now...
Please help me, knowing you should explain it as simply as possible... I
have no idea of SQL Server...
Thanks
NicolasThey need to set Integrated Security =True in their connection string, and
make sure that the nt account they are connecting with can logon to SQL
Serve rand have a db acconut which has rights to the database.
Either that or they should use SQL Authentication with a SQL Account.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Nicolas Heyer" <NicolasHeyer@.discussions.microsoft.com> wrote in message
news:B2AC3BE8-9947-4B3D-99B3-22D7094B3635@.microsoft.com...
> Hello
> First of all, let me tell you, I have no knowledge of SQL server at all.
> We
> have an SQL Server 2005 that has been installed by an external company. I
> have installed a new database on it, using the default settings that were
> displayed on my screen.
> When I try to connect to the database (I'm a domain administrator),
> everything works just fine. If an end user tries the same the following
> error
> is shown of the screen:
> Error: can not connect to the database. ConnectionString:
> Provider=SQLOLEDB.1; Integrated Security Info=False;Inital
> Catalog=ZeugnisManager2006; Data Source=RBS-W11
> I'm almost sure that my end user needs some additional rights to have to
> be
> declared in the SQL console... but when I try to add a domain user in the
> permissions option, the object isn't recognized... I checked that the
> Windows
> Authentication is allowed on the SQL server, so I really do not know where
> to
> start from now...
> Please help me, knowing you should explain it as simply as possible... I
> have no idea of SQL Server...
> Thanks
> Nicolas

Error: can not connect to the database

Hello
First of all, let me tell you, I have no knowledge of SQL server at all. We
have an SQL Server 2005 that has been installed by an external company. I
have installed a new database on it, using the default settings that were
displayed on my screen.
When I try to connect to the database (I'm a domain administrator),
everything works just fine. If an end user tries the same the following error
is shown of the screen:
Error: can not connect to the database. ConnectionString:
Provider=SQLOLEDB.1; Integrated Security Info=False;Inital
Catalog=ZeugnisManager2006; Data Source=RBS-W11
I'm almost sure that my end user needs some additional rights to have to be
declared in the SQL console... but when I try to add a domain user in the
permissions option, the object isn't recognized... I checked that the Windows
Authentication is allowed on the SQL server, so I really do not know where to
start from now...
Please help me, knowing you should explain it as simply as possible... I
have no idea of SQL Server...
Thanks
Nicolas
They need to set Integrated Security =True in their connection string, and
make sure that the nt account they are connecting with can logon to SQL
Serve rand have a db acconut which has rights to the database.
Either that or they should use SQL Authentication with a SQL Account.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Nicolas Heyer" <NicolasHeyer@.discussions.microsoft.com> wrote in message
news:B2AC3BE8-9947-4B3D-99B3-22D7094B3635@.microsoft.com...
> Hello
> First of all, let me tell you, I have no knowledge of SQL server at all.
> We
> have an SQL Server 2005 that has been installed by an external company. I
> have installed a new database on it, using the default settings that were
> displayed on my screen.
> When I try to connect to the database (I'm a domain administrator),
> everything works just fine. If an end user tries the same the following
> error
> is shown of the screen:
> Error: can not connect to the database. ConnectionString:
> Provider=SQLOLEDB.1; Integrated Security Info=False;Inital
> Catalog=ZeugnisManager2006; Data Source=RBS-W11
> I'm almost sure that my end user needs some additional rights to have to
> be
> declared in the SQL console... but when I try to add a domain user in the
> permissions option, the object isn't recognized... I checked that the
> Windows
> Authentication is allowed on the SQL server, so I really do not know where
> to
> start from now...
> Please help me, knowing you should explain it as simply as possible... I
> have no idea of SQL Server...
> Thanks
> Nicolas

error: 18452; very urgent

We have 2 failover servers and one client in our test environment. We
have all the three configured in mixed mode authentication(windows +
sql server authentication). But when we are failing over from 1st
server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login fai
led for
user 'null'. Reason: Not associated with a trusted SQL server
connection.'
I got some clue.
For instance we have ser1 and ser2 as clusters. I registered both in
the client's EM. Now what I did was, I made ser1 to run and stopped sql
service in ser2 (active/passive) through failover. Now in the client's
EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
I failed over to ser2 ( so sql service in ser1 is stopped). But now I
can still be able to access ser1 and also I can access ser2, even I'm
able to open query analyzer in ser1 through EM.But when I try to open
query analyzer directly, it is giving the same error message. ser1 is
the virtual name given to both ser1 and ser2. So I think when
connecting through EM, failover is occuring fine.I'm just wondering why
is this happening only with dsn. Can anybody help me?
Thanks,
Preethihttp://support.microsoft.com/defaul...kb;en-us;555332
"sqldbapree" <mohanpreethi0125@.gmail.com> wrote in message
news:1129898680.495504.25600@.g44g2000cwa.googlegroups.com...
> We have 2 failover servers and one client in our test environment. We
> have all the three configured in mixed mode authentication(windows +
> sql server authentication). But when we are failing over from 1st
> server to 2nd one, we are getting the following error message,
> 'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
> State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login f
ailed for
> user 'null'. Reason: Not associated with a trusted SQL server
> connection.'
> I got some clue.
> For instance we have ser1 and ser2 as clusters. I registered both in
> the client's EM. Now what I did was, I made ser1 to run and stopped sql
> service in ser2 (active/passive) through failover. Now in the client's
> EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
> I failed over to ser2 ( so sql service in ser1 is stopped). But now I
> can still be able to access ser1 and also I can access ser2, even I'm
> able to open query analyzer in ser1 through EM.But when I try to open
> query analyzer directly, it is giving the same error message. ser1 is
> the virtual name given to both ser1 and ser2. So I think when
> connecting through EM, failover is occuring fine.I'm just wondering why
> is this happening only with dsn. Can anybody help me?
> Thanks,
> Preethi
>

error: 18452; very urgent

We have 2 failover servers and one client in our test environment. We
have all the three configured in mixed mode authentication(windows +
sql server authentication). But when we are failing over from 1st
server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'null'. Reason: Not associated with a trusted SQL server
connection.'
I got some clue.
For instance we have ser1 and ser2 as clusters. I registered both in
the client's EM. Now what I did was, I made ser1 to run and stopped sql
service in ser2 (active/passive) through failover. Now in the client's
EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
I failed over to ser2 ( so sql service in ser1 is stopped). But now I
can still be able to access ser1 and also I can access ser2, even I'm
able to open query analyzer in ser1 through EM.But when I try to open
query analyzer directly, it is giving the same error message. ser1 is
the virtual name given to both ser1 and ser2. So I think when
connecting through EM, failover is occuring fine.I'm just wondering why
is this happening only with dsn. Can anybody help me?
Thanks,
Preethi
http://support.microsoft.com/default...b;en-us;555332
"sqldbapree" <mohanpreethi0125@.gmail.com> wrote in message
news:1129898680.495504.25600@.g44g2000cwa.googlegro ups.com...
> We have 2 failover servers and one client in our test environment. We
> have all the three configured in mixed mode authentication(windows +
> sql server authentication). But when we are failing over from 1st
> server to 2nd one, we are getting the following error message,
> 'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
> State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
> user 'null'. Reason: Not associated with a trusted SQL server
> connection.'
> I got some clue.
> For instance we have ser1 and ser2 as clusters. I registered both in
> the client's EM. Now what I did was, I made ser1 to run and stopped sql
> service in ser2 (active/passive) through failover. Now in the client's
> EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
> I failed over to ser2 ( so sql service in ser1 is stopped). But now I
> can still be able to access ser1 and also I can access ser2, even I'm
> able to open query analyzer in ser1 through EM.But when I try to open
> query analyzer directly, it is giving the same error message. ser1 is
> the virtual name given to both ser1 and ser2. So I think when
> connecting through EM, failover is occuring fine.I'm just wondering why
> is this happening only with dsn. Can anybody help me?
> Thanks,
> Preethi
>