Question : Protocol Driver Error - XenApp Plugin 11 with XenApp 5 on Windows 2008 x86

I am totally new to Citrix, but after reading hundreds and hundreds of pages of documentation I seem to have gotten the basics. I have a simple install:

XenApp 5 Advanced Edition, Access Management Console, Web Interface 5.01, Citrix License Server and Management Console, XenApp Advanced Configuration and Terminal Services Role running on just one Windows 2008 Server on a dual quad-core Dell PowerEdge 2950.

I got licenses successfully installed on the License Server and 25 TS Cals. Everything installed with no errors. I setup a XenApp Services and XenApp Web site in Web Interface 5.01. I have an SSL Certificate setup and port sharing with IIS on port 443. I am using XenApp Plugin 11.0.0.5357 on the same server. The firewall on the server is currently off.

I published the Calculator just to test my configuration. I have secure client access setup to Direct (for now while troubleshooting this issue). XenApp Plugin (via system tray running on the same server) successfully connects to the server and shows the Calculator as an application. When I attempt to run it is says "preparing to connect" then "connection in progress" then I get the "Calculator ERROR cannot connect to the XenApp Server Protocol Driver Error."

I get the same error when I try to connect from a different local machine. This server does not have Access Gateway (it didn't look like I needed it for my needs) or Secure Gateway installed. One strange thing I noticed was Password Manager was installed, but I won't use it and didn't ask for it to be installed, but I don't think that's related to this issue. No errors show up in the Event Viewer.

I've searched all over the place, but everything talks about Presentation Server 4.5, much older clients, etc. I haven't found much with this new setup. Anybody have any recommendations on how to troubleshoot and what to do?

Answer : Protocol Driver Error - XenApp Plugin 11 with XenApp 5 on Windows 2008 x86

Changing the XML Server Port as well as assigning the correct alternate external IP via altaddr solved the problem.

Note, there were directions on how to correctly change the XML Server from port sharing with IIS to it's own port in the XenApp Administrator's Guide on page 345. See below.

                       
         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:

           
           
             1. At a command prompt, stop IIS by typing: 
net stop w3svc 
2. Delete the following files from the IIS scripts directory on your Web server: 
" ctxadmin.dll 
" CtxConfProxy.dll 
" ctxsta.dll 
" radexml.dll 
" wpnbr.dll 
3. At a command prompt, restart IIS by typing: 
net start w3svc 
The XML Service no longer shares a port with IIS. 
4. To ensure the XML Service is stopped, at a command prompt, type: 
net stop ctxhttp 
5. At a command prompt, to unload the XML Service from memory, type: 
ctxxmlss /u 
6. To install the XML service, type: 
ctxxmlss /rnn 
where nn is the number of the port you want to use; for example, 
ctxxmlss /r88 forces the Citrix XML Service to use TCP/IP port 88. 
7. At a command prompt, stop the XML Service by typing: 
net stop ctxhttp

           
         

Open in New Window Select All