Error: Could not find stored procedure !!

Hi,

Error: Could not find stored procedure.

I Installed the SQL Server SP2 and the error still occurs when ever I call the stored procedure from my windows app!!

Any Help ?

what's the name of SP you want to call?|||

In design window its : GetMonthRecord;1

in code window its: GetMonthRecord_1

I tried to rename it to : GetMonthRecord

the same error occurs !!

|||

Would you mind running this query and posting the results so that we can get some more information related to the object:

select uid,
left ([name], 30) as [name]
from sysobjects
where [name] like 'GetMonthRecord%'

|||

I run this query:

select uid,

left ([name], 30) as [name]

from sysobjects

where [name] like 'ThisMonthRecords%'

the result is:

1 ThisMonthRecords

|||

Now try:

exec ThisMonthRecords

and post the results

|||

executed succecfully the result is integer:

2

//

I'm facing the problem only with VS2005, when I add the procedure as queryTableAdapter, no error in code, but the error uccours after calling the SP.

Error: can't load configuration file

I had VS 2005 RC installed along with the Sep CTP of SQL Server (tools only)
and it was working fine.
Then I installed VS 2003 on that same machine. Now, everytime I lauch VS
2005 I get this message:
The configuration file RSReportDesigner.config could not be loaded.
The type initializer for "Microsoft.ReportingServices.Library.Global"
threw an exception.
I don't even use reporting services. Does anyone know how to make this
error go away?
TIA,
Mike RodriguezMichael Rodriguez wrote:
> I had VS 2005 RC installed along with the Sep CTP of SQL Server (tools only)
> and it was working fine.
> Then I installed VS 2003 on that same machine. Now, everytime I lauch VS
> 2005 I get this message:
> The configuration file RSReportDesigner.config could not be loaded.
> The type initializer for "Microsoft.ReportingServices.Library.Global"
> threw an exception.
> I don't even use reporting services. Does anyone know how to make this
> error go away?
> TIA,
> Mike Rodriguez
I was using Reporting Services just fine until I've installed VS.net
2003, now I get the same error message you're getting...Can anybody
help?sql

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: Application for .reportproj not installed

Getting error when try to open report project:
The application for D:\Documents and Settings\Administrator\My
Documents\Visual Studio Projects\WinfundsReports.rptproj is not installed.
Make surethe application for the project type (.rptproj) is installed.
Everything had been working fine for a year!
Note: Busuness Intelligence Projects no longer appears in the list of
available project types when setting up new project.
Is this controlled by something in the config files, or will I have to
reinstall Rptg Services?
Thanks.
AlanFollowup Question:
Is there a file that will re-register reporting services withou a complete
re-install?
Thanks.
Alan

error: 40 - Could not open a connection to SQL Server

I posted this on the Dotnetnuke forums but no answer for it, so since it is a SQL error I guess maybe someone here might know.

I installed the core forum that comes with the installation, the page runs great until I add the forum module.

I get this error:

A critical error has occurred.
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

The portal is in godaddy if this can help.

Thanks,

Erick

This problem usually occurs due to these reasons:

1. either your Datasource name is not set to the right value in web.config. If this is the case, check your web.config value with the GoDaddy's SQL server source name value (ask them for this).

2. remote connections are not allowed or there is some firewall issue. For this too contact GoDaddy support.

Hope this helps,

Vivek

Error: 26014, Severity: 16, State: 1.

Hello,

I installed a verisign test certificate (and their root cert) and got the above mentioned error. Googling that error resulted in this link- http://support.microsoft.com/kb/900495 and not much else. Their "cause" does not apply to me because my SQL Server runs under the local system account, not a service account.

So, can anyone suggest another fix besides the one listed in that link? BTW, I did compile and run the code on that page. The only thing it did was throw a bunch of errors......

I am running on Windows Server 2003 Enterprise SP1 with SQL Server 2005 SP2.

Thanks!

Error: 26014 means:

"Unable to load user-specified certificate. The server will not accept a connection. You should verify that the certificate is correctly installed."

Please check this blog and make sure your certificate is valid:

http://blogs.msdn.com/sql_protocols/archive/2005/12/30/508311.aspx

|||

It seems that blog is everyone's answer to all SSL issues when it comes to SQL Server....

There isn't much control over the certs when using the test certs from one of the 3rd party vendors. Here is a dump from certutil-

================ Certificate 0 ================
X509 Certificate:
Version: 3
Serial Number: 6364d64c5790dd5cfc1e070df813ae68
Signature Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.5 sha1RSA
Algorithm Parameters:
05 00
Issuer:
CN=Thawte Test CA Root
OU=TEST TEST TEST
O=Thawte Certification
S=FOR TESTING PURPOSES ONLY
C=ZA

NotBefore: 4/9/2007 2:22 PM
NotAfter: 4/30/2007 2:22 PM

Subject:
CN=slughorn.dbprotector.crossroads.com
OU=Thawte SSL123 certificate
OU=Go to https://www.thawte.com/repository/index.html
OU=Domain Validated
O=slughorn.dbprotector.crossroads.com

Public Key Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.1 RSA
Algorithm Parameters:
05 00
Public Key Length: 1024 bits
Public Key: UnusedBits = 0
0000 30 81 89 02 81 81 00 a2 3c db c8 1d 31 81 c8 60
0010 79 09 d9 f1 61 72 ac c5 c8 57 4b 23 87 ee 05 7a
0020 01 e0 c8 3f 58 c8 af c0 eb 3c c1 61 0b ee 31 5d
0030 92 2e c7 26 b3 a7 ce 73 55 13 15 c7 be 42 ed df
0040 4f 0f 16 71 2a 23 e4 b7 fb 7b bf 55 18 3c 2d 5c
0050 95 6c 65 a6 88 bc 35 05 f4 68 fb b7 24 ec 09 f8
0060 a9 8f 70 64 0e b0 3e 56 62 c9 ed ca d1 2f 5f cb
0070 92 8b bc ce b2 92 57 c0 ad fc e4 3b 29 f2 b0 18
0080 92 97 21 0e e4 a5 47 02 03 01 00 01
Certificate Extensions: 3
2.5.29.19: Flags = 1(Critical), Length = 2
Basic Constraints
Subject Type=End Entity
Path Length Constraint=None

2.5.29.37: Flags = 0, Length = 16
Enhanced Key Usage
Server Authentication (1.3.6.1.5.5.7.3.1)
Client Authentication (1.3.6.1.5.5.7.3.2)

1.3.6.1.5.5.7.1.1: Flags = 0, Length = 26
Authority Information Access
[1]Authority Info Access
Access Method=On-line Certificate Status Protocol (1.3.6.1.5.5.7.48.1)
Alternative Name:
URL=http://ocsp.thawte.com

