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
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
> Nicolassql

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: 17883, Severity: 1, State: 0

MS SQL Server 2000 sp4 Got a series of errors:
Sleeping until external dump process completes.
Resuming after waiting on external debug process for 8 seconds.
Stack Signature for the dump is 0x00000000
Error: 17883, Severity: 1, State: 0
Process 104:0 (fd4) UMS Context 0x0775B548 appears to be non-yielding on
Scheduler 0.
SQL Server has encountered 37 occurrence(s) of IO requests taking longer
than 15 seconds to complete on file [e:\Microsoft SQL
Server\\webslog631_2.mdf] in database [webslog631_2] (35). The OS file handle
is 0x0000071C. The offset of the latest long IO is: 0x0000007e6b8000
Looks like there is a post sp4 hotfix to fix this..
http://support.microsoft.com/kb/909734
how do I contacty MS without having to give them a Credit Card number?"itsonlyme4" wrote:
> MS SQL Server 2000 sp4 Got a series of errors:
> Sleeping until external dump process completes.
> Resuming after waiting on external debug process for 8 seconds.
> Stack Signature for the dump is 0x00000000
> Error: 17883, Severity: 1, State: 0
> Process 104:0 (fd4) UMS Context 0x0775B548 appears to be non-yielding on
> Scheduler 0.
> SQL Server has encountered 37 occurrence(s) of IO requests taking longer
> than 15 seconds to complete on file [e:\Microsoft SQL
> Server\\webslog631_2.mdf] in database [webslog631_2] (35). The OS file handle
> is 0x0000071C. The offset of the latest long IO is: 0x0000007e6b8000
> Looks like there is a post sp4 hotfix to fix this..
> http://support.microsoft.com/kb/909734
> how do I contacty MS without having to give them a Credit Card number?
>
Hi
The cumulative update pack is publically available and will contain this fix
http://support.microsoft.com/kb/916287/
John

error with sp_tables_ex

Hi all,

I am using a sp for show the external tables in a linked server ABC which via Ole DB for Visual Foxpro.
sp_tables_ex ABC
It returns error,
Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 41
The OLE DB provider "SQL Server" for linked server "(null)" reported an error. The provider reported an unexpected catastrophic failure.
Msg 7311, Level 16, State 2, Procedure sp_tables_ex, Line 41
Cannot obtain the schema rowset "DBSCHEMA_TABLES" for OLE DB provider "SQL Server" for linked server "(null)". The provider supports the interface, but returns a failure code when it is used.

When I used the same command to other linked server(with ole DB VFP also but with different path). And I tried 'select * from openquery(ABC, 'select * from product')'. Both work fine.

Kindly advise. Thanks in advance.

Hi Stephanie,

Are you by any chance running into the problem described in this KB article:

FIX: OLE DB Provider Improperly Enumerates DBSCHEMA_TABLES
http://support.microsoft.com/kb/314888

HTH,

Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.