Trying to install Telerik Reporting Q3 2007 SP1
I get prompted for DB login credentials
(local)\SQLExpress with windows authentication
I receive following error:
Error 27502: Could not connect to Microsoft SQL Server '(local)\SQLExpress'. Cannot generate SSPI context(0)
I have tried several variations, connecting to the sql server 2005 developer edition installed, using machine name, localhost, etc. All connections work using Visaul Studio and SQL management studio. I also get successful application connectivity. The only connectivity that is failing is Telerik Reporting installtion. Please advise.
I get prompted for DB login credentials
(local)\SQLExpress with windows authentication
I receive following error:
Error 27502: Could not connect to Microsoft SQL Server '(local)\SQLExpress'. Cannot generate SSPI context(0)
I have tried several variations, connecting to the sql server 2005 developer edition installed, using machine name, localhost, etc. All connections work using Visaul Studio and SQL management studio. I also get successful application connectivity. The only connectivity that is failing is Telerik Reporting installtion. Please advise.
2 Answers, 1 is accepted
0
Vinny D.
Top achievements
Rank 1
Rank 1
answered on 21 May 2008, 08:08 PM
I found an archived blogpost about this:
http://blogs.msdn.com/sql_protocols/archive/2005/10/19/482782.aspx
Gives a very good explanation as to the issue. I'm not sure how the Telerik Reporting installation is trying to access the SQL Server, but it would be slick if it tried multiple protocols, TCP/Shared/Names Pipes, etc. if it detects an error. I went with using 127.0.0.1 instead of (local) or machinename, and it worked. I'm guessing the .\ would of worked as well.
http://blogs.msdn.com/sql_protocols/archive/2005/10/19/482782.aspx
Gives a very good explanation as to the issue. I'm not sure how the Telerik Reporting installation is trying to access the SQL Server, but it would be slick if it tried multiple protocols, TCP/Shared/Names Pipes, etc. if it detects an error. I went with using 127.0.0.1 instead of (local) or machinename, and it worked. I'm guessing the .\ would of worked as well.
0
Hi Vincenzo,
Thank you for your feedback.
Local instances of SQL Server 2005 are enumerated with help of SQL-DMO. Instance names are returned in the form (local)InstanceName. Of course, (local) can be replaced by 127.0.0.1 but in most cases it is not required. Our installation tries to connect to the selected instance and fails if it is not possible.
For the upcoming release, we will research this issue in detail.
Sincerely yours,
Hrisi
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Thank you for your feedback.
Local instances of SQL Server 2005 are enumerated with help of SQL-DMO. Instance names are returned in the form (local)InstanceName. Of course, (local) can be replaced by 127.0.0.1 but in most cases it is not required. Our installation tries to connect to the selected instance and fails if it is not possible.
For the upcoming release, we will research this issue in detail.
Sincerely yours,
Hrisi
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center