You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*['div' start tag on line 96 position 15 does not match the end tag of 'li'. Line 102, position 13.](#div-start-tag-on-line-96-position-15-does-not-match-the-end-tag-of-li-line-102-position-13)
22
21
23
-
Suggested solution:
22
+
*[System.SystemException: Error while creating area : Encountered web exception while fetching image from](#systemsystemexception-error-while-creating-area--encountered-web-exception-while-fetching-image-from)
24
23
25
-
The rendered scheduler output should be valid XHTML. If it is not, you will receive exceptions on export. The most common cause for bad XHTML are symbols like **<**,**>**,**&** that need to be replaced by the correct *XHTML* entity: **& l t ;**, **& g t ;**, **& a m p ;** respectively. Another frequent problem is unclosed tags.
24
+
*[System.ArgumentException: Parameter is not valid. at System.Drawing.Bitmap..ctor(Stream stream)](#systemargumentexception-parameter-is-not-valid-at-systemdrawingbitmapctorstream-stream)
26
25
27
-
*Problem:
26
+
*[An error occurred while parsing EntityName. Line 1246, position 58 or '' is an unexpected token.](#an-error-occurred-while-parsing-entityname-line-1246-position-58-or--is-an-unexpected-token)
28
27
29
-
**'div' start tag on line 96 position 15 does not match the end tag of 'li'. Line 102, position 13.**
28
+
*[System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host](#systemnetsocketssocketexception-an-existing-connection-was-forcibly-closed-by-the-remote-host)
30
29
31
-
Suggested solution:
32
30
33
-
Most likely it is caused by not closed html tags declared in scheduler templates for example.Please [validate](http://validator.w3.org/) the page output.
31
+
## Invalid XHTML Scheduler output
32
+
The rendered scheduler output should be valid XHTML. If it is not, you will receive exceptions on export. Here are some common causes for bad XHTML:
34
33
35
-
*Problem:
34
+
*Special symbols like `<`,`>`,`&`.
36
35
37
-
**System.SystemException: Error while creating area : Encountered web exception while fetching image from**
36
+
They should be replaced by the correct *XHTML* entity: `<`, `>`, `&`
The most probable cause of this issue is incorrect web resource handler registration when the Telerik.Web.UI.dll is referenced trough the GAC. For more details refer to the [General TroubleShooting help topic](http://www.telerik.com/help/aspnet-ajax/introduction-troubleshooting.html).
58
+
The most probable cause of this issue is incorrect web resource handler registration when the Telerik.Web.UI.dll is referenced trough the GAC. For more details refer to the [General TroubleShooting help topic](http://www.telerik.com/help/aspnet-ajax/introduction-troubleshooting.html).
50
59
51
-
* Problem:
60
+
## System.ArgumentException: Parameter is not valid. at System.Drawing.Bitmap..ctor(Stream stream)
52
61
53
-
**System.ArgumentException: Parameter is not valid. at System.Drawing.Bitmap..ctor(Stream stream) at Telerik.Web.Apoc.Image.ApocImage..ctor(String href, Byte[] imageData) at Telerik.Web.Apoc.Image.ApocImageFactory.Make(String href) at Telerik.Web.Apoc.Fo.Flow.ExternalGraphic.Layout(Area area) at Telerik.Web.Apoc.Fo.Flow.Block.Layout(Area area) at Telerik.Web.Apoc.Fo.Flow.Flow.Layout(Area area, Region region) at Telerik.Web.Apoc.Fo.Flow.Flow.Layout(Area area) at Telerik.Web.Apoc.Fo.Pagination.PageSequence.Format(AreaTree areaTree) at Telerik.Web.Apoc.StreamRenderer.Render(PageSequence pageSequence) at Telerik.Web.Apoc.Fo.FOTreeBuilder.EndElement() at Telerik.Web.Apoc.Fo.FOTreeBuilder.Parse(XmlReader reader)**
62
+
````StackTrace
63
+
System.ArgumentException: Parameter is not valid.
64
+
at System.Drawing.Bitmap..ctor(Stream stream)
65
+
at Telerik.Web.Apoc.Image.ApocImage..ctor(String href, Byte[] imageData)
66
+
at Telerik.Web.Apoc.Image.ApocImageFactory.Make(String href)
67
+
at Telerik.Web.Apoc.Fo.Flow.ExternalGraphic.Layout(Area area)
68
+
at Telerik.Web.Apoc.Fo.Flow.Block.Layout(Area area)
69
+
at Telerik.Web.Apoc.Fo.Flow.Flow.Layout(Area area, Region region)
70
+
at Telerik.Web.Apoc.Fo.Flow.Flow.Layout(Area area)
71
+
at Telerik.Web.Apoc.Fo.Pagination.PageSequence.Format(AreaTree areaTree)
72
+
at Telerik.Web.Apoc.StreamRenderer.Render(PageSequence pageSequence)
73
+
at Telerik.Web.Apoc.Fo.FOTreeBuilder.EndElement()
74
+
at Telerik.Web.Apoc.Fo.FOTreeBuilder.Parse(XmlReader reader)
75
+
````
54
76
55
-
Suggested solution:
77
+
This problem appears on export when the Telerik.Web.UI.dll is referenced trough the GAC and the assembly version is different from the WebResource.axd version registered in the web.config file. Please check you web.config for proper handler registration in the following section:
56
78
57
-
1. This problem appears on export when the Telerik.Web.UI.dll is referenced trough the GAC and the assembly version is different from the WebResource.axdversion registered in the web.config file. Please check you web.configfor proper handler registration in the following section:
Where [ASSEMBLY_VERSION] is the exact version of your Telerik.Web.UI.dll.
67
88
68
-
Where [ASSEMBLY_VERSION] is the exact version of your Telerik.Web.UI.dll.
69
-
70
-
2. If you are using Forms authentication please add the following section to your web.config file:
71
-
72
-
In case you are using RadScriptManager:
89
+
If you are using Forms authentication please add the following section to your web.config file:
73
90
74
-
**ASPNET**
91
+
- In case you are using **RadScriptManager**:
75
92
76
-
<location path="Telerik.Web.UI.WebResource.axd">
77
-
<system.web>
78
-
<authorization>
79
-
<allow users="?"/>
80
-
</authorization>
81
-
</system.web>
82
-
</location>
93
+
**web.config**
94
+
95
+
<location path="Telerik.Web.UI.WebResource.axd">
96
+
<system.web>
97
+
<authorization>
98
+
<allow users="?"/>
99
+
</authorization>
100
+
</system.web>
101
+
</location>
83
102
84
103
85
-
In case you are using asp:ScriptManager:
104
+
-In case you are using **asp:ScriptManager**:
86
105
87
-
**ASPNET**
106
+
**web.config**
107
+
108
+
<location path="WebResource.axd">
109
+
<system.web>
110
+
<authorization>
111
+
<allow users="?"/>
112
+
</authorization>
113
+
</system.web>
114
+
</location>
88
115
89
-
<location path="WebResource.axd">
90
-
<system.web>
91
-
<authorization>
92
-
<allow users="?"/>
93
-
</authorization>
94
-
</system.web>
95
-
</location>
96
116
117
+
## An error occurred while parsing EntityName. Line 1246, position 58 or '' is an unexpected token.
118
+
119
+
````ExceptionMessage
120
+
An error occurred while parsing EntityName.
121
+
Line 1246, position 58 or '' is an unexpected token.
122
+
The expected token is ';'. Line 131, position 10.
123
+
````
124
+
125
+
If special characters are used, replace them by valid HTML equivalents: `&` - `&`, `<` - `<`, `>` - `>`, etc.
126
+
127
+
You can use this article for reference - [Special Characters in HTML](http://www.degraeve.com/reference/specialcharacters.php).
128
+
129
+
130
+
## System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
131
+
<span></span>
132
+
### Description
133
+
134
+
Such problems are usually caused by an incorrectly configured server and some generic connection issues.
135
+
136
+
The Stack trace sometimes says that the GetStyleSheet method is failing. The said method only executes a standard HttpWebRequest. The observed error most probably is related to a general connection issue rather than an issue with the control itself.
137
+
138
+
Below you can find some exception messages that you might encounter:
139
+
140
+
### Exception messages
141
+
142
+
*[SocketException (0x2746): An existing connection was forcibly closed by the remote host]
143
+
144
+
**ExceptionMessage**
145
+
146
+
[SocketException (0x2746): An existing connection was forcibly closed by the remote host]
* System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
185
+
186
+
**ExceptionMessage**
187
+
188
+
System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
189
+
System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
190
+
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
191
+
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
192
+
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
193
+
at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
194
+
at System.Net.Security._SslStream.StartFrameHeader(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
195
+
at System.Net.Security._SslStream.StartReading(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
196
+
at System.Net.Security._SslStream.ProcessRead(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
197
+
at System.Net.TlsStream.Read(Byte[] buffer, Int32 offset, Int32 size)
198
+
at System.Net.PooledStream.Read(Byte[] buffer, Int32 offset, Int32 size)
199
+
at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead)
200
+
201
+
202
+
* A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
203
+
204
+
**ExceptionMessage**
205
+
206
+
A connection attempt failed because the connected party did not properly respond after a period of time,
207
+
or established connection failed because connected host has failed to respond 216.146.38.125:89
208
+
209
+
Description:
210
+
An unhandled exception occurred during the execution of the current web request.
211
+
Please review the stack trace for more information about the error and where it originated in the code.
212
+
213
+
Exception Details:
214
+
System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time,
215
+
or established connection failed because connected host has failed to respond 216.146.38.125:89
216
+
217
+
Source Error:
218
+
An unhandled exception was generated during the execution of the current web request.
219
+
Information regarding the origin and location of the exception can be identified using the exception stack trace below.
220
+
221
+
222
+
### Solutions:
97
223
98
-
* Problem:
224
+
* One possible solution would be using the ClientExportManager to export the Scheduler to PDF as demonstrated in the [Scheduler client PDF export with ClientExportManager](https://www.telerik.com/support/code-library/scheduler-client-pdf-export-with-clientexportmanager) Code Library project.
225
+
226
+
* To troubleshoot the GetStyleSheet method itself you can use the extracted logic outside the code of the Scheduler in a TestGetStyleSheet method.
0 commit comments