Good device to put Instance root directory on a SQL Server 2012 Always On Failover Cluster ?

Hello, I'm currently testing SQL Server 2012 AlwaysOn Failover Cluster.
I wonder if I installed it correctly : I installed the software on both server with the instance root directory set to a directory on a cluster shared module.
The reason why I'm not sure is because, when I wanted to upgrade from SP1 to SP2, I wanted to do it first on the passive node, but it failed for most of the components it had to upgrade. So I first upgraded the active node then failover and upgraded the
newly active node.
I installed SQL Server this way because our system admins don't like us to install in on C:\ for their own reasons (maybe backup, or something ...)
I'm pretty sure there is something wrong. What's your point ?
Thanks in advance.

>I wonder if I installed it correctly : I installed the software on both server with the instance root directory set to a directory on a cluster shared module.
Nope.
SQL Server 2012 and earlier don't support data files on CSV volumes (SQL 2014 does).
And for any version of SQL Server the SQL Server instance directory should not be on a clustered disk. The Installation is local to each node, so should be on a non-clustered disk. It may be supported to put the instances in different locations
on the same clustered disk, but I wouldn't recommend it.
Installing the SQL Binaries on C:\ is fine. If you have another local volume you can also install them there.
David
David http://blogs.msdn.com/b/dbrowne/

Similar Messages

How to restore a database backup taken from a SQL Server 2012 instance to SQL Server 2014