Signature Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.5 sha1RSA
Algorithm Parameters:
05 00
Signature: UnusedBits=0
0000 84 88 42 cc 33 2e da b1 8b 61 c8 46 e3 34 b2 07
0010 36 0f 9d 27 63 a6 b2 b0 84 d4 23 7b 06 83 27 dc
0020 d7 1c 02 38 4b 25 10 37 25 ea 4a 27 da a3 b5 43
0030 72 aa 09 f3 07 b3 42 ff fd a6 5f d6 a4 1a 61 42
0040 ab 7f ac bb 70 dc 90 1b 44 d0 eb 53 64 8b 76 19
0050 83 08 17 3d 48 74 a3 03 f7 5f 8f 84 a4 4c 2c 3f
0060 d0 2e 0d 3a 16 c4 c1 08 2d 14 54 83 2b 87 16 b1
0070 d6 71 c5 c5 dd e5 54 6a e4 7b d3 46 65 2b 30 24
Non-root Certificate
Key Id Hash(sha1): 38 21 b5 9d 61 d5 e1 b8 74 97 78 1f c5 6d b3 17 de da 12 7a
Cert Hash(md5): 57 bc a6 f3 8d 33 c9 8e bb 04 d3 c4 0a 79 4b 9d
Cert Hash(sha1): aa a2 74 cf 6c 00 46 7e 04 4c f4 b3 ea fa a3 74 0a 8f 5c 0a

CERT_SHA1_HASH_PROP_ID(3):
aa a2 74 cf 6c 00 46 7e 04 4c f4 b3 ea fa a3 74 0a 8f 5c 0a
No stored keyset property

================ Certificate 1 ================
X509 Certificate:
Version: 3
Serial Number: 675c901500000000001c
Signature Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.5 sha1RSA
Algorithm Parameters:
05 00
Issuer:
CN=Hagrid
DC=dbprotector
DC=crossroads
DC=com

NotBefore: 4/9/2007 12:47 PM
NotAfter: 4/8/2008 12:47 PM

Subject:
EMPTY (DNS Name=slughorn.dbprotector.crossroads.com)

Public Key Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.1 RSA
Algorithm Parameters:
05 00
Public Key Length: 1024 bits
Public Key: UnusedBits = 0
0000 30 81 89 02 81 81 00 da e8 ab 36 f4 05 3e 80 42
0010 4f a1 eb a8 58 09 e4 f9 98 6f bc 86 50 43 c8 a3
0020 ba d4 da 99 9e cf 20 1b 40 42 50 92 64 39 99 c2
0030 01 d8 b1 7c e5 9b a6 fc 73 bd 2c 99 0e 09 cf c6
0040 9c c4 e1 7c 27 0d af 06 d1 fb b6 d7 86 25 1e 5a
0050 9f fa 84 e7 51 aa 92 67 a8 bc 2b 62 a2 2b f0 bc
0060 3c 6a d2 a2 f6 0e 59 23 7e c3 68 33 3e d2 63 c3
0070 91 b1 0e 8a 11 4c 3d 1e 46 ca 16 33 0a 0d 67 5a
0080 65 c8 ae 25 18 17 c7 02 03 01 00 01
Certificate Extensions: 9
2.5.29.15: Flags = 0, Length = 4
Key Usage
Digital Signature, Key Encipherment (a0)

2.5.29.14: Flags = 0, Length = 16
Subject Key Identifier
19 40 a9 11 7d 5d fb 23 3c 67 17 bc fd 2e 63 e7 59 7b 2a b8

1.3.6.1.4.1.311.21.7: Flags = 0, Length = 31
Certificate Template Information
Template=Computer - Exportable Key(1.3.6.1.4.1.311.21.8.5138224.4110583.14633635.5428750.2310230.215.11292564.15266621)
Major Version Number=100
Minor Version Number=6

2.5.29.35: Flags = 0, Length = 18
Authority Key Identifier
KeyID=7c 44 09 cf c6 83 8e 11 54 9b d7 e3 50 f4 31 45 f4 fb 01 9c

2.5.29.31: Flags = 0, Length = 111
CRL Distribution Points
[1]CRL Distribution Point
Distribution Point Name:
Full Name:
URL=ldap:///CN=Hagrid,CN=hagrid,CN=CDP,CN=Public%20Key%20Services,CN=Services,CN=Configuration,DC=dbprotector,DC=crossroads,DC=com?certificateRevocationList?base?objectClass=cRLDistributionPoint
URL=http://hagrid.dbprotector.crossroads.com/CertEnroll/Hagrid.crl

1.3.6.1.5.5.7.1.1: Flags = 0, Length = 12c
Authority Information Access
[1]Authority Info Access
Access Method=Certification Authority Issuer (1.3.6.1.5.5.7.48.2)
Alternative Name:
URL=ldap:///CN=Hagrid,CN=AIA,CN=Public%20Key%20Services,CN=Services,CN=Configuration,DC=dbprotector,DC=crossroads,DC=com?cACertificate?base?objectClass=certificationAuthority
[2]Authority Info Access
Access Method=Certification Authority Issuer (1.3.6.1.5.5.7.48.2)
Alternative Name:
URL=http://hagrid.dbprotector.crossroads.com/CertEnroll/hagrid.dbprotector.crossroads.com_Hagrid.crt

2.5.29.37: Flags = 0, Length = 16
Enhanced Key Usage
Client Authentication (1.3.6.1.5.5.7.3.2)
Server Authentication (1.3.6.1.5.5.7.3.1)

1.3.6.1.4.1.311.21.10: Flags = 0, Length = 1a
Application Policies
[1]Application Certificate Policy:
Policy Identifier=Client Authentication
[2]Application Certificate Policy:
Policy Identifier=Server Authentication

2.5.29.17: Flags = 1(Critical), Length = 27
Subject Alternative Name
DNS Name=slughorn.dbprotector.crossroads.com

