msde and iis

Hi
If I get data from msde remotely
(from another computer)
should I have iis installed on computer
with sql server.?
Does connection should have
static IP?
Thanks
Konrad
"Konrad" <konrad007@.poczta.onet.pl> wrote in message
news:OdFN8F7TEHA.1048@.tk2msftngp13.phx.gbl...
> If I get data from msde remotely
> (from another computer)
> should I have iis installed on computer
> with sql server.?
If you are accessing the data via a web page, then that would work, or
install IIS on another server.

> Does connection should have
> static IP?
I'm not sure what you are asking here... Typically the host server, running
IIS would need a static address, and be registered in DNS. The connection
from the client side, could be the netbios name or the IP addess of the
host.
Steve

MSDE and ADO

When i call ADOConnection.Connected := False
The connection with the MSDE server is still opened, why that?
I want to close that connection with the server
The connection is only closed when my application is terminated
Im using MSDE 2000 and my application is writen in Delphi
Connection pooling is the probably cause. See this article:
http://msdn.microsoft.com/library/de...l/pooling2.asp
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Marcos Lommez" <lommez@.hotmail.com> wrote in message
news:O18zpcbUGHA.5108@.TK2MSFTNGP09.phx.gbl...
> When i call ADOConnection.Connected := False
> The connection with the MSDE server is still opened, why that?
> I want to close that connection with the server
> The connection is only closed when my application is terminated
> Im using MSDE 2000 and my application is writen in Delphi
>
>
|||Thanks
I have found the solution in that article
I just need to put the ';OLE DB Services = -2' to the end of my connetion
string
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> escreveu na mensagem
news:%23Bd2jedUGHA.736@.TK2MSFTNGP12.phx.gbl...
> Connection pooling is the probably cause. See this article:
>
http://msdn.microsoft.com/library/de...l/pooling2.asp
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Marcos Lommez" <lommez@.hotmail.com> wrote in message
> news:O18zpcbUGHA.5108@.TK2MSFTNGP09.phx.gbl...
>
sql

MSDE 2000 SP3 Connection Problem

I am have a problem which has only just started happening while trying to
connect (locally) to MSDE 2000 (SP3a) which also prevents me from using
VS.NET Server Explorer.
When I try OSQL -E -S mimpc\NetSDK (this use to work) I get the following
error
[Named Pipes]SQL Server does not exist or access denied.
[Named Pipes]ConnectionOpen (Connect()).
But it works fine when I call OSQL -E -S (local)\NetSDK or OSQL -E -S
127.0.0.1\NetSDK.
In SVRNETCN application both TCP and Named Pipes are enabled.
I am running Windows XP Professional with 2 network card 1 being Wireless.
The log seems to suggest that the server is listening on all IP address on
port 1433
2004-04-20 18:35:55.50 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2004-04-20 18:35:55.58 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-04-20 18:35:55.58 server All rights reserved.
2004-04-20 18:35:55.58 server Server Process ID is 1092.
2004-04-20 18:35:55.58 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2004-04-20 18:35:55.73 server SQL Server is starting at priority
class 'normal'(1 CPU detected).
2004-04-20 18:35:56.61 server SQL Server configured for thread mode
processing.
2004-04-20 18:35:56.62 server Using dynamic lock allocation. [500]
Lock Blocks, [1000] Lock Owner Blocks.
2004-04-20 18:35:56.74 spid3 Starting up database 'master'.
2004-04-20 18:35:57.40 server Using 'SSNETLIB.DLL' version
'8.0.760'.
2004-04-20 18:35:57.40 spid5 Starting up database 'model'.
2004-04-20 18:35:57.65 server SQL server listening on 198.3.0.27:
1433.
2004-04-20 18:35:57.65 server SQL server listening on 198.2.0.100:
1433.
2004-04-20 18:35:57.65 server SQL server listening on 127.0.0.1:
1433.
2004-04-20 18:35:57.65 server SQL server listening on TCP, Shared
Memory, Named Pipes.
2004-04-20 18:35:57.65 server SQL Server is ready for client
connections
2004-04-20 18:35:57.68 spid3 Server name is 'MIMPC\NETSDK'.
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
4
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
5
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
6
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
7
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
8
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
9
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
10
2004-04-20 18:35:57.93 spid5 Clearing tempdb database.
2004-04-20 18:35:58.95 spid5 Starting up database 'tempdb'.
2004-04-20 18:35:59.28 spid3 Recovery complete.
2004-04-20 18:35:59.28 spid3 SQL global counter collection task is
created.
2004-04-20 19:15:47.20 spid51 Starting up database 'RT_TEST'.
I have gone through all the MS support articles which sugests enabling TCP
but it is or install SP3 which I did.
Any help would be appreciated.
Mark
Sorry.
I have just noticed it works when I add TCP: in front of the server name
osql -E -S tcp:mimpc\NetSDK
So from this I am assuming I have an issue with Named Pipes protocol.
Mark
"Mark Miles" <milesfam@.idirect.com> wrote in message
news:gyihc.165608$2oI1.24269@.twister01.bloor.is.ne t.cable.rogers.com...
> I am have a problem which has only just started happening while trying to
> connect (locally) to MSDE 2000 (SP3a) which also prevents me from using
> VS.NET Server Explorer.
> When I try OSQL -E -S mimpc\NetSDK (this use to work) I get the following
> error
> [Named Pipes]SQL Server does not exist or access denied.
> [Named Pipes]ConnectionOpen (Connect()).
> But it works fine when I call OSQL -E -S (local)\NetSDK or OSQL -E -S
> 127.0.0.1\NetSDK.
> In SVRNETCN application both TCP and Named Pipes are enabled.
> I am running Windows XP Professional with 2 network card 1 being Wireless.
> The log seems to suggest that the server is listening on all IP address on
> port 1433
> 2004-04-20 18:35:55.50 server Microsoft SQL Server 2000 -
8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
> 2004-04-20 18:35:55.58 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2004-04-20 18:35:55.58 server All rights reserved.
> 2004-04-20 18:35:55.58 server Server Process ID is 1092.
> 2004-04-20 18:35:55.58 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
> 2004-04-20 18:35:55.73 server SQL Server is starting at priority
> class 'normal'(1 CPU detected).
> 2004-04-20 18:35:56.61 server SQL Server configured for thread
mode
> processing.
> 2004-04-20 18:35:56.62 server Using dynamic lock allocation. [500]
> Lock Blocks, [1000] Lock Owner Blocks.
> 2004-04-20 18:35:56.74 spid3 Starting up database 'master'.
> 2004-04-20 18:35:57.40 server Using 'SSNETLIB.DLL' version
> '8.0.760'.
> 2004-04-20 18:35:57.40 spid5 Starting up database 'model'.
> 2004-04-20 18:35:57.65 server SQL server listening on 198.3.0.27:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on 198.2.0.100:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on 127.0.0.1:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on TCP, Shared
> Memory, Named Pipes.
> 2004-04-20 18:35:57.65 server SQL Server is ready for client
> connections
> 2004-04-20 18:35:57.68 spid3 Server name is 'MIMPC\NETSDK'.
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 4
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 5
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 6
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 7
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 8
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 9
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 10
> 2004-04-20 18:35:57.93 spid5 Clearing tempdb database.
> 2004-04-20 18:35:58.95 spid5 Starting up database 'tempdb'.
> 2004-04-20 18:35:59.28 spid3 Recovery complete.
> 2004-04-20 18:35:59.28 spid3 SQL global counter collection task
is
> created.
> 2004-04-20 19:15:47.20 spid51 Starting up database 'RT_TEST'.
> I have gone through all the MS support articles which sugests enabling TCP
> but it is or install SP3 which I did.
> Any help would be appreciated.
> Mark
>
sql

MSDE 2000 SP3 Connection Problem

I am have a problem which has only just started happening while trying to
connect (locally) to MSDE 2000 (SP3a) which also prevents me from using
VS.NET Server Explorer.
When I try OSQL -E -S mimpc\NetSDK (this use to work) I get the following
error
[Named Pipes]SQL Server does not exist or access denied.
[Named Pipes]ConnectionOpen (Connect()).
But it works fine when I call OSQL -E -S (local)\NetSDK or OSQL -E -S
127.0.0.1\NetSDK.
In SVRNETCN application both TCP and Named Pipes are enabled.
I am running Windows XP Professional with 2 network card 1 being Wireless.
The log seems to suggest that the server is listening on all IP address on
port 1433
2004-04-20 18:35:55.50 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2004-04-20 18:35:55.58 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-04-20 18:35:55.58 server All rights reserved.
2004-04-20 18:35:55.58 server Server Process ID is 1092.
2004-04-20 18:35:55.58 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2004-04-20 18:35:55.73 server SQL Server is starting at priority
class 'normal'(1 CPU detected).
2004-04-20 18:35:56.61 server SQL Server configured for thread mode
processing.
2004-04-20 18:35:56.62 server Using dynamic lock allocation. [500]
Lock Blocks, [1000] Lock Owner Blocks.
2004-04-20 18:35:56.74 spid3 Starting up database 'master'.
2004-04-20 18:35:57.40 server Using 'SSNETLIB.DLL' version
'8.0.760'.
2004-04-20 18:35:57.40 spid5 Starting up database 'model'.
2004-04-20 18:35:57.65 server SQL server listening on 198.3.0.27:
1433.
2004-04-20 18:35:57.65 server SQL server listening on 198.2.0.100:
1433.
2004-04-20 18:35:57.65 server SQL server listening on 127.0.0.1:
1433.
2004-04-20 18:35:57.65 server SQL server listening on TCP, Shared
Memory, Named Pipes.
2004-04-20 18:35:57.65 server SQL Server is ready for client
connections
2004-04-20 18:35:57.68 spid3 Server name is 'MIMPC\NETSDK'.
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
4
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
5
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
6
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
7
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
8
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
9
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
10
2004-04-20 18:35:57.93 spid5 Clearing tempdb database.
2004-04-20 18:35:58.95 spid5 Starting up database 'tempdb'.
2004-04-20 18:35:59.28 spid3 Recovery complete.
2004-04-20 18:35:59.28 spid3 SQL global counter collection task is
created.
2004-04-20 19:15:47.20 spid51 Starting up database 'RT_TEST'.
I have gone through all the MS support articles which sugests enabling TCP
but it is or install SP3 which I did.
Any help would be appreciated.
Mark
Sorry.
I have just noticed it works when I add TCP: in front of the server name
osql -E -S tcp:mimpc\NetSDK
So from this I am assuming I have an issue with Named Pipes protocol.
Mark
"Mark Miles" <milesfam@.idirect.com> wrote in message
news:gyihc.165608$2oI1.24269@.twister01.bloor.is.ne t.cable.rogers.com...
> I am have a problem which has only just started happening while trying to
> connect (locally) to MSDE 2000 (SP3a) which also prevents me from using
> VS.NET Server Explorer.
> When I try OSQL -E -S mimpc\NetSDK (this use to work) I get the following
> error
> [Named Pipes]SQL Server does not exist or access denied.
> [Named Pipes]ConnectionOpen (Connect()).
> But it works fine when I call OSQL -E -S (local)\NetSDK or OSQL -E -S
> 127.0.0.1\NetSDK.
> In SVRNETCN application both TCP and Named Pipes are enabled.
> I am running Windows XP Professional with 2 network card 1 being Wireless.
> The log seems to suggest that the server is listening on all IP address on
> port 1433
> 2004-04-20 18:35:55.50 server Microsoft SQL Server 2000 -
8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
> 2004-04-20 18:35:55.58 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2004-04-20 18:35:55.58 server All rights reserved.
> 2004-04-20 18:35:55.58 server Server Process ID is 1092.
> 2004-04-20 18:35:55.58 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
> 2004-04-20 18:35:55.73 server SQL Server is starting at priority
> class 'normal'(1 CPU detected).
> 2004-04-20 18:35:56.61 server SQL Server configured for thread
mode
> processing.
> 2004-04-20 18:35:56.62 server Using dynamic lock allocation. [500]
> Lock Blocks, [1000] Lock Owner Blocks.
> 2004-04-20 18:35:56.74 spid3 Starting up database 'master'.
> 2004-04-20 18:35:57.40 server Using 'SSNETLIB.DLL' version
> '8.0.760'.
> 2004-04-20 18:35:57.40 spid5 Starting up database 'model'.
> 2004-04-20 18:35:57.65 server SQL server listening on 198.3.0.27:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on 198.2.0.100:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on 127.0.0.1:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on TCP, Shared
> Memory, Named Pipes.
> 2004-04-20 18:35:57.65 server SQL Server is ready for client
> connections
> 2004-04-20 18:35:57.68 spid3 Server name is 'MIMPC\NETSDK'.
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 4
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 5
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 6
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 7
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 8
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 9
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 10
> 2004-04-20 18:35:57.93 spid5 Clearing tempdb database.
> 2004-04-20 18:35:58.95 spid5 Starting up database 'tempdb'.
> 2004-04-20 18:35:59.28 spid3 Recovery complete.
> 2004-04-20 18:35:59.28 spid3 SQL global counter collection task
is
> created.
> 2004-04-20 19:15:47.20 spid51 Starting up database 'RT_TEST'.
> I have gone through all the MS support articles which sugests enabling TCP
> but it is or install SP3 which I did.
> Any help would be appreciated.
> Mark
>
|||What happens if you run the following command:
net view \\MIMPC
or
Net use * \\MIMPC\IPC$
or
ISQL -Snp:MIMPC\NETSDK -E -Q"select @.@.version"
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