I am trying to restore a database backup taken from a SQL Server 2012 instance to my new SQL Server 2014 instance. When I add the .bak through the Mgmt studio UI, it does not seem to find a backup set in the file so I cannot proceed (does not give
me any errors though either. I tried restoring through TSQL command but only got a database restore terminating abnormally error with no other details. How can I restore this database to SQL 2014?

Hello,
Please examine SQL Server Error Log and share with us any error you can find. The following article may locate the log:
http://msdn.microsoft.com/en-us/library/ms187109.aspx
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server 2012 Developer Edition will not install. Setup files don't even get copied completely. Win 8.1. ACT instance is loaded & can't be deleted. From log file: Error: Action "PreMsiTimingConfigAction" failed during execution.

SQL Server 2012 Developer Edition will not install. Setup files don't even get copied completely. Win 8.1. ACT instance is loaded & can't be deleted. From log file: Error: Action "PreMsiTimingConfigAction" failed during execution.

Hello,
I am glad it worked.
Thank you for visiting MSDN forums!
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server 2012 Express Instance is Not Discovered

I have a single SQL Server 2012 Express instance that is the backend database for a small door security application. I just noticed after having deployed the OpsMgr agent months ago that it never discovered the SQL instance. The SQL instance
is, as stated, Express, and it's the only Express instance I have. Is that why it is not discovered? All the documentation I found seems to indicate the opposite -- that Express is discovered and there are steps you can take to exclude Express
instances. I have no overrides set to exclude any instance or any database.
- System Center Operations Manager 2012 RTM (no SP1, no R2)
- SQL Server 2012 MP version 6.3.173.1
- SQL Server is Windows Server 2012
- SQL Server 2012 Express running on a Hyper-V VM. Instance is named DOORSERVER\Eclipse
- Agent is installed and other discoveries seem to be working fine
- No discovery errors in the event log related to SQL, although there is one about the Windows Server 2008 discovery not being able to start, but I'm on Windows Server 2012, so I am guessing that's okay?
- No overrides are set on the discovery
- Discovery has found every other SQL Server 2012 instance (standard and enterprise editions)

Well, just realized I didn't have the latest MP. Upgrading to 6.4.1.0 version of the SQL MP fixed the discovery issue.

Trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.

I am trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
It verifies the connection and then throws the error:
The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
WSUS Server : Windows Server 2012 R2
Remote SQL Server: 2012 SP1 CU7 hosted on Windows Server 2012 R2
Please let me know if anyone has experienced this issue.

We were trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
It verifies the connection and then throws the error:
The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
Same error even after rebooting the server multiple times.
WSUS Server : Windows Server Standard2012 R2
Remote SQL Server: Windows Server 2012 SP1 CU7 hosted on Windows Server 2012 R2
Event ID 7000:
The Windows Internal Database service failed to start due to the following error:
The service did not start due to a logon failure.
Event ID 7041
The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.
Service: MSSQL$MICROSOFT##WID
Domain and account: NT SERVICE\MSSQL$MICROSOFT##WID
This service account does not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user
right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated
with this node might be removing the right.
I found following article:
"MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID" error when you install WID in Windows Server 2012
http://support.microsoft.com/kb/2832204/en-us
To work around the issue, use one of the following methods:
Assign the Log on as a service user right to NT SERVICE\ALL SERVICES in the GPO that defines the user right.
Exclude the computer from the GPO that defines the user right.
We moved the SCCM server to OU where no policies were getting applied and then applied the new GPO to that OU. Restarted the server and we were able to install WSUS role.
Regards
PR

SQL Server 2012 syspolicy_purge_history job causes cross-instance login failures w. EraseSystemHealthPhantomRecords

I have unique service accounts set up for multiple instances on the same SQL Server 2012.
When step 3 of the inbuilt syspolicy_purge_history job(Erase Phantom System Health Records) runs, it appears to attempt to run against every instance on the server despite being passed the instance path!
The SQLServer's powershell script call:
if ('$(ESCAPE_SQUOTE(INST))' -eq 'MSSQLSERVER') {$a = '\DEFAULT'} ELSE {$a = ''};
(Get-Item SQLSERVER:\SQLPolicy\$(ESCAPE_NONE(SRVR))$a).EraseSystemHealthPhantomRecords()
so with instances SERVER\X this runs as...
(Get-Item SQLSERVER:\SQLPolicy\SERVER\X).EraseSystemHealthPhantomRecords()
SERVER\X's job will run and I will see login failures in the error logs of SERVER\Y and SERVER\Z for the service account set up for instance X.
It seems Microsoft's only 'accepted solution' to this problem is for me to compromise my security by escalating the access of these service accounts?
Has anyone else run into and corrected this failure?

Hi Atombath,
When you install multiple instances on one Server, and the SQL Server’s powershell scripts are the same in inbuilt syspolicy_purge_history job steps. However, when you start PowerShell by right clicking
syspolicy_purge_history job, you will find it will point to their own instance. I do a test in my SQL Server 2012,
it will not across instance to collect the error logs. So I recommend you use its original powershell scripts for the syspolicy_purge_history job.
Sometimes, if you run the syspolicy_purge_history job on a clustered instance, the syspolicy_purge_history SQL Server Agent job may fail due to using the computer node name instead of the virtual server name. For more information, see:
http://support.microsoft.com/kb/955726/en-us
In addition, you can use different service account for your multiple SQL Server instances on the same Server. And make sure the accounts that you created get added to the sysadmin fixed server role, the accounts are also set in the three Agent roles (SqlAgentUserRole,
SqlAgentReaderRole, and SqlAgentOperatorRole).
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Services of 2nd instance disappearded from SQL Server 2012 Configuration Manager but still running

We recently configured multiple SQL Server 2012 R1 (two-node) clusters. Some with two instances. However, we discovered later that the Configuration Manager only lists the services of the 1st instance (the default MSSQLSERVER instance). The other named instance
is still running and can be failed over from one node to the other using Cluster Failover Manager but the services are not showing up in Configuration Manager in any of the two nodes.
Any thoughts as to why we see this odd behavior and how to fix it? We have done two instances before in SQL Server 2008 R2 but never saw this behavior.
Thanks,
Omer

Please see my answer above about the SQLCM version. We use the highest.
As I said before that this happens only when we have two instances running in a SQL2012 cluster. We configured 7 SQL 2012 clusters. three of them have two instances but only the services of one instance are displayed in CM. Services of the default instance
are listed in two of these clusters while services of the named instance are listed in the 3rd one.
One thing to note about these configurations is that the installer could not bring the services at the end of installation online because it did not have permission to create the computer objects in AD during setup thus we had to follow a known workaround
that involves having the domain admin fix these permissions and then we were able to add the SQL Agent Service to the cluster and bring the services online after modifying the ConfigurationState key value of each instance in the registry.
The installer account is setup as a local admin and we asked the domain admin to give it "Read All properties" and "create computer objects" in AD but for some reason it does not seem to have the ability to create these computer objects during installation
and the objects are to be pre-created and their permissions reset afterward.
I am giving this information and I am not sure if it has anything to do with the fact that SQLCM is listing the services of one instance and not the other.

Unable to set (ssl) certificate on a SQL Server 2012 clustered instance

Hello everyone!
I'm trying to encrypt the SQL Server communication with SSL but I can't add the certificate in the configuration manager. I've found and tried a lot of different explaination but none of them worked. I'll described what I've done and hope someone will point
out what I'm missing.
Here is my situation:
- SQL Server 2012 Enterprise Edition. Instance name = INSTANCE, FQDN = SQINSTANCE.mydomain.com. The instance is running under a customized service account: mydomain\sql_sa
- Two cluster nodes running Win Server 2008R2: NODE1.mydomain.com and NODE2.mydomain.com. Cluster itself is CLUSTER.mydomain.com
What I've done:
1) Asked the team in charge to generate a certificate issued to "SQINSTANCE.mydomain.com" with aliases to "NODE1.mydomain.com", "NODE2.mydomain.com" and "CLUSTER.mydomain.com". I get a certificate with "p7b"
as extension
2) Connect on "NODE2.mydomain.com" with account "mydomain\sql_sa". Opened MMC and added the certificate under "Personnal" folder. I tried to add it with "Current user" and "Local computer" settings. Saw both
on internet since I use a specific service account
3) Get the thumbprint of the certificate and add it under HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL11.INSTANCE\MSSQLServer\SuperSocketNetLib\Certificate. (I triple checked to remove blanks or special characters)
4) Reboot the node
5) Open the SQL Server Configuration Manager, go to the network properties. Certificate does not appear in the list
I tried to check with certutil and saw the certificate in the output. Some guys talked about some private key but I don't see this particularity in my situation. I tried to check if the certificate is valid and, according to the criterias, it is.
Does anyone can help me with this?

