Showing posts with label osql. Show all posts
Showing posts with label osql. Show all posts

Tuesday, March 20, 2012

can't access MSDE database after setup

I can't log in with osql. My setup config file is as below.
[Options]
INSTANCENAME=NetSDK
SECURITYMODE=SQL
SAPWD=mypassword
It seems to install and run (green arrow in service bar after giving
it
myservername\NetSDK). Then I try this:
osql -U sa
Password: 'I give mypassword here
[Shared Memory]SQL Server does not exists or access denied.
[Shared Memory]ConnectionOpen (Connect()).
What does this mean? Am I missing something basic? I would really like
to use MSDE, but it seems broken or I just don't have enough
information.
Please cc to jhestess@.yahoo.com. Thanks in advance.
John Estess
El Paso, Texas
This may be a problem with ports or other things. Try these:
"Potential causes of the "SQL Server Does Not Exist or Access Denied" error message"
http://support.microsoft.com/default...06&Product=sql
http://support.microsoft.com/?id=287932
http://support.microsoft.com/default.aspx?kbid=814130
Mark Ferguson
"John Estess" wrote:

> I can't log in with osql. My setup config file is as below.
> [Options]
> INSTANCENAME=NetSDK
> SECURITYMODE=SQL
> SAPWD=mypassword
> It seems to install and run (green arrow in service bar after giving
> it
> myservername\NetSDK). Then I try this:
> osql -U sa
> Password: 'I give mypassword here
> [Shared Memory]SQL Server does not exists or access denied.
> [Shared Memory]ConnectionOpen (Connect()).
> What does this mean? Am I missing something basic? I would really like
> to use MSDE, but it seems broken or I just don't have enough
> information.
> Please cc to jhestess@.yahoo.com. Thanks in advance.
> John Estess
> El Paso, Texas
>
|||hi John,
"John Estess" <jhestess@.yahoo.com> ha scritto nel messaggio
news:136cf350.0406250942.1417a8a7@.posting.google.c om...
> I can't log in with osql. My setup config file is as below.
> [Options]
> INSTANCENAME=NetSDK
> SECURITYMODE=SQL
> SAPWD=mypassword
> It seems to install and run (green arrow in service bar after giving
> it
> myservername\NetSDK). Then I try this:
> osql -U sa
> Password: 'I give mypassword here
> [Shared Memory]SQL Server does not exists or access denied.
> [Shared Memory]ConnectionOpen (Connect()).
> What does this mean? Am I missing something basic? I would really like
> to use MSDE, but it seems broken or I just don't have enough
> information.
> Please cc to jhestess@.yahoo.com. Thanks in advance.
> John Estess
> El Paso, Texas
try
c:\>osql -Smyservername\NetSDK -Usa -Pyour_pwd
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

Tuesday, February 14, 2012

Cannot see an instance with BrowseConnect or OSQL /L

This summary is not available. Please click here to view the post.

Cannot see an instance with BrowseConnect or OSQL /L

Hi,
I have 3 instances of SQL server currently on my machine. The default
instance is MSDE 2000, I also have an SQL Express 2005 instance
\MACHINE\SQLEXPRESS and I have an instance of SQL Server 2000 Workgroup
Edition, named \MACHINE\WORKGROUP. When I execute SqlBrowseConnect or
"ListAllAvailableInstances" from SQL-DMO methods, I can see the 2005
instance and the default instance (local), but not the workgroup instance.
When I execute OSQL /L, I get the same result. I cannot see the Workgroup
Instance. I can however connect to the workgroup instance via. management
studio and can register it with SQL Server Configuration Manager.
I can connect to it via. OSQL and execute statements however, if I specify
the instance name on the command line. Any ideas on why it isn't visible?
According to connection properties in Management Studio (Server
Properties -> Connections), "allow remote connections" is switched on.
Robin
Okay, I fixed this by using the registry for local enumeration. Still, it's
a bit suprising to me that the browser won't enumerate all local instances -
or at least that there isn't a solid mechanism for doing so apart from
accessing the registry.
"Robinson" <toomuchspamhaspassed@.myinboxtoomuchtoooften.com > wrote in
message news:ego20b$g7q$1$830fa17d@.news.demon.co.uk...
> Hi,
> I have 3 instances of SQL server currently on my machine. The default
> instance is MSDE 2000, I also have an SQL Express 2005 instance
> \MACHINE\SQLEXPRESS and I have an instance of SQL Server 2000 Workgroup
> Edition, named \MACHINE\WORKGROUP. When I execute SqlBrowseConnect or
> "ListAllAvailableInstances" from SQL-DMO methods, I can see the 2005
> instance and the default instance (local), but not the workgroup instance.
> When I execute OSQL /L, I get the same result. I cannot see the Workgroup
> Instance. I can however connect to the workgroup instance via.
> management studio and can register it with SQL Server Configuration
> Manager.
> I can connect to it via. OSQL and execute statements however, if I specify
> the instance name on the command line. Any ideas on why it isn't visible?
> According to connection properties in Management Studio (Server
> Properties -> Connections), "allow remote connections" is switched on.
>
> Robin
>