Untitled

1.Ensure GWHA is installed correctly and functioning.

When GroupWise 18.3 isinstalled on SLES12 and SLES 15, it will lay down gwha.socket andgwha@.service in/usr/lib/systemd/system.

SLES 12 is supporting bothxInetd and Systemd. You can still enable gwha using the NetworkServices. If you want to use Systemd to support gwha, you candisable the gwha through the Network Services.

To enable the GWHA on SLES 12and SLES 15 using systemd:

systemctl enablegwha.socket

This will create a symboliclink from /etc/system/system/sockets.target.wants to

gwha.socket in/usr/lib/system/system.This will enable gwha.socket started at the server reboot.

To start the gwha.socket atrun time,

systemctl startgwha.socket

systemctl status gwha.socketgives you the status of the gwha. gwha@.service will only be invokedwhen there is a connection to gwha port 8400 for action.

gwha reads in the/etc/opt/novell/groupwise/gwha.conf to manage the local GroupWiseagents.

To test if gwha isfunctioning as it should, do the following:

a.Create a user who you can use to log in to gwha.

e.g. useradd gwhauser

passwdgwhauser

( provide your password)

If you intend to have one gwmonitor to monitor agents on multipleservers, you need to have the same user and password created in allthese servers.

Steps to test gwhausing telnet:

telnet <ip address of yourserver or 127.0.0.1>8400

telnet 137.65.67.100 8400

Trying 137.65.67.100…

Connected to137.65.67.100.

Escape character is ‘^]’.

user:

Enter your gwha user name andpassword. If gwharejects your user name and password by displaying “bye”, you needto check these 3 things.

1.You have created valid user and its correct password.

2.Make sure PAM is installed on your server. Pluggable Authentication Modules (PAM) .

Make sure “Additional PAM modules” are installed on your SLES 15server. If they areinstalled, pam_unix.so and pam_unix2.so should be in/lib64/security.

3.Make sure you have added the created user to/etc/opt/novell/groupwise/gwha.allow

e.g.

# Uncomment or addthe local user(s) names that are allowed

# access to the gwhaservice to manage groupwise agents.

#

#gwhauser

Gwha

Once you can log in to gwha, you can do a few of these testing toverify your configuration.

user: gwha

password: novell

version: 1.0

000 Ok

e.g.

status <po>.<domain>

It should have returns such as

009 program is running

To end the telnet session, type quit.

Important notes:

If you started thegwha using network services or xInetd, gwha will be running asingle instance. Youneed to quit to exit the session, otherwise other session such asgwmonitor will not work.

If you started thegwha through systemd, gwha can run in multiple instances.

2.Configure gwmonitor.

Follow the detailedinstruction in GroupWise 2018 Installation guide to install thegwmonitor software and to configure.

There should be a start upgrpwise-ma in /etc/sysconfig, in which you can modify the monitoroptions. E.g.

# GroupWise monitoroptions

#

# To enable the GroupWiseHigh Availablilty service to allow the Monitor

# Agent to restart otherGroupWise agents, use the example line

# and provide a valid Linuxuser and password. The Linux user does not

# need any specificpermissions. The–hapoll option controls how often,

# in seconds, that theMonitor Agent polls to determine if an agent is running.

# You may also add otherMonitor Agent startup options to this variable.

# Example: –hauser username–hapassword password –hapoll 120

GROUPWISE_MA_OPTIONS=”–hauser gwha –hapassword novell –hapoll20″

There should be a monitor.xmlfile created in /opt/novell/groupwise/agents/share.

e.g.

<?xml version=”1.0″?>

<OPTIONS>

<FILE_VERSION value=”2″ upgrade_allowed=”1″ />

<HOME_MTA address=”137.65.67.104″ port=”7100″ />

<LANG value=”en” />

<HTTP>

<HTTP_POLL_CYCLE value=”300″ />

<HTTP_PORT value=”8200″ />

<HTTP_BROWSER_REFRESH value=”300″ />

<HTTP_NEW_BROWSER value=”0″ />

<HTTP_AUTHENTICATE value=”1″ />