Hi,
Are you sure you've got the certificate correct? http://msdn.microsoft.com/en-us/library/ms191192.aspx
To use encryption with a failover cluster, you must install the server certificate with the fully qualified DNS name of the virtual server
on all nodes in the failover cluster. For example, if you have a two-node cluster, with nodes named test1.<your
company>.com and test2.<your
company>.com, and you have a virtual server named virtsql, you need to install a certificate for virtsql.<your
company>.com on both nodes. You can set the value of the ForceEncryptionoption
toYes
In your case, shouldn't it be created for CLUSTER.mydomain.com?
Thanks, Andrew
My blog...

SQL Server 2012 is prompting wrong message while creating new instance.

Summary:
While performing two task simultaneously 1) deleting existing SQL Server 2008 r2 instance 2) Creating SQL Server 2012 Instance. I received wrong message.
Explanation:
I have SQL Server 2012 setup in my server. By mistake I created SQL Server 2008 r2 instance.
Now simultaneously I was performing two task 1) deleting SQL Server 2008 r2 instance 2) Creating SQL Server 2012 Instance.
While creating SQL Server 2012 instance i received popup message "Another SQL Server 2012 setup is running but the running setup was not SQL Server 2012, it was SQL Server 2008 r2.

Hello,
You should not run two SQL Server setups at the same time. In fact, SQL Server has a rule to verify there is no pending restart because of an installation/uninstallation in progress.
Please cancel the installation of SQL Server and continue uninstalling the SQL Server 2008 R2 instance.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server 2012 - Cannot Use Network Drive as a Backup Device