Signature Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.5 sha1RSA
Algorithm Parameters:
05 00
Signature: UnusedBits=0
0000 bb 6f a7 86 30 21 96 ed e4 9c d8 53 f5 67 2e c9
0010 9f b7 26 fb 41 b4 0c 6d 81 49 79 8d 45 0f f1 f1
0020 5a 1d 15 a7 4a 42 8c f4 77 6f 14 4d d7 ff 8d fc
0030 19 90 e0 5e 7d c3 be 48 f7 db 2c 7f e8 19 bf 61
0040 71 3b 3f 76 ae 35 48 7f 73 aa 1f 5e a0 b0 bc 1a
0050 71 0f 33 77 6a b8 d3 8e c4 65 0b 86 39 09 40 ec
0060 cf 0e 56 11 a3 ee 92 06 da 27 9b f8 60 02 6c 7b
0070 c1 d3 ac 9a 84 7c 9d 1b 85 f7 95 42 85 bc 6d 3d
0080 ef 00 8e bc 42 92 ec 52 33 2e 01 91 51 0e 3b 35
0090 46 d9 a8 ce 00 bb 0e 0f bc 01 b6 4a d7 12 cf 64
00a0 a3 7a 2f 9c 67 2c 83 d4 6c ee ad b9 4d bd 33 cf
00b0 31 bf da ed fb 52 5b c1 fe 25 53 17 e8 8b df a9
00c0 ce 5e cb af c2 9b 6e 5a e1 b5 1b 46 d1 f1 40 5a
00d0 0f 08 e4 ef 59 5e 5b 5b c7 95 47 b2 2d ba d0 ea
00e0 d4 e0 cf 94 3b 29 04 5c 4d c8 0a 0b 57 52 eb 60
00f0 cd cb d5 f0 00 c6 f3 89 86 96 31 0b 64 ae 4c 0d
Non-root Certificate
Key Id Hash(sha1): 19 40 a9 11 7d 5d fb 23 3c 67 17 bc fd 2e 63 e7 59 7b 2a b8
Cert Hash(md5): e7 f8 20 8f 19 5a b1 43 46 1e d7 dc 5d 78 2d 48
Cert Hash(sha1): 68 ca 1e d3 81 eb 23 5d 2e 64 e1 02 5c 6e 28 e1 fd a7 2f 38

CERT_ISSUER_PUBLIC_KEY_MD5_HASH_PROP_ID(24):
f8 bb f0 33 2e 21 d9 56 fd 01 8d 73 75 b8 08 fa

CERT_SUBJECT_PUBLIC_KEY_MD5_HASH_PROP_ID(25):
cf 2b e1 e7 2c f4 2f de ca 57 83 f7 4d 51 cf f4

CERT_SHA1_HASH_PROP_ID(3):
68 ca 1e d3 81 eb 23 5d 2e 64 e1 02 5c 6e 28 e1 fd a7 2f 38

CERT_KEY_PROV_INFO_PROP_ID(2):
Key Container = 2716a703c2b974b82dac9d51ce0f9cdd_6fda5789-4c9a-4c8f-8c3e-79950eb4238b
Provider = Microsoft RSA SChannel Cryptographic Provider
ProviderType = c
Flags = 60
KeySpec = 1

CERT_FRIENDLY_NAME_PROP_ID(11):
Computer - Exportable Key

CERT_KEY_IDENTIFIER_PROP_ID(20):
19 40 a9 11 7d 5d fb 23 3c 67 17 bc fd 2e 63 e7 59 7b 2a b8

CERT_MD5_HASH_PROP_ID(4):
e7 f8 20 8f 19 5a b1 43 46 1e d7 dc 5d 78 2d 48

CERT_SIGNATURE_HASH_PROP_ID(15):
78 07 74 19 73 c2 a1 e2 d6 b3 47 82 b8 10 60 e8 6c 8f 5d aa
2716a703c2b974b82dac9d51ce0f9cdd_6fda5789-4c9a-4c8f-8c3e-79950eb4238b

Private Key:
PRIVATEKEYBLOB
Version: 2
aiKeyAlg: 0xa400
CALG_RSA_KEYX
Algorithm Class: 0xa000(5) ALG_CLASS_KEY_EXCHANGE
Algorithm Type: 0x400(2) ALG_TYPE_RSA
Algorithm Sub-id: 0x0(0) ALG_SID_RSA_ANY
0000 52 53 41 32 RSA2
0000 ...
024c
Encryption test passed
CertUtil: -store command completed successfully.

Certificate 0 is the test Thawte cert. Can you see anything wrong with it?

Certificate 1 is a Windows CA issued cert based on the Computer template. It is a version 2.0 cert. It does not show up in the SQL Server Management console, but it works if I put its hash into the registry. Now I need to get a 3rd party cert working.

I am installing the certs in the Local Computer certificate store. SQL Server is running under the local system account.

From the blog-

1) It is in the local computer cert store and SQL Server runs under that account

2) Time stamps are good

3) From the above dump - Enhanced Key Usage
Server Authentication (1.3.6.1.5.5.7.3.1)
Client Authentication (1.3.6.1.5.5.7.3.2)

4) I don't see this anywhere, AT_KEYEXCHANGE

5) Does not apply to me.

Thanks for the help!

|||

The first one does not have:

Key Usage
Digital Signature, Key Encipherment (a0)

where Key Encipherment (a0) means AT_KEYEXCHANGE,

A certificate without AT_KEYEXCHANGE is not meant for Data Exchange and cannot be used as certificate by SQL Server. Please check the purpose of your certificate.

Another Anonymous asked similar question days ago, I'm not sure if that is you. Please register a real name if possible.

|||

No, that wasn't me.

Anyway, it wasn't a problem with the cert. It was a problem with the horrible process required to get SQL Server to use it. Basically,

1) Create CSR with IIS

2) Request cert from Verisign

3) Complete pending cert request in IIS

4) Open cert snap-in for local computer, export the new cert using PFX format, ensuring to export private key.

5) Re-import cert from PFX format.

After that nonsense, SQL Server's tools recognized the cert the used it no problem.....

I'm not sure if the other 3rd party certs will work this way or not. I haven't tried them.

error: 26 - error locating server/instance specified

