Results 1 to 8 of 8
  1. #1
    Join Date
    Oct 2003
    Posts
    4

    Unanswered: Accessing SQL Server 8

    We're running a point of sale/inventory management system that uses MS SQL Server as the backend. I'm looking to do some reporting and need to query data from the existing inventory databases but the server is not responding via OSQL and the ODBC "Test Data Source" fails.

    osql -L reports:

    "Servers: CONNPOS"

    osql -E -S CONNPOS reports:

    [Shared Memory]SQL Server does not exist or access denied.
    [Shared Memory]ConnectionOpen (Connect()).

    I am logged in as the admin which was the account used to install the server and create the databases.

    Any suggestions?

  2. #2
    Join Date
    Sep 2003
    Posts
    522
    try pinging it. also check if using ip for the server name will do the trick. here i managed to simulate the error only by stopping the server.

  3. #3
    Join Date
    Dec 2002
    Posts
    29
    Have you tried to login using SQL authenthification?
    If this succeds, then it means that your user's rights have been removed somehow, if not your connection is down. And I think this is the problem, at least the second message (ConnectionOpen (Connect()) is suggesting that. Probably you were connected to the database, and while beeing connected the connection got lost.
    Try disconnecting and reconecting, and check if the server is REALLY running, because it's not necessarily has to run to be reported by the "osql -L" statement.

    Best regards!

  4. #4
    Join Date
    Oct 2003
    Posts
    4
    According to sqlmangr/services panel the server is up and running... I should note that the osql commands were run from the local machine (2000 Server), not from a remote system. I haven't tried SQL auth... just NT.

    I did notice that netstat doesn't report ms-sql-* on any TCP ports... hmm.

  5. #5
    Join Date
    Oct 2003
    Posts
    4
    Well, looks like we're up and running.

    "osql -E -S servername/instancename" works like a charm... I've also established a user DSN as well and the test passed.

    Thanks for the help.

  6. #6
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,799
    Provided Answers: 11
    I have run into this sort of thing before. In the server network utility, you will find a checkbox that says something like "Enable Shared Memory Protocol" (not sure of the wording, so that could be pretty wrong). Uncheck that box. Then retry the query. Good luck.

  7. #7
    Join Date
    Oct 2003
    Posts
    4
    I am able to connect via OSQL and can execute queries. I have also configured a user DSN for this database via the ODBC Control Panel but can not connect through an ASP script even tho the ODBC data source test passed. Here's the error that is returned to the browser when the script attempts to open a connection:

    [Microsoft][ODBC Driver Manager]Data Source Name not found and no default driver specified.

    I had selected "SQL Server" as the driver and again, the data source test had passed.

    Suggestions?

  8. #8
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,799
    Provided Answers: 11
    Create a system DSN. User DSNs are only available to the user that creates them.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •