User (Legacy) Posted December 8, 2003 Report Share Posted December 8, 2003 Hi, We're just testing using Chartfx.net 62 on a windows 2003 server and have had some issues -- some we've been able to get around others not and hoping you can help with the one we cant work out. Firstly when we install the development install (ie no the production) on the server it doesnt create a virtual folder for ChartFX62 -- this means that downloading the client side components is a problem. We tried creating a virtual folder point to the \Program Files\etc folder but this didnt work despite playing with permissions etc. We finally created a virutal folder with the same name under wwwroot (removed the one pointing to \Program Files\etc first of course) and copied the stuff over to these folders from \Program Files\etc and that seems to have help and the client side component at least now shows. However that all aside when the component tries to show the chart it comes up with "Failed to download Chart Protocol Error - Not Found (404)" The chart is created and I can in fact view it by placing a link in a browser but obviously there is some issue I cant determine. Any ideas? James Link to comment Share on other sites More sharing options...
Software FX Posted December 9, 2003 Report Share Posted December 9, 2003 Did a file got created in the chartfx62\temp folder ? If so, and the DataPath seems to point to the right file (e.g. \chartfx62\temp\tempfilename) you may be experiencing a new behavior win Windows Server 2003 where IIS will only serve files with a recognized extension. This is what you have to do - Internet Information Service Manager - Right click "Default Web Site" and select properties - HTTP Headers page - Click on the "MIME Types" button - Click new - Set the extension to chw and the mime type to "application/octet-stream" - OK ... Even after working around this issue I would recommend you try to se your vroot back to \Program Files\ChartFX for .NET 6.2\chartfx62, this is because if you install a service pack we will update these files but not the ones under your wwwroot folder. -- Regards, JC Software FX Support "James Beauchamp" <jamesbeauchamp@replacewithcompany.com.au> wrote in message news:aFab1pUvDHA.3808@WEBSERVER1... > Hi, > We're just testing using Chartfx.net 62 on a windows 2003 server and have > had some issues -- some we've been able to get around others not and hoping > you can help with the one we cant work out. > > Firstly when we install the development install (ie no the production) on > the server it doesnt create a virtual folder for ChartFX62 -- this means > that downloading the client side components is a problem. We tried creating > a virtual folder point to the \Program Files\etc folder but this didnt work > despite playing with permissions etc. > > We finally created a virutal folder with the same name under wwwroot > (removed the one pointing to \Program Files\etc first of course) and copied > the stuff over to these folders from \Program Files\etc and that seems to > have help and the client side component at least now shows. > > However that all aside when the component tries to show the chart it comes > up with "Failed to download Chart Protocol Error - Not Found (404)" > > The chart is created and I can in fact view it by placing a link in a > browser but obviously there is some issue I cant determine. > > Any ideas? > > James > > Link to comment Share on other sites More sharing options...
User (Legacy) Posted December 10, 2003 Author Report Share Posted December 10, 2003 Thanks JC, Excellent it now works -- not sure if that was the precise solution as had been trying some other things too but hey it now works so we move forward., Thx James "SoftwareFX Support" <support@softwarefx.com> wrote in message news:r7Oq44lvDHA.3512@WEBSERVER1... > Did a file got created in the chartfx62\temp folder ? If so, and the > DataPath seems to point to the right file (e.g. > \chartfx62\temp\tempfilename) you may be experiencing a new behavior win > Windows Server 2003 where IIS will only serve files with a recognized > extension. This is what you have to do > > - Internet Information Service Manager > - Right click "Default Web Site" and select properties > - HTTP Headers page > - Click on the "MIME Types" button > - Click new > - Set the extension to chw and the mime type to "application/octet-stream" > - OK ... > > Even after working around this issue I would recommend you try to se your > vroot back to \Program Files\ChartFX for .NET 6.2\chartfx62, this is because > if you install a service pack we will update these files but not the ones > under your wwwroot folder. > > -- > Regards, > > JC > Software FX Support > "James Beauchamp" <jamesbeauchamp@replacewithcompany.com.au> wrote in > message news:aFab1pUvDHA.3808@WEBSERVER1... > > Hi, > > We're just testing using Chartfx.net 62 on a windows 2003 server and have > > had some issues -- some we've been able to get around others not and > hoping > > you can help with the one we cant work out. > > > > Firstly when we install the development install (ie no the production) on > > the server it doesnt create a virtual folder for ChartFX62 -- this means > > that downloading the client side components is a problem. We tried > creating > > a virtual folder point to the \Program Files\etc folder but this didnt > work > > despite playing with permissions etc. > > > > We finally created a virutal folder with the same name under wwwroot > > (removed the one pointing to \Program Files\etc first of course) and > copied > > the stuff over to these folders from \Program Files\etc and that seems to > > have help and the client side component at least now shows. > > > > However that all aside when the component tries to show the chart it comes > > up with "Failed to download Chart Protocol Error - Not Found (404)" > > > > The chart is created and I can in fact view it by placing a link in a > > browser but obviously there is some issue I cant determine. > > > > Any ideas? > > > > James > > > > > > Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.