CANNOT GENERATE SSPI CONTENT

Dear support,
I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
Server SP4. However, when I register the SQL Server through Enterprise
Manager (or connect the SQL Server through Query Analyzer), the error:
A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
REASON: CANNOT GENERATE SSPI CONTENT
PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
However, I can succesfully register by typing the IP Address.
Can anyone help?Maybe the server is unable to resolve the "mySQLServer" name? Can you ping
it? Are you trying to connect using Named Pipes? Is it using port 1433?
I would consider adding an Alias to the client network utility that points
"mySQLServer" at the IP address that works correctly (and of course points
to the correct port).
Or, if it ain't broke, don't fix it; since IP address works, use the IP
address?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"jenny" <jenny@.discussions.microsoft.com> wrote in message
news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> Dear support,
> I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
> Server SP4. However, when I register the SQL Server through Enterprise
> Manager (or connect the SQL Server through Query Analyzer), the error:
> A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> REASON: CANNOT GENERATE SSPI CONTENT
> PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
> PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
> However, I can succesfully register by typing the IP Address.
> Can anyone help?
>|||Probably problem is with your DNS, on the computer on which SQL server is
installed check computer name and primary DNS suffix.
Regards,
Daniel
"jenny" <jenny@.discussions.microsoft.com> wrote in message
news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> Dear support,
> I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
> Server SP4. However, when I register the SQL Server through Enterprise
> Manager (or connect the SQL Server through Query Analyzer), the error:
> A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> REASON: CANNOT GENERATE SSPI CONTENT
> PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
> PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
> However, I can succesfully register by typing the IP Address.
> Can anyone help?
>|||Hi all,
I can successfully ping my SQL server (with my SQL server name is the same
as my Server name).
It is quite impossible to use IP as my system (a lot of programs and
configure) has been developed and is using SQL server name for the SQL
connection.
BTW, I have many SQL server and only this SQL server got the "Cannot
generate SSPI content" problem. Any more hints ?
"Daniel Joskovski" wrote:
> Probably problem is with your DNS, on the computer on which SQL server is
> installed check computer name and primary DNS suffix.
> Regards,
> Daniel
> "jenny" <jenny@.discussions.microsoft.com> wrote in message
> news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> > Dear support,
> >
> > I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
> > Server SP4. However, when I register the SQL Server through Enterprise
> > Manager (or connect the SQL Server through Query Analyzer), the error:
> > A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> > REASON: CANNOT GENERATE SSPI CONTENT
> > PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
> > PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
> > However, I can succesfully register by typing the IP Address.
> >
> > Can anyone help?
> >
> >
>
>|||> It is quite impossible to use IP as my system (a lot of programs and
> configure) has been developed and is using SQL server name for the SQL
> connection.
(a) the name of the data source should not be hard-coded into programs. At
the very least, all of your applications should get this kind of global
parameter from a single, central location. In your current state, what are
you going to do when you change the SQL auth password? Or switch from SQL
auth to Windows auth? Or move the database to a server with a different
name?
(b) barring (a), have you seen my suggestion to add the server name -> IP
mapping in the client network utility on the workstations that can't connect
to this SQL Server by name?
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Hi Aaron,
Thanks first.
The SQL server name is not hardcode... It is stored in the configuration
file or database value. To be more accurate, now my system is working fine
by using the SQL Server Name except for the following cases:
- Register the SQL Server through Enterprise Manager
- Connect to the SQL Server through Query Analyzer
- Run osql command with connection typed with the SQL Server Name
Some of my predefined script are coded with the SQL Server Name and is
worked fine for other SQL Servers except the one I mentioned. I even got the
same problem when I connect the SQL Server on the same Server. (e.g. The SQL
Server A is installed in the Windows Server A.) However, I have one finding
that if I add the SQL Server IP entry in the "host" file, I can then solve
the above 3 problems. I wonder, is adding the host file the only
(appropriate) way to solve the problem ? Is there any other methods as I
only got one SQL Server having this problem. Thanks a lot again.
For more information, my SQL Server is running cluster, using NamePiped and
TCP/IP connection with port 1433.
For your option (b), I'll consider... But curious that why other SQL servers
of my system works without problem (they have similar settings during
installation)
"Aaron [SQL Server MVP]" wrote:
> > It is quite impossible to use IP as my system (a lot of programs and
> > configure) has been developed and is using SQL server name for the SQL
> > connection.
> (a) the name of the data source should not be hard-coded into programs. At
> the very least, all of your applications should get this kind of global
> parameter from a single, central location. In your current state, what are
> you going to do when you change the SQL auth password? Or switch from SQL
> auth to Windows auth? Or move the database to a server with a different
> name?
> (b) barring (a), have you seen my suggestion to add the server name -> IP
> mapping in the client network utility on the workstations that can't connect
> to this SQL Server by name?
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>|||It is possible to ping your server name and still have problems with DNS,
try to ping FQDN for example instead of Ping Stockholm, ping
Stockholm.nwtraders.msft or better check full name of computer on which is
SQL server installed.
Regards,
Daniel
"jenny" <jenny@.discussions.microsoft.com> wrote in message
news:952A3B38-2035-4D64-95FA-0CC2F0F2BB87@.microsoft.com...
> Hi all,
> I can successfully ping my SQL server (with my SQL server name is the same
> as my Server name).
> It is quite impossible to use IP as my system (a lot of programs and
> configure) has been developed and is using SQL server name for the SQL
> connection.
> BTW, I have many SQL server and only this SQL server got the "Cannot
> generate SSPI content" problem. Any more hints ?
> "Daniel Joskovski" wrote:
> > Probably problem is with your DNS, on the computer on which SQL server
is
> > installed check computer name and primary DNS suffix.
> > Regards,
> > Daniel
> >
> > "jenny" <jenny@.discussions.microsoft.com> wrote in message
> > news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> > > Dear support,
> > >
> > > I'm running SQL Server Enterprise Edition with SP3a on Windows
Advanced
> > > Server SP4. However, when I register the SQL Server through
Enterprise
> > > Manager (or connect the SQL Server through Query Analyzer), the error:
> > > A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> > > REASON: CANNOT GENERATE SSPI CONTENT
> > > PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER
REGISRATION
> > > PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY
AGAIN
> > > However, I can succesfully register by typing the IP Address.
> > >
> > > Can anyone help?
> > >
> > >
> >
> >
> >