Link to home
Start Free TrialLog in
Avatar of rpassero
rpasseroFlag for United States of America

asked on

Citrix XML Service Bad Request

I am running XenApp on Windows Server 2003 (32-bit). My web interface was working fine until we applied Hotfix Rollup Pack 4 (we were previously running HR03); now all of a sudden some of my users receive the following error when trying to log in through it --

"The supplied credentials could not be validated. Either they are incorrect, or there is a problem with the authentication system. Try again, or contact your help desk or system administrator for help."

When this happens the following event is logged in the server's Application Log:

Event Type:      Error
Event Source:      Web Interface at c:\inetpub\wwwroot\Citrix\AccessPlatform
Event Category:      None
Event ID:      0
Date:            9/15/2009
Time:            9:53:48 AM
User:            N/A
Computer:      servername
Description:
The servers sent HTTP headers indicating that an error occurred: "400" "Bad Request".  This message was reported from the XML Service at address "http://servername:8080/scripts/wpnbr.dll [com.citrix.xml.NFuseProtocol.RequestAddress]".  This XML Service could not be contacted and will be temporarily removed from the list of active services. [Log ID: 17c7ab29]

Anyone have any ideas as to how to resolve this?
Avatar of rpassero
rpassero
Flag of United States of America image

ASKER

I've followed the instructions to unregister the service and tried to configure it to share the port with IIS (80) per http://support.citrix.com/article/CTX107683 but I still get the same results.
The problem seems to be that when I installed the new hotfix rollup package I also had to update the license server, which is now monopolizing port 8080. For some reason even though I've gone through the procedure listed above it's still looking on 8080 for the XML service, even after changing the port in CAMC and restarting the IMA. jad;flkja;dlfjkasdf....
SOLUTION
Avatar of BLipman
BLipman
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Ahh, perfect, so did it change throughout this process?  If you were set to "share with IIS/port 80" then I could see more potential for issues than if you started out with an alternate port.
It was originally set to not share - the WI was on :80 and the XML service was on :8080. After the hotfix install and license upgrade I got a very few users who got the message about a possible problem with the authentication system -- somehow there were only 5 users out of almost 250 employees and partners that use my system that were affected. They would get the error message, and the XML service error would be logged in my app log. I gave up on trying to find the real solution and just changed the port to share with IIS, but since I didn't change the port on the web interface farm settings it didn't fix the problem until I noticed that mistake.