My machine is WinXP with SP2. I installed SQL Server 2005 Developer
Edition on my machine last week, and I could bring up the Microsoft
SQL Server Management Studio fine, no error.
Today in Microsoft SQL Server Management Studio when I tried to
connect to machinename\SQL2005 (the SQL 2005 instance), I got the
error:
"An error has occured while establishing a connection to the server.
when connecting to sql server 2005, this failure may be caused by the
fact that under the default settings sql server does not allow remote
connections. (provider: sql network interfaces, error: 26 - error
locating server/instance specified)(microsoft sql server)"
But, I am not trying to connect to it remotely, the SQL Server 2005 is
on my machine.
In the Start >> Programs >> Microsoft SQL Server 2005 >> Configuration
Tools >> SQL Server 2005 Surface Area Configuration >> Surface Area
Configuration for Services and connections
"Local and remote connections" is not selected.
How can I fix this problem ?
Thank you.
Never mind.
On the "Server name", i click on Browse more and select the instance
from there, I guess the machinename is different today than last week.
So, I selected that one and now it works.
THanks
On Jun 10, 1:25 pm, fiefie.ni...@.gmail.com wrote:
> My machine is WinXP with SP2. I installed SQL Server 2005 Developer
> Edition on my machine last week, and I could bring up the Microsoft
> SQL Server Management Studio fine, no error.
> Today in Microsoft SQL Server Management Studio when I tried to
> connect to machinename\SQL2005 (the SQL 2005 instance), I got the
> error:
> "An error has occured while establishing a connection to the server.
> when connecting to sql server 2005, this failure may be caused by the
> fact that under the default settings sql server does not allow remote
> connections. (provider: sql network interfaces, error: 26 - error
> locating server/instance specified)(microsoft sql server)"
> But, I am not trying to connect to it remotely, the SQL Server 2005 is
> on my machine.
> In the Start >> Programs >> Microsoft SQL Server 2005 >> Configuration
> Tools >> SQL Server 2005 Surface Area Configuration >> Surface Area
> Configuration for Services and connections
> "Local and remote connections" is not selected.
> How can I fix this problem ?
> Thank you.
|||On Jun 10, 1:27 pm, fiefie.ni...@.gmail.com wrote:[vbcol=seagreen]
> Never mind.
> On the "Server name", i click on Browse more and select the instance
> from there, I guess the machinename is different today than last week.
> So, I selected that one and now it works.
> THanks
> On Jun 10, 1:25 pm, fiefie.ni...@.gmail.com wrote:
>
>
I get the same error. Please advise.
sql

error: 26 - error locating server/instance specified

My machine is WinXP with SP2. I installed SQL Server 2005 Developer
Edition on my machine last week, and I could bring up the Microsoft
SQL Server Management Studio fine, no error.
Today in Microsoft SQL Server Management Studio when I tried to
connect to machinename\SQL2005 (the SQL 2005 instance), I got the
error:
"An error has occured while establishing a connection to the server.
when connecting to sql server 2005, this failure may be caused by the
fact that under the default settings sql server does not allow remote
connections. (provider: sql network interfaces, error: 26 - error
locating server/instance specified)(microsoft sql server)"
But, I am not trying to connect to it remotely, the SQL Server 2005 is
on my machine.
In the Start >> Programs >> Microsoft SQL Server 2005 >> Configuration
Tools >> SQL Server 2005 Surface Area Configuration >> Surface Area
Configuration for Services and connections
"Local and remote connections" is not selected.
How can I fix this problem ?
Thank you.Never mind.
On the "Server name", i click on Browse more and select the instance
from there, I guess the machinename is different today than last week.
So, I selected that one and now it works.
THanks
On Jun 10, 1:25 pm, fiefie.ni...@.gmail.com wrote:
> My machine is WinXP with SP2. I installed SQL Server 2005 Developer
> Edition on my machine last week, and I could bring up the Microsoft
> SQL Server Management Studio fine, no error.
> Today in Microsoft SQL Server Management Studio when I tried to
> connect to machinename\SQL2005 (the SQL 2005 instance), I got the
> error:
> "An error has occured while establishing a connection to the server.
> when connecting to sql server 2005, this failure may be caused by the
> fact that under the default settings sql server does not allow remote
> connections. (provider: sql network interfaces, error: 26 - error
> locating server/instance specified)(microsoft sql server)"
> But, I am not trying to connect to it remotely, the SQL Server 2005 is
> on my machine.
> In the Start >> Programs >> Microsoft SQL Server 2005 >> Configuration
> Tools >> SQL Server 2005 Surface Area Configuration >> Surface Area
> Configuration for Services and connections
> "Local and remote connections" is not selected.
> How can I fix this problem ?
> Thank you.|||On Jun 10, 1:27 pm, fiefie.ni...@.gmail.com wrote:[vbcol=seagreen]
> Never mind.
> On the "Server name", i click on Browse more and select the instance
> from there, I guess the machinename is different today than last week.
> So, I selected that one and now it works.
> THanks
> On Jun 10, 1:25 pm, fiefie.ni...@.gmail.com wrote:
>
>
>
>
I get the same error. Please advise.

error: 26 - error locating server/instance specified

My machine is WinXP with SP2. I installed SQL Server 2005 Developer
Edition on my machine last week, and I could bring up the Microsoft
SQL Server Management Studio fine, no error.
Today in Microsoft SQL Server Management Studio when I tried to
connect to machinename\SQL2005 (the SQL 2005 instance), I got the
error:
"An error has occured while establishing a connection to the server.
when connecting to sql server 2005, this failure may be caused by the
fact that under the default settings sql server does not allow remote
connections. (provider: sql network interfaces, error: 26 - error
locating server/instance specified)(microsoft sql server)"
But, I am not trying to connect to it remotely, the SQL Server 2005 is
on my machine.
In the Start >> Programs >> Microsoft SQL Server 2005 >> Configuration
Tools >> SQL Server 2005 Surface Area Configuration >> Surface Area
Configuration for Services and connections
"Local and remote connections" is not selected.
How can I fix this problem ?
Thank you.Never mind.
On the "Server name", i click on Browse more and select the instance
from there, I guess the machinename is different today than last week.
So, I selected that one and now it works.
THanks
On Jun 10, 1:25 pm, fiefie.ni...@.gmail.com wrote:
> My machine is WinXP with SP2. I installed SQL Server 2005 Developer
> Edition on my machine last week, and I could bring up the Microsoft
> SQL Server Management Studio fine, no error.
> Today in Microsoft SQL Server Management Studio when I tried to
> connect to machinename\SQL2005 (the SQL 2005 instance), I got the
> error:
> "An error has occured while establishing a connection to the server.
> when connecting to sql server 2005, this failure may be caused by the
> fact that under the default settings sql server does not allow remote
> connections. (provider: sql network interfaces, error: 26 - error
> locating server/instance specified)(microsoft sql server)"
> But, I am not trying to connect to it remotely, the SQL Server 2005 is
> on my machine.
> In the Start >> Programs >> Microsoft SQL Server 2005 >> Configuration
> Tools >> SQL Server 2005 Surface Area Configuration >> Surface Area
> Configuration for Services and connections
> "Local and remote connections" is not selected.
> How can I fix this problem ?
> Thank you.|||On Jun 10, 1:27 pm, fiefie.ni...@.gmail.com wrote:
> Never mind.
> On the "Server name", i click on Browse more and select the instance
> from there, I guess the machinename is different today than last week.
> So, I selected that one and now it works.
> THanks
> On Jun 10, 1:25 pm, fiefie.ni...@.gmail.com wrote:
> > My machine is WinXP with SP2. I installedSQLServer 2005 Developer
> > Edition on my machine last week, and I could bring up the Microsoft
> >SQLServer Management Studio fine, noerror.
> > Today in MicrosoftSQLServer Management Studio when I tried to
> > connect to machinename\SQL2005 (theSQL2005 instance), I got the
> >error:
> > "Anerrorhas occured while establishing a connection to the server.
> > when connecting tosqlserver 2005, this failure may be caused by the
> > fact that under the default settingssqlserver does not allow remote
> > connections. (provider:sqlnetwork interfaces,error:26-error
> > locating server/instance specified)(microsoftsqlserver)"
> > But, I am not trying to connect to it remotely, theSQLServer 2005 is
> > on my machine.
> > In the Start >> Programs >> MicrosoftSQLServer 2005 >> Configuration
> > Tools >>SQLServer 2005 Surface Area Configuration >> Surface Area
> > Configuration for Services and connections
> > "Local and remote connections" is not selected.
> > How can I fix this problem ?
> > Thank you.
I get the same error. Please advise.