MSDE 2000 SP3 Connection Problem

I am have a problem which has only just started happening while trying to
connect (locally) to MSDE 2000 (SP3a) which also prevents me from using
VS.NET Server Explorer.
When I try OSQL -E -S mimpc\NetSDK (this use to work) I get the following
error
[Named Pipes]SQL Server does not exist or access denied.
[Named Pipes]ConnectionOpen (Connect()).
But it works fine when I call OSQL -E -S (local)\NetSDK or OSQL -E -S
127.0.0.1\NetSDK.
In SVRNETCN application both TCP and Named Pipes are enabled.
I am running Windows XP Professional with 2 network card 1 being Wireless.
The log seems to suggest that the server is listening on all IP address on
port 1433
2004-04-20 18:35:55.50 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2004-04-20 18:35:55.58 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-04-20 18:35:55.58 server All rights reserved.
2004-04-20 18:35:55.58 server Server Process ID is 1092.
2004-04-20 18:35:55.58 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2004-04-20 18:35:55.73 server SQL Server is starting at priority
class 'normal'(1 CPU detected).
2004-04-20 18:35:56.61 server SQL Server configured for thread mode
processing.
2004-04-20 18:35:56.62 server Using dynamic lock allocation. [500]
Lock Blocks, [1000] Lock Owner Blocks.
2004-04-20 18:35:56.74 spid3 Starting up database 'master'.
2004-04-20 18:35:57.40 server Using 'SSNETLIB.DLL' version
'8.0.760'.
2004-04-20 18:35:57.40 spid5 Starting up database 'model'.
2004-04-20 18:35:57.65 server SQL server listening on 198.3.0.27:
1433.
2004-04-20 18:35:57.65 server SQL server listening on 198.2.0.100:
1433.
2004-04-20 18:35:57.65 server SQL server listening on 127.0.0.1:
1433.
2004-04-20 18:35:57.65 server SQL server listening on TCP, Shared
Memory, Named Pipes.
2004-04-20 18:35:57.65 server SQL Server is ready for client
connections
2004-04-20 18:35:57.68 spid3 Server name is 'MIMPC\NETSDK'.
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
4
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
5
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
6
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
7
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
8
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
9
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
10
2004-04-20 18:35:57.93 spid5 Clearing tempdb database.
2004-04-20 18:35:58.95 spid5 Starting up database 'tempdb'.
2004-04-20 18:35:59.28 spid3 Recovery complete.
2004-04-20 18:35:59.28 spid3 SQL global counter collection task is
created.
2004-04-20 19:15:47.20 spid51 Starting up database 'RT_TEST'.
I have gone through all the MS support articles which sugests enabling TCP
but it is or install SP3 which I did.
Any help would be appreciated.
MarkSorry.
I have just noticed it works when I add TCP: in front of the server name
osql -E -S tcp:mimpc\NetSDK
So from this I am assuming I have an issue with Named Pipes protocol.
Mark
"Mark Miles" <milesfam@.idirect.com> wrote in message
news:gyihc.165608$2oI1.24269@.twister01.bloor.is.net.cable.rogers.com...
> I am have a problem which has only just started happening while trying to
> connect (locally) to MSDE 2000 (SP3a) which also prevents me from using
> VS.NET Server Explorer.
> When I try OSQL -E -S mimpc\NetSDK (this use to work) I get the following
> error
> [Named Pipes]SQL Server does not exist or access denied.
> [Named Pipes]ConnectionOpen (Connect()).
> But it works fine when I call OSQL -E -S (local)\NetSDK or OSQL -E -S
> 127.0.0.1\NetSDK.
> In SVRNETCN application both TCP and Named Pipes are enabled.
> I am running Windows XP Professional with 2 network card 1 being Wireless.
> The log seems to suggest that the server is listening on all IP address on
> port 1433
> 2004-04-20 18:35:55.50 server Microsoft SQL Server 2000 -
8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
> 2004-04-20 18:35:55.58 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2004-04-20 18:35:55.58 server All rights reserved.
> 2004-04-20 18:35:55.58 server Server Process ID is 1092.
> 2004-04-20 18:35:55.58 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
> 2004-04-20 18:35:55.73 server SQL Server is starting at priority
> class 'normal'(1 CPU detected).
> 2004-04-20 18:35:56.61 server SQL Server configured for thread
mode
> processing.
> 2004-04-20 18:35:56.62 server Using dynamic lock allocation. [500]
> Lock Blocks, [1000] Lock Owner Blocks.
> 2004-04-20 18:35:56.74 spid3 Starting up database 'master'.
> 2004-04-20 18:35:57.40 server Using 'SSNETLIB.DLL' version
> '8.0.760'.
> 2004-04-20 18:35:57.40 spid5 Starting up database 'model'.
> 2004-04-20 18:35:57.65 server SQL server listening on 198.3.0.27:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on 198.2.0.100:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on 127.0.0.1:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on TCP, Shared
> Memory, Named Pipes.
> 2004-04-20 18:35:57.65 server SQL Server is ready for client
> connections
> 2004-04-20 18:35:57.68 spid3 Server name is 'MIMPC\NETSDK'.
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 4
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 5
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 6
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 7
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 8
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 9
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 10
> 2004-04-20 18:35:57.93 spid5 Clearing tempdb database.
> 2004-04-20 18:35:58.95 spid5 Starting up database 'tempdb'.
> 2004-04-20 18:35:59.28 spid3 Recovery complete.
> 2004-04-20 18:35:59.28 spid3 SQL global counter collection task
is
> created.
> 2004-04-20 19:15:47.20 spid51 Starting up database 'RT_TEST'.
> I have gone through all the MS support articles which sugests enabling TCP
> but it is or install SP3 which I did.
> Any help would be appreciated.
> Mark
>

