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 SP3 Merge Module does not installing on windowx XP

Dear Sirs.
MSDE 2000 SP 3a Merge Module Does not installing on Windows XP Without XP
Service Pack.
It is work if SP1 is instaled on Windows XP. But how i can use that merge
modules if SP1 is not installed on Windows XP ?
Thank you in advance.
Install SP1 on Windows XP. You can generally do this if it's a legal copy.
"Irakli Lomidze" <Irakli_Lomidze@.access.sanet.ge> wrote in message
news:uzsiaVNuEHA.2196@.TK2MSFTNGP14.phx.gbl...
> Dear Sirs.
> MSDE 2000 SP 3a Merge Module Does not installing on Windows XP Without XP
> Service Pack.
> It is work if SP1 is instaled on Windows XP. But how i can use that merge
> modules if SP1 is not installed on Windows XP ?
> Thank you in advance.
>

msde 2000 sp3 install problem on win 2000

server. I am building an installshield package. During this process I must install to win 2000, xp pro etc, at home on my 2000 server I had hell of a time installing the msde. I have tried the msde 2000 sp3 patch as well. The installation rolls back after it is almost done. the log won't tell me anything meaningful. Is there any secret to msde on 2000 severs? I one time managed to install the server after succesfullu monkeying with the security profiles on the server, now it is uninstalled but despite the profile set correctlty I can't install? I need some help FAST!!!
The xp works like a charm.
I have attached the log...so if someone is an expert maybe can shed the ligh for me...Log file is not attached.|||msde setup has a bug - it needs upper case machine id for the network (I wonder if there is a workaround since changing my machine name is not that trivial - I am a cable broadband user.)|||Where did you find out about the upper case machine name - do you have a link ?|||Originally posted by rnealejr
Where did you find out about the upper case machine name - do you have a link ?
? if(document.domain.indexOf('.microsoft.com') > 0) document.domain = 'support.microsoft.com';

Home Search FAQs Downloads Newsgroups Customer Service

Microsoft Knowledge Base Article - 285100

Comments?
Provide us with feedback on this article

Support Centers
Small Business Server
SQL Server

Other Support Options
Contact Microsoft
Phone Numbers, Support Options and Pricing, Online Help, and more.

Customer Service
For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.

Newsgroups
Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.


Page Options
Send
Print



FIX: Installation Fails When Windows Computer Name Is Mixed or Lowercase
View products that this article applies to.
This article was previously published under Q285100
BUG #: 351711(SQL2000)
SYMPTOMS
Connection attempts over the shared memory network library fail on a server where GetComputerName returns a lower or mixed case server name.

When the shared memory connection attempt fails the SQL Server 2000 network library attempts to connect over an alternate protocol.

When you install any edition of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) on a computer whose name is all lowercase or mixed case, Setup may fail, and you receive one of the following messages:

For MSDE 2000:

Setup failed to configure the server. Refer to the server error logs and setup error logs for more information.
For SQL Server 2000:

Setup failed to configure the server. Refer to the server error logs and sqlstp.log for more information.
CAUSE
GetComputerName is used to obtain the local computer name. The client network library component (DBMSLPCn.dll) converts the name to all upper case. The server network library component (SSMSLPCn.dll) leaves the name as returned.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
File name Platform
-------

SSMSLPCn323 Intel

The following file is available for download from the Microsoft Download Center:

SSMSLPCn323.exe

Release Date: JAN-22-2001

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How To Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

The SSMSLPCn323.exe file contains the following files:

File name Size
EULA.txt 2 KB
Readme.txt 1 KB
SSmsLPCn.dll 29 KB
SSmsLPCn.pdb 73 KB
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.

WORKAROUND
To work around this problem, change the computer name to all uppercase characters.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
The failure is prohibitive to a SQL Server 2000 setup. A SQL Server 2000 setup prevents external connections by only allowing the shared network library connections.

If a shared memory connection can not be established, the setup fails when it attempts to configure the SQL Server server.

For SQL Server 2000:

The Sqlstp.log file contains an error message similar to:

2:44:57 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINNT\sqlstp.log" -dbdebug -I MSSQLSERVER -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 262404 -U sa -P
Starting Service ...
SQL_Latin1_General_CP1_CI_AS -m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=MyServer;UID=sa;PWD=;database=maste r [Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
In the same Sqlstp.log file you can verify the naming failure by locating the following at the top of the log file:
12:30:08 Name = MYSERVER, Type = 0x1
12:30:08 ComputerName: MyServer

For MSDE 2000:

Run the following command so the installation does not roll back upon failure:
setup.exe /DISABLEROLLBACK=1 /L*v C:\temp\msdesetup.log

You must run this code so that the Cnfgsvr.out file can be collected. Using the /L*v switch enables verbose logging for MSDE 2000 Setup.

After the MSDE 2000 installation fails, when you review the contents of the Cnfgsvr.out file, you see an error message similar to the following:

Starting Service ...

SQL_Latin1_General_CP1_CI_AS

-m -Q -T4022 -T3659

Connecting to Server ...

driver={sql server};server=MyServer;UID=sa;PWD=;database=maste r

[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.

[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
The naming failure can be located from the server parameter. The Msdesetup.log file has an entry similar to the following:
ComputerName =MyServer

The information in this article applies to:
Microsoft SQL Server 2000 (all editions)
Microsoft SQL Server 2000 Desktop Engine (MSDE)
Last Reviewed: 11/3/2003 (4.0)
Keywords: kbBug kbfix kbQFE KB285100 kbAudDeveloper






Contact Us

? 2003 Microsoft Corporation. All rights reserved. Terms of use Security & Privacy Accessibility
function thisLoad(){ setcookieval("SITE","GN"); gsfxUpLevel(); g_reSupportedHostnames = new RegExp(".msn.com$|.passport.com$|.xbox.com$|.microsoft.com $|.microsoft.cz$|.msbpn.com$|.microsoft.co.*", "i"); ForeignLink_Hookup(true);LogHit('http://c.microsoft.com/trans_pixel.asp?TYPE=SSPV&SOURCE=SUPPORT&URI=/GN/EN-US/kb_en-us_285100&GUID=1F4FC18C-F71E-47fb-8FC9-612F8EE59C61&R='); } function thisUnload(){ ; }|||The fix is included in the article - do you download the fix ?|||Originally posted by rnealejr
The fix is included in the article - do you download the fix ?
Yes.
The problem is that I do not know how to update the CAB file and I can't even find reference to SSmsLPCn.pdb - I found the dll but I have not replace it yet in the CAB.
I found it incomprehansible that there is this bug and MSFT can NOT provide a decent fix only this weird one that you need to manually update dll's and fix THEIR setup. I have yet to find a reference to fix an existing setup distributable.|||If you follow the instructions in the readme.txt, you should be fine.

MSDE 2000 SP3 fails to install

MSDE 2000 SP3 fails to install on a windows 2000 terminal server. The error
message I get is "MSDE 200 SP3 installation failed with exit code 1603" and
“A strong password is required for security reasons. Please use SAPWD switch
to supply the same. Refer to read me for more details. Setup will now exit.”
I have come across this once before and removed the server from the domain,
in this case that is not an option. I have denied the read right to the
default domain policy which is the only policy that is applying. Anybody have
any ideas on how I can install this.
hi bob,
bob wrote:
> MSDE 2000 SP3 fails to install on a windows 2000 terminal server. The
> error message I get is "MSDE 200 SP3 installation failed with exit
> code 1603" and "A strong password is required for security reasons.
> Please use SAPWD switch to supply the same. Refer to read me for more
> details. Setup will now exit." I have come across this once before
> and removed the server from the domain, in this case that is not an
> option. I have denied the read right to the default domain policy
> which is the only policy that is applying. Anybody have any ideas on
> how I can install this.
as indicated by the error description, you have to provide a strong password
for "sa" login as a parameter, in the form of
c:\...\>setup.exe ... SAPWD="your strong password" ...
all available parameters for the setup.exe bootstrap installer are provided
at
http://msdn.microsoft.com/library/de...stsql_84xl.asp
or, if you really are sure (please don't) you do not need a strong sa
password, you have to provide the
BLANKSAPWD=1
parameter
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea
I tried BLANKSAPWD=1 and I even tried setting a strong password, neither one
worked. Do you have any other suggestions?
"Andrea Montanari" wrote:

> hi bob,
> bob wrote:
> as indicated by the error description, you have to provide a strong password
> for "sa" login as a parameter, in the form of
> c:\...\>setup.exe ... SAPWD="your strong password" ...
> all available parameters for the setup.exe bootstrap installer are provided
> at
> http://msdn.microsoft.com/library/de...stsql_84xl.asp
> or, if you really are sure (please don't) you do not need a strong sa
> password, you have to provide the
> BLANKSAPWD=1
> parameter
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Bob,
bob wrote:
> Andrea
> I tried BLANKSAPWD=1 and I even tried setting a strong password,
> neither one worked. Do you have any other suggestions?
>
can you please post your paramenters?
what kind of error do you get?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

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 Rel A Installation Failure

try install previuos version of msde 2000 rel a, and update with sp3.
"chris fearnley" <anonymous@.discussions.microsoft.com> escreveu na mensagem
news:3D93D00C-1AAD-427F-905C-26533B3388F6@.microsoft.com...
> I have the same problem. I am trying to do test installtions of MSDE 2000
Release A on several systems, along with our own app which uses .NET. About
half the PCs halt the installation, usually when there is '7 seconds left'
and just hang. Same problem on XP SP1 and even old Win98 SE.
all right, see the 320873 article from microsoft's knowledge base to
manually remove a msde. since you don't have msde installed anymore, looking
for the key in registry and delete them.
after that, try to install msde 2000 (not msde 2000 rel a) and sp3.
"Joe Schillace" <anonymous@.discussions.microsoft.com> escreveu na mensagem
news:B835C284-FF56-4A3E-82F3-E467218FAF03@.microsoft.com...
> Adriano:
> The previous version of MSDE that I had installed was from MS Office 2000.
It appears that it installs SQL 7.
> I re-installed this version and it went in without a hitch. I then tried
installing SP3a.
> It got to about 3 or 4 seconds left and then rolled back. The setup log
indicates a failed installation.
> It seems that MSDE 2000 Rel A left some scraps in the windows registry. I
searched for "microsoft sql server" and found more than a hundred. I can't
tell from the log file which entry is causing the problem.
> I have deleted the microsoft sql server folder and ran regclean, hoping it
would remove the orphans. But, I am still having the problem.
|||Just found some more info to help solve previous posting.
There is an error line in the install log file:
......
Executing "G:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "Latin1_General_CI_AS""
Setup failed to configure the server. Refer to the server error logs and setup error logs for more information.
Action ended 10:43:17: InstallFinalize. Return value 3.
......
...and in the error log from the newly-crtated SQL folder: (created by cnfgsvr?)
.....
2004-05-28 10:41:11.83 spid3 Default collation successfully changed.
2004-05-28 10:41:11.93 spid3 Recovery complete.
2004-05-28 10:41:11.93 spid3 SQL global counter collection task is created.
2004-05-28 10:41:12.64 spid3 Warning: override, autoexec procedures skipped.
2004-05-28 10:42:58.51 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.
(that was the last line in the log)
Note the time delay between the last 2 entries.

MSDE 2000 Install Problem

Hi
I am trying to install MSDE 2000 sp3 on a Windows XP that has had a previous
installation in the past. The previous installation has been removed, but
when I try installing MSDE again from the command prompt, it starts to set
up the gives me an error saying installation failed.
I have deleted the Microsoft SQL Server directory from Program Files,
cleaned out all registry entries for the instance name and have run the
install using the following command:
Setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1
SAPWD=<password>
Obviously replacing <password> with an appropriate password.
Are there any other known issues that anyone knows that will get this
installation working? Any advice would be appreciated.
Regards
Jason
hi Jason,
please add the
/L*v 'c:\...\log.txt'
parameter, in order to get a 2mb log file for the installation, where you
can search for
"value 3"
as error indication
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE 2000 Install - setup.ini

I have installed MSDE 2000 on my Windows 2000 laptop using the SP3 setup.exe and associated setup.ini file.
So far I have included the following parameters in the setup.ini file -
SAPWD=<my own SA password>
SECURITYMODE=SQL
COLLATION=SQL_Latin1_General_CP1_CI_AS

My next test is to connect to a database on the laptop from my desktop (via my LAN) using SQL Server 2000 Enterprise Manager and/or Query Analyser.

The problem is that although I can 'see' my laptop (ping/My Network Places etc.), I can not see the MSDE installation hense my database on the laptop. The message I get is '[Microsoft]ODBC SQL server driver [DBNETLIB] SQL Server does not exist or access denied'

Have I missed a parameter i.e. do I need to set up a parameter to ensure I can connect to the installation from remote?

Being new to installing MSDE, are there any other parameters I have missed?

Ian

p.s. Anyone know of a simple to follow install instruction set for MSDE 2000 which shows what parameters can be set upSolved the problem myself.
With Service Pack 3, msde has added a new parameter to the install = DISABLENETWORKPROTOCOLS. This parameter is defaulted to 1 which blocks remote access to the database. By adding the parameter with a value of 0 to the setup.ini file I can now connect from remote.
Ian

Originally posted by Ian Grant
I have installed MSDE 2000 on my Windows 2000 laptop using the SP3 setup.exe and associated setup.ini file.
So far I have included the following parameters in the setup.ini file -
SAPWD=<my own SA password>
SECURITYMODE=SQL
COLLATION=SQL_Latin1_General_CP1_CI_AS

My next test is to connect to a database on the laptop from my desktop (via my LAN) using SQL Server 2000 Enterprise Manager and/or Query Analyser.

The problem is that although I can 'see' my laptop (ping/My Network Places etc.), I can not see the MSDE installation hense my database on the laptop. The message I get is '[Microsoft]ODBC SQL server driver [DBNETLIB] SQL Server does not exist or access denied'

Have I missed a parameter i.e. do I need to set up a parameter to ensure I can connect to the installation from remote?

Being new to installing MSDE, are there any other parameters I have missed?

Ian

p.s. Anyone know of a simple to follow install instruction set for MSDE 2000 which shows what parameters can be set up

Msde 2000

Hi folks!

Ive got here a Windows 2000 Professional PC and want to install the MSDE 2000 (incl. SP3) Desktop Server.

But when i execute the setup.exe the following Error Message will return:

http://www.dorst.de/sql.jpg

Here is the setup.ini

[Options]
TARGETDIR="C:\Programme\MSDE2000"
DATADIR="C:\Programme\MSDE2000\Daten"
SAPWD="*****"
SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0

Can anyone help?

THX !!!!!

Bye
CdRNoone knows why i cant install?|||Where did you get the the MDSE CD from? In seems that it may be corrupt.

I don't recall any internet calls during any installation I have performed. The fact that the website called s in Germany makes me wonder about the validity of the installation CD.

Be careful that it isn't corrupting your system.

Is there a reason that you are installing the German version?
("C:\Programme" as opposed to "C:\Program Files")|||The MSDE is included in a Program CD of Microsoft, but i tried to download it and install the MSDE... nothing change.

"C:\Programme" <- Thats the Standard-Programm-Dir :)

thx 4 help!

Bye

MSDE 1.0 and SQL Server

Apparently since I downloaded SQL Server SP3 and tried to install it on a computer without SQL Server in the first place, it's a bad thing.

I'm trying to get SQL Server Desktop Engine to install and I do the cmd.exe thing and it works, then 1 second before it finishes it rolls back.

All the files are still there, just missing the ones you need to run the SQL Server.

I used to have it on my 98, before I upgraded. Now I have the ASP.NET WebMatrix on my XP Home.

Is there a way to get SQL to install correctly?

JohnAre you sure you want to install MSDE 1.0?? That is a SQL Server 7-compatible data engine.

There seems to be a good walkthrough on installing MSDE 2000 in the ASP.NET Web Matrix Guided Tour:Install MSDE 2000.

Terri|||I tried that, perfectly and by all the things it said, and it still backed out at the last few seconds.

I have no idea. I've only herd that XP Home dosn't support IIS but this thing had XP (General) as in Home and Pro for the supported OS's. I really don't now whats wrong.

John

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 + JDBC SP3 - Run Together in WS

I have a java application running with JDK 1.3.1. I`d like connect this
application through the SQL DB ( MSDE + SQL Server 2000 Driver for JDBC
Service Pack 3, both are free ). Is it possible.
Txs in advance,
Jose R Castro / MCP W2K
| Thread-Topic: MSDE + JDBC SP3 - Run Together in WS
| thread-index: AcTXTYaW1R/kc6+DROSEIv2/byEYnw==
| X-WBNR-Posting-Host: 201.1.124.200
| From: "=?Utf-8?B?Sm9zZSBSIENhc3Rybw==?=" <Jose R
Castro@.discussions.microsoft.com>
| Subject: MSDE + JDBC SP3 - Run Together in WS
| Date: Tue, 30 Nov 2004 18:29:04 -0800
| Lines: 7
| Message-ID: <0EF992D0-735C-439E-B581-A6FA4464B99A@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.jdbcdriver:6519
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| I have a java application running with JDK 1.3.1. I`d like connect this
| application through the SQL DB ( MSDE + SQL Server 2000 Driver for JDBC
| Service Pack 3, both are free ). Is it possible.
| Txs in advance,
|
| Jose R Castro / MCP W2K
|
|
Yes, you can connect to MSDE from JDBC in the same way that you connect to
a full-blown instance of SQL Server..
Carb Simien, MCSE MCDBA MCAD
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/security.

MSDE /XP Problem -Please Help

Hi,
I have2 machines connected to each other. Both the systems
have MS XP operating systems with SP2 patch on them. I
have installed MSDE SP3 on both the systems.
I would like to run a query from one machine on a database
on the other using osql.I was unable to. It gives an error
saying "Access denied"
Are there any settings that i will have to change. I want
one to be like a server and another a client. Each has
its own database.
osql -Usa -Ppassword -S<servername> <enter>
Does not work.
-ZS
If you aren't getting a logon failure, check to make sure you have port 1433
(or the MSDE sqlserver exe) set up as an exception in the XP SP2 firewall
settings.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"ZS" <anonymous@.discussions.microsoft.com> wrote in message
news:07f001c4b7af$fc2835f0$a301280a@.phx.gbl...
> Hi,
> I have2 machines connected to each other. Both the systems
> have MS XP operating systems with SP2 patch on them. I
> have installed MSDE SP3 on both the systems.
> I would like to run a query from one machine on a database
> on the other using osql.I was unable to. It gives an error
> saying "Access denied"
> Are there any settings that i will have to change. I want
> one to be like a server and another a client. Each has
> its own database.
> osql -Usa -Ppassword -S<servername> <enter>
> Does not work.
> -ZS
>
>
|||Thanks Greg. Yes the problem was with the firewall.
So it is fixed now. Thanks.
=ZS
>--Original Message--
>If you aren't getting a logon failure, check to make sure
you have port 1433
>(or the MSDE sqlserver exe) set up as an exception in the
XP SP2 firewall
>settings.
>HTH,
>--
>Greg Low [MVP]
>MSDE Manager SQL Tools
>www.whitebearconsulting.com
>"ZS" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:07f001c4b7af$fc2835f0$a301280a@.phx.gbl...
systems[vbcol=seagreen]
database[vbcol=seagreen]
error[vbcol=seagreen]
want
>
>.
>

MSDE

We are running MSDE on Windows 2000 Server. The version number SQL2000,
8.00.760, 5.2 (Build 3790:SP1). So, I am running SP3. Is it necessary to
apply SP3a? If it is, is the "SP3a" file the same running on both SQL 2000
and MSDE? Thanks.It says here its not necessary unless you want the new "disable network
protocols" option.
http://www.microsoft.com/downloads/...&displaylang=en
Also note SP4 is available.
http://www.microsoft.com/downloads/...&displaylang=en
Regards,
Dave Patrick ...Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Diane Walker" wrote:
| We are running MSDE on Windows 2000 Server. The version number SQL2000,
| 8.00.760, 5.2 (Build 3790:SP1). So, I am running SP3. Is it necessary
to
| apply SP3a? If it is, is the "SP3a" file the same running on both SQL
2000
| and MSDE? Thanks.
|
||||Thank you very much, Dave.
"Dave Patrick" <DSPatrick@.nospam.gmail.com> wrote in message
news:OaYOqyQ9GHA.3736@.TK2MSFTNGP02.phx.gbl...
> It says here its not necessary unless you want the new "disable network
> protocols" option.
>
http://www.microsoft.com/downloads/... />
laylang=en
> Also note SP4 is available.
>
http://www.microsoft.com/downloads/... />
laylang=en
>
> --
> Regards,
> Dave Patrick ...Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
> "Diane Walker" wrote:
> | We are running MSDE on Windows 2000 Server. The version number SQL2000,
> | 8.00.760, 5.2 (Build 3790:SP1). So, I am running SP3. Is it
necessary
> to
> | apply SP3a? If it is, is the "SP3a" file the same running on both SQL
> 2000
> | and MSDE? Thanks.
> |
> |
>|||You're welcome.
Regards,
Dave Patrick ...Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Diane Walker" wrote:
| Thank you very much, Dave.

MSDE

We are running MSDE on Windows 2000 Server. The version number SQL2000,
8.00.760, 5.2 (Build 3790:SP1). So, I am running SP3. Is it necessary to
apply SP3a? If it is, is the "SP3a" file the same running on both SQL 2000
and MSDE? Thanks.
It says here its not necessary unless you want the new "disable network
protocols" option.
http://www.microsoft.com/downloads/d...displaylang=en
Also note SP4 is available.
http://www.microsoft.com/downloads/d...displaylang=en

Regards,
Dave Patrick ...Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Diane Walker" wrote:
| We are running MSDE on Windows 2000 Server. The version number SQL2000,
| 8.00.760, 5.2 (Build 3790:SP1). So, I am running SP3. Is it necessary
to
| apply SP3a? If it is, is the "SP3a" file the same running on both SQL
2000
| and MSDE? Thanks.
|
|
|||Thank you very much, Dave.
"Dave Patrick" <DSPatrick@.nospam.gmail.com> wrote in message
news:OaYOqyQ9GHA.3736@.TK2MSFTNGP02.phx.gbl...
> It says here its not necessary unless you want the new "disable network
> protocols" option.
>
http://www.microsoft.com/downloads/d...displaylang=en
> Also note SP4 is available.
>
http://www.microsoft.com/downloads/d...displaylang=en
>
> --
> Regards,
> Dave Patrick ...Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
> "Diane Walker" wrote:
> | We are running MSDE on Windows 2000 Server. The version number SQL2000,
> | 8.00.760, 5.2 (Build 3790:SP1). So, I am running SP3. Is it
necessary
> to
> | apply SP3a? If it is, is the "SP3a" file the same running on both SQL
> 2000
> | and MSDE? Thanks.
> |
> |
>
|||You're welcome.
Regards,
Dave Patrick ...Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Diane Walker" wrote:
| Thank you very much, Dave.