• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 918
  • Last Modified:

Reporting Services IPv6 login error after Server name change

SQL server 2008 running on a Server 2008 R2 box, member of a domain, not a domain controller.  We had to change the name of the server.  Changed it, rebooted; SQL server and server 2008 worked fine except for a logon error that apeared in the SQL Server log every minute.
SSPI handshake failed with error code 0x8009030c....... connection closed.  [CLIENT:  the IPv6 IP address).  We are not using IPv6 that I know of.
Using nltest to put net logon into debug mode revealed the issue was the SQLexec account (domain account) that is used for several SQL services, including SQL Agent and the main SQL service.  But SQLexec works fine with these other services.  Stopping Reporting Services stopped the errors.

Any idea why renaming the file server triggered the errors and how to fix this without reloading SQL server?
0
dakota5
Asked:
dakota5
  • 5
  • 3
2 Solutions
 
Jason Yousef, MSSr. BI  DeveloperCommented:
Hi,

how many characters was the old name and the new name?
0
 
dakota5Author Commented:
old name 11 characters
new name 10 characters

Why does Reporting Services use IPv6?   The other MS SQL related services don't use it.
Is this some type of tunneling connection?
0
 
Jason Yousef, MSSr. BI  DeveloperCommented:
thats weired, i thought the name might be more than 15 char.!!!

SSRS is not using it since you're not using it in ur network...

looks like something wrong with connection string? pointing to the old server name
I would go to "reporting services configuration" and see what's the excusion account.

also go to "sql server configuration manager" to see which account is used to run the reporting services.

looks like you're using a local service account and it's still pointing to the old name, changing it or refereshing it might help.

try that and get back to me again :)
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

 
dakota5Author Commented:
No, that's not it. As I mentioned in the question, the service is using a domain account SQLexec which has the correct permissions.  This somehow relates to networking and IPv6-- Reporting Service must use IPv6 preferentially.
0
 
Jason Yousef, MSSr. BI  DeveloperCommented:
When you configure reporting services, it uses a security ceritifcate key, so it looks like it has the old server name.

Remove reporting services, uninstall it, and re-install it again.
that might help.

0
 
dakota5Author Commented:
I found the answer in MSDN.  One needs to change the value for @@servername of the SQL server
http://msdn.microsoft.com/en-us/library/ms143799%28v=SQL.100%29.aspx

and also open the Report Server configuration file and modify the entry to reflect the new server name.
http://msdn.microsoft.com/en-us/library/ms345235%28v=SQL.100%29.aspx
0
 
dakota5Author Commented:
To correct the SQL Server name in Report Server configuration, probably easiest to use the reporting services configuration program.
http://msdn.microsoft.com/en-us/library/ms159644%28v=SQL.100%29.aspx
0
 
dakota5Author Commented:
Removing and reinstalling report server will probably work as long as you also correct the entry in @@servername.  But reinstalling report server is not necessary
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now