MSDE 2000 SP3 Connection Problem

I am have a problem which has only just started happening while trying to
connect (locally) to MSDE 2000 (SP3a) which also prevents me from using
VS.NET Server Explorer.
When I try OSQL -E -S mimpc\NetSDK (this use to work) I get the following
error
[Named Pipes]SQL Server does not exist or access denied.
[Named Pipes]ConnectionOpen (Connect()).
But it works fine when I call OSQL -E -S (local)\NetSDK or OSQL -E -S
127.0.0.1\NetSDK.
In SVRNETCN application both TCP and Named Pipes are enabled.
I am running Windows XP Professional with 2 network card 1 being Wireless.
The log seems to suggest that the server is listening on all IP address on
port 1433
2004-04-20 18:35:55.50 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2004-04-20 18:35:55.58 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-04-20 18:35:55.58 server All rights reserved.
2004-04-20 18:35:55.58 server Server Process ID is 1092.
2004-04-20 18:35:55.58 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2004-04-20 18:35:55.73 server SQL Server is starting at priority
class 'normal'(1 CPU detected).
2004-04-20 18:35:56.61 server SQL Server configured for thread mode
processing.
2004-04-20 18:35:56.62 server Using dynamic lock allocation. [500]
Lock Blocks, [1000] Lock Owner Blocks.
2004-04-20 18:35:56.74 spid3 Starting up database 'master'.
2004-04-20 18:35:57.40 server Using 'SSNETLIB.DLL' version
'8.0.760'.
2004-04-20 18:35:57.40 spid5 Starting up database 'model'.
2004-04-20 18:35:57.65 server SQL server listening on 198.3.0.27:
1433.
2004-04-20 18:35:57.65 server SQL server listening on 198.2.0.100:
1433.
2004-04-20 18:35:57.65 server SQL server listening on 127.0.0.1:
1433.
2004-04-20 18:35:57.65 server SQL server listening on TCP, Shared
Memory, Named Pipes.
2004-04-20 18:35:57.65 server SQL Server is ready for client
connections
2004-04-20 18:35:57.68 spid3 Server name is 'MIMPC\NETSDK'.
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
4
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
5
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
6
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
7
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
8
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
9
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
10
2004-04-20 18:35:57.93 spid5 Clearing tempdb database.
2004-04-20 18:35:58.95 spid5 Starting up database 'tempdb'.
2004-04-20 18:35:59.28 spid3 Recovery complete.
2004-04-20 18:35:59.28 spid3 SQL global counter collection task is
created.
2004-04-20 19:15:47.20 spid51 Starting up database 'RT_TEST'.
I have gone through all the MS support articles which sugests enabling TCP
but it is or install SP3 which I did.
Any help would be appreciated.
MarkSorry.
I have just noticed it works when I add TCP: in front of the server name
osql -E -S tcp:mimpc\NetSDK
So from this I am assuming I have an issue with Named Pipes protocol.
Mark
"Mark Miles" <milesfam@.idirect.com> wrote in message
news:gyihc.165608$2oI1.24269@.twister01.bloor.is.net.cable.rogers.com...
> I am have a problem which has only just started happening while trying to
> connect (locally) to MSDE 2000 (SP3a) which also prevents me from using
> VS.NET Server Explorer.
> When I try OSQL -E -S mimpc\NetSDK (this use to work) I get the following
> error
> [Named Pipes]SQL Server does not exist or access denied.
> [Named Pipes]ConnectionOpen (Connect()).
> But it works fine when I call OSQL -E -S (local)\NetSDK or OSQL -E -S
> 127.0.0.1\NetSDK.
> In SVRNETCN application both TCP and Named Pipes are enabled.
> I am running Windows XP Professional with 2 network card 1 being Wireless.
> The log seems to suggest that the server is listening on all IP address on
> port 1433
> 2004-04-20 18:35:55.50 server Microsoft SQL Server 2000 -
8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
> 2004-04-20 18:35:55.58 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2004-04-20 18:35:55.58 server All rights reserved.
> 2004-04-20 18:35:55.58 server Server Process ID is 1092.
> 2004-04-20 18:35:55.58 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
> 2004-04-20 18:35:55.73 server SQL Server is starting at priority
> class 'normal'(1 CPU detected).
> 2004-04-20 18:35:56.61 server SQL Server configured for thread
mode
> processing.
> 2004-04-20 18:35:56.62 server Using dynamic lock allocation. [
500]
> Lock Blocks, [1000] Lock Owner Blocks.
> 2004-04-20 18:35:56.74 spid3 Starting up database 'master'.
> 2004-04-20 18:35:57.40 server Using 'SSNETLIB.DLL' version
> '8.0.760'.
> 2004-04-20 18:35:57.40 spid5 Starting up database 'model'.
> 2004-04-20 18:35:57.65 server SQL server listening on 198.3.0.27:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on 198.2.0.100:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on 127.0.0.1:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on TCP, Shared
> Memory, Named Pipes.
> 2004-04-20 18:35:57.65 server SQL Server is ready for client
> connections
> 2004-04-20 18:35:57.68 spid3 Server name is 'MIMPC\NETSDK'.
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 4
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 5
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 6
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 7
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 8
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 9
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 10
> 2004-04-20 18:35:57.93 spid5 Clearing tempdb database.
> 2004-04-20 18:35:58.95 spid5 Starting up database 'tempdb'.
> 2004-04-20 18:35:59.28 spid3 Recovery complete.
> 2004-04-20 18:35:59.28 spid3 SQL global counter collection task
is
> created.
> 2004-04-20 19:15:47.20 spid51 Starting up database 'RT_TEST'.
> I have gone through all the MS support articles which sugests enabling TCP
> but it is or install SP3 which I did.
> Any help would be appreciated.
> Mark
>|||What happens if you run the following command:
net view \\MIMPC
or
Net use * \\MIMPC\IPC$
or
ISQL -Snp:MIMPC\NETSDK -E -Q"select @.@.version"
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