<HTTP_USERvalue=”Z3c6Z3c=” />

<HTTP_POLL_USERvalue=”Z3c6Z3c=” />

<HTTP_SSL_REQUIRED value=”1″ />

<HTTP_SSL_CERT value=”/home/rtse/tools/sslcert/server.crt”/>

<HTTP_SSL_KEY value=”/home/rtse/tools/sslcert/server.key”/>

</HTTP>

<SNMP>

<SNMP_COMMUNITY value=”public” />

<SNMP_POLL_CYCLE value=”300″ />

<SNMP_NUM_RETRIES value=”2″ />

<SNMP_TIME_OUTvalue=”30″ />

<SNMP_FORCE_SNMP value=”0″ />

</SNMP>

<LOG>

<LOG_PATH path=”/var/log/novell/groupwise/gwmon” />

<LOG_DISK size=”5120″ age=”7″ />

<LOG_HISTORY size=”5120″ age=”7″ />

<LOG_ACCOUNTING size=”10240″ age=”7″ />

<LOG_ACCOUNTING_PATH path=”/var/log/novell/groupwise/gwmon/acct”/>

<LOG_EDITOR value=”” />

</LOG>

<NOTIFY>

<NOTIFY_LIST value=”” />

<NOTIFY_DOMAIN_NAME value=”” />

<NOTIFY_RELAY_ADDRESS value=”” />

<NOTIFY_SNMP_TRAP value=”FALSE” />

<NOTIFY_SNMP_TRAP_TARGET value=”” />

<NOTIFY_RESET value=”900″/>

<NOTIFY_OPTIONSvalue=”-1″ />

<NOTIFY_PERIODIC value=”0″ />

<NOTIFY_MIN_THRESHOLD value=”0″ />

</NOTIFY>

<TRACE>

<TRACE_LISTEN_PORT value=”0″ />

<TRACE_FREQUENCYvalue=”300″ />

<TRACE_AGENTSvalue=”FALSE” />

<TRACE_ACTIVEvalue=”FALSE” />

</TRACE>

<GROUPSexpanded=”FALSE” subgroup=”FALSE”>

</GROUPS>

</OPTIONS>

To start gwmonitor:

Rcgrpwise-ma start

Related:

  • No Related Posts

Untitled

1.Ensure GWHA is installed correctly and functioning.

When GroupWise 18.3 isinstalled on SLES12 and SLES 15, it will lay down gwha.socket andgwha@.service in/usr/lib/systemd/system.

SLES 12 is supporting bothxInetd and Systemd. You can still enable gwha using the NetworkServices. If you want to use Systemd to support gwha, you candisable the gwha through the Network Services.

To enable the GWHA on SLES 12and SLES 15 using systemd:

systemctl enablegwha.socket

This will create a symboliclink from /etc/system/system/sockets.target.wants to

gwha.socket in/usr/lib/system/system.This will enable gwha.socket started at the server reboot.

To start the gwha.socket atrun time,

systemctl startgwha.socket

systemctl status gwha.socketgives you the status of the gwha. gwha@.service will only be invokedwhen there is a connection to gwha port 8400 for action.

gwha reads in the/etc/opt/novell/groupwise/gwha.conf to manage the local GroupWiseagents.

To test if gwha isfunctioning as it should, do the following:

a.Create a user who you can use to log in to gwha.

e.g. useradd gwhauser

passwdgwhauser

( provide your password)

If you intend to have one gwmonitor to monitor agents on multipleservers, you need to have the same user and password created in allthese servers.

Steps to test gwhausing telnet:

telnet <ip address of yourserver or 127.0.0.1>8400

telnet 137.65.67.100 8400

Trying 137.65.67.100…

Connected to137.65.67.100.

Escape character is ‘^]’.

user:

Enter your gwha user name andpassword. If gwharejects your user name and password by displaying “bye”, you needto check these 3 things.

1.You have created valid user and its correct password.

2.Make sure PAM is installed on your server. Pluggable Authentication Modules (PAM) .