Hello Community,
I am using SQL Server 2012 and I am trying to add a mapped drive as a backup device, but I am not even to see that drive from SQL Server. Has anyone else had this issue and if so can you help me resolve it?
Thanks!
Tom
Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award -
Linked-In - SharePoint Gypsy

Hey David,
I checked the drive and share permissions, and the service account for SQL Server, in this case named "sqlsvc" has been granted full permission to both. I tried the script but it also failed, the code is below:
DATABASE[TestDb]TO
DISK=N'\\sqlclus02\SharePointBackup\TestDb.bak'WITHNOFORMAT,NOINIT,
NAME=N'TestDb-Full
Database Backup',SKIP,NOREWIND,NOUNLOAD,
STATS=10
Also, I haven't been able to confirm that the sqlsvc account is a domain account, but I do know the server is clustered.
Thanks!
Tom
Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award -
Linked-In - SharePoint Gypsy

Configure SSL SQL Server 2012 Cluster Instance

Hi,
I am trying to configure a SSL Certificate on a named clustered instance but i can't
This is the errorlog message
2014-12-11 14:28:51.49 spid10s Error: 17182, Severity: 16, State: 1.
2014-12-11 14:28:51.49 spid10s TDSSNIClient initialization failed with error 0xd, status code 0x38. Reason: An error occurred while obtaining or using the certificate for SSL. Check settings in Configuration
Manager. The data is invalid.
2014-12-11 14:28:51.49 spid10s Error: 17182, Severity: 16, State: 1.
2014-12-11 14:28:51.49 spid10s TDSSNIClient initialization failed with error 0xd, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The data is invalid.
2014-12-11 14:28:51.49 spid10s Error: 17826, Severity: 18, State: 3.
2014-12-11 14:28:51.49 spid10s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error
log.
2014-12-11 14:28:51.50 spid10s Error: 17120, Severity: 16, State: 1.
2014-12-11 14:28:51.50 spid10s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Hi Jame,
According to your description, you encountered the error when you were trying to configure a named clustered instance to use SSL certificate.
Based on my research, the error 17182 "TDSSNIClient initialization failed with error 0xd, status code 0x38" occurs specifically because of the fact that the string under Certificate value cannot be properly converted back to a valid thumbprint
of the certificate.
A common root cause for these symptoms is an invisible character that may have been inadvertently added to the certificate's Thumbprint value, when it gets copied out of the Certificates snap-in's rich-edit control in MMC. For example, if the thumbprint
contains the Unicode character, then it may cause this issue, the following similar issue is for your reference:
http://blogs.msdn.com/b/sqljourney/archive/2013/07/23/when-using-ssl-sql-failover-cluster-instance-fails-to-start-with-error-17182.aspx
For more details and the resolution about this issue, please refer to the following article:
https://support.microsoft.com/kb/2023869?wa=wsignin1.0
If you have any question, please feel free to let me know.
Regards,
Jerry Li

Cannot install Windows Azure Active Directory Sync tool on Server 2012 w/ SQL Server 2012