MSDE 2000 SP3 Connection Problem

I am have a problem which has only just started happening while trying to
connect (locally) to MSDE 2000 (SP3a) which also prevents me from using
VS.NET Server Explorer.
When I try OSQL -E -S mimpc\NetSDK (this use to work) I get the following
error
[Named Pipes]SQL Server does not exist or access denied.
[Named Pipes]ConnectionOpen (Connect()).
But it works fine when I call OSQL -E -S (local)\NetSDK or OSQL -E -S
127.0.0.1\NetSDK.
In SVRNETCN application both TCP and Named Pipes are enabled.
I am running Windows XP Professional with 2 network card 1 being Wireless.
The log seems to suggest that the server is listening on all IP address on
port 1433
2004-04-20 18:35:55.50 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2004-04-20 18:35:55.58 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-04-20 18:35:55.58 server All rights reserved.
2004-04-20 18:35:55.58 server Server Process ID is 1092.
2004-04-20 18:35:55.58 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2004-04-20 18:35:55.73 server SQL Server is starting at priority
class 'normal'(1 CPU detected).
2004-04-20 18:35:56.61 server SQL Server configured for thread mode
processing.
2004-04-20 18:35:56.62 server Using dynamic lock allocation. [500]
Lock Blocks, [1000] Lock Owner Blocks.
2004-04-20 18:35:56.74 spid3 Starting up database 'master'.
2004-04-20 18:35:57.40 server Using 'SSNETLIB.DLL' version
'8.0.760'.
2004-04-20 18:35:57.40 spid5 Starting up database 'model'.
2004-04-20 18:35:57.65 server SQL server listening on 198.3.0.27:
1433.
2004-04-20 18:35:57.65 server SQL server listening on 198.2.0.100:
1433.
2004-04-20 18:35:57.65 server SQL server listening on 127.0.0.1:
1433.
2004-04-20 18:35:57.65 server SQL server listening on TCP, Shared
Memory, Named Pipes.
2004-04-20 18:35:57.65 server SQL Server is ready for client
connections
2004-04-20 18:35:57.68 spid3 Server name is 'MIMPC\NETSDK'.
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
4
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
5
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
6
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
7
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
8
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
9
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
10
2004-04-20 18:35:57.93 spid5 Clearing tempdb database.
2004-04-20 18:35:58.95 spid5 Starting up database 'tempdb'.
2004-04-20 18:35:59.28 spid3 Recovery complete.
2004-04-20 18:35:59.28 spid3 SQL global counter collection task is
created.
2004-04-20 19:15:47.20 spid51 Starting up database 'RT_TEST'.
I have gone through all the MS support articles which sugests enabling TCP
but it is or install SP3 which I did.
Any help would be appreciated.
MarkSorry.
I have just noticed it works when I add TCP: in front of the server name
osql -E -S tcp:mimpc\NetSDK
So from this I am assuming I have an issue with Named Pipes protocol.
Mark
"Mark Miles" <milesfam@.idirect.com> wrote in message
news:gyihc.165608$2oI1.24269@.twister01.bloor.is.net.cable.rogers.com...
> I am have a problem which has only just started happening while trying to
> connect (locally) to MSDE 2000 (SP3a) which also prevents me from using
> VS.NET Server Explorer.
> When I try OSQL -E -S mimpc\NetSDK (this use to work) I get the following
> error
> [Named Pipes]SQL Server does not exist or access denied.
> [Named Pipes]ConnectionOpen (Connect()).
> But it works fine when I call OSQL -E -S (local)\NetSDK or OSQL -E -S
> 127.0.0.1\NetSDK.
> In SVRNETCN application both TCP and Named Pipes are enabled.
> I am running Windows XP Professional with 2 network card 1 being Wireless.
> The log seems to suggest that the server is listening on all IP address on
> port 1433
> 2004-04-20 18:35:55.50 server Microsoft SQL Server 2000 -
8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
> 2004-04-20 18:35:55.58 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2004-04-20 18:35:55.58 server All rights reserved.
> 2004-04-20 18:35:55.58 server Server Process ID is 1092.
> 2004-04-20 18:35:55.58 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
> 2004-04-20 18:35:55.73 server SQL Server is starting at priority
> class 'normal'(1 CPU detected).
> 2004-04-20 18:35:56.61 server SQL Server configured for thread
mode
> processing.
> 2004-04-20 18:35:56.62 server Using dynamic lock allocation. [
500]
> Lock Blocks, [1000] Lock Owner Blocks.
> 2004-04-20 18:35:56.74 spid3 Starting up database 'master'.
> 2004-04-20 18:35:57.40 server Using 'SSNETLIB.DLL' version
> '8.0.760'.
> 2004-04-20 18:35:57.40 spid5 Starting up database 'model'.
> 2004-04-20 18:35:57.65 server SQL server listening on 198.3.0.27:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on 198.2.0.100:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on 127.0.0.1:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on TCP, Shared
> Memory, Named Pipes.
> 2004-04-20 18:35:57.65 server SQL Server is ready for client
> connections
> 2004-04-20 18:35:57.68 spid3 Server name is 'MIMPC\NETSDK'.
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 4
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 5
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 6
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 7
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 8
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 9
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 10
> 2004-04-20 18:35:57.93 spid5 Clearing tempdb database.
> 2004-04-20 18:35:58.95 spid5 Starting up database 'tempdb'.
> 2004-04-20 18:35:59.28 spid3 Recovery complete.
> 2004-04-20 18:35:59.28 spid3 SQL global counter collection task
is
> created.
> 2004-04-20 19:15:47.20 spid51 Starting up database 'RT_TEST'.
> I have gone through all the MS support articles which sugests enabling TCP
> but it is or install SP3 which I did.
> Any help would be appreciated.
> Mark
>