Make sure “Additional PAM modules” are installed on your SLES 15server. If they areinstalled, pam_unix.so and pam_unix2.so should be in/lib64/security.

3.Make sure you have added the created user to/etc/opt/novell/groupwise/gwha.allow

e.g.

# Uncomment or addthe local user(s) names that are allowed

# access to the gwhaservice to manage groupwise agents.

#

#gwhauser

Gwha

Once you can log in to gwha, you can do a few of these testing toverify your configuration.

user: gwha

password: novell

version: 1.0

000 Ok

e.g.

status <po>.<domain>

It should have returns such as

009 program is running

To end the telnet session, type quit.

Important notes:

If you started thegwha using network services or xInetd, gwha will be running asingle instance. Youneed to quit to exit the session, otherwise other session such asgwmonitor will not work.

If you started thegwha through systemd, gwha can run in multiple instances.

2.Configure gwmonitor.

Follow the detailedinstruction in GroupWise 2018 Installation guide to install thegwmonitor software and to configure.

There should be a start upgrpwise-ma in /etc/sysconfig, in which you can modify the monitoroptions. E.g.

# GroupWise monitoroptions

#

# To enable the GroupWiseHigh Availablilty service to allow the Monitor

# Agent to restart otherGroupWise agents, use the example line

# and provide a valid Linuxuser and password. The Linux user does not

# need any specificpermissions. The–hapoll option controls how often,

# in seconds, that theMonitor Agent polls to determine if an agent is running.

# You may also add otherMonitor Agent startup options to this variable.

# Example: –hauser username–hapassword password –hapoll 120

GROUPWISE_MA_OPTIONS=”–hauser gwha –hapassword novell –hapoll20″

There should be a monitor.xmlfile created in /opt/novell/groupwise/agents/share.

e.g.

<?xml version=”1.0″?>

<OPTIONS>

<FILE_VERSION value=”2″ upgrade_allowed=”1″ />

<HOME_MTA address=”137.65.67.104″ port=”7100″ />

<LANG value=”en” />

<HTTP>

<HTTP_POLL_CYCLE value=”300″ />

<HTTP_PORT value=”8200″ />

<HTTP_BROWSER_REFRESH value=”300″ />

<HTTP_NEW_BROWSER value=”0″ />

<HTTP_AUTHENTICATE value=”1″ />

<HTTP_USERvalue=”Z3c6Z3c=” />

<HTTP_POLL_USERvalue=”Z3c6Z3c=” />

<HTTP_SSL_REQUIRED value=”1″ />

<HTTP_SSL_CERT value=”/home/rtse/tools/sslcert/server.crt”/>

<HTTP_SSL_KEY value=”/home/rtse/tools/sslcert/server.key”/>

</HTTP>

<SNMP>

<SNMP_COMMUNITY value=”public” />

<SNMP_POLL_CYCLE value=”300″ />

<SNMP_NUM_RETRIES value=”2″ />

<SNMP_TIME_OUTvalue=”30″ />

<SNMP_FORCE_SNMP value=”0″ />

</SNMP>

<LOG>

<LOG_PATH path=”/var/log/novell/groupwise/gwmon” />

<LOG_DISK size=”5120″ age=”7″ />

<LOG_HISTORY size=”5120″ age=”7″ />

<LOG_ACCOUNTING size=”10240″ age=”7″ />

<LOG_ACCOUNTING_PATH path=”/var/log/novell/groupwise/gwmon/acct”/>

<LOG_EDITOR value=”” />

</LOG>

<NOTIFY>

<NOTIFY_LIST value=”” />

<NOTIFY_DOMAIN_NAME value=”” />

<NOTIFY_RELAY_ADDRESS value=”” />

<NOTIFY_SNMP_TRAP value=”FALSE” />

<NOTIFY_SNMP_TRAP_TARGET value=”” />

<NOTIFY_RESET value=”900″/>

<NOTIFY_OPTIONSvalue=”-1″ />

<NOTIFY_PERIODIC value=”0″ />

<NOTIFY_MIN_THRESHOLD value=”0″ />

</NOTIFY>

<TRACE>

