Jump to content


Photo

PVS 7.12 with SQL 2016 Failover Cluster - Undefined Database Error (11)

Started by mkoers , 13 February 2017 - 04:28 PM
5 replies to this topic

Best Answer mkoers , 20 February 2017 - 12:14 PM

Spend some time this weekend to find the cause / solution.

I cannot give an exact root cause but at least I got it up and running.

 

What did I do:

 

- Updated the SQL 2016 SP1 Cluster to the lastest patches

- Clean install of the PVS servers with Windows Server 2016 Standard + latest updates

- Clean install of the latest SQL 2012 Native client

- Clean install of PVS 7.12

- New database

 

TLS 1.2 is still enabled and the registry key mentioned before are NOT implemented.

 

Did a full test of PVS and everything functions as it's suposed to.

Services can be restarted, server states are live and so on.

mkoers Members

Mattheus Johannes Koers
  • 8 posts

Posted 13 February 2017 - 04:28 PM

Ran into the following with my homelab this weekend and cannot find a rootcause/solution. Therefor trying it through the forums.

 

Original situation:

 

Database server: SQL 2016 Standard - StandAlone (W2K16)

Database Name: CitrixProvisioningServices

PVS Servers:       PVS01 / PVS02

 

New situation:

 

Database server: SQL 2016 Standard - Failover Cluster (W2K16)

(NOT an AlwaysOnCluster)

Database Name: CitrixProvisioningServices

PVS Servers:       PVS01 / PVS02

 

To put explaination to the above, it the setup fase of my lab I did not have shared storage available so went with a single standalone SQL server. This hosted the databases for Xendesktop and Provisioning Services.

 

This weekend I had my storage so I have setup an two node SQL Failover cluster hosting two instances (INSTANCE01 / INSTANCE02).

 

After this was done I moved the Xendesktop databases to INSTANCE02 without any issues.

Following up on that I moved the PVS database to INSTANCE01 without any issues.

At least no errors in the configwizard...

 

When browing in the PVS Console to the site servers folder the servers were in an UNKOWN state. Rerunning the wizard did not help, reverting to the old SQL server worked.

 

As it's not used that much I tried creating a new farm. The database is created by the configwizard and services start fine. But in the console once again the servers are offline.

 

Moved around the instances with my tests but keep ending up with these errors.

In all cases the services are all up and running but the eventlogs comes up with the: Undefined Database Error (11).

 

I have had the same setup in the past with SQL 2014 in W2K8R2 servers and PVS 7.7 without issues. So now I was wondering if I'm trying something thats not supported.

Reading through the Citrix documentation/blogs and forums this setup should be supported.

 

Firewalls are all checked and open.

 

Clustering is supported according to the docs:

https://docs.citrix.com/en-us/provisioning/7-12/system-requirements.html

 

SQL 2016 SP1 is supported:

https://support.citrix.com/article/CTX114501

 

Running out of ideas so hoping it rings a bell for someone here.

 



Harish A Citrix Employees

Harish A
  • 19 posts

Posted 14 February 2017 - 05:25 PM

Hello,

 

You can either try disabling TLS 1.2 on database server or you can try installing latest version of SQL Native Client on PVS servers post which you should be able to see PVS servers online on PVS Console

 

You can download latest version of Native Client from below link

 

https://www.microsoft.com/en-us/download/details.aspx?id=50402

 

Please let me know if this works for you!



mkoers Members

Mattheus Johannes Koers
  • 8 posts

Posted 14 February 2017 - 06:25 PM

Thank you for the link, did look for a native client for 2016 but 2012 is the latest one.

Did not think of checking the version  :rolleyes:

 

So downloaded, updated the servers.

Rebooted, no results the servers are still down.

It's the same error in the eventviewer.

 

One good point is that after pointing it to my originally moved database the status is just down and not with the extra unkown reason remark.



Harish A Citrix Employees

Harish A
  • 19 posts

Posted 14 February 2017 - 06:46 PM

Thanks for the update!

 

Can you try disabling TLS 1.2 on SQL Server

 

[HKLM\SYSTEM\CCS\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client]

"DisabledByDefault"=dword:00000001

"Enabled"=dword:0000000

 

[HKLM\SYSTEM\CCS\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server]

"DisabledByDefault"=dword:00000001

"Enabled"=dword:0000000

 

Once you make above changes, Re-run configuration wizard & test.

 

Please help me with SQL Native Client version installed on PVS Servers (Screen shot of installed programs) & also event ID 11 screen shot.

 

Thanks!



mkoers Members

Mattheus Johannes Koers
  • 8 posts

Posted 14 February 2017 - 08:34 PM

Added the settings for TLS.

 

[HKLM\SYSTEM\CCS\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client]

"DisabledByDefault"=dword:00000001

"Enabled"=dword:0000000

 

[HKLM\SYSTEM\CCS\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server]

"DisabledByDefault"=dword:00000001

"Enabled"=dword:0000000

 

Rebooted the noded but the cluster breaks due to this as nodes are not able to communicate, due to this running on a single node.

 

Reran the PVS wizard and the servers show online. So at least it helped on that level.

 

 

Next I removed the settings from the registry and fixed the cluster.

Rebooted both nodes once again.

 

Reran the wizard on both PVS servers connecting to the existing database.

Servers show online, but restarting services fails. So looks like the old stat they had in the BD

 

Rerans the wizard again creating a new farm.

Servers state is online but restarting services does not work.

 

Reverted back to the standalone SQL and it runs fine again.

 

 

- I must say I forgot to test the restarting of services by the console when I was running on a single cluster node.

 

-edit-

Checked, also failing.

Attached Thumbnails

  • PVS01.jpg
  • PVS02.jpg
  • Error.jpg
  • Error details.jpg
  • DATABASE Connection.jpg


mkoers Members

Mattheus Johannes Koers
  • 8 posts

Posted 20 February 2017 - 12:14 PM

Spend some time this weekend to find the cause / solution.

I cannot give an exact root cause but at least I got it up and running.

 

What did I do:

 

- Updated the SQL 2016 SP1 Cluster to the lastest patches

- Clean install of the PVS servers with Windows Server 2016 Standard + latest updates

- Clean install of the latest SQL 2012 Native client

- Clean install of PVS 7.12

- New database

 

TLS 1.2 is still enabled and the registry key mentioned before are NOT implemented.

 

Did a full test of PVS and everything functions as it's suposed to.

Services can be restarted, server states are live and so on.


Best Answer