msde 2000 odbc connection failed

i have msde 2000 running on a server i am able to create an odbc connection to my db on that pc. when i try to create anpther odbc connection on another pc on that network i get the following error:

sql state '01000'
server error 2
[microsoft][odbc sql server driver][named pipes] connectionopen (connect()).
connection failed
sql state '08001'
server error 17
[microsoft][odbc sql server driver][named pipes]server does not exist or access denied.

what do i have to do to get this odbc connection on this pc working?

Thank You,
ThomasHave you enabled network protocols? If not try this. Easier to do this by uninstalling and then reinstalling.|||True, and take help of this KBA http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q328306 to overcome the issue.

MSDE 2000 and ODBC (Connection failed)

Hi
I Installed MSDE 2000 and try to connect with it via ODBC.
I want the connection with SQL Server authentication using a login ID "sa" and blank password
But it is dispaly this message:
====================
Connection failed:
SQLState:'28000'
SQL Server Error:18456
[Microsoft][ODBC Sql Server Driver][SQL Server]Login failed for user 'sa'
====================check what authentication method your msde is using and make sure that standard security is available.|||Thanks ms_sql_dba

My MSDE use both WINDOWS/SQL Server authentication
I check "LoginMode" value in REGISTRY it's = Zero which mean both|||Thanks ms_sql_dba

My MSDE use both WINDOWS/SQL Server authentication
I check "LoginMode" value in REGISTRY it's = Zero which mean both|||Up 4 Help|||I found the Solution in Archive which guide me to this link:
http://www.dbforums.com/showthread.php?threadid=711306

The Solution is very simple:
Change "SA" password

use this command line in DOS:
osql -Q"exec sp_password null,'newpassword','sa'" -E

MSDE 1.0 --> MSDE 2000 DB Connection Failure

Just recently updated to MSDE 2000 using the SP3 Desktop upgrade. Now when this software runs it cannot connect to the Database.
I believe the problem to come in a line wrote as so:
BSTR bstrOpen = gServerName.AllocSysString();
although I'm not 100%.
Just wondering if anyone might had the same problem with MSDE 2000 and what they did to fix it. Thanks!
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Hi,
One of the things that's different about MSDE2000 is that by default, tcp is
not enabled. You might need to re-enable it. You can do this by running
svrnetcn.exe.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:%234NbSXufEHA.2984@.tk2msftngp13.phx.gbl...
> Just recently updated to MSDE 2000 using the SP3 Desktop upgrade. Now
when this software runs it cannot connect to the Database.
> I believe the problem to come in a line wrote as so:
> BSTR bstrOpen = gServerName.AllocSysString();
> although I'm not 100%.
> Just wondering if anyone might had the same problem with MSDE 2000 and
what they did to fix it. Thanks!
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.

MSDE ,SSMSE connection

hi friends,

I'll be thankful if anyone solve this problem.

When i developed my application, i used sql 2000 as a server side DB.
Now my client want to install MSDE instead of SQL 2000.

so i uninstall SQL2000 and installed MSDE .

AS we all know, MSDE doesn't have GUI. So i installed Microsoft SQL Server Management Studio Express - Community Technology Preview (CTP)
(includeing xmlparser,windows installer,.net 2.0).

now i could able to view tables and everything. but i couldn't make the connection. Getting error like "SQL server not found. CMPNAME\MSDERELA"
I used same kind of connection string for SQL 2000. Worked well.here what happened?

Connection String : "Data Source = CMPNAME\MSDERELA;Database =TEST; User id ="xxx; Password =xxxx;"

OS: Windows server 2003.
i used VB.NET to develop the apps. (VS2003). Connecting from Pocket PC.

kindly help me to solve this problem.

(Already i posted this in SQL tools forum. i hope this is the right place to post this question. so posting again.)

Thank u!

First I suggest you install the release version of SSMS-E.

Then can you go into the services panel in Windows and see if there are any services that start with MSSQL$, if there are please make sure it is started.

If it is started then please test the connection by using osql from a cmd prompt.

|||

You mean i need to install SSMSE before installing MSDE?

Let me share, what i 've done

1) installed MSDE

2)Windows installer 3.1

3).net framework 2

4)XML Parser

5) SSMSE

6) Start the MSDE agent and enabled TCP/IP.

Only thing is, i didn't check the connection in command prompt.

I checked with apps.

Thanks.

|||

So you know for sure the the MSSQL$ service is running (not the agent service)?

Can you please try connecting using osql from the command line please?

MSDE & SSMSE -CTP connection problem

hi friends,

I'll be thankful if anyone solve this problem.

When i developed my application i used sql 2000 as a server side DB.
Now my client want to install MSDE instead of SQL 2000.

so i uninstall SQL2000 and installed MSDE .

AS we all know, MSDE doesn't have GUI. So i installed Microsoft SQL Server Management Studio Express - Community Technology Preview (CTP)
(includeing xmlparser,windows installer,.net 2.0).

now i could able to view tables and everything. but i couldn't make the connection. Getting error like "SQL server not found. CMPNAME\MSDERELA"
I used same kind of connection string for SQL 2000. Worked well.here what happened?

OS: Windows server 2003.
i used VB.NET to develop the apps.

kindly help me to solve this problem.

why do you need to have a gui interface on the same box. you can connect to it from another SQL client machine/Server.|||

I don't understand ur point.

My server machine has MSDE DB only.

Clients are Pocket PCs.

|||? Hi, I have seen one other person with a problem like this when they created a SQL Server database from Visual Studio. Can you confirm that MSDE is installed as a named instance MSDERELA? Open a command shell window and type the following: SQLCMD -S .\MSDERELA What do you see? If you see a prompt like this: 1> then you are able to connect to the instance using SQLCMD which is a start. I notice that you have a CTP installed. You need to be VERY careful when you later come to uninstall this and go to SSMSE RTM build. There is a specific order in which to uninstall items to achieve a successful uninstall. Andrew Watt MVP <ar_pad@.discussions.microsoft.com> wrote in message news:434cb1f0-4b2c-43c5-97da-5aea1f39295f@.discussions.microsoft.com... hi friends, I'll be thankful if anyone solve this problem. When i developed my application i used sql 2000 as a server side DB.Now my client want to install MSDE instead of SQL 2000. so i uninstall SQL2000 and installed MSDE . AS we all know, MSDE doesn't have GUI. So i installed Microsoft SQL Server Management Studio Express - Community Technology Preview (CTP) (includeing xmlparser,windows installer,.net 2.0). now i could able to view tables and everything. but i couldn't make the connection. Getting error like "SQL server not found. CMPNAME\MSDERELA"I used same kind of connection string for SQL 2000. Worked well.here what happened? OS: Windows server 2003.i used VB.NET to develop the apps. kindly help me to solve this problem.|||

Hi,

Yes. It's a named instance. computername\MSDERelA.

can i use the same cmd? SQLCMD -S .\MSDERELA where can i see these kind of commands?

I followed this order. 1) windows installer

2)dotnetfx.exe

3)msxml6.msi

4) SSMSE

is it correct?

Thanks!

|||

That's the right order to install Management Studio Express.

The command line syntax for sqlcmd is very similar to the syntax for osql. You can get the command line syntax for sqlcmd by typing the following in a command window:

sqlcmd /?

"sqlcmd -S .\msderela -E" will connect to your local msderela instance using Windows authentication. You can type "quit" to exit sqlcmd.

Here's the online help topic for sqlcmd: http://msdn2.microsoft.com/en-us/library/ms165702(SQL.90).aspx

Hope this helps,
Steve

MSDE & SSMSE -CTP connection problem

hi friends,

I'll be thankful if anyone solve this problem.

When i developed my application i used sql 2000 as a server side DB.
Now my client want to install MSDE instead of SQL 2000.

so i uninstall SQL2000 and installed MSDE .

AS we all know, MSDE doesn't have GUI. So i installed Microsoft SQL Server Management Studio Express - Community Technology Preview (CTP)
(includeing xmlparser,windows installer,.net 2.0).

now i could able to view tables and everything. but i couldn't make the connection. Getting error like "SQL server not found. CMPNAME\MSDERELA"
I used same kind of connection string for SQL 2000. Worked well.here what happened?

OS: Windows server 2003.
i used VB.NET to develop the apps.

kindly help me to solve this problem.

why do you need to have a gui interface on the same box. you can connect to it from another SQL client machine/Server.|||

I don't understand ur point.

My server machine has MSDE DB only.

Clients are Pocket PCs.

|||? Hi, I have seen one other person with a problem like this when they created a SQL Server database from Visual Studio. Can you confirm that MSDE is installed as a named instance MSDERELA? Open a command shell window and type the following: SQLCMD -S .\MSDERELA What do you see? If you see a prompt like this: 1> then you are able to connect to the instance using SQLCMD which is a start. I notice that you have a CTP installed. You need to be VERY careful when you later come to uninstall this and go to SSMSE RTM build. There is a specific order in which to uninstall items to achieve a successful uninstall. Andrew Watt MVP <ar_pad@.discussions.microsoft.com> wrote in message news:434cb1f0-4b2c-43c5-97da-5aea1f39295f@.discussions.microsoft.com... hi friends, I'll be thankful if anyone solve this problem. When i developed my application i used sql 2000 as a server side DB.Now my client want to install MSDE instead of SQL 2000. so i uninstall SQL2000 and installed MSDE . AS we all know, MSDE doesn't have GUI. So i installed Microsoft SQL Server Management Studio Express - Community Technology Preview (CTP) (includeing xmlparser,windows installer,.net 2.0). now i could able to view tables and everything. but i couldn't make the connection. Getting error like "SQL server not found. CMPNAME\MSDERELA"I used same kind of connection string for SQL 2000. Worked well.here what happened? OS: Windows server 2003.i used VB.NET to develop the apps. kindly help me to solve this problem.|||

Hi,

Yes. It's a named instance. computername\MSDERelA.

can i use the same cmd? SQLCMD -S .\MSDERELA where can i see these kind of commands?

I followed this order. 1) windows installer

2)dotnetfx.exe

3)msxml6.msi

4) SSMSE

is it correct?

Thanks!

|||

That's the right order to install Management Studio Express.

The command line syntax for sqlcmd is very similar to the syntax for osql. You can get the command line syntax for sqlcmd by typing the following in a command window:

sqlcmd /?