error: 25 - Connection string is not valid -- HELP Please!

I have been having a problem trying to connect to a SQL Server. I have installed the Developer edition on an MS Small Business edition 2003 server

I also installed MS Sql Manager and I was able to create a database and connect to it. The database server is in the same PC. I used the surface configuration to enable remote connections using TCP /IP and pipe lines.

My application runs without a problem on my development machine but when I deployed on this server I get theprovider: SQL Network Interfaces, error: 25 - Connection string is not valid Error.

this is my config file setup

<connectionStrings>
<add name="Diamond_dbConnectionString" connectionString="Data Source=192.168.1.104\MSSQLSERVER;Initial Catalog=Diamond_db;Integrated Security=True"
providerName="System.Data.SqlClient" />
</connectionStrings>

I have google and yahoo this error I found a lot of information I've tried many of them but still having the problem. I will appreciate your help solving this problem. I have a customer waiting since last week to see this site and I'm still stuck.

Tia

Charles

PS. Below I pasted the complete error info I get.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid)

Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details:System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid)

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SqlException (0x80131904): An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +734995 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +820 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +359 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +121 System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior) +162 System.Data.Common.DbDataAdapter.Fill(DataTable dataTable) +107 DiamondTableAdapters.COUNTRIES_TEMPLATETableAdapter.GetContriesTemplate() +108[TargetInvocationException: Exception has been thrown by the target of an invocation.] System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) +0 System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) +72 System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) +296 System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) +29 System.Web.UI.WebControls.ObjectDataSourceView.InvokeMethod(ObjectDataSourceMethod method, Boolean disposeInstance, Object& instance) +482 System.Web.UI.WebControls.ObjectDataSourceView.ExecuteSelect(DataSourceSelectArguments arguments) +2040 System.Web.UI.WebControls.BaseDataList.GetData() +53 System.Web.UI.WebControls.DataList.CreateControlHierarchy(Boolean useDataSource) +284 System.Web.UI.WebControls.BaseDataList.OnDataBinding(EventArgs e) +56 System.Web.UI.WebControls.BaseDataList.DataBind() +72 System.Web.UI.WebControls.BaseDataList.EnsureDataBound() +55 System.Web.UI.WebControls.BaseDataList.CreateChildControls() +63 System.Web.UI.Control.EnsureChildControls() +87 System.Web.UI.Control.PreRenderRecursiveInternal() +41 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1360

---

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

Do you have ISA running on the server? Can you connect through Server Manager to the server using the same credentials?

Jeff

|||

Jeff,

I'm using EMS SQL Manager for SQL Server

http://sqlmanager.net/products/mssql/manager/

to create and manage my SQL server. I can connect to the server using windows credentials but when I try with the ASP application I can't

Thanks

Charles

|||

Is the ASP.NET app using the same Windows account to access the database, or is it using the ASP.NET process account?

Jeff

|||

Jeff,

Honestly I'm very green regarding ASP.NET and MS-SQL Server

When I installed the server I asigned the Windows account to gain access to the SQL Server. When I created the database in question I also used the Windows Account.

When I registered the database with MS Server manager tool I also used the same Windows Account.

How can I check If I'm using the ASP.NET process account instead of the Windows Account?

I will appreciate your inputs.

Tia

Charles

|||

The ASP.NET process account, unless you have set it or changed it, is ASPNET or NETWORK SERVICE depending on operatiing system. It is unlikely you chose this account for access to SQL. But normally you would get a mdifferent error if that was the problem.

Take a look at connectionstrings.com for some possibilities in changing your connection string. You may want to use a standard authentication with SQL user and password rather than rely on a trusted connection.

Is your SQL on a different server than the web server? I wouldn't think so but you use the IP address of the SQL server in your connection. You should just need to enable TCP/IP, which you said you've done.

Jeff

|||Are you sure the MSSQLSERVER is the name of the named (not default) instance? It seems to be the SQL service name of default instance. If you're trying to connect to a default SQL instance on a remote server, just set the Data Source to the IP address of the remote server is ok.sql

Error: 18456, Severity: 14, State: 11 when logging in

I just installed SQL Server 2005 with SP2 on Vista. When I try to login from SQL Server Management Studio, I get the following error message in the log:

2007-09-15 18:58:02.23 Logon Error: 18456, Severity: 14, State: 11.
2007-09-15 18:58:02.23 Logon Login failed for user '<computer name>\<user account>'.[CLIENT: <local machine>]

Since I can't login, I can't try some of the stuff I have seen here, such as creating new logins etc.

I installed Analysis Server and Integration Services at the same time. Logging in to them both works fine.

I use windows authentication. I don't know if changing that helps, as I don't know how to change it without logging in in the first place...

I think you entered in Windows with an account (<computer name>\<user account>) that hasn't a SQL login.

If your windows account should have administrator privillege it should enter with SQL login named "Builtin\administrators"

To the other part reading this the builtin administrator is disabled by default in Vista.

So repair first this.

|||

Gigi is correct. You can also read about this issue here: http://msdn2.microsoft.com/en-us/library/Aa905868.aspx.

Thanks

Laurentiu

Error: 18456, Severity: 14, State: 11 when logging in

I just installed SQL Server 2005 with SP2 on Vista. When I try to login from SQL Server Management Studio, I get the following error message in the log:

2007-09-15 18:58:02.23 Logon Error: 18456, Severity: 14, State: 11.
2007-09-15 18:58:02.23 Logon Login failed for user '<computer name>\<user account>'.[CLIENT: <local machine>]

Since I can't login, I can't try some of the stuff I have seen here, such as creating new logins etc.

I installed Analysis Server and Integration Services at the same time. Logging in to them both works fine.

