Jump to content
Software FX Community

Failed to download .NET charts


User (Legacy)

Recommended Posts

Hello,

In the past two months I have had several problems with the .NET Component:

Failed to download chart System.

Timeouts

ConnectFailure

None of these have been solved yet but everything seems to work fine on my

dev station, I only had a timeout once.

I'm using the latest ChartFX for .NET version: 6.0.1262.25350 running on a

Win2k Server SP3 and .NET Framework 1.0

Can you help me?

--

Regards,

Eric Garza, .NET MVP

AMIGE Project Manager

Link to comment
Share on other sites

We have been unable to reproduce this problem and can not determine the

cause for it. A failed connection seems to be the cause but without

reproducing it we can not be sure how to fix it.

We continue to research this issue and we will post something in our support

site when we find a solution/workaround.

--

FP

Software FX, Inc.

Link to comment
Share on other sites

  • 2 years later...

Hi,

I got the same problem. Using ChartFX .Net version 6.2.2211.* and .Net

Framework 1.1, running on Microsoft Windows 2000 server - sp4.

Have you come up with a solution?

Regards,

Lars

> We have been unable to reproduce this problem and can not determine the

> cause for it. A failed connection seems to be the cause but without

> reproducing it we can not be sure how to fix it.

>

> We continue to research this issue and we will post something in our support

> site when we find a solution/workaround.

>

Link to comment
Share on other sites

I do not know what this posting refers to. Can you please explain the 

problem.

--

Francisco Padron

www.chartfx.com

"Fosco Gamgee" <fosco.gamgee@gmail.com> wrote in message

news:cfMLQj3bGHA.1536@webserver3.softwarefx.com...

> Hi,

>

> I got the same problem. Using ChartFX .Net version 6.2.2211.* and .Net

> Framework 1.1, running on Microsoft Windows 2000 server - sp4.

>

> Have you come up with a solution?

>

> Regards,

> Lars

>

>

>

>

>> We have been unable to reproduce this problem and can not determine the

>> cause for it. A failed connection seems to be the cause but without

>> reproducing it we can not be sure how to fix it.

>>

>> We continue to research this issue and we will post something in our

>> support

>> site when we find a solution/workaround.

>>

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...