<TRACE_LISTEN_PORT value=”0″ />

<TRACE_FREQUENCYvalue=”300″ />

<TRACE_AGENTSvalue=”FALSE” />

<TRACE_ACTIVEvalue=”FALSE” />

</TRACE>

<GROUPSexpanded=”FALSE” subgroup=”FALSE”>

</GROUPS>

</OPTIONS>

To start gwmonitor:

Rcgrpwise-ma start

Related:

  • No Related Posts

Untitled

1.Ensure GWHA is installed correctly and functioning.

When GroupWise 18.3 isinstalled on SLES12 and SLES 15, it will lay down gwha.socket andgwha@.service in/usr/lib/systemd/system.

SLES 12 is supporting bothxInetd and Systemd. You can still enable gwha using the NetworkServices. If you want to use Systemd to support gwha, you candisable the gwha through the Network Services.

To enable the GWHA on SLES 12and SLES 15 using systemd:

systemctl enablegwha.socket

This will create a symboliclink from /etc/system/system/sockets.target.wants to

gwha.socket in/usr/lib/system/system.This will enable gwha.socket started at the server reboot.

To start the gwha.socket atrun time,

systemctl startgwha.socket

systemctl status gwha.socketgives you the status of the gwha. gwha@.service will only be invokedwhen there is a connection to gwha port 8400 for action.

gwha reads in the/etc/opt/novell/groupwise/gwha.conf to manage the local GroupWiseagents.

To test if gwha isfunctioning as it should, do the following:

a.Create a user who you can use to log in to gwha.

e.g. useradd gwhauser

passwdgwhauser

( provide your password)

If you intend to have one gwmonitor to monitor agents on multipleservers, you need to have the same user and password created in allthese servers.

Steps to test gwhausing telnet:

telnet <ip address of yourserver or 127.0.0.1>8400

telnet 137.65.67.100 8400

Trying 137.65.67.100…

Connected to137.65.67.100.

Escape character is ‘^]’.

user:

Enter your gwha user name andpassword. If gwharejects your user name and password by displaying “bye”, you needto check these 3 things.

1.You have created valid user and its correct password.

2.Make sure PAM is installed on your server. Pluggable Authentication Modules (PAM) .

Make sure “Additional PAM modules” are installed on your SLES 15server. If they areinstalled, pam_unix.so and pam_unix2.so should be in/lib64/security.

3.Make sure you have added the created user to/etc/opt/novell/groupwise/gwha.allow

e.g.

# Uncomment or addthe local user(s) names that are allowed

# access to the gwhaservice to manage groupwise agents.

#

#gwhauser

Gwha

Once you can log in to gwha, you can do a few of these testing toverify your configuration.

user: gwha

password: novell

version: 1.0

000 Ok

e.g.

status <po>.<domain>

It should have returns such as

009 program is running

To end the telnet session, type quit.

Important notes:

If you started thegwha using network services or xInetd, gwha will be running asingle instance. Youneed to quit to exit the session, otherwise other session such asgwmonitor will not work.

If you started thegwha through systemd, gwha can run in multiple instances.

2.Configure gwmonitor.

Follow the detailedinstruction in GroupWise 2018 Installation guide to install thegwmonitor software and to configure.

There should be a start upgrpwise-ma in /etc/sysconfig, in which you can modify the monitoroptions. E.g.

# GroupWise monitoroptions

#

# To enable the GroupWiseHigh Availablilty service to allow the Monitor

# Agent to restart otherGroupWise agents, use the example line

# and provide a valid Linuxuser and password. The Linux user does not

# need any specificpermissions. The–hapoll option controls how often,

# in seconds, that theMonitor Agent polls to determine if an agent is running.

# You may also add otherMonitor Agent startup options to this variable.

# Example: –hauser username–hapassword password –hapoll 120

GROUPWISE_MA_OPTIONS=”–hauser gwha –hapassword novell –hapoll20″

There should be a monitor.xmlfile created in /opt/novell/groupwise/agents/share.

e.g.

<?xml version=”1.0″?>

<OPTIONS>

<FILE_VERSION value=”2″ upgrade_allowed=”1″ />