I went to change a user password on the server today and after changing the password I logged into the SQL server to run “Import-module dirsync” & “Start-onlinecoexistencesync” in powershell in order to sync the new password with Exchange Online. After
waiting ten minutes I tried setting up the email on the user’s PC but the new password was not being accepted. I logged into Office 365 and I got the following warning.
"Warning: Last synced more than 3 days ago | Troubleshoot"
So I pressed troubleshoot and the site installed a tool on the server to try and find out what the issue was. After the tool ran it told me that the version of dirsync.exe was out of date and that I should download the new one and install it. So I downloaded
the new dirsync.exe (version 7020 I believe) and tried installing it. I kept getting error after error, different ones to boot.
First it told me I wasn’t part of the FIMSyncAdmins group (so I added myself), then it told me that it could not connect to MIIS server, so I tried starting it and windows said that there was a problem with the sign on used by the service so I had
to reset the password for the local user named “AAD_bfd1d6f0cef7” which was being used by that service. The service started successfully and when I went to install it told me I could not and if the problem persisted I should uninstall the old version and reinstall.
Looking in the log file, before I even install the software I see the following Information...
Level: Information
Date: 2015-03-24 12:49:17 PM
Source: Directory Synchronization
Event ID: 0
Task Category: None
"The current configuration of the Windows Azure Active Directory Sync tool is invalid. Please reinstall the Windows Azure Active Directory Sync tool."
So I tried to reinstall (i even manually uninstalled the old version and removed the folder in C:\Program Files\ called "Windows Azure Active Directory Sync") and on reinstall I get as far as "Installing Components" and then after a little
while it errors out with the error "The install was unable to setup a required component. Check the event logs for more information. Please try the installation again and if the error persists, contact Technical Support. "
Looking at the log file there are a bunch of new entries, created by the installer. There's over 300 new entries and I can not post them all here due to character count restriction. you can find the log file here...
www.clarkfreightways.com/wp-content/uploads/2015/03/dirsync_log.txt
Can anyone tell me what is going on, I've been looking through the log files and I can see errors but I'm not sure what to do to fix it.

Greetings!
Wanted to know if you've hosted the DirSync tool (latest version) on a VM? Also, if this is deployed in a Production or Lab environment? If it's a lab setup, you may
try installing the DirSync on a new VM / Server (suspecting that it could be some machine related issues).
Here's a Support KB helping with different errors:
http://support.microsoft.com/en-us/kb/2684395
If its a production environment, would suggest to raise a
Technical Support Ticket for assisting further with break-fix.
Thank you,
Arvind

Sql server 2012 express - tcp/ip connection to named instance using dynamic port not working

I have a named instance on a SQL 2012 Express server that won't connect via TCP/IP when wanting to connect off of the dynamic port. I can connect via shared memory locally on the server.   I can connect to the namespace when specifying the
dynamic port listed in the configuration manager.
This is the only named instance on the server and it is not the default.
TCP/IP is enabled
Allow Remote connections is enabled
the server browser service is running
I can connect via the dynamic port number
I am testing the connection locally on the server, so I don't believe a firewall is the issue. I get the same results if I test it from a remote computer.
When using the sqlcmd (sqlcmd -S tcp:SQLSRVR\NAMEINST -E) I get the message that "the requested protocol isn't supported [xfffffffff]".   The command (sqlcmd -S tcp:SQLSRVR\NAMEINST,59992 -E) works.
Through SSMS, I get the message "the connection was actively refused".
On other boxes, I can connect with the named instance without having to specify the port.
I have looked through the sql logs and nothing much shows up. The log does show that is listening on the port # for ipv4 and ipv6.   There is also a line in there talking about the SPN not being registered and not to worry about it if
you are not using Kerberos. I logged in through shared memory and it said I was using NTLM.
Any help would be appreciated.
thanks.

Hi clw,
I’m writing to follow up with you on this post. According to your description, I do a test, if you configure the database engine to listen on a specific TCP port (59992), and
the port is opened in the firewall. If you want to connect to the SQL Server instance, you 'd better to
use the port number.
In my opinion, by default, the default instance of the Database Engine uses port 1433, usually, if you have configured the server to listen on a non-default port number, when an instance of SQL Server uses dynamic port allocation, the connection string that
is built at the SQL Server client does not specify the destination TCP/IP port unless the user or the programmer explicitly specifies the port. Therefore, the SQL Server client library queries the server on UDP port 1434 to collect the information about the
destination instance of SQL Server.
If UDP port 1434 is disabled, the SQL Server client cannot dynamically determine the port of the named instance of SQL Server. Therefore, the SQL Server client may be unable to connect to the named instance of SQL Server. In this situation, the SQL Server
client must specify the dynamically allocated port where the named instance of SQL Server is listening.
For more information about configuring an instance of SQL Server to listen on a specific TCP port or dynamic port, you can review the following article.
https://support.transfrm.com/entries/503111-How-to-configure-an-instance-of-SQL-Server-to-listen-on-a-specific-TCP-port-or-dynamic-port
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

