Problem with ExportToPdf on web servers

3 posts, 0 answers
  1. Lee
    Lee avatar
    5 posts
    Member since:
    Jul 2011

    Posted 22 May 2012 Link to this post

    Hi, the ExportToPdf function works fine in my local dev environment. However the moment i move it to any uat or prod server it fails with the error:

    System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it <IP ADDRESS>:80     at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)     at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)     at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)

    Everything else works find, the Radscheduler is bound to a sql data source and all works flawlessy. However i have been unable to determine why the above occurs on any webserver but not my local dev env. Is this a permissions thing? I am not sure what is occuring inside of ExportToPdf for this occur? I am assuming it just uses the same datasource as specified in DatasourceID that works fine elsewhere?  Any help would be greatly appreciated as the export to pdf is a big need for this project.
    Thanks

     

  2. Plamen
    Admin
    Plamen avatar
    2731 posts

    Posted 24 May 2012 Link to this post

    Hello Lee,

    This sounds like a quite unusual behavior. So far we are not aware what may be causing such error and how to deal with it and could not observe it locally or at our on-line Demo. It sounds like some deployment issue so I will recommend you to review our help topic about the PDF export and implement the suggestions from there. If it doesn't help please provide the exact code that will help us reproduce the issue and test it locally. 

    Please share any specific information about the server that you are using so we can make our tests more precisely. 

    Greetings,
    Plamen Zdravkov
    the Telerik team
    If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Ross Dunham
    Ross Dunham avatar
    11 posts
    Member since:
    Mar 2006

    Posted 27 Apr 2015 in reply to Lee Link to this post

    Hey Lee, 

    This is an old post but I am hoping you are still around ...

    I am having the same issue you described in the post.  Server is refusing connection on public, but works in development.  How did you resolve this?  I am having the same issue.  I opened a ticket with Telerik directly, but they don't have any suggestions on this one.  Thanks in advance.

Back to Top