I use windows authentication. I don't know if changing that helps, as I don't know how to change it without logging in in the first place...

I think you entered in Windows with an account (<computer name>\<user account>) that hasn't a SQL login.

If your windows account should have administrator privillege it should enter with SQL login named "Builtin\administrators"

To the other part reading this the builtin administrator is disabled by default in Vista.

So repair first this.

|||

Gigi is correct. You can also read about this issue here: http://msdn2.microsoft.com/en-us/library/Aa905868.aspx.

Thanks

Laurentiu

Error: 18456, Severity: 14, State: 11

We have SQL Server 2005 Developer Edition with SP2 installed on Windows
Server 2003 Standard Edition SP1. When one of our programmers tries to
connect to the SQL instance he receives the 'Error: 18456, Severity: 14,
State: 11' error.
I found where this refers to a connect to server error and have checked, he
does have connect priviliges. I deleted both the server account and database
account and recreated them but he still receives the error. The only way he
can get access is to be a member of the sysadmin role. This was done for
testing but cannot be given as normal practice.
Does anyone have any ideas or solutions?
Thank You,
Bertbert
CREATE LOGIN test
WITH PASSWORD = 'balabalabala';USE AdventureWorks;
CREATE USER 'test' FOR LOGIN test;
GO Note , you can use ALTER LOGIN ... WITH default_database=..."-bert"
<bert@.discussions.microsoft.com> wrote in message
news:C9CDD261-B1AD-48BC-B821-9DCC80F64480@.microsoft.com...
> We have SQL Server 2005 Developer Edition with SP2 installed on Windows
> Server 2003 Standard Edition SP1. When one of our programmers tries to
> connect to the SQL instance he receives the 'Error: 18456, Severity: 14,
> State: 11' error.
> I found where this refers to a connect to server error and have checked,
> he
> does have connect priviliges. I deleted both the server account and
> database
> account and recreated them but he still receives the error. The only way
> he
> can get access is to be a member of the sysadmin role. This was done for
> testing but cannot be given as normal practice.
> Does anyone have any ideas or solutions?
> Thank You,
> Bert

Error: 18456 Severity: 14, State: 10

I have SQL 2005 Expess installed on Windows Server 2003 SP1.

My application is running as a service and is set to depend on SQL Server instance...
During the startup my app attempts to connect to the databes and it fails to do so,
after 30 retries (1second appart). SQL Server log has this error msg:
Error: 18456 "Severity: 14, State: 10"

Once the server has started, I cam manually start my application and it then sucesfully
opens a connection to the database.

What does this error mean?

Srdjan

Hi Srdjan,

Looks like you are getting a login failed error:

http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

How is your app connecting to your db? If you are using Windows authentication, it could be that the service account you are using when running your app as a service does not have permission to log on to the database.

Sung

|||

This error seems to only be reachable when using SQL Authentication, but I'm not sure what could cause it.

You can start SQL Server with "-y 18456", to produce a dump when the error occurs. As the dump will happen during authentication, the login password might appear in it, so you should use a bogus test password for the purpose of the creating this dump, just in case. Once you have the dump, please open a report at https://connect.microsoft.com/feedback/default.aspx?SiteID=68, attach the dump, and mention my name in the report, so it will get assigned to me.

If you can repro this issue with a smaller application that attempts the same connection on startup, you could attach that application as well, so we can attempt to repro the issue in our labs.

Thanks
Laurentiu

|||tried a couple of times to post a bug report...
but getting errors from the web site.

Anyway, new information:

if I run using Windows authentication, error is the ame but
state is now 16.

Still, after loging in - I have no problem starting the same service that failed during automatic startup.

Even the simplest windows servce that just opens connection
behaves the same...

Thanks,
Srdjan|||

State 16 means there was an error in determining the database to be used by the connection. Can you still connect if you start your application manually?

Thanks
Laurentiu

|||yes, as soon as I log in, I can start my application manually.
During Startup my application fails to start because of the unhandled exception thrown from Sql.Client:

System.Data.SqlClient.SqlException: Cannot open database "Db_260" requested by the login. The login failed.
Login failed for user 'NT AUTHORITY\SYSTEM'.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()

Also here are couple of lines from the SQL errorlog file during machine startup:
2006-07-15 13:56:39.67 spid8s Clearing tempdb database.
2006-07-15 13:56:39.71 Logon Error: 18456, Severity: 14, State: 16.
2006-07-15 13:56:39.71 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
2006-07-15 13:56:39.95 Logon Error: 18456, Severity: 14, State: 16.
2006-07-15 13:56:39.95 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
2006-07-15 13:56:40.34 spid8s Starting up database 'tempdb'.
2006-07-15 13:56:40.45 spid5s Recovery is complete. This is an informational message only. No user action is required.
2006-07-15 13:56:40.46 spid11s The Service Broker protocol transport is disabled or not configured.
2006-07-15 13:56:40.46 spid11s The Database Mirroring protocol transport is disabled or not configured.
2006-07-15 13:56:40.56 spid11s Service Broker manager has started.
2006-07-15 13:56:44.78 spid51 Starting up database 'ReportServer$TRBR'.
2006-07-15 13:56:45.09 spid52 Starting up database 'Db_260'.
2006-07-15 13:57:38.96 Server Server resumed execution after being idle 25 seconds: user activity awakened the server. This is an informational message only. No user action is required.

Srdjan|||

You are trying to connect to database Db_260, but the database has not been started up yet. If you will look in the log, you'll see that the server is accepting connections before starting up the database Db_260, so the requests that you make before the database startup will fail. You should take this into account and retry to connect after a delay, to give time to the server to start up the database.

Thanks
Laurentiu

|||Laurentiu,

My code actually retries until it gets connection succesfully.
The problem is that after a couple of failed atempts, I actally get a success, but then it is the the next attempt to connect to database fails with the exception:

Login Failed for user 'NT AUTHORITY SYSTEM'...

Now, I've tried to postpone the first call to database for up to
3 minutes (more is not practical) and nothing really changes,
I get the same behaviour (System.Data.SqlClient.SqlException) on the second call to database...

Srdjan

|||

Are you saying that you get login failure errors after the database is started up? The log excerpt from your previous message doesn't show that. Can you post your errorlog from beginning up to and including the first couple of login failures that you get AFTER the Db_260 database was started up?

Thanks
Laurentiu

|||Laurentiu,

I managed to get around this problem...
My original code that was checking if SQL is ready was simply opening a connection but didn't execute any dabase commands.

For some reason at one point one of these attempts would successed, but then on the first real database access, exception was thrown.

So, I now do retries on the first real access to datbase and that seems to work.

I appreciate your help.

Srdjan
|||

Hi Laurentiu,

I am having a similar problem when after programmatically creating a database I try to create a table, if I do not put an arbitrarily large delay before issuing the create table statement, I get this same "Error: 18456, Severity: 14, State: 16."

Is there any way to issue a SQL statement and block on the call until a new database has been fully initialized and started before continuing? Alternatively, is there a way to get a callback once the DB is online?, Finally, if neither of the previous are possible, is there any entry in the master DB that one could poll to see when the new DB is up and running? I've tried the ovbious state in sys.databases, and Database.Status in DMO with no luck.

Any ideas? Thanks in advance!

GDM

|||

If you are getting a login failed message, it sounds like you are executing the CREATE DATABASE and CREATE TABLE statements on two different connections. Have you considered executing these statements using the same connection? If you would execute the CREATE TABLE after the CREATE DATABASE, on the same connection, you would not see such a failure.

The state you can query is state_desc in sys.databases - if it is ONLINE, it means the database was started.

Thanks
Laurentiu

|||How do i start sql server with "-y 18456"|||

Start->Run...->services.msc

Then go to the SQL Server service and stop it. Then Click <Properties> and in the <Start Parameters> field enter -y 18456. You can then click <Start> to restart the server with that parameter and then press cancel to exit without saving the parameter, so that future restarts won't use it. If you press OK, then the server will be restarted with that parameter - you probably don't want that.

Thanks
Laurentiu

|||

Ok I have an issue here....I am trying to do a full system recovery and this is what I am getting...

File/minint/system32/biosinfo.inf could not be loaded the error is code 14 ?

And I do NOT have the Windows XP Disk either...so if theres a way around this please by all means help me .......

can some please help me with this please

Error: 18456 Severity: 14, State: 10

I have SQL 2005 Expess installed on Windows Server 2003 SP1.

My application is running as a service and is set to depend on SQL Server instance...
During the startup my app attempts to connect to the databes and it fails to do so,
after 30 retries (1second appart). SQL Server log has this error msg:
Error: 18456 "Severity: 14, State: 10"

Once the server has started, I cam manually start my application and it then sucesfully
opens a connection to the database.

What does this error mean?

Srdjan

Hi Srdjan,

Looks like you are getting a login failed error:

http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

How is your app connecting to your db? If you are using Windows authentication, it could be that the service account you are using when running your app as a service does not have permission to log on to the database.

Sung

|||

This error seems to only be reachable when using SQL Authentication, but I'm not sure what could cause it.

You can start SQL Server with "-y 18456", to produce a dump when the error occurs. As the dump will happen during authentication, the login password might appear in it, so you should use a bogus test password for the purpose of the creating this dump, just in case. Once you have the dump, please open a report at https://connect.microsoft.com/feedback/default.aspx?SiteID=68, attach the dump, and mention my name in the report, so it will get assigned to me.

If you can repro this issue with a smaller application that attempts the same connection on startup, you could attach that application as well, so we can attempt to repro the issue in our labs.

Thanks
Laurentiu

|||tried a couple of times to post a bug report...
but getting errors from the web site.

Anyway, new information:

if I run using Windows authentication, error is the ame but
state is now 16.

Still, after loging in - I have no problem starting the same service that failed during automatic startup.

Even the simplest windows servce that just opens connection
behaves the same...

Thanks,
Srdjan|||

State 16 means there was an error in determining the database to be used by the connection. Can you still connect if you start your application manually?

Thanks
Laurentiu

|||yes, as soon as I log in, I can start my application manually.
During Startup my application fails to start because of the unhandled exception thrown from Sql.Client:

System.Data.SqlClient.SqlException: Cannot open database "Db_260" requested by the login. The login failed.
Login failed for user 'NT AUTHORITY\SYSTEM'.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()

Also here are couple of lines from the SQL errorlog file during machine startup:
2006-07-15 13:56:39.67 spid8s Clearing tempdb database.
2006-07-15 13:56:39.71 Logon Error: 18456, Severity: 14, State: 16.
2006-07-15 13:56:39.71 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
2006-07-15 13:56:39.95 Logon Error: 18456, Severity: 14, State: 16.
2006-07-15 13:56:39.95 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
2006-07-15 13:56:40.34 spid8s Starting up database 'tempdb'.
2006-07-15 13:56:40.45 spid5s Recovery is complete. This is an informational message only. No user action is required.
2006-07-15 13:56:40.46 spid11s The Service Broker protocol transport is disabled or not configured.
2006-07-15 13:56:40.46 spid11s The Database Mirroring protocol transport is disabled or not configured.
2006-07-15 13:56:40.56 spid11s Service Broker manager has started.
2006-07-15 13:56:44.78 spid51 Starting up database 'ReportServer$TRBR'.
2006-07-15 13:56:45.09 spid52 Starting up database 'Db_260'.
2006-07-15 13:57:38.96 Server Server resumed execution after being idle 25 seconds: user activity awakened the server. This is an informational message only. No user action is required.

Srdjan|||

You are trying to connect to database Db_260, but the database has not been started up yet. If you will look in the log, you'll see that the server is accepting connections before starting up the database Db_260, so the requests that you make before the database startup will fail. You should take this into account and retry to connect after a delay, to give time to the server to start up the database.

Thanks
Laurentiu

|||Laurentiu,

My code actually retries until it gets connection succesfully.
The problem is that after a couple of failed atempts, I actally get a success, but then it is the the next attempt to connect to database fails with the exception:

Login Failed for user 'NT AUTHORITY SYSTEM'...

Now, I've tried to postpone the first call to database for up to
3 minutes (more is not practical) and nothing really changes,
I get the same behaviour (System.Data.SqlClient.SqlException) on the second call to database...

Srdjan

|||

Are you saying that you get login failure errors after the database is started up? The log excerpt from your previous message doesn't show that. Can you post your errorlog from beginning up to and including the first couple of login failures that you get AFTER the Db_260 database was started up?

Thanks
Laurentiu

|||Laurentiu,

I managed to get around this problem...
My original code that was checking if SQL is ready was simply opening a connection but didn't execute any dabase commands.

For some reason at one point one of these attempts would successed, but then on the first real database access, exception was thrown.

So, I now do retries on the first real access to datbase and that seems to work.

I appreciate your help.

Srdjan
|||

Hi Laurentiu,

I am having a similar problem when after programmatically creating a database I try to create a table, if I do not put an arbitrarily large delay before issuing the create table statement, I get this same "Error: 18456, Severity: 14, State: 16."

