Jump to content


Photo

LHC XD 7.12 and W2K8SR2 SP1

Started by Carsten Peukert , 04 January 2017 - 02:12 PM
LHC
3 replies to this topic

Best Answer Carsten Peukert , 06 January 2017 - 02:35 PM

I found the problem.

 

powershell v3 is required and the powershell ExecutionPolicy must set to RemoteSigned on the DDC.

Carsten Peukert Members

Carsten Peukert
  • 24 posts

Posted 04 January 2017 - 02:12 PM

I have installed XD 7.12 in an environment with only W2K8SR2 SP1 servers (SQL Server 2008 R2 SP2).

I activate the LHC feature. There was no 503/504/505 events in the eventlog and storefront show no applications in failure mode (EnableCssTraceMode=1).

 

The same configuration on a W2K12SR2 DDC in the same W2K8SR2 lab works. There are 503/504/505 entrys in the eventlog an the failover works.

 

Is there any limitation?

Work this feature on a DDC with W2K8SR2 SP1?

 

Thanks

Carsten Peukert

 



Sebastian Amrogowicz Citrix Employees

Sebastian Amrogowicz
  • 11 posts

Posted 06 January 2017 - 10:19 AM

Do you have powershell v3 or newer present on that machine?

 

Regards

Sebastian



Carsten Peukert Members

Carsten Peukert
  • 24 posts

Posted 06 January 2017 - 11:10 AM

I have install XD 7.12 on a fresh W2K8SR2 SP1 installation - LHC not work.

I have full fix the Server OS from MS - LHC not work.

I install PS v3.0 (Windows6.1-KB2506143-x64.msu) - LHC not work.

 

There are no 503/504/505 events in the application log.

 

OutageModeForced=1 was recognized, but Storefront says "no application available ..."

 

 

PS C:\> $PSVersionTable.PSVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
3      0      -1     -1


PS C:\> get-brokersite


BaseOU                                  :
BrokerServiceGroupUid                   : 53d22b32-a6de-4789-857d-31becb5d4794
ColorDepth                              : TwentyFourBit
ConfigLastChangeTime                    : 06.01.2017 11:52:53
ConfigurationServiceGroupUid            : 8cfadc4c-29d4-4b67-91c2-1032ae90994e
ConnectionLeasingEnabled                : False
DefaultMinimumFunctionalLevel           : L7_9
DesktopGroupIconUid                     : 1
DnsResolutionEnabled                    : False
IsSecondaryBroker                       : False
LicenseEdition                          : ENT
LicenseGraceSessionsRemaining           :
LicenseModel                            : Concurrent
LicenseServerName                       : srv-dc1
LicenseServerPort                       : 27000
LicensedSessionsActive                  : 0
LicensingBurnIn                         : 2016.1117
LicensingBurnInDate                     : 17.11.2016 01:00:00
LicensingGraceHoursLeft                 :
LicensingGracePeriodActive              : False
LicensingOutOfBoxGracePeriodActive      : False
LocalHostCacheEnabled                   : True
MetadataMap                             : {}
Name                                    : XD712
PeakConcurrentLicenseUsers              : 1
SecureIcaRequired                       : False
TotalUniqueLicenseUsers                 : 1
TrustManagedAnonymousXmlServiceRequests : False
TrustRequestsSentToTheXmlServicePort    : False
 

Information    06.01.2017 12:00:12    Citrix Broker Service    2003    None    The Citrix Broker Service successfully started XML services.
Information    06.01.2017 12:00:12    Citrix Broker Service    3500    None    The Citrix Broker Service has detected that the issue with communication with the database has been resolved and will resume normal brokering activity using configuration in the main site database.
Information    06.01.2017 12:00:12    Citrix High Availability Service    3503    None    The issue discovered with the normal brokering activity has been resolved, and the Citrix High Availability Service has now stopped participating in brokering user requests for sessions
Information    06.01.2017 11:59:52    Citrix Broker Service    2008    None    The Citrix Broker Service successfully stopped XML HTTP services.
Information    06.01.2017 11:59:52    Citrix Broker Service    2007    None    The Citrix Broker Service is stopping XML HTTP services.
Information    06.01.2017 11:59:52    Citrix Broker Service    3501    None    "The Citrix Broker Service has detected an issue with communication with the database. To preserve functionality, responsibility for brokering requests will be handed over to the Citrix High Availability Service using locally cached site configuration.
 
 



Carsten Peukert Members

Carsten Peukert
  • 24 posts

Posted 06 January 2017 - 02:35 PM

I found the problem.

 

powershell v3 is required and the powershell ExecutionPolicy must set to RemoteSigned on the DDC.


Best Answer