Unable to connect SQL 2012 on Windows 8 ???

Thread is closed for posting
3 posts, 0 answers
  1. Richard
    Richard avatar
    9 posts
    Member since:
    Sep 2011

    Posted 03 Oct 2013 Link to this post

    I use telerik :
    * version : 2011.1.411.2
    * Version runtime : v2.0.50727

    Is that version is compatible with SQL 2012 ?
    I can't to connect my GUI to SQL 2012 on windows 8 ?

    --> I can connect to the database SQL2012 with a remote PC with my GUI.
    --> In fact, I have the problem only on local mode (GUI+SQL 2012)
    -->I desactivate on winows 8 the firewall.

    Just to precise....
    I update the telerik version 2013 --> I again the problem (same problems)

    Can you help me, please ????

    In advance,
  2. Kristian Nikolov
    Kristian Nikolov avatar
    206 posts

    Posted 07 Oct 2013 Link to this post

    Hi Richard,

    Microsoft SQL Server 2012 support was introduced with the Q1 2012 SP1 release (2012.1.301) of Telerik OpenAccess ORM and is present in all later versions of the product.

    Could you please provide us with some additional information about your case, to help us troubleshoot it:
    1. Is SQL Server 2012 running on the same machine on which you are having problems connecting to the database?
    2. Is OpenAccess installed on the machine where you cannot connect to the database?
    3. Is OpenAccess installed on your remote PC or are you deploying the OpenAccess assemblies with your application?
    4. Can you connect to the same instance of SQL Server 2012 with SQL Server Management Studio (locally and remotely)?
    5. Are you receiving some kind of error message? Could you post it here so that we are sure we are fighting the correct issue?

    I am looking forward to your feedback.

    Kristian Nikolov
    OpenAccess ORM Q3 2013 Beta is available for immediate download in your account. Get it now and play with the latest bits. See what's new >>
  3. Richard
    Richard avatar
    9 posts
    Member since:
    Sep 2011

    Posted 07 Oct 2013 Link to this post

    Hi Kristian,

    In fact, I solve my problem, it was a problem instance named with SQL.
    It works fine.

Back to Top