Solved

Reporting Services IPv6 login error after Server name change

Posted on 2010-11-16
8
884 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
  • 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
 

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
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
LVL 21

Accepted Solution

by:
Jason Yousef, MS earned 500 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

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Question has a verified solution.

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

In this article I will describe the Copy Database Wizard method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
Along with being a a promotional video for my three-day Annielytics Dashboard Seminor, this Micro Tutorial is an intro to Google Analytics API data.
As a trusted technology advisor to your customers you are likely getting the daily question of, ‘should I put this in the cloud?’ As customer demands for cloud services increases, companies will see a shift from traditional buying patterns to new…

920 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

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now