"sqlcmd -S .\msderela -E" will connect to your local msderela instance using Windows authentication. You can type "quit" to exit sqlcmd.

Here's the online help topic for sqlcmd: http://msdn2.microsoft.com/en-us/library/ms165702(SQL.90).aspx

Hope this helps,
Steve

MSDE - Not associated with a trusted SQL Server connection

I have just installed MSDE on my PC running WinXP Pro. I set it up to use
mixed mode for security mode. However, when I try to log in to the database
using a user account I created I get the following error:
Login Failed for user 'username'. Reason: Not associated with a trusted SQL
server connection.
I am using DbaMgr 2k to view the database settings. I have provided all
admin level access to this user. However, I just cannot login using a
username. I have tried using the sa account to login and I get the same
error. I can only login using a Trusted NT Connection option. Any ideas what
I should try? When I searched it on the web, the only suggestion I can see
is to make sure the security mode is set to mixed mode, which seems to be
correct in this case.
Any help will be appreciated.
DeepaliHi
You don't say how you are trying to connect to the server? Try the following
from a command prompt
osql -S <Servername> -U <username> -P <Password>
John
"Deepali Garg" wrote:

> I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the databas
e
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted SQ
L
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas wh
at
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>
>|||SQL will not use the changes until it has been re-started... The error
seems to be saying it will only use trusted connections... perhaps you
simply need to re-start SQL...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
>I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the
> database
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted
> SQL
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas
> what
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>|||Wayne,
Thanks for your help. This is exactly what the problem was. As soon as I
restarted the SQL Server everything worked ok!
Deepali
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eW1ECQnGFHA.3628@.TK2MSFTNGP15.phx.gbl...
> SQL will not use the changes until it has been re-started... The error
> seems to be saying it will only use trusted connections... perhaps you
> simply need to re-start SQL...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
> news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
see[vbcol=seagreen]
be[vbcol=seagreen]
>

MSDE - Not associated with a trusted SQL Server connection

I have just installed MSDE on my PC running WinXP Pro. I set it up to use
mixed mode for security mode. However, when I try to log in to the database
using a user account I created I get the following error:
Login Failed for user 'username'. Reason: Not associated with a trusted SQL
server connection.
I am using DbaMgr 2k to view the database settings. I have provided all
admin level access to this user. However, I just cannot login using a
username. I have tried using the sa account to login and I get the same
error. I can only login using a Trusted NT Connection option. Any ideas what
I should try? When I searched it on the web, the only suggestion I can see
is to make sure the security mode is set to mixed mode, which seems to be
correct in this case.
Any help will be appreciated.
Deepali
Hi
You don't say how you are trying to connect to the server? Try the following
from a command prompt
osql -S <Servername> -U <username> -P <Password>
John
"Deepali Garg" wrote:

> I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the database
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted SQL
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas what
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>
>
|||SQL will not use the changes until it has been re-started... The error
seems to be saying it will only use trusted connections... perhaps you
simply need to re-start SQL...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
>I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the
> database
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted
> SQL
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas
> what
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>
|||Wayne,
Thanks for your help. This is exactly what the problem was. As soon as I
restarted the SQL Server everything worked ok!
Deepali
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eW1ECQnGFHA.3628@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> SQL will not use the changes until it has been re-started... The error
> seems to be saying it will only use trusted connections... perhaps you
> simply need to re-start SQL...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
> news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
see[vbcol=seagreen]
be
>

MSDE - Not associated with a trusted SQL Server connection

I have just installed MSDE on my PC running WinXP Pro. I set it up to use
mixed mode for security mode. However, when I try to log in to the database
using a user account I created I get the following error:
Login Failed for user 'username'. Reason: Not associated with a trusted SQL
server connection.
I am using DbaMgr 2k to view the database settings. I have provided all
admin level access to this user. However, I just cannot login using a
username. I have tried using the sa account to login and I get the same
error. I can only login using a Trusted NT Connection option. Any ideas what
I should try? When I searched it on the web, the only suggestion I can see
is to make sure the security mode is set to mixed mode, which seems to be
correct in this case.
Any help will be appreciated.
DeepaliHi
You don't say how you are trying to connect to the server? Try the following
from a command prompt
osql -S <Servername> -U <username> -P <Password>
John
"Deepali Garg" wrote:
> I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the database
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted SQL
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas what
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>
>|||SQL will not use the changes until it has been re-started... The error
seems to be saying it will only use trusted connections... perhaps you
simply need to re-start SQL...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
>I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the
> database
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted
> SQL
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas
> what
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>|||Wayne,
Thanks for your help. This is exactly what the problem was. As soon as I
restarted the SQL Server everything worked ok!
Deepali
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eW1ECQnGFHA.3628@.TK2MSFTNGP15.phx.gbl...
> SQL will not use the changes until it has been re-started... The error
> seems to be saying it will only use trusted connections... perhaps you
> simply need to re-start SQL...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
> news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
> >I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> > mixed mode for security mode. However, when I try to log in to the
> > database
> > using a user account I created I get the following error:
> >
> > Login Failed for user 'username'. Reason: Not associated with a trusted
> > SQL
> > server connection.
> >
> > I am using DbaMgr 2k to view the database settings. I have provided all
> > admin level access to this user. However, I just cannot login using a
> > username. I have tried using the sa account to login and I get the same
> > error. I can only login using a Trusted NT Connection option. Any ideas
> > what
> > I should try? When I searched it on the web, the only suggestion I can
see
> > is to make sure the security mode is set to mixed mode, which seems to
be
> > correct in this case.
> >
> > Any help will be appreciated.
> >
> > Deepali
> >
> >
>

MSDE

Having Problem connecting to Database with WebMatrix

When I try to ADD Database in WebMatrix through Sql Connection & enter USERNAME & PASSWORD it fails. Is there a way to create New USERNAME & PASSWORD? Perhaps through
the Command Line Prompt?

Any Help/Advice TIA

Tristen"setup /upgradesp" option may be for U.
Read carefullySQL Server MSDE notes.