build 7bbbddf7 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 267 | 0 skipped | | format
apiVersion: soultec.ch/v1kind: Postmetadata: name: unrecognized-requests-xml-api locale: en labels: author: raphael-thommen capability/modern-workplace: 2.11 capability/virtualization: 1.37 vendor/omnissa: 2.39 vendor/vmware: 0.88 annotations: source: blog-content/posts/en/unrecognized-requests-xml-api.md route: /en/insights/unrecognized-requests-xml-api/ schema: /nerd/schema/posts.json markdown: /en/insights/unrecognized-requests-xml-api.mdspec: title: Unrecognized requests in the Horizon Console XML API log date: 2024-09-14 author: raphael-thommen locale: en summary: >- The Horizon Console dashboard shows a warning about unrecognized requests on the XML API protocol connection. Usually these have no direct effect on user sessions. capabilities: [modern-workplace, virtualization] vendors: [omnissa, vmware] hero: /blog-assets/unrecognized-requests-xml-api/hero.webp migrated: 2026-08-24 translationReviewed: false draft: false sections: - body: | The Horizon Console dashboard shows a warning about unrecognized requests on the XML API protocol connection. These warnings normally have **no direct effect on user sessions**. A typical log entry on the Horizon Connection Server looks like this: `[ConnectionServerHandler] Incrementing the warning count : Reason : unrecognized request detected` #### **Worth knowing** - On **Horizon 2209 and 2212** these warnings are usually **false positives**. - From **2303** onwards they are worth looking into, to keep the user experience consistent. If session problems such as dropped connections do occur on older versions like 2209 or 2212, it is often a problem with the **load balancer persistence settings**. Requests then get sent to the wrong connection server. #### **Cause** These warnings appear when a user tries to connect to the connection server with an **expired session cookie**. #### **Solution** 1. **The Horizon feature "View Unrecognized Session Count"** Introduced in Horizon 2209, it shows harmless warnings on the dashboard. It lets administrators investigate dropped connections caused by unrecognized requests. 2. **Improvements in Horizon 2303 and later** From Horizon 2303 the error handling was extended. A typical log entry reads: `[EventLogger] Error_Event:[BROKER_DETECTED_UNRECOGNIZED_SESSIONS] "ConnectionServer MyBroker detected 2 unrecognized requests for XMLApi protocol connection` That means network traffic is not reaching the connection server it should. 1. **Investigating the load balancer** - Disable the load balancer temporarily to identify where the problem comes from. - For the recommended persistence settings, see [*Monitoring health of Horizon Connection Server using Load Balancer, timeout, Load Balancer persistence settings in Horizon 7.x and 8 (56636)*](https://kb.omnissa.com/s/article/56636). - Working with the load balancer vendor is worthwhile too. 2. **The client IP address changing** If the Horizon Client's incoming IP address changes during an authenticated session, that may be logged as an unrecognized request. #### **Conclusion** These warnings are often harmless, but if sessions drop repeatedly or behave unexpectedly, check the network traffic and the load balancer configuration. Horizon 2303 brings additional tooling for finding and fixing the cause.status: corpus: 267 alsoLike: - {ref: posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus, score: 1.00} - {ref: posts/ubersicht-omnissa-horizon-fur-citrix-kunden, score: 1.00} - {ref: solutions/omnissa/horizon/omnissa-app-volumes, score: 1.00}
{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "unrecognized-requests-xml-api", "locale": "en", "labels": { "author": "raphael-thommen", "capability/modern-workplace": "2.11", "capability/virtualization": "1.37", "vendor/omnissa": "2.39", "vendor/vmware": "0.88" }, "annotations": { "source": "blog-content/posts/en/unrecognized-requests-xml-api.md", "route": "/en/insights/unrecognized-requests-xml-api/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/unrecognized-requests-xml-api.md" } }, "spec": { "title": "Unrecognized requests in the Horizon Console XML API log", "date": "2024-09-14", "author": "raphael-thommen", "locale": "en", "summary": "The Horizon Console dashboard shows a warning about unrecognized requests on the XML API protocol connection. Usually these have no direct effect on user sessions.", "capabilities": [ "modern-workplace", "virtualization" ], "vendors": [ "omnissa", "vmware" ], "hero": "/blog-assets/unrecognized-requests-xml-api/hero.webp", "migrated": "2026-08-24", "translationReviewed": false, "draft": false }, "sections": [ { "body": "The Horizon Console dashboard shows a warning about unrecognized requests on the XML API protocol connection. These warnings normally have **no direct effect on user sessions**.\n\nA typical log entry on the Horizon Connection Server looks like this: \n`[ConnectionServerHandler] Incrementing the warning count : Reason : unrecognized request detected`\n\n#### **Worth knowing**\n\n- On **Horizon 2209 and 2212** these warnings are usually **false positives**.\n- From **2303** onwards they are worth looking into, to keep the user experience consistent.\n\nIf session problems such as dropped connections do occur on older versions like 2209 or 2212, it is often a problem with the **load balancer persistence settings**. Requests then get sent to the wrong connection server.\n\n#### **Cause**\n\nThese warnings appear when a user tries to connect to the connection server with an **expired session cookie**.\n\n#### **Solution**\n\n1. **The Horizon feature \"View Unrecognized Session Count\"** \n Introduced in Horizon 2209, it shows harmless warnings on the dashboard. It lets administrators investigate dropped connections caused by unrecognized requests.\n2. **Improvements in Horizon 2303 and later** \n From Horizon 2303 the error handling was extended. A typical log entry reads: \n `[EventLogger] Error_Event:[BROKER_DETECTED_UNRECOGNIZED_SESSIONS] \"ConnectionServer MyBroker detected 2 unrecognized requests for XMLApi protocol connection`\n\nThat means network traffic is not reaching the connection server it should.\n\n1. **Investigating the load balancer**\n - Disable the load balancer temporarily to identify where the problem comes from.\n - For the recommended persistence settings, see [*Monitoring health of Horizon Connection Server using Load Balancer, timeout, Load Balancer persistence settings in Horizon 7.x and 8 (56636)*](https://kb.omnissa.com/s/article/56636).\n - Working with the load balancer vendor is worthwhile too.\n2. **The client IP address changing** \n If the Horizon Client's incoming IP address changes during an authenticated session, that may be logged as an unrecognized request.\n\n#### **Conclusion**\n\nThese warnings are often harmless, but if sessions drop repeatedly or behave unexpectedly, check the network traffic and the load balancer configuration. Horizon 2303 brings additional tooling for finding and fixing the cause." } ], "status": { "corpus": 267, "alsoLike": [ { "ref": "posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus", "score": "1.00" }, { "ref": "posts/ubersicht-omnissa-horizon-fur-citrix-kunden", "score": "1.00" }, { "ref": "solutions/omnissa/horizon/omnissa-app-volumes", "score": "1.00" } ] }}
apiVersion = "soultec.ch/v1"kind = "Post"[metadata]name = "unrecognized-requests-xml-api"locale = "en"[metadata.labels]author = "raphael-thommen""capability/modern-workplace" = "2.11""capability/virtualization" = "1.37""vendor/omnissa" = "2.39""vendor/vmware" = "0.88"[metadata.annotations]source = "blog-content/posts/en/unrecognized-requests-xml-api.md"route = "/en/insights/unrecognized-requests-xml-api/"schema = "/nerd/schema/posts.json"markdown = "/en/insights/unrecognized-requests-xml-api.md"[spec]title = "Unrecognized requests in the Horizon Console XML API log"date = 2024-09-14author = "raphael-thommen"locale = "en"summary = "The Horizon Console dashboard shows a warning about unrecognized requests on the XML API protocol connection. Usually these have no direct effect on user sessions."capabilities = ["modern-workplace", "virtualization"]vendors = ["omnissa", "vmware"]hero = "/blog-assets/unrecognized-requests-xml-api/hero.webp"migrated = 2026-08-24translationReviewed = falsedraft = false[[sections]]body = '''The Horizon Console dashboard shows a warning about unrecognized requests on the XML API protocol connection. These warnings normally have **no direct effect on user sessions**.A typical log entry on the Horizon Connection Server looks like this: `[ConnectionServerHandler] Incrementing the warning count : Reason : unrecognized request detected`#### **Worth knowing**- On **Horizon 2209 and 2212** these warnings are usually **false positives**.- From **2303** onwards they are worth looking into, to keep the user experience consistent.If session problems such as dropped connections do occur on older versions like 2209 or 2212, it is often a problem with the **load balancer persistence settings**. Requests then get sent to the wrong connection server.#### **Cause**These warnings appear when a user tries to connect to the connection server with an **expired session cookie**.#### **Solution**1. **The Horizon feature "View Unrecognized Session Count"** Introduced in Horizon 2209, it shows harmless warnings on the dashboard. It lets administrators investigate dropped connections caused by unrecognized requests.2. **Improvements in Horizon 2303 and later** From Horizon 2303 the error handling was extended. A typical log entry reads: `[EventLogger] Error_Event:[BROKER_DETECTED_UNRECOGNIZED_SESSIONS] "ConnectionServer MyBroker detected 2 unrecognized requests for XMLApi protocol connection`That means network traffic is not reaching the connection server it should.1. **Investigating the load balancer** - Disable the load balancer temporarily to identify where the problem comes from. - For the recommended persistence settings, see [*Monitoring health of Horizon Connection Server using Load Balancer, timeout, Load Balancer persistence settings in Horizon 7.x and 8 (56636)*](https://kb.omnissa.com/s/article/56636). - Working with the load balancer vendor is worthwhile too.2. **The client IP address changing** If the Horizon Client's incoming IP address changes during an authenticated session, that may be logged as an unrecognized request.#### **Conclusion**These warnings are often harmless, but if sessions drop repeatedly or behave unexpectedly, check the network traffic and the load balancer configuration. Horizon 2303 brings additional tooling for finding and fixing the cause.'''[status]corpus = 267[[status.alsoLike]]ref = "posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus"score = "1.00"[[status.alsoLike]]ref = "posts/ubersicht-omnissa-horizon-fur-citrix-kunden"score = "1.00"[[status.alsoLike]]ref = "solutions/omnissa/horizon/omnissa-app-volumes"score = "1.00"
<?xml version="1.0" encoding="UTF-8"?><manifest kind="Post"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>unrecognized-requests-xml-api</name> <locale>en</locale> <labels> <author>raphael-thommen</author> <entry key="capability/modern-workplace">2.11</entry> <entry key="capability/virtualization">1.37</entry> <entry key="vendor/omnissa">2.39</entry> <entry key="vendor/vmware">0.88</entry> </labels> <annotations> <source>blog-content/posts/en/unrecognized-requests-xml-api.md</source> <route>/en/insights/unrecognized-requests-xml-api/</route> <schema>/nerd/schema/posts.json</schema> <markdown>/en/insights/unrecognized-requests-xml-api.md</markdown> </annotations> </metadata> <spec> <title>Unrecognized requests in the Horizon Console XML API log</title> <date>2024-09-14</date> <author>raphael-thommen</author> <locale>en</locale> <summary>The Horizon Console dashboard shows a warning about unrecognized requests on the XML API protocol connection. Usually these have no direct effect on user sessions.</summary> <capabilities> <item>modern-workplace</item> <item>virtualization</item> </capabilities> <vendors> <item>omnissa</item> <item>vmware</item> </vendors> <hero>/blog-assets/unrecognized-requests-xml-api/hero.webp</hero> <migrated>2026-08-24</migrated> <translationReviewed>false</translationReviewed> <draft>false</draft> </spec> <sections> <section> <body>The Horizon Console dashboard shows a warning about unrecognized requests on the XML API protocol connection. These warnings normally have **no direct effect on user sessions**.A typical log entry on the Horizon Connection Server looks like this: `[ConnectionServerHandler] Incrementing the warning count : Reason : unrecognized request detected`#### **Worth knowing**- On **Horizon 2209 and 2212** these warnings are usually **false positives**.- From **2303** onwards they are worth looking into, to keep the user experience consistent.If session problems such as dropped connections do occur on older versions like 2209 or 2212, it is often a problem with the **load balancer persistence settings**. Requests then get sent to the wrong connection server.#### **Cause**These warnings appear when a user tries to connect to the connection server with an **expired session cookie**.#### **Solution**1. **The Horizon feature "View Unrecognized Session Count"** Introduced in Horizon 2209, it shows harmless warnings on the dashboard. It lets administrators investigate dropped connections caused by unrecognized requests.2. **Improvements in Horizon 2303 and later** From Horizon 2303 the error handling was extended. A typical log entry reads: `[EventLogger] Error_Event:[BROKER_DETECTED_UNRECOGNIZED_SESSIONS] "ConnectionServer MyBroker detected 2 unrecognized requests for XMLApi protocol connection`That means network traffic is not reaching the connection server it should.1. **Investigating the load balancer** - Disable the load balancer temporarily to identify where the problem comes from. - For the recommended persistence settings, see [*Monitoring health of Horizon Connection Server using Load Balancer, timeout, Load Balancer persistence settings in Horizon 7.x and 8 (56636)*](https://kb.omnissa.com/s/article/56636). - Working with the load balancer vendor is worthwhile too.2. **The client IP address changing** If the Horizon Client's incoming IP address changes during an authenticated session, that may be logged as an unrecognized request.#### **Conclusion**These warnings are often harmless, but if sessions drop repeatedly or behave unexpectedly, check the network traffic and the load balancer configuration. Horizon 2303 brings additional tooling for finding and fixing the cause. </body> </section> </sections> <status> <corpus>267</corpus> <alsoLike> <item> <ref>posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus</ref> <score>1.00</score> </item> <item> <ref>posts/ubersicht-omnissa-horizon-fur-citrix-kunden</ref> <score>1.00</score> </item> <item> <ref>solutions/omnissa/horizon/omnissa-app-volumes</ref> <score>1.00</score> </item> </alsoLike> </status></manifest>
Post · 2024-09-14