<HOME_MTA address=”137.65.67.104″ port=”7100″ />

<LANG value=”en” />

<HTTP>

<HTTP_POLL_CYCLE value=”300″ />

<HTTP_PORT value=”8200″ />

<HTTP_BROWSER_REFRESH value=”300″ />

<HTTP_NEW_BROWSER value=”0″ />

<HTTP_AUTHENTICATE value=”1″ />

<HTTP_USERvalue=”Z3c6Z3c=” />

<HTTP_POLL_USERvalue=”Z3c6Z3c=” />

<HTTP_SSL_REQUIRED value=”1″ />

<HTTP_SSL_CERT value=”/home/rtse/tools/sslcert/server.crt”/>

<HTTP_SSL_KEY value=”/home/rtse/tools/sslcert/server.key”/>

</HTTP>

<SNMP>

<SNMP_COMMUNITY value=”public” />

<SNMP_POLL_CYCLE value=”300″ />

<SNMP_NUM_RETRIES value=”2″ />

<SNMP_TIME_OUTvalue=”30″ />

<SNMP_FORCE_SNMP value=”0″ />

</SNMP>

<LOG>

<LOG_PATH path=”/var/log/novell/groupwise/gwmon” />

<LOG_DISK size=”5120″ age=”7″ />

<LOG_HISTORY size=”5120″ age=”7″ />

<LOG_ACCOUNTING size=”10240″ age=”7″ />

<LOG_ACCOUNTING_PATH path=”/var/log/novell/groupwise/gwmon/acct”/>

<LOG_EDITOR value=”” />

</LOG>

<NOTIFY>

<NOTIFY_LIST value=”” />

<NOTIFY_DOMAIN_NAME value=”” />

<NOTIFY_RELAY_ADDRESS value=”” />

<NOTIFY_SNMP_TRAP value=”FALSE” />

<NOTIFY_SNMP_TRAP_TARGET value=”” />

<NOTIFY_RESET value=”900″/>

<NOTIFY_OPTIONSvalue=”-1″ />

<NOTIFY_PERIODIC value=”0″ />

<NOTIFY_MIN_THRESHOLD value=”0″ />

</NOTIFY>

<TRACE>

<TRACE_LISTEN_PORT value=”0″ />

<TRACE_FREQUENCYvalue=”300″ />

<TRACE_AGENTSvalue=”FALSE” />

<TRACE_ACTIVEvalue=”FALSE” />

</TRACE>

<GROUPSexpanded=”FALSE” subgroup=”FALSE”>

</GROUPS>

</OPTIONS>

To start gwmonitor:

Rcgrpwise-ma start

Related:

  • No Related Posts

Untitled

1.Ensure GWHA is installed correctly and functioning.

When GroupWise 18.3 isinstalled on SLES12 and SLES 15, it will lay down gwha.socket andgwha@.service in/usr/lib/systemd/system.

SLES 12 is supporting bothxInetd and Systemd. You can still enable gwha using the NetworkServices. If you want to use Systemd to support gwha, you candisable the gwha through the Network Services.

To enable the GWHA on SLES 12and SLES 15 using systemd:

systemctl enablegwha.socket

This will create a symboliclink from /etc/system/system/sockets.target.wants to

gwha.socket in/usr/lib/system/system.This will enable gwha.socket started at the server reboot.

To start the gwha.socket atrun time,

systemctl startgwha.socket

systemctl status gwha.socketgives you the status of the gwha. gwha@.service will only be invokedwhen there is a connection to gwha port 8400 for action.

gwha reads in the/etc/opt/novell/groupwise/gwha.conf to manage the local GroupWiseagents.

To test if gwha isfunctioning as it should, do the following:

a.Create a user who you can use to log in to gwha.

e.g. useradd gwhauser

passwdgwhauser

( provide your password)

If you intend to have one gwmonitor to monitor agents on multipleservers, you need to have the same user and password created in allthese servers.

Steps to test gwhausing telnet:

telnet <ip address of yourserver or 127.0.0.1>8400

