unable to start the ORM profiler

4 posts, 0 answers
  1. Henk
    Henk avatar
    113 posts
    Member since:
    Apr 2006

    Posted 22 Jan 2014 Link to this post

    I used the latest ORM, vs2013 with win7 and try to used the profiler and follow the instructions "How to: Configure OpenAccess Project For Real-Time Monitoring"

    The project is an asp,net ajax application; 2 IIS express are running ( a service app on port 2350) and the web application on 15000
    The port for profiling is 15555.  After succesfully login in the application I try to start the profiler with server: localhost, port: 15555, and connection: MHVConnectionString the same name as in the web.config file of the web application:
     the string in the web.config: <add name="MHVConnectionString" connectionString="data source=HENK-ASUS\SQLEXPRESS;initial catalog=MHVDB....
    But the test connection button generate an error: Test Connection failed"

    Any idea what the reason is of the error?

    Thanks,

    error:

    Telerik.OpenAccess.Exceptions.ConfigurationException: Server did not accept communication, maybe the server runs an older OpenAccess version. You have to use the same OpenAccess version on both sides. (Client: 2 / 2013.3.1211.3) ---> System.ServiceModel.EndpointNotFoundException: Kan geen verbinding maken met net.tcp://localhost:15555/ServerTasks. De poging verbinding te maken heeft 00:00:00.9960570 geduurd. TCP-foutcode 10061: Kan geen verbinding maken omdat de doelcomputer de verbinding actief heeft geweigerd 127.0.0.1:15555.  ---> System.Net.Sockets.SocketException: Kan geen verbinding maken omdat de doelcomputer de verbinding actief heeft geweigerd 127.0.0.1:15555
       bij System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
       bij System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
       bij System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       --- Einde van intern uitzonderingsstackpad ---

    Server stack trace:
       bij System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       bij System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       bij System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
       bij System.ServiceModel.Channels.StreamedFramingRequestChannel.StreamedFramingRequest.SendRequest(Message message, TimeSpan timeout)
       bij System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
       bij System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       bij System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       bij System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [0]:
       bij System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       bij System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       bij Telerik.OpenAccess.ProfilerClient.ProfilerService.IProfilerService.GetServiceVersion()
       bij Telerik.OpenAccess.ProfilerClient.ClientService..ctor(String server, Int32 port)
       --- Einde van intern uitzonderingsstackpad ---
       bij Telerik.OpenAccess.ProfilerClient.ClientService..ctor(String server, Int32 port)

  2. Boris Georgiev
    Admin
    Boris Georgiev avatar
    190 posts

    Posted 27 Jan 2014 Link to this post

    Hello Henk,

    This error could occur if your application is using Telerik OpenAccess ORM version different than the version of Telerik OpenAccess Profiler. The cause of the problem could be, if you have installed a new OpenAccess version but you didn't update the OpenAccess references in the solution, then there will be a mismatch between the Profiler and solution version. You can refer to this article How to: Upgrade References.
     
    I hope that helps. If this is not the cause of the problem or you have other troubles, do not hesitate to contact us again.

    Regards,
    Boris Georgiev
    Telerik
    OpenAccess ORM Q3 2013 simplifies your model operations even further providing you with greater flexibility. Check out the list of new features shipped with our latest release!
  3. DevCraft banner
  4. Henk
    Henk avatar
    113 posts
    Member since:
    Apr 2006

    Posted 31 Jan 2014 in reply to Boris Georgiev Link to this post

    Hi Boris,

    I did follow the steps regarding "upgrading references" and rebuild the solution before I post this problem.

    I dont know if it is worth mentioning but the model(rlinq) is defined in a separate service project and the services are used in a separate webapp project where the global asax is located.

    I also dont see in the connection combobox of the profiler the connection string used in the web.config.

    Henk
  5. Henk
    Henk avatar
    113 posts
    Member since:
    Apr 2006

    Posted 31 Jan 2014 in reply to Henk Link to this post

    It is solved by creating a global asax on the service project!
Back to Top