Unrecognized requests in the Horizon Console XML API log

The Horizon Console dashboard shows a warning about unrecognized requests on the XML API protocol connection. Usually these have no direct effect on user sessions.

2024-09-14Date
Raphael ThommenAuthor
2Min read
Topics Modern Workplace 2.11 Virtualization 1.37
Vendors Omnissa 2.39 VMware 0.88

The Horizon Console dashboard shows a warning about unrecognized requests on the XML API protocol connection. These warnings normally have no direct effect on user sessions.

A typical log entry on the Horizon Connection Server looks like this:
[ConnectionServerHandler] Incrementing the warning count : Reason : unrecognized request detected

Worth knowing

  • On Horizon 2209 and 2212 these warnings are usually false positives.
  • From 2303 onwards they are worth looking into, to keep the user experience consistent.

If session problems such as dropped connections do occur on older versions like 2209 or 2212, it is often a problem with the load balancer persistence settings. Requests then get sent to the wrong connection server.

Cause

These warnings appear when a user tries to connect to the connection server with an expired session cookie.

Solution

  1. The Horizon feature “View Unrecognized Session Count”
    Introduced in Horizon 2209, it shows harmless warnings on the dashboard. It lets administrators investigate dropped connections caused by unrecognized requests.
  2. Improvements in Horizon 2303 and later
    From Horizon 2303 the error handling was extended. A typical log entry reads:
    [EventLogger] Error_Event:[BROKER_DETECTED_UNRECOGNIZED_SESSIONS] "ConnectionServer MyBroker detected 2 unrecognized requests for XMLApi protocol connection

That means network traffic is not reaching the connection server it should.

  1. Investigating the load balancer
  2. The client IP address changing
    If the Horizon Client’s incoming IP address changes during an authenticated session, that may be logged as an unrecognized request.

Conclusion

These warnings are often harmless, but if sessions drop repeatedly or behave unexpectedly, check the network traffic and the load balancer configuration. Horizon 2303 brings additional tooling for finding and fixing the cause.

You might also like