telnet 137.65.67.100 8400

Trying 137.65.67.100…

Connected to137.65.67.100.

Escape character is ‘^]’.

user:

Enter your gwha user name andpassword. If gwharejects your user name and password by displaying “bye”, you needto check these 3 things.

1.You have created valid user and its correct password.

2.Make sure PAM is installed on your server. Pluggable Authentication Modules (PAM) .

Make sure “Additional PAM modules” are installed on your SLES 15server. If they areinstalled, pam_unix.so and pam_unix2.so should be in/lib64/security.

3.Make sure you have added the created user to/etc/opt/novell/groupwise/gwha.allow

e.g.

# Uncomment or addthe local user(s) names that are allowed

# access to the gwhaservice to manage groupwise agents.

#

#gwhauser

Gwha

Once you can log in to gwha, you can do a few of these testing toverify your configuration.

user: gwha

password: novell

version: 1.0

000 Ok

e.g.

status <po>.<domain>

It should have returns such as

009 program is running

To end the telnet session, type quit.

Important notes:

If you started thegwha using network services or xInetd, gwha will be running asingle instance. Youneed to quit to exit the session, otherwise other session such asgwmonitor will not work.

If you started thegwha through systemd, gwha can run in multiple instances.

2.Configure gwmonitor.

Follow the detailedinstruction in GroupWise 2018 Installation guide to install thegwmonitor software and to configure.

There should be a start upgrpwise-ma in /etc/sysconfig, in which you can modify the monitoroptions. E.g.

# GroupWise monitoroptions

#

# To enable the GroupWiseHigh Availablilty service to allow the Monitor

# Agent to restart otherGroupWise agents, use the example line

# and provide a valid Linuxuser and password. The Linux user does not

# need any specificpermissions. The–hapoll option controls how often,

# in seconds, that theMonitor Agent polls to determine if an agent is running.

# You may also add otherMonitor Agent startup options to this variable.

# Example: –hauser username–hapassword password –hapoll 120

GROUPWISE_MA_OPTIONS=”–hauser gwha –hapassword novell –hapoll20″

There should be a monitor.xmlfile created in /opt/novell/groupwise/agents/share.

e.g.

<?xml version=”1.0″?>

<OPTIONS>

<FILE_VERSION value=”2″ upgrade_allowed=”1″ />

<HOME_MTA address=”137.65.67.104″ port=”7100″ />

<LANG value=”en” />

<HTTP>

<HTTP_POLL_CYCLE value=”300″ />

<HTTP_PORT value=”8200″ />

<HTTP_BROWSER_REFRESH value=”300″ />

<HTTP_NEW_BROWSER value=”0″ />

<HTTP_AUTHENTICATE value=”1″ />

<HTTP_USERvalue=”Z3c6Z3c=” />

<HTTP_POLL_USERvalue=”Z3c6Z3c=” />

<HTTP_SSL_REQUIRED value=”1″ />

<HTTP_SSL_CERT value=”/home/rtse/tools/sslcert/server.crt”/>

<HTTP_SSL_KEY value=”/home/rtse/tools/sslcert/server.key”/>

</HTTP>

<SNMP>

<SNMP_COMMUNITY value=”public” />

<SNMP_POLL_CYCLE value=”300″ />

<SNMP_NUM_RETRIES value=”2″ />

<SNMP_TIME_OUTvalue=”30″ />

<SNMP_FORCE_SNMP value=”0″ />

</SNMP>

<LOG>

<LOG_PATH path=”/var/log/novell/groupwise/gwmon” />

<LOG_DISK size=”5120″ age=”7″ />

<LOG_HISTORY size=”5120″ age=”7″ />

<LOG_ACCOUNTING size=”10240″ age=”7″ />

<LOG_ACCOUNTING_PATH path=”/var/log/novell/groupwise/gwmon/acct”/>

<LOG_EDITOR value=”” />

</LOG>

<NOTIFY>

<NOTIFY_LIST value=”” />

<NOTIFY_DOMAIN_NAME value=”” />

<NOTIFY_RELAY_ADDRESS value=”” />

