Post reply

SQL Enterprise manager not available in Snap-in

  • August 21, 2009 at 12:21 pm

    #225172

    Hi,

    I was asked to work on a sql server instance where client tools are not installed. I know the only way is to create a console for SQL enterprise manager and work on it, but i do not see enterprise manager available snap-in. I only see SQL Configuration manager. Can anybody pls help in this

    Thanks,

    ek

  • August 21, 2009 at 12:36 pm

    #1043057

    Can you access this instance remotely or is there a particular reason you need to work on the server?

    Regards,

    Andras

    Andras Belokosztolszki, MCPD, PhD
    GoldenGate Software

  • August 21, 2009 at 12:43 pm

    #1043066

    i cannot access this server remotely, thats the whole issue. I think we can configure only through SSMS to allow remote connections, pls let me know if there's any other way that i can access

    Thanks,

    ek

  • August 21, 2009 at 12:55 pm

    #1043076

    eranna (8/21/2009)

    i cannot access this server remotely, thats the whole issue. I think we can configure only through SSMS to allow remote connections, pls let me know if there's any other way that i can access

    Thanks,

    ek

    You do not need SSMS for this, you can allow remote connections by executing:

    EXEC sys.sp_configure N'remote access', N'1'

    GO

    RECONFIGURE WITH OVERRIDE

    GO

    do you have anything to connect to this database and execute queries? sqlcmd/custom application/etc?

    - Andras

    Andras Belokosztolszki, MCPD, PhD
    GoldenGate Software

  • August 21, 2009 at 1:03 pm

    #1043084

    I do not have anything to connect to this server instance, all i know is only SSMS which i am not able to connect through. I get this while connect through SSMS

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)

    Let me know is there any other way that i can connect.

    Thanks,

    ek

  • August 21, 2009 at 1:06 pm

    #1043088

    For SQLCMD it says that my login failed, what could be the issue ?

    Thanks,

    ek

  • August 21, 2009 at 1:29 pm

    #1043109

    I tried with SQLCMD from my system using -S option to connect to the server, but i got this error

    Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.

    Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi

    shing a connection to the server. When connecting to SQL Server 2005, this failu

    re may be caused by the fact that under the default settings SQL Server does not

    allow remote connections..

    Thanks,

    ek

  • August 21, 2009 at 2:39 pm

    #1043159

    The issue is resolved. The instance is not running in default port, so it worked when i connected with the port number.

    Thanks

    ek

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply