MSDE and Access Project Issue

I installed MSDE SP3a on my XP Pro laptop using the following options:
SAPWD=abc456
instancename=MSDE01
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
DATADIR="C:\MSDE"
TARGETDIR="C:\MSDE"
I went to services and started MSSQL$MSDE01 and SQLAgent$MSDE01.
I opened up MSACCESS 2003 and created a new project with new data. The SQL Server Database Wizard popped up and I entered (local)MSDE01 for the SQL server and clicked the Use Trusted Connection.
After several seconds, I receive an error message:
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or access denied.
I can connect to this instance of MSDE using ASP.NET and the Server Explorer. So I'm pretty sure that I have a good install of MSDE.
Does anyone have a clue as to what I am doing wrong when I try to connect via Access?
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Hi,
Try (local)\MSDE01 instead.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:uv46MJeIEHA.3968@.TK2MSFTNGP12.phx.gbl...
> I installed MSDE SP3a on my XP Pro laptop using the following options:
> SAPWD=abc456
> instancename=MSDE01
> DISABLENETWORKPROTOCOLS=0
> SECURITYMODE=SQL
> DATADIR="C:\MSDE"
> TARGETDIR="C:\MSDE"
> I went to services and started MSSQL$MSDE01 and SQLAgent$MSDE01.
> I opened up MSACCESS 2003 and created a new project with new data. The
SQL Server Database Wizard popped up and I entered (local)MSDE01 for the SQL
server and clicked the Use Trusted Connection.
> After several seconds, I receive an error message:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen(Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or
access denied.
> I can connect to this instance of MSDE using ASP.NET and the Server
Explorer. So I'm pretty sure that I have a good install of MSDE.
> Does anyone have a clue as to what I am doing wrong when I try to connect
via Access?
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
|||or .\MSDE01
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:uv46MJeIEHA.3968@.TK2MSFTNGP12.phx.gbl...
> I installed MSDE SP3a on my XP Pro laptop using the following options:
> SAPWD=abc456
> instancename=MSDE01
> DISABLENETWORKPROTOCOLS=0
> SECURITYMODE=SQL
> DATADIR="C:\MSDE"
> TARGETDIR="C:\MSDE"
> I went to services and started MSSQL$MSDE01 and SQLAgent$MSDE01.
> I opened up MSACCESS 2003 and created a new project with new data. The
SQL Server Database Wizard popped up and I entered (local)MSDE01 for the SQL
server and clicked the Use Trusted Connection.
> After several seconds, I receive an error message:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen(Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or
access denied.
> I can connect to this instance of MSDE using ASP.NET and the Server
Explorer. So I'm pretty sure that I have a good install of MSDE.
> Does anyone have a clue as to what I am doing wrong when I try to connect
via Access?
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.

MSDE access over network slow for XP workstations, not Win2K

I've installed MSDE SP3a on a Windows 2000 Server, and the VB6 client
application on multiple workstations.
These workstations are either Win2000 Pro or WinXP Pro (both SP1 and SP2).
All workstations can access and ping the server under 1MS.
When the client application opens and reads data from the database server,
it takes a short time for this to be performed on the Win2000 Pro machines,
but all the XP machines take an abnormally long time to connect and to
retrieve the data.
The XP's do connect, but the retrieval is very slow, sometimes it timesout
during a retrieval.
This occurs even when nobody is connected to the database, so I've ruled out
the governer.
I'm using ADO to connect and all PC's have MDAC 2.7 or greater.
The install process only installed MDAC 2.7 if the current version is before
that.
Anybody have an idea what might be the problem?
All responses are welcome.
TIA
Jim K
Hi Jim,
Name resolution problems perhaps? Try connecting to the IP address instead
of the server name to find out.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim K" <krusej@.megsinet.net> wrote in message
news:enMo6BQ7EHA.1596@.tk2msftngp13.phx.gbl...
> I've installed MSDE SP3a on a Windows 2000 Server, and the VB6 client
> application on multiple workstations.
> These workstations are either Win2000 Pro or WinXP Pro (both SP1 and SP2).
> All workstations can access and ping the server under 1MS.
> When the client application opens and reads data from the database server,
> it takes a short time for this to be performed on the Win2000 Pro
> machines,
> but all the XP machines take an abnormally long time to connect and to
> retrieve the data.
> The XP's do connect, but the retrieval is very slow, sometimes it timesout
> during a retrieval.
> This occurs even when nobody is connected to the database, so I've ruled
> out
> the governer.
> I'm using ADO to connect and all PC's have MDAC 2.7 or greater.
> The install process only installed MDAC 2.7 if the current version is
> before
> that.
> Anybody have an idea what might be the problem?
> All responses are welcome.
> TIA
> Jim K
>
|||Thanks, I didn't think of that.
I have connected using the IP in other apps, but that was to the default
instance.
Since I have a named instance in this case, how would I format the IP and
instance?
Ex: default instance installed on server SERVER1, I can substitute the IP
for SERVER1
for named instance SERVER1/DB1, how would I format the IP? IP#/DB1 ?
Thanks!
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:u0zukkl7EHA.3124@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Hi Jim,
> Name resolution problems perhaps? Try connecting to the IP address instead
> of the server name to find out.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Jim K" <krusej@.megsinet.net> wrote in message
> news:enMo6BQ7EHA.1596@.tk2msftngp13.phx.gbl...
SP2).[vbcol=seagreen]
server,[vbcol=seagreen]
timesout
>
|||Hi Jim,
I'd suggest setting a fixed port for the named instance, then just connect
to that port. Even set up an alias on the client boxes that knows about the
port. It would completely avoid the sql browser function that essentially
just maps your instance name to a port anyway. To do that:
1. Open svrnetcn.exe and for the named instance, uncheck the "dynamic port"
box and select your own port (ie 38474 or something).
2. Restart the instance.
3. On the client, run cliconfg.exe and set up an alias pointing to that port
on the server.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim K" <krusej@.megsinet.net> wrote in message
news:u6vH8Mo7EHA.2196@.TK2MSFTNGP11.phx.gbl...
> Thanks, I didn't think of that.
> I have connected using the IP in other apps, but that was to the default
> instance.
> Since I have a named instance in this case, how would I format the IP and
> instance?
> Ex: default instance installed on server SERVER1, I can substitute the
> IP
> for SERVER1
> for named instance SERVER1/DB1, how would I format the IP? IP#/DB1 ?
> Thanks!
> "Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
> news:u0zukkl7EHA.3124@.TK2MSFTNGP11.phx.gbl...
> SP2).
> server,
> timesout
>
sql

MSDE 2000A Upgrade to SQL Express SP1 with Merge Replication

Hello,

I have the following scenario. An application using SQL Server 2000 SP3 on the server side and clients using MSDE 2000A (SP3a) on the client machine. Since the client is offline quite often merge replication is used to keep the clients in sync.

Now we try to upgrade to SQL Server 2005 SP1. The publisher and distributor upgrade (on the same box) worked fine and all clients could still synchronize. Fine :-)

Now we try to upgrade the clients to SQL Express SP1. Now the problems start :-(

1) After the upgrade the entry within the Synchronization Manager is gone (we can overcome this by using sp_MSregistersubscription or by manually disable and enable Synchronization manager on the subscription properties)

2) Initial Synchronization (takes a long time but) works fine, if I apply changes to the subscriber or force a reinitialize all following synchronization will fail. With the following messages:

Error messages:
The merge process could not clean up the subscription to 'tstvmw23':'TestBase:'TestBase'. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200965)
Get help: http://help/MSSQL_REPL-2147200965
New request is not allowed to start because it should come with valid transaction descriptor. (Source: MSSQLServer, Error number: 3989)
Get help: http://help/3989

Remark the test system I use is a nearly empty db (only with full schema and a few lookup tables) with 15MB. The same error occures if I create a new database an subscribe to the same publication.

Please help otherwise I'm forced to step back to MSDE.

Thanks in advance,

Thomas Hotz

Hi,

just to make sure you do not want SQL Server Express to the a merge replicant...

http://msdn2.microsoft.com/en-us/library/ms165616.aspx

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||What this table on the BOL means is that SQL Server Express cannot act as a Distributor/Publisher on a merge replication and the main cause is that it does not have an Agent.
http://technet.microsoft.com/en-us/library/ms143470.aspx
See the topic SQL Server does not include an agent on that reference.

SQL Server Express can act as a subscriber on Merge Replication though. If you have a type of subscription Pull, as the Agent runs on the subscribers you have to use RMO on your code to instantiate an agent or use Windows Synchronization Manager (Start Menu-> Accessories -> Synchronize)

We have SQLE running as subscribers on a pull merge replication topology...sql

MSDE 2000A Upgrade to SQL Express SP1 with Merge Replication

Hello,

I have the following scenario. An application using SQL Server 2000 SP3 on the server side and clients using MSDE 2000A (SP3a) on the client machine. Since the client is offline quite often merge replication is used to keep the clients in sync.

Now we try to upgrade to SQL Server 2005 SP1. The publisher and distributor upgrade (on the same box) worked fine and all clients could still synchronize. Fine :-)

Now we try to upgrade the clients to SQL Express SP1. Now the problems start :-(

1) After the upgrade the entry within the Synchronization Manager is gone (we can overcome this by using sp_MSregistersubscription or by manually disable and enable Synchronization manager on the subscription properties)

2) Initial Synchronization (takes a long time but) works fine, if I apply changes to the subscriber or force a reinitialize all following synchronization will fail. With the following messages:

Error messages:
The merge process could not clean up the subscription to 'tstvmw23':'TestBase:'TestBase'. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200965)
Get help: http://help/MSSQL_REPL-2147200965
New request is not allowed to start because it should come with valid transaction descriptor. (Source: MSSQLServer, Error number: 3989)
Get help: http://help/3989

Remark the test system I use is a nearly empty db (only with full schema and a few lookup tables) with 15MB. The same error occures if I create a new database an subscribe to the same publication.

Please help otherwise I'm forced to step back to MSDE.

Thanks in advance,

Thomas Hotz

Hi,

just to make sure you do not want SQL Server Express to the a merge replicant...

http://msdn2.microsoft.com/en-us/library/ms165616.aspx

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||What this table on the BOL means is that SQL Server Express cannot act as a Distributor/Publisher on a merge replication and the main cause is that it does not have an Agent.
http://technet.microsoft.com/en-us/library/ms143470.aspx
See the topic SQL Server does not include an agent on that reference.

SQL Server Express can act as a subscriber on Merge Replication though. If you have a type of subscription Pull, as the Agent runs on the subscribers you have to use RMO on your code to instantiate an agent or use Windows Synchronization Manager (Start Menu-> Accessories -> Synchronize)

We have SQLE running as subscribers on a pull merge replication topology...

MSDE 2000 SP3a Workgroup Access

Greetings everyone.

I work in a retail environment and have an MSDE2000 SP3a server installed in 350+ stores. I need to access the server from another computer in the workgroup (not domain) and I can't. I'm getting "SQL Server does not exist or access denied." The server was installed using the default option of Windows Authentication and I have changed it to Mixed mode authentication on one of my in-house lab systems with no luck. Also, when I try to create and OLEDB connection for the database and drop down the list of servers, there is nothing there (not even the local server.) Sorry but I do not have the error message that I get when that happens but I think when I solve the first problem the second will go away too.

Thanks for your inputHi,

Are you saying that when you changed a server to mixed mode you were still unable to connect to it? Even from the local machine?

In my experience with MSDE, when running in mixed mode you should be able to connect remotely with EM or QA with the UID & PWD.

Have you confirmed that you are able to connect over 1433/1434 on the network? I guess this is the equivalent of "have you checked your cables" but it's worth checking to make sure.

Dan|||Hi Dan -- thanks for the reply.

I have always been able to connect to the server, both in Windows Authentication mode and Mixed mode from the local machine on which the server resides. The problem is that I cannot connect in either mode from a different machine in the workgroup. I tried telnet to the local machine using port 1433 and got a connect failed even on the same machine as the server. I did not know about port 1434. I'll try that one when I get back to the office tomorrow.

Thanks Again|||Use the server network utility.|||Not to be dense but what's the "Server Network Utility?"

I know about osql and can connect to the server while on the local machine but not from another machine.|||It's one of the utilities installed with SQL. You'll need to run it from the machine you want to connect from. You'll need to set up the connection. You create an alias where you specify the connection properties for the server.

Dan|||Nevermind -- I found it. I dialed into my office computer and ran the server network utility and all protocols were disabled. I won't be able to check the results until Friday but I'm optimistic that this will resolve my problems. Thanks a lot.|||all protocols were disabled That will do it.|||Once I enabled named pipes and tcp/ip on the server, the workgroup connection works fabulously. Thanks for your help.

One more question. Is there a registry setting for this that I can download a .reg file to the stores to set this or do I have to manually configure this setting in all my stores? Thanks again.

MSDE 2000 SP3a Won't install on 2003 server

I hope someone has seen this... I have a 2003 server that refuses to install MSDE 2000 SP3a. The install goes to 99% complete, then rolls back and automatically uninstalls. I have seen this in the past when file and printer sharing is not installed or
insufficient permissions, but this time it has me stumped. Event viewer is useless, it just reports that the install failed and doesn't give any reason. No error logs get created, no errors come up, the install just won't take. I have sucessfully insta
lled MSDE 2000 on other 2003 servers and have never had this much trouble. I have a verbose install log available from the install if anyone wants to look at it. Any ideas?
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
hi,
<dnoble@.-NOSPAM-raymorgan.com> ha scritto nel messaggio
news:%23fZGykYpEHA.648@.tk2msftngp13.phx.gbl
> I hope someone has seen this... I have a 2003 server that refuses to
> install MSDE 2000 SP3a. The install goes to 99% complete, then rolls
> back and automatically uninstalls. I have seen this in the past when
> file and printer sharing is not installed or insufficient
> permissions, but this time it has me stumped. Event viewer is
> useless, it just reports that the install failed and doesn't give any
> reason. No error logs get created, no errors come up, the install
> just won't take. I have sucessfully installed MSDE 2000 on other
> 2003 servers and have never had this much trouble. I have a verbose
> install log available from the install if anyone wants to look at it.
> Any ideas?
search for
RETURN VALUE 3
in your install log... it usually reports where the problem is
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks for the reply... I did locate a spot with Return Value 3. From the
log file:
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (FOX,LocalSystem,87).
Action ended 10:04:07: InstallFinalize. Return value 3.
Any thoughts on this?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2rtpgpF1f5farU1@.uni-berlin.de...
> hi,
> <dnoble@.-NOSPAM-raymorgan.com> ha scritto nel messaggio
> news:%23fZGykYpEHA.648@.tk2msftngp13.phx.gbl
> search for
> RETURN VALUE 3
> in your install log... it usually reports where the problem is
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||"News" <david-noble@.sbcglobal.net> ha scritto nel messaggio
news:TDk6d.3964$nj.741@.newssvr13.news.prodigy.com
> Thanks for the reply... I did locate a spot with Return Value 3.
> From the log file:
> Starting custom action InstallSQLAgentSecurity
> InstallSQLAgentSecurity failed (FOX,LocalSystem,87).
> Action ended 10:04:07: InstallFinalize. Return value 3.
> Any thoughts on this?
please have a look at http://tinyurl.com/69vo6 if can help solving your
problem
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||If you setup is failing, specify a command line parameter DISABLEROLLBACK =
1, this would stop MSDE Installer from rolling back in case of failure.
Also specify /L*v <log file patch with name>. This would enable setup to
write logs into the specified file. Try to search "return value 3" and
check where did it fail.
Once we know where it is failing we can help better. Also add the logfile
when you reply .
|||Thanks for all the replys, but so far all are off base a bit... The server
service is already running and file sharing is installed. A log file was
created and return value 3 came up with the following:
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (FOX,LocalSystem,87).
Action ended 10:04:07: InstallFinalize. Return value 3.
All responses to this so far have referred me to articles that talk about
making sure the server service is running, which is already the case.
<dnoble@.-NOSPAM-raymorgan.com> wrote in message
news:%23fZGykYpEHA.648@.tk2msftngp13.phx.gbl...
> I hope someone has seen this... I have a 2003 server that refuses to
install MSDE 2000 SP3a. The install goes to 99% complete, then rolls back
and automatically uninstalls. I have seen this in the past when file and
printer sharing is not installed or insufficient permissions, but this time
it has me stumped. Event viewer is useless, it just reports that the
install failed and doesn't give any reason. No error logs get created, no
errors come up, the install just won't take. I have sucessfully installed
MSDE 2000 on other 2003 servers and have never had this much trouble. I
have a verbose install log available from the install if anyone wants to
look at it. Any ideas?
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.

MSDE 2000 sp3a microsoft JDBC & W98

hi
I'm esperiencing a problem within a notebook where I have to run a web
application (I use a TomCat Catalina server). This notebook isn't connect in
a network and don't have a network card in it.
I've set TCP protocol within MSDE via SVRNETCN but I can't run my
appilcation I get an errore like Can't create a pooling connection
The same application with same Hardware + network card run fine.
please help
Gian Claudio
Hello Gian Claudio,
Are you sure the MSDE instance is listening on TCP/IP? You can check that
in your error log. You should see something like:
2005-05-02 14:35:38.48 server SQL server listening on 65.53.8.223: 1433.
2005-05-02 14:35:38.49 server SQL server listening on 127.0.0.1: 1433.
2005-05-02 14:35:38.56 server SQL server listening on TCP, Named Pipes.
2005-05-02 14:35:38.64 server SQL Server is ready for client connections
That tells you which IPs and port the server is listening on.
On a default installation of MSDE you would see something like:
2005-05-03 11:33:20.95 server SQL server listening on Shared Memory.
2005-05-03 11:33:20.95 server SQL Server is ready for client connections
which means it only listens on Shared Memory. The JDBC driver can only
connect through TCP/IP.
Additionally, can you test that you can connect to the SQL Server locally
with Query Analyzer over TCP/IP? You can specify tcp:servername in the
connect dialog to force connecting with TCP/IP. Otherwise you could be
connecting with named pipes or shared memory.
If all that works, can you also try connecting with a simple JDBC
application outside of TomCat and let me know what the exact exception and
full stack is?
Thanks,
Kamil
Kamil Sykora
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/securXity.
| From: "Gian Claudio Bernardi" <poc3796@.iperbole.bologna.it>
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| Subject: MSDE 2000 sp3a microsoft JDBC & W98
| Date: Thu, 14 Apr 2005 18:27:42 GMT
|
| hi
| I'm esperiencing a problem within a notebook where I have to run a web
| application (I use a TomCat Catalina server). This notebook isn't connect
in
| a network and don't have a network card in it.
|
| I've set TCP protocol within MSDE via SVRNETCN but I can't run my
| appilcation I get an errore like Can't create a pooling connection
|
| The same application with same Hardware + network card run fine.
|
| please help
|
| Gian Claudio
|
|
|
sql

MSDE 2000 SP3a install failure

I am getting an error when installing SP3a of MSDE. I get the error message "The instance name specified is invalid." This is the first SQL database installed, so there is no instance name. I have tried "default" and "MSSQLSERVER" as instance names without success.

your help is appreciated.the instance name is "MSDE"

Why is this not in the setup documentation?

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 do not listen

Hi all,
I install MSDE with SP3a on my server. The service starts well and with the
local host I'm able to access the MSDE server, but if I want to access it
from another workstation the connection always failed. I troubleshoot the
problem and I found that MSDE 2000 doesn't listen on the port 1433. Why?
There is a way to enable MSDE listening on TCP 1433 port and accept
connection form other client?
Regards
YanickIn the default configuration of MSDE TCP/IP as a server network library is
disabled. There is a utility, svrnetcn.exe, that can be used to enable it.
The utility is installed with MSDE so it shoulb be on the computer. Search
for this file and open it. You should tehn be able to enable TCP/IP.
Rand
This posting is provided "as is" with no warranties and confers no rights.sql

MSDE 2000 and SQL 2005 Express on one machine

Is it possible to have these two services on one machine? I notice that my
server requires MSDE 2000 SP3a and don't know it there will be a conflict if
I will install it (or is it possible to have these on the same machine) or I
will just install the 2005 version since it was the replacement of MSDE.
Hoping for your response.
Me
I don't believe you can install both at the same time, at least using
the default installs. 2005 Express attempts to upgrade MSDE
|||I'm running MSDE as the default instance and a SQLEXPRESS
instance on the same machine.
Karl Tarbet
MCSD .net
sql

MSDE 2000 and SQL 2005 Express on one machine

Is it possible to have these two services on one machine? I notice that my
server requires MSDE 2000 SP3a and don't know it there will be a conflict if
I will install it (or is it possible to have these on the same machine) or I
will just install the 2005 version since it was the replacement of MSDE.
Hoping for your response.
MeI don't believe you can install both at the same time, at least using
the default installs. 2005 Express attempts to upgrade MSDE|||I'm running MSDE as the default instance and a SQLEXPRESS
instance on the same machine.
--
Karl Tarbet
MCSD .net

MSDE 2000 and SQL 2005 Express on one machine

Is it possible to have these two services on one machine? I notice that my
server requires MSDE 2000 SP3a and don't know it there will be a conflict if
I will install it (or is it possible to have these on the same machine) or I
will just install the 2005 version since it was the replacement of MSDE.
Hoping for your response.
MeI don't believe you can install both at the same time, at least using
the default installs. 2005 Express attempts to upgrade MSDE|||I'm running MSDE as the default instance and a SQLEXPRESS
instance on the same machine.
Karl Tarbet
MCSD .net

MSDE 1 => msde 2 => MSDE 2 SP3a

I'm able to successfully upgrade my MSDE 1 installation from Office 2k to
MSDE 2, using any of the versions 1 thru 3a. However, I can't figure out
the command-line parameters to upgrade MSDE 2 to a newer version of MSDE 2,
at least not retaining my Office Server Extensions database. Considering
that SP 4 for MSDE 2 will probably be out soon, what's the proper method to
upgrade MSDE 2 when it was used to upgrade MSDE 1?
Well, I figured out the easy way to do things. First, you install MSDE 2.
Then you install office server extensions using the /nd switch to avoid
installing an older version of MSDE. Had a lot of registry cleaning to do,
had to unregister ows.dll, and a few other problems to fix before I could
get a successful install of OSE. Works fine, though. I was even able to
apply the OSE SP3 patch.
"Ellen Langton" <elangton@.wctc.net> wrote in message
news:emnXe$XCFHA.3688@.TK2MSFTNGP14.phx.gbl...
> I'm able to successfully upgrade my MSDE 1 installation from Office 2k to
> MSDE 2, using any of the versions 1 thru 3a. However, I can't figure out
> the command-line parameters to upgrade MSDE 2 to a newer version of MSDE
2,
> at least not retaining my Office Server Extensions database. Considering
> that SP 4 for MSDE 2 will probably be out soon, what's the proper method
to
> upgrade MSDE 2 when it was used to upgrade MSDE 1?
>
|||Well, I figured out the easy way to do things. First, you install MSDE 2.
Then you install office server extensions using the /nd switch to avoid
installing an older version of MSDE. Had a lot of registry cleaning to do,
had to unregister ows.dll, and a few other problems to fix before I could
get a successful install of OSE. Works fine, though. I was even able to
apply the OSE SP3 patch.
"Ellen Langton" <elangton@.wctc.net> wrote in message
news:emnXe$XCFHA.3688@.TK2MSFTNGP14.phx.gbl...
> I'm able to successfully upgrade my MSDE 1 installation from Office 2k to
> MSDE 2, using any of the versions 1 thru 3a. However, I can't figure out
> the command-line parameters to upgrade MSDE 2 to a newer version of MSDE
2,
> at least not retaining my Office Server Extensions database. Considering
> that SP 4 for MSDE 2 will probably be out soon, what's the proper method
to
> upgrade MSDE 2 when it was used to upgrade MSDE 1?
>

MSDE & SQL Server 2000

I have MSDE 2000 SP3a (default instance) installed and working on my XP Pro
machine, but I'd like to follow some development labs that use the SQL Server
2000 databases. Can I also install SQL Server 2000 3a and if so, what special
'things' must I do to install it?
Dale Cowan
hi Dale,
"Dale" <Dale@.discussions.microsoft.com> ha scritto nel messaggio
news:D5AC5D41-BAA8-4502-B847-06DD990929CF@.microsoft.com...
> I have MSDE 2000 SP3a (default instance) installed and working on my XP
Pro
> machine, but I'd like to follow some development labs that use the SQL
Server
> 2000 databases. Can I also install SQL Server 2000 3a and if so, what
special
> 'things' must I do to install it?
you can only install SQL Server 2000 Developer edition, Personal Edition and
MSDE, on Windows clients platforms... the Standard and Enterprise edition
are only for server platforms...
as long as you install a supported version, you only have to specify a named
instance installation, as your pc already hosts a default instance.
you can have different service pack levels (never tried different localized
versions, but may be =;-D), but the shared binaries in \Program
Files\Microsoft SQL Server\80 folders will be updated at the highes
installed service pack level.
at the moment there's no SQL Server service pack 3 installation, you have to
install the RTM and apply the desired service pack
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||RTM?
"Andrea Montanari" wrote:

> hi Dale,
> "Dale" <Dale@.discussions.microsoft.com> ha scritto nel messaggio
> news:D5AC5D41-BAA8-4502-B847-06DD990929CF@.microsoft.com...
> Pro
> Server
> special
> you can only install SQL Server 2000 Developer edition, Personal Edition and
> MSDE, on Windows clients platforms... the Standard and Enterprise edition
> are only for server platforms...
> as long as you install a supported version, you only have to specify a named
> instance installation, as your pc already hosts a default instance.
> you can have different service pack levels (never tried different localized
> versions, but may be =;-D), but the shared binaries in \Program
> Files\Microsoft SQL Server\80 folders will be updated at the highes
> installed service pack level.
> at the moment there's no SQL Server service pack 3 installation, you have to
> install the RTM and apply the desired service pack
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Dale,
"Dale" <Dale@.discussions.microsoft.com> ha scritto nel messaggio
news:610C1A77-A467-4BD9-92E5-BE5B5961AEC2@.microsoft.com...
> RTM?
Release To Manufacturer =;-D
the 1st at al retail version
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks for your help. Everything installed just fine - even MS03-031 security
update afterward. MBSA reports few problems.
"Andrea Montanari" wrote:

> hi Dale,
> "Dale" <Dale@.discussions.microsoft.com> ha scritto nel messaggio
> news:610C1A77-A467-4BD9-92E5-BE5B5961AEC2@.microsoft.com...
> Release To Manufacturer =;-D
> the 1st at al retail version
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

MSDB database

I have under SQL Server 2000 Standard Version with SP3a on Windows 2000 SP4
a Database Maintenance plan to backup transaction logs of all databases
hourly.
This job has been frequently failing, and the reason is that on the MSDB
database, the Recovery option has for some mysterious reason frequently been
reset from FULL to SIMPLE, and in order to get transaction logs backing up,
it needs to be set to FULL.
anyone has any ideas why/what process, etc. would reset the recovery option
from FULL to SIMPLE?> I have under SQL Server 2000 Standard Version with SP3a on Windows 2000
SP4
> a Database Maintenance plan to backup transaction logs of all databases
> hourly.
Backing up the transaction logs from all databases seems like overkill.
What is the point, e.g. for tempdb?

> anyone has any ideas why/what process, etc. would reset the recovery
option
> from FULL to SIMPLE?
This is the way SQL Server works.
http://www.support.microsoft.com/?id=257856
If you really want to back up msdb every hour, then you can make a task in
your job to temporarily set the recovery model to FULL. However this won't
accomplish much as the transaction logs won't be complete (and maybe not
even usable, depending on how you plan to use them).
If you want the behavior to be different, you can let Microsoft know how you
feel: sqlwish@.microsoft.com
Aaron Bertrand
SQL Server MVP|||Aaron Bertrand - MVP wrote:

> option
> This is the way SQL Server works.
> http://www.support.microsoft.com/?id=257856
>
that link is interesting. sort of contradicts the line from BOL "All recove
ry
models are supported for model, msdb and distribution." since full recovery
on
msdb only works until sqlagent is restarted.
i always prefer to have a dbmp for user databases and one for system databas
es.
in the system one, i don't back up transaction logs.
i think it's sort of goofy that the transaction log backup from a dbmp will
try
to backup the logs for db's in simple recovery and then generate errors. i'
ve
written a script that skips simple recovery db's for the log backups, why ca
n't
microsoft implement it in the dbmp jobs?