?
Solved

Reporting Services IPv6 login error after Server name change

Posted on 2010-11-16
8
Medium Priority
?
890 Views
Last Modified: 2012-05-10
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
Comment
Question by:dakota5
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
8 Comments
 
LVL 21

Expert Comment

by:Jason Yousef, MS
ID: 34154879
Hi,

how many characters was the old name and the new name?
0
 

Author Comment

by:dakota5
ID: 34160402
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
 
LVL 21

Expert Comment

by:Jason Yousef, MS
ID: 34160528
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
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 

Author Comment

by:dakota5
ID: 34161353
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
 
LVL 21

Accepted Solution

by:
Jason Yousef, MS earned 2000 total points
ID: 34164059
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
 

Assisted Solution

by:dakota5
dakota5 earned 0 total points
ID: 34181048
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
 

Author Comment

by:dakota5
ID: 34185290
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
 

Author Closing Comment

by:dakota5
ID: 34211359
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

Featured Post

On Demand Webinar: Networking for the Cloud Era

Ready to improve network connectivity? Watch this webinar to learn how SD-WANs and a one-click instant connect tool can boost provisions, deployment, and management of your cloud connection.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

     When we have to pass multiple rows of data to SQL Server, the developers either have to send one row at a time or come up with other workarounds to meet requirements like using XML to pass data, which is complex and tedious to use. There is a …
How to leverage one TLS certificate to encrypt Microsoft SQL traffic and Remote Desktop Services, versus creating multiple tickets for the same server.
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question