invalid filter on server level filter must be empty or server attribute must be equal with the true server name.

_{Monday, November 4, 2013 2:18 PM | 1 vote}

Hi all,

• given sysadmin or server admin permissions for particular login ended up with this error:

invalid filter on server level filter must be empty or server attribute must be equal with the true server name.

_{Monday, November 4, 2013 2:39 PM}

The following blog deals with the issue:

SQL Server - Invalid Urn filter on server level: filter must be empty, or server attribute must be equal with the true server name

Kalman Toth Database & OLAP Architect IPAD SELECT Query Video Tutorial 3.5 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

_{Tuesday, February 28, 2017 8:31 PM}

Kalman,

This item is of interest but the link above is not an allowed link on our network.   Can you post what you know about an Invalid Urn?   I've never seen the error and it looks interesting.   I think I've seen this issue occur when SQL is installed on one server and then the name of the server is changed.

R, J

_{Wednesday, December 13, 2017 1:31 PM | 5 votes}

Hi,

I received this error when I tried to change the password of SQL Login through GUI.

I am using on SQL Server 2016 Standard Edition on windows server 2012.

So as I said I received the same error when I tried to change the password of SQL Login through GUI.

So instead of GUI I simply used the following command to update / change / reset the password of the SQL login and issue resolved.

Use Master

Go

ALTER LOGIN [LOGIN_NAME] WITH DEFAULT_DATABASE=[master]
GO
USE [master]
GO
ALTER LOGIN [LOGIN_NAME] WITH PASSWORD=N’NewPassword’ MUST_CHANGE
GO

Now that was about my issue but in your case :

SQL Server Setup sets the server name to the computer name during the installation. If someone has changed the Hostname of the computer after installing MSSQL; the MSSQL server name actually does not get changed and this causes error message "Invalid Urn filter on server level: filter must be empty, or server attribute must be equal with the true server name".

To check this, execute following:

1. Open cmd, type hostname and execute. OR you can also check the Hostname in SQL Server as well using the command: SELECT HOST_NAME() AS 'HostName
2. Open SSMS i.e. SQL management studio, in the new query window type SELECT @@SERVERNAME AS 'Server Name' and execute.

Result of 1 and 2 will be different.

To correct the server name, from “Server1” to “Server2”, run the query in SQL management studio as follows: 
sp_dropserver 'Server1';
GO
sp_addserver 'Server2', local;
GO

Restart the server and run the SELECT query again to see the change.

For more information, click here.

_{Thursday, December 14, 2017 2:57 PM}

Kalman,

I was able to get to your proposed link this morning.   It is closer to what is occurring.   I'm running it past of system administrators.   We now there is a DNS issue somewhere because we are using a three network solution to keep SQL in the DMZ.   I'm guessing it is possible that the AD may have registered the wrong IP for the DNS.  

Thanks

1. Go to Network settings and IP v4 properties
2. Uncheck the register this connection’s addresses in DNS
3. Open DNS mmc and remove old A records for that SQL01
4. Create new A record for the SQL01\MSSQLSERVER
5. Create new A record for the SQL01\Inst02 for SQL02.domain.local
6. Repeat for other named SQL instances

R, J

_{Thursday, December 14, 2017 2:59 PM}

Kundan,

Thanks for your reply.  This has actually happened on our network in the past when servers were setup before the actual server names were known, but in this case, the names are setup correctly.  But the advice is on target.

R, J