<NOTIFY_SNMP_TRAP value=”FALSE” />

<NOTIFY_SNMP_TRAP_TARGET value=”” />

<NOTIFY_RESET value=”900″/>

<NOTIFY_OPTIONSvalue=”-1″ />

<NOTIFY_PERIODIC value=”0″ />

<NOTIFY_MIN_THRESHOLD value=”0″ />

</NOTIFY>

<TRACE>

<TRACE_LISTEN_PORT value=”0″ />

<TRACE_FREQUENCYvalue=”300″ />

<TRACE_AGENTSvalue=”FALSE” />

<TRACE_ACTIVEvalue=”FALSE” />

</TRACE>

<GROUPSexpanded=”FALSE” subgroup=”FALSE”>

</GROUPS>

</OPTIONS>

To start gwmonitor:

Rcgrpwise-ma start

Related:

  • No Related Posts

Error: “There is no Citrix Xenapp server configured on the specified address” during app launch through Netscaler Gateway

On Storefront server open web.config for the store from C:inetpubwwwrootcitrix<StoreName> in notepad as an administrator on storefront server

Search for optimal gateway. You will see following parameters.

User-added image

Remove the part from <clear /> to </optimalgatewayForFarmsCollection>

Change the 1st line to “<optimalGatewayForFarmsCollection>” by adding ‘/’ before ‘>’ :::: “<optimalGatewayForFarmsCollection />”

Save the file and run IISRESET in command prompt as an administrator.

Test the application launch.

Related:

  • No Related Posts

Error: “There is no Citrix Xenapp server configured on the specified address” during app launch through Netscaler Gateway

On Storefront server open web.config for the store from C:inetpubwwwrootcitrix<StoreName> in notepad as an administrator on storefront server

Search for optimal gateway. You will see following parameters.

User-added image

Remove the part from <clear /> to </optimalgatewayForFarmsCollection>

Change the 1st line to “<optimalGatewayForFarmsCollection>” by adding ‘/’ before ‘>’ :::: “<optimalGatewayForFarmsCollection />”

Save the file and run IISRESET in command prompt as an administrator.

Test the application launch.

Related:

  • No Related Posts

Error: “There is no Citrix Xenapp server configured on the specified address” during app launch through Netscaler Gateway

On Storefront server open web.config for the store from C:inetpubwwwrootcitrix<StoreName> in notepad as an administrator on storefront server

Search for optimal gateway. You will see following parameters.

User-added image

Remove the part from <clear /> to </optimalgatewayForFarmsCollection>

Change the 1st line to “<optimalGatewayForFarmsCollection>” by adding ‘/’ before ‘>’ :::: “<optimalGatewayForFarmsCollection />”

Save the file and run IISRESET in command prompt as an administrator.

Test the application launch.

Related:

  • No Related Posts

Error: “There is no Citrix Xenapp server configured on the specified address” during app launch through Netscaler Gateway

On Storefront server open web.config for the store from C:inetpubwwwrootcitrix<StoreName> in notepad as an administrator on storefront server

Search for optimal gateway. You will see following parameters.

User-added image

Remove the part from <clear /> to </optimalgatewayForFarmsCollection>

Change the 1st line to “<optimalGatewayForFarmsCollection>” by adding ‘/’ before ‘>’ :::: “<optimalGatewayForFarmsCollection />”

Save the file and run IISRESET in command prompt as an administrator.

Test the application launch.

Related:

  • No Related Posts

Error: “There is no Citrix Xenapp server configured on the specified address” during app launch through Netscaler Gateway

On Storefront server open web.config for the store from C:inetpubwwwrootcitrix<StoreName> in notepad as an administrator on storefront server

Search for optimal gateway. You will see following parameters.

User-added image

Remove the part from <clear /> to </optimalgatewayForFarmsCollection>

Change the 1st line to “<optimalGatewayForFarmsCollection>” by adding ‘/’ before ‘>’ :::: “<optimalGatewayForFarmsCollection />”

Save the file and run IISRESET in command prompt as an administrator.

Test the application launch.

Related:

  • No Related Posts