Is there any way to issue a SQL statement and block on the call until a new database has been fully initialized and started before continuing? Alternatively, is there a way to get a callback once the DB is online?, Finally, if neither of the previous are possible, is there any entry in the master DB that one could poll to see when the new DB is up and running? I've tried the ovbious state in sys.databases, and Database.Status in DMO with no luck.

Any ideas? Thanks in advance!

GDM

|||

If you are getting a login failed message, it sounds like you are executing the CREATE DATABASE and CREATE TABLE statements on two different connections. Have you considered executing these statements using the same connection? If you would execute the CREATE TABLE after the CREATE DATABASE, on the same connection, you would not see such a failure.

The state you can query is state_desc in sys.databases - if it is ONLINE, it means the database was started.

Thanks
Laurentiu

|||How do i start sql server with "-y 18456"|||

Start->Run...->services.msc

Then go to the SQL Server service and stop it. Then Click <Properties> and in the <Start Parameters> field enter -y 18456. You can then click <Start> to restart the server with that parameter and then press cancel to exit without saving the parameter, so that future restarts won't use it. If you press OK, then the server will be restarted with that parameter - you probably don't want that.

Thanks
Laurentiu

|||

Ok I have an issue here....I am trying to do a full system recovery and this is what I am getting...

File/minint/system32/biosinfo.inf could not be loaded the error is code 14 ?

And I do NOT have the Windows XP Disk either...so if theres a way around this please by all means help me .......

can some please help me with this please

sql

Error: 18456 Severity: 14 State:11

Hi,
I posted this in the server-group, but no response, I removed the
message and now trying with this group...
I installed a SQL Server 2005 Workgroup on a W2k server.
Every 20 second the SQL errorlog log the two lines below:
DateTime Logon Error: 18456, Severity: 14, State: 11.
DateTime Logon Login failed for user 'DOMAIN\SERVERNAME$'. [CLIENT:
x.x.x.x]
The x.x.x.x is the server's IP.
State 11 means that the login doesn't have access to the server.
Yah...? So...?
The strange thing is that the "user" in this case is my 2003-server
(note the dollar-sign).
Could anyone point me in any direction - I am very lost.
( - and yes, the errorlog-file is now reaching 20MB after 2 weeks of
headless logging...)
Tanx in advance.
/oIt seems like some service on your Win 2003 machine is trying to connect to
the SQL Server instance on the Windows 2000 one.
The machine account (DOMAIN\machine_name$) is typically used when a
service running as system or network service try to access an external
resource, in this case establish a connection to SQL Server.
I would recommend taking a look to all your services and other automated
tasks in the Windows 2003 machine and try to find out which one is the one
trying to connect to SQL Server.
-Raul Garcia
SDE/T
SQL Server Engine
________________________________________
This posting is provided "AS IS" with no warranties, and confers no rights.
"ola.martins@.gmail.com" wrote:

> Hi,
> I posted this in the server-group, but no response, I removed the
> message and now trying with this group...
> I installed a SQL Server 2005 Workgroup on a W2k server.
> Every 20 second the SQL errorlog log the two lines below:
> DateTime Logon Error: 18456, Severity: 14, State: 11.
> DateTime Logon Login failed for user 'DOMAIN\SERVERNAME$'. [CLIENT:
> x.x.x.x]
> The x.x.x.x is the server's IP.
> State 11 means that the login doesn't have access to the server.
> Yah...? So...?
> The strange thing is that the "user" in this case is my 2003-server
> (note the dollar-sign).
> Could anyone point me in any direction - I am very lost.
> ( - and yes, the errorlog-file is now reaching 20MB after 2 weeks of
> headless logging...)
> Tanx in advance.
> /o
>|||Ok,
I'll look in to that.
I've got Brightstor ARCServe Backup installed, but I used the
"sa"-logon when defining the connection.
It's peculiar that something - and that I don't know what it is - is
connecting to the sql server...
Thank you for your response,
/o
Raul skrev:
[vbcol=seagreen]
> It seems like some service on your Win 2003 machine is trying to connect t
o
> the SQL Server instance on the Windows 2000 one.
> The machine account (DOMAIN\machine_name$) is typically used when a
> service running as system or network service try to access an external
> resource, in this case establish a connection to SQL Server.
> I would recommend taking a look to all your services and other automated
> tasks in the Windows 2003 machine and try to find out which one is the one
> trying to connect to SQL Server.
> -Raul Garcia
> SDE/T
> SQL Server Engine
> ________________________________________
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> "ola.martins@.gmail.com" wrote:
>|||If the windows 2003 server is running ARCserve and pointing to your database
try this;
Change your ARCserve Backup to use SQL authentication. I'm guessing from
your error that you are using Windows Authentication, is this correct.
Run Setupsql.exe from your CA install directory.
Good luck,
Carl
"ola.martins@.gmail.com" wrote:

> Hi,
> I posted this in the server-group, but no response, I removed the
> message and now trying with this group...
> I installed a SQL Server 2005 Workgroup on a W2k server.
> Every 20 second the SQL errorlog log the two lines below:
> DateTime Logon Error: 18456, Severity: 14, State: 11.
> DateTime Logon Login failed for user 'DOMAIN\SERVERNAME$'. [CLIENT:
> x.x.x.x]
> The x.x.x.x is the server's IP.
> State 11 means that the login doesn't have access to the server.
> Yah...? So...?
> The strange thing is that the "user" in this case is my 2003-server
> (note the dollar-sign).
> Could anyone point me in any direction - I am very lost.
> ( - and yes, the errorlog-file is now reaching 20MB after 2 weeks of
> headless logging...)
> Tanx in advance.
> /o
>

Error: 17806, Severity: 20, State: 2

We installed SQL Server 2005 Std Ed and MSProject application uses the instance..

Getting following Eorr Message

SSPI handshake failed with error code 0x80090311 while establishing a connection with integrated security; the connection has been closed. [CLIENT: <named pipe>]

Appreciate your help to fix this

Thanks

Arul

This is an SSIS forum. Try here for Project - http://www.microsoft.com/office/community/en-us/default.mspx

|||Hi,

1.) Mention the servername in FQDN format or use ip address. This may be due to Named pipes
2.) Try changing the protocols, its better to use TCP/IP port. Try connect using servername,portnumber

Error: 17802, Severity: 18, State: 3

I am getting this error on one of our SQL 7 server, with SP4 installed..
Error: 17802, Severity: 18, State: 3, Could not create server event thread..
Hi
See this knowladge base ,
http://support.microsoft.com/defaul...b;en-us;Q316749
"Brijesh" wrote:

> I am getting this error on one of our SQL 7 server, with SP4 installed..
> Error: 17802, Severity: 18, State: 3, Could not create server event thread..