MS SQL 2008 R2 Named instance: Login failed. Microsoft SQL server, Error: 18452) - Tryig to access using the FQDN assigned for the backup network card.

Hi,
I have a windows 2008 R2 Enterprise servers with standalone MS-SQL 2008 R2 named instance. The server is having two networks, once production and the second for backup. The server FQDN is resolving to the production IP. The backup NIC
DNS dynamic update is disabled and an "A" record is registered with the dns. While trying to connect to the instance using the management studio:
Successfuly able to connect using the instance name, the production hostname, production IP and backup IP.
but while trying to connect to the insance using the backup hostname getting the below error:
"Login failed. The login is an untrusted domain and cannot be used with windows authentication. (Microsoft SQL server, Error: 18452) "
This is required for the backup tool to get connected using the backup FQDN of the server.
Should I need to create a host name alias, request you to kindly assist me with the best recommedation to fix this.
http://blogs.msdn.com/b/dbrowne/archive/2012/05/21/how-to-add-a-hostname-alias-for-a-sql-server-instance.aspx

Hi,
It might be a kerberos issue. Check that there are valid SPN's registered using the setspn utility - http://technet.microsoft.com/en-us/library/cc731241.aspx
Thanks, Andrew
My blog...

Report Services Install - SQL Server 2012 instance blank

I have looked at all the links and tried the suggestions and I am still having the problem:
SCCM 2012 R2 SQL 2012 SP1 SSRS installed and configured (separate boxes)
When I try to add the reporting services role, it finds the SCCM database and verifies connectivity to it, the SSRS instance drop down is blank.
Using a domain service accout with local admin rights on both machines and sa rights in SQL.
There is a firewall between the Primary Server and the SQL Server and ports 80, 135, 443, 445, 1433 and the high RPC range.
Does anyone know how it is determining the instance? I have read it is via WMI but I am not sure if it is a query or executing a method. I have verified the svc acct has the correct DCOM privs.

Hi Jo75,
According to my understanding, you get the error message “Unable to connect to the database: Network error IOException: Connection refused: connect” when you connect to the SQL Server database
during installation of Trend Micro's DSM.
Based on my test, I was able to connect to the SQL Server database with the user name “sa” during the installation of Deep Security Manager and no error message appeared. Besides, I created
a new SQL Server login and it also worked fine.
Make sure you can connect to the SQL Server instance successfully, you can follow these steps:
1. Open SQL Server Management Studio and click Database Engine from pull-down menu of Connect in Object Explorer.
2. In the Server name box, you should type hostname\instance name. And you should choose SQL Server Authentication in Authentication box and type “sa” in Login box, then type your password
and click Connect.
If you can’t connect to SQL Server, you can try to create a new login and give it full permission. Please follow these steps:
1. Open SQL Server Management Studio and connect to SQL Server with administrator account.
2. Click Security and right click Logins then choose New Login.
3. In General page, type your new Login name and choose SQL Server Authentication, then set your password.
4. Click Server Roles
at
the
top-left
corner
and check the dbcreator box.
5. Click Status at the top-left corner and check enabled under the login, then click ok.
6. Click the database you want to connect during the installation of Deep Security Manager, expand the security and right click the users, then choose New User.
7. Type your user name and login name in General page. Click Owned Schemas page and check db_owner. Also check db_owner in Membership page then click ok.
8. Retry install Deep Security Manager.
Please follow these steps and how it works.
Best regards,
Qiuyun Yu

Good device to put Instance root directory on a SQL Server 2012 Always On Failover Cluster ?

Similar Messages

Maybe you are looking for